Playbook
Board pack and MIS: from six days of copy-paste to a draft you can trace.
The board pack is assembled by pulling numbers from several systems into slides and spreadsheets by hand. Every late change means doing it again.
The problem
Numbers are copied from the core, GL, recon sheets and other systems into a template. Nobody can say quickly where a figure came from, and a change to one source means re-checking the whole pack.
The playbook
- List every number in the pack and the system and query it comes from.
- Reconcile the sources first; a pack built on unreconciled data repeats the breaks.
- Define each metric once, with its query, and reuse it in MIS and the board pack.
- Draft the pack from those queries, so every number links to its source.
- Highlight what changed since the last pack, for reviewers.
- Have a maker prepare and a checker sign off before it goes out.
- Keep the same record for regulatory returns, so numbers agree across documents.
Review checklist
- Totals tie back to the GL.
- Period and cut-off are the same everywhere.
- Every number has a source query.
- Changes since last pack are explained.
- Commentary agrees with the numbers.
Confirm the content and format required by your board and regulators with your company secretary and auditor. Daily reconciliation underneath the pack is covered in reconciliation break management.
How AutoRecon does it
AutoRecon is built for finance, operations and treasury teams at banks, NBFCs and payment companies. Switch, network, core, GL, bank and MT950 statements and ERP files are loaded as they land and mapped to one schema, with bad rows rejected and the reason given. UPI and IMPS, cards, NEFT/RTGS, nostro and vendor recons are matched daily on rules you write: exact, tolerance and fuzzy narration matching. Each break is classified, aged and given an owner; recurring breaks become a suggested rule, which takes effect only after maker-checker. The daily close is approved by maker and checker, and MIS, board packs and regulatory returns are drafted with every number traced to the query that produced it. It is read-only by default and writes nothing to your core unless you open the path.
Questions
How can board pack preparation be made faster?
Reconcile sources first, define each metric once with its query, draft the pack from those queries so every number is traced, and highlight changes since the last pack for the checker.
Why should every MIS number be traced to a query?
So reviewers can check any figure quickly and a source change updates the pack without re-checking everything by hand.
See it on your own data. AutoRecon — Close the day before it starts. Book a 30-minute working session with an engineer.