Configure Basic Bank Reconciliation Imports & Negative-Sign Identifiers

In this article, we’ll learn how to import a CSV file for bank reconciliations in Microsoft Business Central. We’ll cover two types of files: 1. A simple file with a few columns, and 2. A file where all amounts are positive, with a column indicating whether they are credit or debit. Below is a picture…

3–4 minutes

In this article, we’ll learn how to import a CSV file for bank reconciliations in Microsoft Business Central. We’ll cover two types of files: 1. A simple file with a few columns, and 2. A file where all amounts are positive, with a column indicating whether they are credit or debit.

Below is a picture of the simple file and the three tasks we need to complete.

  1. Create a Data Exchange: Map the import file fields to Business Central fields
  2. Bank Import/ Export Setup: Create a new code and link it to the data exchange
  3. Update the Bank Account Card
Table displaying a simple CSV file for bank reconciliations, including columns for Account No., Transaction Date, Check No., Transaction ID, Type, Amount, and Description.

Data Exchange Setup

Screenshot of Data Exchange Definition setup in Microsoft Business Central, highlighting General, Line Definitions, and Column Definitions sections.

General Section

  • Code and Name: Whatever your heart desires..
  • File Type: Variable Text
  • Type: Bank Statement Import
  • Reading/ Writing XMLport: 1220
  • Ext. Data Handling Codeunit: 1240
  • File Encoding: Windows
  • Column Separator: Comma
  • Header Lines: 1

Line Definitions

  • Line Type: Detail
  • Code and Name: Up to you…
  • Column Count: Number of columns your file contains

Column Definitions

Here you add the columns you wish to import into Business Central. Mapping all columns is not required; only select the relevant ones.

  • Column No.: The position number of the column in the file.
  • Name: Column name from file
  • Data Type: Choose the appropriate type
  • Data Format: For Dates you want to use M/d/yyyy
  • Data Formatting Culture: en-US for US formatting of dates and decimals
  • Length: Set a character limit for the incoming value, ensuring it does not exceed the field limit in Business Central.
  • Negative-Sign Identifier: Enter the value in the data file that indicates negative amounts. This identifier converts those amounts to negative values during import.

Field Mapping

After completing the above sections, you need to map the Column Definitions to the related fields in Business Central.

Screenshot of the Line Definitions section in Microsoft Business Central, highlighting the 'Field Mapping' button.
  1. Select the Field Mapping button in the Line Definitions section.
  2. Table ID: 274
  3. Mapping Codeunit: 1248
  4. Use the dropdown in the Column No. field to select a column from the file. Then, in the Field ID, map it to the corresponding Business Central field.
  5. Optional: Select this for columns that may not always require a value, like checks. If not selected, the import will error if the value is empty. If your Debit and Credits are in different columns both will need this checked off.
  6. Multiplier: Useful for situations where Debit and Credit columns are separate, but both show positive numbers. You can add a -1 to the Credit column to reverse the sign.
Field mapping interface in Microsoft Business Central showing Table ID, Name, and Mapping Codeunit, along with a list of column mappings for a bank import file.

Bank Export/ Import Setup

  • Code and Name: Your choice
  • Direction: Import
  • Processing Codeunit ID: 1270
  • Data Exch. Def. Code: Select the data exchange we previously created

Final Step: Add to Bank Account Card

To finish, open the Bank Account Card and add our new code in the ‘Bank Statement Import Format’ found in the Transfer section.

Screenshot of the 'Transfer' section in Microsoft Business Central, displaying fields for various export formats including the 'Bank Statement Import Format' which is highlighted.

Now you’re ready to use the import, let’s see this in action! 😊

Now, let’s look at using the Negative-Sign Identifier for files with only positive numbers and a column indicating debit or credit. We’ll use the example file below.

A screenshot of a simple CSV file for bank reconciliation, showing columns for Account Number, Transaction Date, Check Number, Transaction ID, Type, Amount, Description, and Identifier with entries indicating Debit or Credit.

There’s two slight changes we need to make from the configuration we did already.

  1. Add a column for the negative indicator and enter the credit code in the Negative-Sign Identifier field.
A screenshot showing a table for Column Definitions in a software interface. The table includes fields for Column No., Name, Data Type, Data Format, Data Formatting Culture, Length, Description, and a highlighted Negative-Sign Identifier column with the value 'Credit'.

2. In the Field Mapping you need to map this identifier field to the Statement Amount

Screenshot of the Field Mapping interface showing a table with column numbers, captions, and field IDs, highlighting an identifier for mapping statement amounts.

ANNDDDDDD that’s it!! Now on imports the amounts will change to credits when the Negative-Sign Identifier is found.

Thank you for reading, I hope you learned something new.

As always, stay SAASY my friend.

-Dino

One response to “Configure Basic Bank Reconciliation Imports & Negative-Sign Identifiers”

  1. […] Last Note 😊: Data Exchange Definitions are also used for importing bank statements to a Bank Reconciliation. For more information, check out this article: Configure Basic Bank Reconciliation Imports & Negative-Sign Identifiers […]

    Like

Leave a comment

Trending