Checklists and reconciliations
Reliable accounting is not a one-off clean-up but daily tick marks. The checklist records what was checked, by whom and with what result — for every day, week and month. Pilots check the aircraft by checklist before every flight, not “when there's time”.
Discuss implementationDaily checklist: each role sees its own
The bookkeeper, the assistant and the manager each have their own checks. A summary sheet gathers everything into one row per day: a row with no gaps — the day is closed. A gap is visible at once — and fixed on Wednesday, rather than surfacing at month-end close.
Reconciliation checklist: the report is confirmed, not just sent
Key reports have their own checklist with indicators. Example — the weekly balance reconciliation: system balance against the actual for every account and every cash desk. A 7 CZK discrepancy is trivial for the amount but not for the system: unnoticed small discrepancies are how trust in the accounts dies.
Three reconciliation outcomes
Three scenarios rule out the worst case — “a nice-looking report you can't trust”.
Three rhythms — three checklists
What you get
Honestly: what it does not do
Checklists are tailored to your transactions during implementation
The set of checks comes not from a template but from your transaction map: whatever transactions you have, that’s what we check. From the third month your team works with them, and we oversee the reconciliations.
Discuss implementation