Meridian Finance Group is a mid-size financial services firm with formal monthly close procedures and VAT reporting obligations. Claire Bennett, Senior Reconciliation Analyst, owns the full close cycle — bank data, discrepancy classification, VAT adjustments, excluded-transaction documentation, and the verified summary to finance leadership. Errors here — a miscoded discrepancy, an untraceable excluded transaction — surface as audit findings weeks later.
The reconciliation package lived in institutional memory, not documents
Five distinct artifacts were needed to run the close cycle: a standalone monthly reference guide, a bank reconciliation template, a VAT reconciliation reference, a justification log template, and a summary email template. None existed in a consistent, usable form.
Prior attempts had produced partial workbooks. But discrepancy reason codes in the justification log did not match categories in the reconciliation template. The VAT reference used different column-naming conventions than the main bank template. Inconsistencies created friction in sign-off workflows and made cross-period comparisons unreliable.
Three pressures converged: a new team member had spent two slow close cycles learning sequencing decisions that should have been documented; an external audit review was approaching and the disconnected templates were not presentable; and growing VAT complexity had made the informal reconciliation approach unworkable.
Energent.ai built the full package from a single shared data model
Rather than drafting five documents sequentially, the agent maintained the complete reconciliation workflow in context and produced all deliverables in parallel:
- Scoped the full deliverable set before writing any single file, establishing shared taxonomy — reason codes, column labels, sign-off steps — for every downstream artifact
- Carried discrepancy reason classes from the reference guide into the justification log template and the dashboard without a manual reconciliation step between files
- Generated an HTML dashboard directly from the same structured data model — four views: workflow risk and control checkpoint status, discrepancy reason-class comparison, excluded-transactions roll-forward, and summary-email verification checklist
- Ran an independent verification pass across all five markdown files and the dashboard, identified one gap, and resolved it before delivery
No manual cross-file consistency check. No separate dashboard build. No verbal sign-off on terminology.
Consistent logic across all artifacts, not just cleaner formatting
- Shared data model as the source of truth — reason codes, column labels, and sign-off steps were defined once and propagated to all five deliverables and the dashboard simultaneously.
- Parallel production, not sequential drafting — written deliverables and visualization ran as concurrent tracks, preserving the internal consistency that sequential drafting routinely breaks.
- Independent verification before delivery — a deliberate stage checked gaps between the reference guide and templates, terminology inconsistencies, and missing sign-off steps across the full package.
- Immediately deployable outputs — the justification log template, with pre-populated reason classes, was pulled directly into the next month-end close without modification.
Five-file backlog resolved in one session
- Five reusable deliverables produced in a single session, each consistent with the others and ready for the next month-end close.
- One HTML dashboard covering all four control-checkpoint views, requiring no additional tooling to deploy.
- One gap caught and resolved during the independent verification pass before the analyst reviewed the final output.
- Onboarding reference complete — structured documentation for traps, trade-offs, and sequencing gave the new team member a walkthrough for the first solo close cycle.
"The VAT reconciliation reference gave us the first structured view of VAT control checkpoints we'd ever operated with. The justification log went straight into the next close package without a single edit. We finally have a process that lives in documents, not someone's head." — Claire Bennett, Senior Reconciliation Analyst at Meridian Finance Group