Cash application demo · AR open entries → electronic bank statement

Bank File Generator

Turn open customer invoices into a bank-statement file LN can import and auto-match.
1Statement→ 2Pick invoices→ 3Download & import

2Open customer invoices

Tick the invoices the bank file should show as paid. LN calls these AR open entries — invoices customers haven't paid yet.
—

1Statement

Which of our bank accounts received the money, and the statement's number, date and starting balance.
Looking up the previous statement in LN…
Advanced value date, LN company

3Download & import

Which bank-statement layout to write. Leave on the LN format unless you are demoing a specific standard.
About the formats
No invoices selected yet.
Tick at least one invoice to enable.
Remittance advice demo (RPA / IDP) Off
For the RPA demo: the bank file is written incomplete (no invoice numbers and/or a short payment), so LN can't fully match it. You then download a remittance-advice PDF per customer; the RPA / IDP flow reads the PDF and completes the cash application.
Diagnostics dev
—
Open /api/diag/api/status

How it imports

After you download

LN format. 1 Copy the file (YYYYMMDDE.txt) to the bank's EBS incoming folder on the LN server (…/appdata/EBS/Incoming). 2 Run Distribution of MT940 Bank Files (tfcmg5207m000) — it reads the bank address in line 1 and files the statement under that bank relation. 3 Open the Bank Statement Workbench (tfcmg5610m100) → Convert → Match → Post. Each line matches its invoice by number.
Definitions. Bank relation — one of our bank accounts as LN knows it (tfcmg0510m000). Opening balance — must equal the previous statement's closing balance, or LN rejects the import. No bank account in LN — the customer's pay-by business partner has no bank account on file; only matters for CAMT.053 / MT940 / BAI2. The LN format matches on invoice number (Conversion Data for EBS, tfcmg5105m000).
No invoices selected