Skip to content

Reconciliation templates

A template is a complete reconciliation set-up to start from: its sides, the fields they are mapped onto, the matching passes in order, the checks that prove the result and, for some, reason codes. Starting from one copies it into a new reconciliation you then adapt in the designer: connect your own data sources, map your columns, and change anything else. Your workspace can add its own templates as well (Settings → Library); see Creating a reconciliation.

This list is generated from the product’s template library.

Start from scratch

Two datasets matched on a reference and an amount. Rename the sides, add the fields you need, then add passes, checks and rules.

Sides2 — Side A · Side B
FieldsDate · Reference · Description · Amount
Matching passes, in order
  1. Reference and amount
ChecksReferences and amounts present

Bank reconciliation

Bank statement against the cash book. Matches by reference, then by amount and date, then batched deposits and split payments, and proves the result with a bank reconciliation statement.

Sides2 — Bank statement · Cash book
FieldsDate · Reference (cheque, UTR) · Narration · Amount · Balance
Matching passes, in order
  1. Reference and amount
  2. Amount and date
  3. One deposit for several receipts
  4. Several entries for one book entry
  5. Amount within a week
ChecksStatement duplicates · Statement running balance · Bank reconciliation statement · Open items by age

Cash book integrity (single-sided)

One ledger or statement on its own: every balance follows from the previous one, no duplicates, nothing missing, large movements flagged.

Sides1 — Cash book
FieldsDate · Voucher · Amount · Balance
Matching passes, in orderNone: a single-sided check
ChecksRequired values · Duplicate vouchers · Running balance · Large movements

Corporate card reconciliation

The card statement against expense claims. Matches by authorisation code, then amount, date and merchant, splits one charge across several claims, and catches claims made twice.

Sides2 — Card statement · Expense claims
FieldsTransaction date · Authorisation code · Merchant · Cardholder · Amount
Matching passes, in order
  1. Authorisation code
  2. Amount, date and merchant
  3. One charge split across claims
  4. Amount and date only
ChecksClaimed twice · Large charges · Statement and claims totals · Open items by age

Customer receipts against open invoices

Cash application: money received from customers against their open invoices. One receipt can pay several invoices, part payments stay open, and balances are compared per customer.

Sides2 — Customer receipts · Open invoices
FieldsDate · Invoice number · Customer · Amount · Currency
Matching passes, in order
  1. Invoice number quoted
  2. One receipt for several invoices
  3. Same customer and amount
ChecksDuplicate invoices · Balance per customer · Receivables by age
Reason codesCustomer paid less

Data checks (single-sided)

One dataset on its own: required values, duplicates and values outside a range. Each failing row is an exception to fix.

Sides1 — Data
FieldsReference · Date · Amount
Matching passes, in orderNone: a single-sided check
ChecksRequired values · Duplicates · Amount range

GSTR-2B against purchase register

Input tax credit: invoices on the GST portal (GSTR-2B) against your purchase register by supplier GSTIN and invoice number, with taxable value and IGST, CGST, SGST and cess compared. Shows credit you can take, credit at risk and invoices you have not recorded.

Sides2 — GSTR-2B · Purchase register
FieldsSupplier GSTIN · Supplier name · Invoice number · Invoice date · Taxable value · IGST · CGST · SGST · Cess · Input tax credit
Matching passes, in order
  1. GSTIN, invoice number and date
  2. GSTIN and invoice number, date differs
  3. Probable: GSTIN, tax and date, similar invoice number
ChecksSupplier GSTIN valid · Tax components · Invoice booked twice · Input tax credit · Credit per supplier

Intercompany transactions

One entity's receivable against the other entity's payable. Amounts are opposite in sign, matched within each currency and entity pair; differences show by counterparty.

Sides2 — Entity books (receivable) · Counterparty books (payable)
FieldsDate · Intercompany reference · Counterparty · Amount · Currency
Matching passes, in order
  1. Reference, opposite amount
  2. Same amount within a week
  3. Several entries against one
ChecksBalance per counterparty · References present · Open items by age

Online payments (four-way)

Orders, the payment gateway's settlement report, the bank statement and the ledger. Each order is traced to its gateway payment, the gateway's batch payout to the bank credit, and the bank credit to the ledger entry.

