BAS Digital
BAS Digital product · accounting discipline

Checklists and reconciliations

Accounting reliability isn't a one-off cleanup — it's daily checkmarks. A checklist records what was checked, by whom, and with what result — for every day, week, and month. Pilots check the plane against a checklist before every flight, not 'when there's time'.

The question that catches most companies: 'for the Tuesday two weeks ago, are all operations in the system — yes or no?' Without a checklist, the answer doesn't exist. With one, it's a single cell.

The daily checklist: each role sees its own

The conductor, the assistant, and the manager each have their own checks. A summary sheet rolls everything into one row per day: a green row = the day is closed.

'Day close' checklist — summary sheet (excerpt)
DateBank: operations in the systemBank: postedCash desk: operations enteredDocuments attachedOrders enteredCustomer payments matched
Mon 16.02
Tue 17.02
Wed 18.02

A red cell is visible immediately — and gets fixed on Wednesday instead of surfacing at the month close. Each column is assigned to a specific role.

The reconciliation checklist: a report is confirmed, not just sent

Key reports get their own checklist with indicators. An example — the weekly balance reconciliation: the balance in the system versus the actual for every account and every cash desk.

'Cash balances' checklist — cash desk reconciliation (excerpt)
DateStore cash desk: actualStore cash desk: in the systemAssistant's cash desk: actualAssistant's cash desk: in the systemResult
22.0523 43423 43430 00030 000matches
23.053 4413 43457 00057 000off by 7

A 7-crown discrepancy — trivial? For the amount, yes; for the system, no: a seven found on Friday is control that wasn't lost. Unnoticed small discrepancies are how trust in the books dies.

1 · The report is correctAll accounts and cash desks reconciled, no discrepancies — the report is confirmed and goes out on time.
2 · Correct with caveatsThere are agreed deviations — the report goes out with a comment on each one.
3 · Not confirmedThe discrepancy needs time — the report is not sent 'as is': you get a notification with the reason and a deadline.

The three scenarios rule out the worst case — 'a beautiful report you can't trust'.

Three rhythms — three checklists

Daily
Day closeoperations entered and posted, documents attached — by role, 5 minutes per person
Weekly
Week closebalance reconciliation with the bank and cash desks, settlements, payment calendar update
Monthly
Month closethe full trusted-close checklist: suspense = 0, accruals, depreciation, P&L/cash flow/balance sheet reconciled

What it gives you

Errors are caught the day they appear — the cost of fixing is minimal, and history isn't rewritten retroactively.
The month close is a process, not a feat. When 30 days are ticked off, the month closes in days, with no fire drills.
You can see who keeps the discipline. A checklist by role is an honest picture of execution for the owner and for us.
Reports get a 'quality mark': confirmed / with caveats / not confirmed — you always know the status of the numbers.
Honestly: what checklists do not do.
  • They don't fill themselves in — for the first weeks we check daily, until the habit becomes the team's routine.
  • They don't catch what isn't in them — new operation types are added to the checklist as they appear (it's a living document).
  • They don't replace people — a 'reconciled' checkmark is worth exactly as much as the honesty of whoever set it; that's why we duplicate the key reconciliations ourselves.

Checklists are tailored to your operations during implementation

The set of checks comes not from a template but from your transaction map: whatever operations you have, that's what we check. From the third month your team works by them, and we oversee the reconciliations.

Discuss implementation →
How we work