Two transactions can share an amount without representing the same payment. That simple fact explains why bank reconciliation needs more than a matching button.
DNA supports importing a bank statement and using DNA Intelligence to reconcile automatically. The useful operating model combines that automation with a clear way to inspect the statement, the candidate ledger entries and the remaining differences. Speed matters, but a reviewer must still be able to explain the result.
Establish the statement boundary
Confirm the bank account, currency, opening balance, closing balance and statement period before comparing transactions. Review the imported rows for missing dates, unexpected signs and duplicate lines. Keep a reference to the source statement so a reviewer can trace the import.
Importing the same period twice is a valuable acceptance test. Ask what the system detects, what it prevents and how the operator sees the overlap. Do this with demonstration data before relying on a production process.
Test more than exact matches
An exact amount and reference is a straightforward case. Other cases expose the quality of the workflow: several invoices settled by one payment, bank fees deducted from a receipt, timing differences, partial payments and two transactions with the same amount.
For an illustrative receipt, a customer pays 10,000 while the bank credits 9,975 after a 25 fee. Matching the net bank line to the gross customer receipt without explaining the fee leaves an accounting difference. The team needs to identify the components and apply its approved treatment.
Keep exceptions visible
Organize unresolved differences by cause rather than hiding them in one residual amount. Distinguish missing ledger entries, timing differences, incorrect references and potential duplicates. Assign an owner and keep the supporting document close to the decision.
The acceptance question is specific: can another accountant reopen the reconciliation and understand why each line was matched or left outstanding? A high match rate alone does not answer it.
Demonstrate the complete loop
In Banking & GL, inspect the statement-import and reconciliation workflow. Include an exact match, an ambiguous match and an unmatched charge in the sample. Explore DNA Intelligence as the connected intelligence layer.
Your go-live evidence should include the reconciled balances, the exception list and the review responsibilities. Automatic reconciliation is most useful when its outcome remains explainable.
