Bank account ledger entries
What 365 business Banking adds to bank account ledger entries: message to recipient, end-to-end reference and the bank transaction FactBox.
A bank account ledger entry is created whenever you post to a bank account in Microsoft Dynamics 365 Business Central, for example a payment from the payment journal or a line of the payment reconciliation journal. 365 business Banking stores the payment details on the entry: the payment reference, the reference for the bank and the bank transaction the entry came from.
Standard functionality in Business Central
In the standard product, the Bank Account Ledger Entries page lists every posting to a bank account with date, document, amount and open status. Bank account reconciliation closes the entries. See Reconcile bank accounts on Microsoft Learn.
What 365 business Banking adds
Additional fields
| Field | Meaning | Shown |
|---|---|---|
| Message to Recipient | The payment reference as it was sent to the bank. | column after Description |
| Transit Account No. | The transit account this entry was posted to instead of the bank G/L account. | hidden |
| Transit Account Cleared | Whether the amount has already been transferred from the transit account to the bank G/L account. | hidden |
| In Transit | Whether the amount is still on the transit account. These entries are excluded from Balance excl. Transit on the bank account card. | hidden |
Show the hidden columns via Personalize. For the transit account, see Transit account.
365 business Banking also stores further fields on the entry without showing them on the page:
| Field | Purpose |
|---|---|
| End-to-End Reference | The reference under which the payment was sent to the bank. When the payment appears on the statement, application uses it to recognize your own payment. See Recognise own payments. |
| Transaction ID | The identifier of the bank transaction the entry came from. The Bank Transaction FactBox uses this identifier to find its details. |
| Standing Order No. | The standing order the entry belongs to. See Standing order. |
| Remittance Advice No. | The number of the remittance advice the payment was announced with. See Remittance advice. |
Bank transaction FactBox
If a bank account ledger entry comes from a retrieved bank transaction, the Bank Transaction FactBox shows its details as read-only:
- Purpose, split into sections,
- Sender or Recipient (depending on the sign) with Name, IBAN, Account No. and Bank Name,
- the transaction's Classification, SEPA Purpose Code and ZKA Code.
The FactBox only appears when a bank transaction exists for the entry. It is the same FactBox as in the payment reconciliation journal, which is described in Payment reconciliation journal.
Where the details come from
The details are stored in the Bank Transaction Detail table when the payment reconciliation journal is posted. If they are missing, for example because a retention policy deleted them, Business Central tries once per session to retrieve them again when the entry is opened:
| Bank connection | Can be retrieved again |
|---|---|
| PSD2/XS2A via finAPI | yes, as long as finAPI still knows the transaction |
| EBICS, camt file, payment service providers, Universal | no; the FactBox is then not shown |
You define how long the details are kept in Retention policies for banking data.
Other kinds of entries
The same Bank Transaction FactBox also appears in Customer Ledger Entries, Vendor Ledger Entries, Employee Ledger Entries and General Ledger Entries when the entry comes from a bank transaction (field Bank Transaction ID). This shows where the payment came from, even on an applied invoice.
From Business Central 27, 365 business Banking also adds the Remaining Amount column in General Ledger Entries. For G/L accounts whose entries are reviewed, it shows the amount not yet reconciled; choosing it opens the reviewed G/L entries. For more information, see G/L entry matching.