Bank reconciliation
Bank reconciliation checks that every statement transaction is in the books exactly once, matched to a document (invoice, act, receipt), and that the closing balance in the books equals the statement’s. Differences are duplicates, omissions, payments without documents and partial payments.
- Author
- Centa AI editorial team · Centa AI product and content teamWrites the guides and product pages. Rates and deadlines are checked against the Tax Code text stored from LexUZ; feature statuses come from one list in the product code.
- Last updated
Step by step
- Balances. The opening balance in the books equals the statement’s; if not, find the difference in the previous period first.
- Completeness. Every statement line is in the books; every bank transaction in the books is on the statement.
- Duplicates. One transaction loaded twice (from a file and from an integration) is a common cause of inflated turnover.
- Documents. Every supplier payment and every customer receipt has a document; no document — a question.
- Partial payments. A payment smaller than the invoice does not close it; the remaining debt must stay visible.
- Closing balance. Agrees with the statement — reconciliation done.
How Centa does it
- Duplicates are stopped before they are written: by the bank’s id, then by reference, date and amount, then by a “date | amount | direction | counterparty” fingerprint. Two real payments with different ids are never merged.
- Direction (in or out) comes from the file — a Direction column, Debit/Credit, or the sign of the amount.
- Payments are matched to invoices, acts and receipts; automatically only on a strong match, otherwise as a question in the Exception Engine.
- Non-UZS transactions are listed separately and never booked as soums.
- A payment proven only by a receipt stays “not confirmed by the bank” and is excluded from cash until the statement arrives.
Reconciliation is one of the jobs AI accounting software takes over; the others are documents, taxes and reports.