Import bank transactions and apply payments

When the customer pays, Alice imports the bank statement as evidence, identifies the payment transaction in the normalized bank dataset, and then records reconciliation and any required ledger impact in append-only datasets. This keeps the workflow deterministic and reviewable, and it can scale from direct one-to-one matches to two-phase proposal and batch-apply reconciliation.

Alice imports the raw bank statement evidence with Bus Bank:

bus bank import --file 202602-bank-statement.csv

Bus Bank writes schema-validated bank datasets and preserves source statement identifiers so each imported transaction remains traceable back to the original evidence.

Alice reviews the imported bank transactions and finds the February payment row that corresponds to invoice INV-1001:

bus bank list --month 2026-2

If the module supports filters, she narrows the output to the February date range or to rows that contain the invoice number or counterparty reference. The exact filtering flags are part of the module surface area, so she uses bus bank list --help to see what is available in her pinned version.

Alice records a direct reconciliation when the payment is an exact one-to-one match:

bus reconcile match --bank-id BANK-2026-02-14-001 --invoice-id INV-1001

For partial payments, batch settlements, or fee splits, she uses allocation instead of one-to-one match.

Alice records allocation rows when one bank movement settles multiple targets:

bus reconcile allocate --bank-id BANK-2026-02-14-002 \
  --invoice INV-1001=900 \
  --journal JRN-2026-014=40 \
  --journal JRN-2026-015=300

If reconciliation planning reveals missing bookkeeping (for example bank fees that are not yet posted), she appends the missing journal entry with bus journal add and then reruns matching or allocation.

If she is unsure about the available flags in her pinned version, she uses bus reconcile --help.

Alice verifies the result by reviewing the bank list output and the resulting journal postings, then uses invoice listing as a cross-check:

bus invoices list

When the goal is high-volume or historical reconciliation with deterministic candidate planning and batch application, use Deterministic reconciliation proposals and batch apply. The first-class bus reconcile propose and bus reconcile apply commands support that flow directly.

When the goal is historical ERP onboarding of invoices and bank datasets, use Import ERP history into canonical invoices and bank datasets.

← Evolution over time (extending the model) BusDK Docs Deterministic reconciliation proposals and batch apply →

Import bank transactions and apply payments

Sources