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

SEEREFERTTO Refer to documentation Implementation

Screen management

Header

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.

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

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.

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.

Tables used

SEEREFERTTO Refer to documentation Implementation