Sides4 — Orders · Gateway settlements · Bank statement · Ledger
FieldsDate · Order number · Settlement ID / UTR · Amount
Matching passes, in order
  1. Order to gateway
  2. Gateway payout to bank
  3. Gateway batch to bank by total
  4. Bank to ledger
  5. Bank to ledger by amount and date
ChecksDuplicate orders · Gateway and bank totals · Open items by age

Payment gateway settlements

Orders against the gateway's settlement report, then each settlement batch against the bank credit. Gateway fees make the bank amount smaller, so amounts agree within a percentage.

Sides3 — Orders · Gateway settlement report · Bank statement
FieldsDate · Order or payment ID · Settlement batch · Amount · Fee
Matching passes, in order
  1. Order to gateway payment
  2. Settlement batch to bank credit
  3. Batch total by date
ChecksOrders paid twice · Fees above 3% · Open items by age

Payroll against salary payments

The payroll register's net pay per employee against the salary payments from the bank, by employee and amount, with totals compared for the month.

Sides2 — Payroll register · Salary payments
FieldsPay date · Employee code · Employee name · Bank account · Net pay
Matching passes, in order
  1. Employee code and net pay
  2. Bank account and net pay
  3. Name and net pay
ChecksPaid twice · Total net pay agrees · Employees without a bank account

Stock records against physical count

The stock ledger's quantities per item and location against a physical count or warehouse system. Several ledger lines per item roll up before matching; quantities may differ within a tolerance.

Sides2 — Stock ledger · Physical count
FieldsItem code · Location · Item · Quantity · Value
Matching passes, in order
  1. Item and quantity
  2. Item, quantity differs
ChecksCounted items have a code · Negative stock · Total units agree

Sub-ledger against general ledger

Each sub-ledger (receivables, payables, fixed assets, inventory) totalled per control account against the general ledger balance of that account.

Sides2 — Sub-ledger · General ledger balances
FieldsControl account · Account name · Amount
Matching passes, in order
  1. Account balance agrees
  2. Account balance differs
ChecksAccounts present · Totals agree

TDS: Form 26AS against books

Tax deducted by customers as Form 26AS shows it, against the TDS receivable in your books, per deductor (TAN) and quarter. Credit missing from 26AS is at risk.

Sides2 — Form 26AS · TDS receivable in books
FieldsDate of deduction · Deductor TAN · Deductor · Reference · Section · TDS amount
Matching passes, in order
  1. TAN, amount and date
  2. Several deductions, one entry
  3. Deductor name and amount
ChecksTAN present · Credit per deductor · Totals agree
Reason codesDeducted but not in Form 26AS

Three-way match (PO, goods receipt, invoice)

Every purchase order line is received and invoiced: quantity received against quantity ordered, invoice against receipt, within tolerance. A line missing from any of the three stays open.

Sides3 — Purchase orders · Goods receipts · Invoices
FieldsPO number · Item · Date · Supplier · Quantity · Value
Matching passes, in order
  1. PO to receipts
  2. PO to receipt, quantity differs
  3. Receipt to invoice
ChecksPO lines present · Duplicate invoices · Open lines by age

Trades: front office and back office

Trades booked in the front office against the back office or custodian: trade by trade on ID with security, quantity, price, settlement date and counterparty compared, then positions per security and account.

Sides2 — Front office · Back office
FieldsTrade ID · Trade date · Settlement date · Security (ISIN) · Account · Counterparty · Quantity · Price · Consideration
Matching passes, in order
  1. Trade ID
  2. Security, account, quantity and trade date
  3. Position per security and account
ChecksTrade details present · Duplicate trade IDs · Quantity totals

Vendor statement reconciliation

A supplier's statement against your purchase ledger. Invoices and credit notes by document number, one payment against several invoices, and balances per supplier.

Sides2 — Vendor statement · Purchase ledger
FieldsDocument date · Document number · Supplier · Document type · Amount
Matching passes, in order
  1. Document number and amount
  2. Payment against several invoices
  3. Several entries against one
  4. Amount and date, same supplier
ChecksDocument numbers present · Duplicate documents in the ledger · Balance per supplier · Open items by age