Bank statement reconciliation processing - Bank statement import
The Bank statement page is used to manually import the bank statement into your D365 environment. Users can navigate to the page by going to Cash and bank management > Bank statement reconciliation > Bank statements
Note: Setup File attachment document type on Financial utilities parameters to attach the import file to the created D365 Bank statement(s).
Select Import statement. Where the selected statement format is marked as Customised format the following additional fields are available on the import:
Field | Description | Options |
---|---|---|
From date | Select transactions >= this date | Calendar |
To date | Select transactions <= this date | Calendar |
Date | Select which date to use when Mark as new transactions are posted |
• Today’s date • Statement Transaction Date (To date of the Bank statement header) |
Note: Where the bank statement file contains transactions related to multiple dates and multiple bank accounts (i.e. the file is imported using the option Import statement for multiple bank accounts in all legal entities, separate bank statement records get created in D365 for each bank account.
The Statement ID number sequence in Cash and bank management parameters is used to generate the Statement identifier.
When a bank statement (BAI2/NAI/BRS/Flat file) is imported, statement lines will only be imported where the following matching rules are validated:
In addition, where Import statement for multiple bank accounts in all legal entities is enabled, and if D365 finds multiple bank accounts in same/different legal entities with the same bank account number while importing the statement, following order of priority is applied:
The bank statement can also automatically be imported by using periodic task Import bank statements via financial utilities connection.
Filter Imported via financial utilities connection on the Bank statement import, can be used to filter to bank statements imported using above periodic task.
Error process if there are issues with creating all the bank statement(s) for the file using the periodic task:
If the Bank statement format is:
Example error that will result in not all bank statement(s) being created: An unique bank account was not found for a Bank account number within the file
View and manage Bank statement files imported via the periodic task.
It allows users to easily view logs and applicable files state for each bank statement file.
Field | Description | Options / Examples |
---|---|---|
Name | Name of the Financial utilities connection | SFTP |
File name | Name if the bank statement file | xxx.txt |
Statement format | Name for the bank statement format used on the periodic task | BAI2 |
Status | File state | • Completed - Succesfully created bank statement/s • Error - Bank statement wasn’t created, for example ‘No matching bank account found’ • Cancelled - Option to cancel, which changes the status from Error to Cancelled. |
Created date and time | Date and time the file was imported |
The following buttons are available on the Action Pane.
Button | Description |
---|---|
Import | |
Retrieve files | Opens periodic task ‘Import bank statements via financial utilities connection’ |
Process | |
Log | View info, warning or error logs |
Process | Ability to reprocess error files. File attached in document handling will be used for re-process - Required to assign a ‘File attachment document type’ in ‘Financial utilities parameters’ in order to attach the file when the file is imported with the periodic task. |
Process | |
Bank statement | Opens Bank statement form, filtered to bank statement/s created for the file |
Maintain | |
Reset format | Ability to change error files to a different bank statement format |
Cancel | Ability to change error files to cancelled status |