Why do I need to map the data?

Mapping translates your internal data name into a name the software knows.  Without this step, the software will not know, for example, if a field holds transaction date or check number.

 

Choosing fields

 

For the majority of cases, the mappings below are suggested.

 

Bank Reconciliation

 

At a minimum, positive pay files sent to the bank will include: check number, amount, date, usually the payee name, and sometimes a void indicator.  Perform these mappings as follows:

 

 

See Mapping General Ledger Data for the steps to actually create the mapping.

 

Bank Reconciliation

 

In Bank Reconciliation, you will have two kinds of data: bank data and general ledger data.  For the most part, you can follow the guidelines listed above for Bank Positive Pay.  However, you must pay special attention to how the amounts are listed.  In some cases, the bank data will have two columns, one marked Debit and one Credit, while other times the amounts are in one field and signed.  Special care must be taken as positive and negative values have different meaning to the bank than to your company.

 

For Debit/Credit mappings, please see Debit versus Credit.

 

For amounts in one field, it is important to know that Bank Reconciliation views all negative values as being ones that reduce your general ledger, such as payments and issued checks, while positive values increased your general ledger, such as deposits and void checks.  If this is accurately represented in the bank data, map the amount as Amount.  If the signs are exactly the opposite, map the amount as Amount_Reverse_Sign.  See Selecting fields to represent amount for more information

 

More Resources

 

For definitions of the available fields, see Definitions - Mapping Fields

 

To learn how to map the data, see Mapping Bank Data and Mapping General Ledger Data