Posting a Bank Statement
The final step that ends the electronic banking workflow is posting a bank statement. To post a bank statement, choose the Post action in the Process section on bank statement card.
At the beginning, the post function checks the bank statement for errors (missing data, unapplied entries, etc.). Each error message stops posting, and an error and warning list is shown in the Bank Statement Errors section on the right. Similarly, it will be the case when errors occur during posting.
Note
If the validation process results only in warnings, the posting process can be continued, but the app displays an additional warning to the user.
Structures Created when Posting
As a result of the posting, the following structures are created:
- Recipient ledger entries (customer, vendor, employee) apply-to payments. They can be checked from the standard ...Ledger Entries pages (to view such pages, choose Posted Documents in the Electronic Banking Role Center);
- Entries on the Electronic Banking Register page (see Electronic Banking Register);
- Posted Bank Statement that you can display by choosing Posted Documents, Posted Bank Statements. It is used only for informative purposes.
In addition, on the Archived Payment Proposals page, the applied lines are highlighted in green.
The Source Code of Posted Bank Statements
Note
Each posted bank statement has a source code that is set up on the Source Code Setup page. By default, the WYCBANK (BANKSTMT) source code is assigned to bank statements. For more details about the source code setup for bank statements in the standard Dynamics 365 Business Central, see Setting Up Source Codes and Reason Codes for Audit Trails.
Bank Statement Report
Note
You can post a bank statement and print a report for this posted bank statement at the same time. To do so, use the Post and Print action.