Bank Accounts
This function is used to characterize those bank accounts with which payment operations must be saved.
The detailed characteristics are attached to the administrative domain as well as the financial and accounting domains.
This section is available for Positive Pay.
To print checks, the CHQMG - Check management activity code must be active and the following parameters must be set to Yes:
USACHK - US/CAN Check printing (LOC chapter, USA group)
CHQCT - Check controls (TRS chapter, BNK group)
Check printing controls give you the option for Magnetic Ink Character Recognition (MICR) printing so that routing and account numbers can be read and scanned by the check clearing system.
Prerequisites
Refer to documentation Implementation
Screen management
Header
Code (field BAN) |
This code identifies a bank account. You can enter the code directly or select from the bank account table. |
Description (field DES) |
This field is used to link a description to its record. This description can be printed on the records, displayed when the record code is entered in a screen, or used on selection. By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language. The connection language must be defined as a default language for thefolder. |
Tab General
Code and title
The identification basis key of the bank account is its code, entered using 1 to 5 alphanumerical characters.
The title, which should be a short description, is used by default in reports, search windows, and entry masks. It is replaced by the short title whenever the display or printing constraints require it.
Identifiers with an "external purpose"
Both the BIC and IBAN codes are used to identify the bank in a unique manner on the basis of a preset codification applying to the banks as a whole.
The other data on this tab are mainly used to constitute ASCII files making banking electronic transmission possible: the Bank ID Number and the associated paying bank, the transfer issuing number.
As far as the cash interface code is concerned, when an external application provides for cash management, it is used to attach the code under which it is known in this application to the bank.
Address
The entry of the bank geographical address is optional.
Identity
Address (field ADDLIG) |
Bank address. |
Country (field CRY) |
This code is used to identify amongst other things, the Country of a BP.
|
field CRYNAM |
Postal code (field POSCOD) |
The postal code, which entry format is defined in the Country table, is used to define the town/city, state/region and the geographical subdivision, if defined for the country. Particular cases: - for ANDORRA, indicate 99130, When the postal code is defined as mandatory for the country, it must be entered if the Postal Code or City/town fields are entered, or if information is modified in the BP address window. However, this control is not applied in document creation. |
City (field CTY) |
The city automatically suggested is the one associated with the postal code previously indicated. It is also possible to manually enter the name of a town/city: Notes.
|
Map (field ITINERAIRE) |
Click this icon to open a mapping site and locate the entered address. |
State (field SAT) |
Code making it possible to specify the county where the bank is located. |
Telephone (field TEL) |
Telephone number. The format depends on the country. |
Fax (field FAX) |
Fax number The format depends on the country. |
Internet (field WEB) |
Full email address. |
Paying bank
Short description (field DESSHO) |
Title used in some screens or reports when there is not enough space to view the long title. By default the short title, the long title or the column header of a data are recorded (on creation/update) in the connection language of the user.
A user who logs on with this language will view the short description, long description or column header in their connection language if a translation exists. Otherwise, these descriptions will be available in the folder language. The connection language must be defined as a default language for thefolder. |
Site tax ID no. (field CRN) |
Bank acct. number (field BIDNUM) |
Default bank account number. |
BIC code (field BICCOD) |
International identification code for banking institutions defined by the ISO standard. |
IBAN code (field IBACOD) |
For countries for which the IBAN management box is checked, the IBAN is automatically calculated after the user has entered the Bank ID field. |
QR-IBAN (field QRCIBACOD) |
Enter the QR-IBAN number for the sender. This is used when generating sales invoices as QR-bills and this number is used as the sender's account number in the QR payment slip. |
ABA number (field ABANUM) |
Enter the 9-digit routing or transit number for the bank. This field is required when generating bank files with an ACH format, whether fixed or XML file. Note: The KUS activity code must be active to use ACH payments. |
ACH individual ID (field SGLIDACH) |
Enter the unique 15-character code assigned to you by the bank. This field is required when generating bank files with an ACH format as an XML file. Note: The KUS activity code must be active to use ACH payments. |
MTS individual ID (field SGLIDMTS) |
Enter the unique 15-character code assigned to you by the bank. This field is required when generating bank files with an ACH format as an XML MTS file. Note: The KUS activity code must be active to use ACH payments. |
Paying bank 1 (field PAB1) |
Paying bank linked to the Bank ID number. |
Paying bank 2 (field PAB2) |
Additional paying bank linked to Bank ID number. |
Additional issuer identification (field SENNUM) |
Specify here the issuer number to be provided during a magnetic transfer. |
Treasury interface (field TRECOD) |
Bank code for the interfaces to the cash management software |
Direct debit issuer no. (field SENNUM2) |
Portuguese bank code (field PORBANCOD) |
Tab Management
Operation record - Management
Accounting characteristics
Most of the data in this tab relates to generating payment entries recorded on the bank account:
Journals, entry types, and cash account for payment posting
This table is used to set up the journal, entry type, and cash account to be used based on the journal type being used, depending on the posting phase.
- About the journal:
- It is mandatory to specify the bank type journal for the bank.
- For a Cash journal type, the account attached to it is mentioned in the Account field.
- About the entry type:
- The entry type is only relevant for journals with a value other than None.
- It is used to specify an entry type according to the journal, in other words, according to the posting phase. For example, using this setup makes it possible to isolate draft management entries in specific entry types, separate from the cash receipt/withdrawal.
- About the cash account:
- The entry type is only relevant for journals with a value other than None.
- It is used to specify an account according to the journal, in other words, according to the posting phase. For example, using this setup makes it possible to load a draft account for draft management, without using the accounting codes.
Payment management rules
- Off/on site check deposit: If this option is selected, the check deposit slips generated for this bank will group the payments based on the Check type (local menu 654) associated with them.
- Deposit by due date: Select this option to generate an entry by due date upon validation of the draft/bill of exchange deposit on the bank. Otherwise, the process generates an entry by deposit slip.
- Paying bank notice by due date: Same option for the paying bank notices.
Bookkeeping currency of the bank
This field cannot be modified because it is automatically loaded with the currency in which the general account associated with the bank is kept, or by default, with the local currency.
The bank currency determines the transaction currency of those operations posted on this bank to facilitate the banking reconciliation and the valuation of the accounts kept in foreign currency upon fiscal year closing.
Payments issued in a currency other than the bookkeeping currency generate an automatic inter-currency entry.
For the changeover to the EURO, the bookkeeping currency for accounts kept so far in 'IN' currency will be modified. The "Euro conversion date" field is automatically completed whenever the user modifies the bookkeeping currency associated with the bank account.
This date is used to:
- Control the currency used to enter entries into the bank journal, and bank statements
- Determine the currency when printing the bank reconciliation report
Other characteristics:
- Identify the site and/or the company that the bank is attached to
- Define the bank as a BP code when the account for the bank journal is a control account
- Select the accounting code that determines the choice of the account for bank expenses on doubtful receipt entries
Setting up bank account records linked to cash accounts to perform a reconciliation
You can define a bank account record at the company or site level that is linked to a normal cash account or a control cash account plus business partner. To reconcile these records, you need to ensure that bank records defined at the same level do not share any of the following definitions: bank, company, site, account, and business partner. The bank record definitions need to be unique.
In reconciliation functions, journal entry lines that are considered are those posted to the site or company as defined in the bank account record and on the cash account plus business partner, as defined in the bank account record. As a result, when several bank account records are created for the same company or site and with the same bank account (plus business partner), the exact same journal entry lines display when running reconciliation functions.
Note: This also applies to the Bank inquiry function (CONSBAN).
For example:
In the bank records below, the lines for Bank codes AAA and BBB cannot reconcile because they share the same definitions for Company, Site, and Account. A reconciliation in this case would return the exact same journal entry lines.
Bank codes III and JJJ also cannot reconcile because they share the same definitions for Company, Site, Account, and BP code.
Bank account records before reconciliation
Bank code |
Company |
Site |
Bank journal type |
Cash account |
Control account |
BP code |
AAA |
FR10 |
BNK |
512000 |
No |
||
BBB |
FR10 |
BNQ |
512000 |
No |
||
CCC |
FR10 |
FR011 |
BNQ |
512000 |
No |
|
DDD |
FR10 |
BAN |
512001 |
No |
||
EEE |
FR10 |
FR011 |
BAK |
512002 |
No |
|
FFF |
FR10 |
FR012 |
BAK |
512002 |
No |
|
GGG |
FR10 |
BNQ |
512003 |
Yes |
GGG |
|
HHH |
FR10 |
BNQ |
512003 |
Yes |
HHH |
|
III |
FR10 |
BNQ |
512003 |
Yes |
BAQ |
|
JJJ |
FR10 |
BNQ |
512003 |
Yes |
BAQ |
|
LLL |
FR20 |
BNK |
512000 |
No |
Journal entry lines displayed after reconciliation
Bank code |
Company |
Site or Sites |
Account number |
BP |
Journal code |
Reason reconciliation impossible |
AAA |
FR10 |
All |
512000 |
|
NNNN |
Shared definitions with BBB |
BBB |
FR10 |
All |
512000 |
NNNN |
Shared definitions with AAA |
|
CCC |
FR10 |
FR011 |
512000 |
NNNN |
||
DDD |
FR10 |
All |
512001 |
NNNN |
||
EEE |
FR10 |
FR011 |
512002 |
NNNN |
||
FFF |
FR10 |
FR012 |
512002 |
NNNN |
||
GGG |
FR10 |
All |
512003 |
GGG |
NNNN |
|
HHH |
FR10 |
All |
512003 |
HHH |
NNNN |
|
III |
FR10 |
All |
512003 |
BAQ |
NNNN |
Shared definitions with JJJ |
JJJ |
FR10 |
All |
512003 |
BAQ |
NNNN |
Shared definitions with III |
LLL |
FR20 |
All |
512000 |
NNNN |
Parameters
Access code (field ACS) |
Access code used to limit the access to the bank for certain users. |
Site (field FCY) |
Site that possesses this bank account. Entering this information automatically updates the company code. |
Company (field CPY) |
Bank statement identifier (field BSIREFBAN) |
Enter a unique code or string appearing in the bank statement file to identify this bank account. This field is optionally used in the context of the advanced bank statement import process. Depending on the setup, the bank statement import uses this information to automatically find the Sage X3 bank account belonging to the bank statement file. Typically, this is needed when importing statement files containing multiple statements from different bank accounts for the same bank in one file. Refer to the Advanced Bank Statement how to guide for more details. |
ISR customer no. (field BVRNUM) |
This field requires the KSW – Swiss localization activity code to be active. You use it to enter the ISR customer number for the given bank account. This number is used for payments with ISR number (inpayment slip with reference numbers). For suppliers, the ISR customer no. is also used to search for a matching BP account if support for ISR code line entry on purchase invoices is active in the SWIPURBVR - Swiss ISR usage purchasing parameter (LOC chapter, SWI group). Refer to the Swiss legislation guide on the How to tab for more details regarding payment and ISR setup. |
Customer ID ISR (field BVRCUSTID) |
Enter the ISR customer ID if you use ISR customer invoices with a standard bank account and not a Postfinance account. The ISR customer ID is issued by your bank. This field is only available if the KSW – Swiss localization activity code is active. |
Bank register
Incoming payment transaction (field INPAYTRA) |
Enter or select the Revenue Payment entry type (GESTPY) code for this bank account. This code is used in the related Bank register. This field only displays for a Polish or South African legislation for a Bank register. |
Outgoing payment transaction (field OUTPAYTRA) |
Enter or select the Expense Payment entry type (GESTPY) code for this bank account. This code is used in the related Bank register. This field only displays for a Polish or South African legislation for a Bank register. |
field BAK11 |
field BAK12 |
field BAK13 |
field BAK14 |
Deposits/Remittances
O/L check remit. (field CHQTYPFLG) |
Deposit by due date (field FRMDUDFLG) |
Use this option to create one journal entry by open item or one journal entry by remittance when posting the notes payable/receivable to the bank. If you select Yes, one journal entry is created by open item with an entry date set to the open item date. If you select No, the entry date is set to the remittance date. |
Payment order by due date (field PABDUDFLG) |
This option makes it possible to create a document for each due date or a document by note during the validation of a paying bank notice on the bank. If 'yes', there will be an item by due date with as posting date the due date. If not the posting date will be the note date. |
Grid Journals
No. (field NUMLIG1) |
Current line of the grid. |
Journal type (field JOUTYP) |
Two journals can used whether the payments relate to fixed asset suppliers or not:
Each journal can be set to Cash management or Miscellaneous operations. |
Journal (field JOU) |
The entry of the bank journal is mandatory. |
Entry type (field GTE) |
Used to associate a document type to a journal type, in other words a posting phase. |
Cash acct. (field TREACC) |
Used to associate a cash account to a journal type, in other words, a posting phase. |
Accounting parameters
BP code (field BANBPR) |
This field displays the BP Code, which is mandatory when one of the journals is associated with a collective account. The BP code must be a miscellaneous BP and is considered as a subdivision of the bank account. For example, this setup makes it possible to follow the entries and avoid duplicating bank accounts in Financials. |
Accounting code (field ACCCOD) |
Use this field to specify the accounting code of the site. |
Currency (field CUR) |
Specifies the operation-keeping currency. |
Rate type (field CHGTYP) |
The entries posted on a bank account held in a different currency to that of the company will be valued in company currency. Mention here the exchange rate type to be used to perform the conversion. The type is used in the bank allocation function to value the virtual balance of the bank in company currency. |
Date of currency change (field CHGDAT) |
Cash excluded (field CFOEXD) |
FIFO conversion process (field FLDFIFCP) |
If this check box is selected, general entries for this account are excluded from the FIFO rate calculation process (GESFIFCV). This is useful to exclude short-term or overnight deposits and funds posted as Outgoing payment and Incoming payment on the same account. This field is only available if the account currency is different from the related ledger or journal and if the FIFRC- activity code is active and the FIFRC – FIFO rate calculation parameter (CPT chapter, CLO group) is set to Yes. |
Start date (field FLDSDA) |
Enter a start date of an open period to include journal entries beginning on that date.
This field is only available if the account currency is different from the related ledger or journal currency and if the FIFRC- activity code is active and the FIFRC – FIFO rate calculation parameter (CPT chapter, CLO group) is set to Yes. |
Expense allocation
Bank account number (field BIDEXS) |
Use this field to enter the bank account number from which the bank charges wlll be debited. |
Currency (field CUREXS) |
This field is used to enter the currency of the account on which the bank charges will be debited. |
IBAN code (field IBAEXS) |
This field displays the IBAN prefix (International Bank Account Number) of the account from which the bank charges will be debited. |
Conditions
Bank terms (field BANTRM) |
Field not used by the software. |
Early discount rate (field DEPRAT) |
Field not used by the software. |
Balance control (field BNKPROBALC) |
If this field is set to ‘Yes’, the balance control for this bank is activated in function Payment/receipt entry. The balance control will be run in the currency of the bank. |
File
File extension (field FILEXT) |
Enter the extension for file names that are generated for electronic transfers. The extension is required when the bank account contains more than three characters. |
Bank file (Portugal) (field BANFIL) |
Additional record (field RECCPT) |
When checked, this box is used to generate bank files with format AFB160 and line '07' ('Additional records'). |
Processing by batch (field SCTPROLOT) |
When this box is checked, the bank carries out a global posting (one debit line taken into account by deposit slip). |
Grid Analytical
Dimension type (field DIE) |
Dimension (field CCE) |
This field displays the analytical dimension type associated with the bank. The displayed dimension types default from the Company/site associated with the bank/cash. |
Tab Checks
Check printing
This section is used to control check printing.
The following parameters must be set to Yes to enable the fields in the Check printing block.
USACHK - US/CAN Check printing (LOC chapter, USA group)
CHQCT - Check controls (TRS chapter, BNK group)
MICR printing
In this section, you can enter information required for MICR printing.
If MICR printing is set to Yes, bank transit numbers and checking account numbers are required.
Check printing
Format (field CHKFMT) |
Select the check format based on the type of check you are printing to:
If the parameter USACHK - US/Can Check Printing (chapter LOC, group USA) is set to Yes, the field is active. If this parameter is set to No, the field is in active and set to Not Used. |
Next check no. (field NXTSEQ) |
This field displays the next check number or you can enter a check number. Check numbers must first be entered in the Checks (GESCHB) function. You can access this from the Checkbook icon. This field is only active when the CHQCT - Check controls parameter (TRS chapter, BNK group is set to Yes. |
Checkbook (field CHK_BTN) |
Click the Checkbook icon to open the Checks (GESCHB) function to assign check numbers for a unique bank account. Enter the beginning and ending numbers from the check stock. |
Check status (field STA_BTN) |
Click the Lookup icon to view the check status and the corresponding Positive Pay date and Positive Pay sequence number if relevant. Statuses include:
You cannot manually adjust a check with a status of issued, posted, or cleared. Those statuses are set systematically when activities are performed on the linked payment. Only unposted checks can be reprinted. This field is only active when the CHQCT - Check controls (TRS chapter, BNK group) parameter is set to Yes. |
MICR printing
Print (field MCRPRT) |
Select Yes for MICR printing. This enables the Bank transit and Checking account fields. The check number and the MICR line are printed on the checks. |
Bank transit (field BANTRA) |
Enter the bank transit numbers to be printed on the MICR line for checks. |
Checking account (field CHKACC) |
Enter the bank's checking account number to be printed on the MICR line on checks. |
Positive Pay
File name (field POSPAYFIL) |
Enter the Positive Pay bank file name created in the Bank files function (GESTFB). This field is available only if the CHQCT - Check controls (TRS chapter, BNK group) parameter of the bank is set to Yes and if the Bank file check box is selected in the Bank files function (GESTFB). |
Definition of the journals, journal types and accounts in payments
The journals, document and treasury account types used in the accounting journals for the payments can be set up. They are determined in cascade based on the manipulated data in the database (BP, Bank), the automatic journals or general parameters.
Journal entry type
The evaluation of the journal type is carried out in cascade following the rules specified below. The iteration stops at the first rule that is used to define the journal type:
- Journal type set up in the payment automatic journal.
- When not available, the journal type set up in the bank record, for the journal type, therefore the posting stage. This rule is only processed if the journal type is other than "None".
Journal
The evaluation of the journal is carried out in cascade following the rules specified below. The iteration stops at the first rule that is used to define the journal:
- Journal set up in the payment automatic journal.
- When not available, the journal set up in the bank record, for the journal type, therefore the accounting stage. This rule is only processed if the journal type is other than "None".
- When not the case, the journal set up in the general parameters JOUPAY*.
- Otherwise, the journal associated with the journal type.
Treasury account
The "Treasury account" term used here is generic. It is the account to be used to complete the previous stage. It can therefore be an intermediate account in case of intermediate payment and bank account in case of a bank receipt...
Moreover, all that follows is linked to the functioning of the variable for the automatic journal 'CPTTRESO' used as standard by the majority of automatic journals linked to the different payment steps. It is obvious that if the standard automatic journals are modified, this rule is no longer valid.
Finally, the rules specified below only apply if the bank is known at the time of the evaluation. The treasury account evaluation in the accounting structures that do not impose in the presence of the bank in the payment (in the case if the cashbook) use other rules: Accounting code associated with the business partners, JOUPAY* parameters, ...
The treasury account calculation is carried out in cascade following the rules specified below. The iteration stops at the first rule that is used to define the account.
- The treasury account set up in the bank record, for the journal type, therefore the accounting stage. This rule is only processed if the journal type is other than "None". Also implicit in this, it is only processed if a bank is associated with the payment.
- Otherwise, the control account associated with the journal. This assumes that this journal is of the treasury type. This journal is determined by the following rule cascade:
- The journal associated with the accounting stage for the payment in the bank record.
- Otherwise, the journal associated with the automatic journal.
- When not the case, the journal defined in the general parameters JOUPAY*.
- Otherwise, the treasury account is evaluated as a function of the accounting codes parameterized in the automatic journal.
- Otherwise, by the general parameter ACCDEF.
The practical consequences are as follows:
- If a journal of the type treasury (with a control account) is defined for a journal type, the treasury account that is moved during the corresponding accounting stage will always be this control account.
- If the assignment rule for the account depends on a parameter other than the journal (for example accounting codes), it is necessary that the journal is not of the type treasury.
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
"No interface code: XXX Bank without cash tracking"
Management of the cash interface is activated. The absence of a cash interface code for the bank implies that none of the payments connected to it will be exported to the cash software.
"Cash interface code already used: XXX"
Management of the cash interface is activated. The cash interface code for the current record has already been entered on bank XXX.
"Mandatory field"
Although it is not necessary to attach a bank to a site, said bank must necessarily be attached to at least a company.
In the same way, the accounting code that defines the recording conditions of the doubtful receipt entry expenses must be identified.
"The bank journal must be entered"
The only journal that absolutely needs to be entered is the bank type journal, in the table of the second tab.
"XXX: Not legal"
The company to which the bank is attached must be defined as legal company.
"This is not a miscellaneous BP"
Since some of the bank entries can be posted to a control account, the selected code/BP account that identifies the bank must necessarily concern a miscellaneous type BP, and not a supplier, customer etc. type.
"Enter a cash or Miscellaneous Operations journal"
The bank journals, the journals for checks to be cashed etc. are necessarily of Cash or MO type.