Work and close management for accounting teams
Tied out. Signed off.
RECON turns the month-end close, the recurring bookkeeping around it and the evidence behind it into one system of work. Checklists on business-day offsets, reconciliations that tie to the ledger, workpapers filed as audit evidence, and a sign-off that explains itself.
Built by accountants who close the books for nine entities every month. Now opening to other teams.
Current close
October 2026
Today
BD2
Target
BD9
Projected
BD11
| Entity | Progress | Verdict |
|---|---|---|
NWH Northwind Holdings 18 of 42 6 with reviewer 1 flagged | On track | |
ATL Atlas Logistics 12 of 36 4 with reviewer 2 flagged | On track | |
HBF Harbor Foods 9 of 28 2 with reviewer | On track | |
MER Meridian Services 8 of 19 3 with reviewer | On track |
The close dashboard, shown with example entities as close week advances.
What the name stands for
Review, Execute, Close, Organize, Note.
Why RECON
From spreadsheets and chat threads to one system of work.
Close week runs on questions. RECON answers them before anyone has to ask, because the checklist, the evidence and the sign-off live in the same place.
Close week today
- Which copy of the close checklist is the current one?
- Was the operating cash reconciliation reviewed, and by whom?
- Where is September's prepaid amortization workpaper?
- Who is overloaded on business day 3, and who is free?
- Did the balance we reconciled to match what the ledger says today?
- What did we send the auditors last year, and what did they ask for?
Features
Everything the close needs, nothing it does not.
RECON replaces the checklist spreadsheet, the shared drive and the status thread. It does not try to replace the ledger.
Close checklists on business days
Templates set due dates as BD+N from period end, with lead days, review offsets and a holiday calendar management controls. Generate once and every entity gets its checklist, dependencies included.
One review queue
Reviewers see every item waiting on them across all entities, sorted by their own due date, with the evidence in a side panel and Sign and Return pinned at the bottom. Keyboard-fast on a desk, usable on a phone.
A sign-off that explains itself
One to three levels per template or item. When signing is not allowed, the button lists what is unmet: a missing workpaper, an open prerequisite, a tie-out over threshold. No self-review; every override is logged with a reason.
Reconciliations that tie out
Ledger balance against reconciled balance, reconciling items with an owner and an explanation, per-account thresholds and aging. Balances arrive nightly from Sage Intacct and QuickBooks Online, with a staleness badge when they do not.
Workpapers kept as evidence
Files are stored under one folder convention by entity, fiscal year, period and category, with a SHA-256 checksum verified on upload. Nothing is deleted: a final file is superseded with a reason, and locked periods stay locked.
Close, lock, certify
Each entity's period moves from open to closing to closed to locked. Closing stores a sign-off register and a close certificate as workpapers; a retrospective shows what ran late and why.
Time and workload
A stopwatch or a manual entry on every item, planned against actual. Workload spreads remaining estimates over business days per person, with absences, capacity and reassignment from one grid.
Notifications that stay quiet
One morning email per person, skipped when empty and never on a weekend. Immediate email only for ready for review, returned, redo and mentions. Every message links to the item.
Auditors and the CFO, scoped
Invite external people with a role, an entity, a period range and a last day of access. They see only what the grant covers, sign in with two-step verification, and raise audit queries and PBC requests inside the system.
Dashboards and reporting
A current close card per entity with pace, projected finish and flags; a month-over-month flux report; saved views and CSV exports of every list; an activity report of what external users opened.
Works with
- Sage Intacct
- QuickBooks Online
- Microsoft Entra ID
- n8n
- Cloudflare R2
- Neon Postgres
Read-only ERP access: RECON reads charts of accounts and balances and never posts a journal entry.
Review
One queue, every entity, sorted by your due date.
A reviewer with thirty items in close week does not open each one. Every row carries who prepared it, how long it has waited, the tie-out and the evidence, so the decision happens in the list.
- Sign and Return pinned at the bottom; j, k, s and r on the keyboard.
- The evidence in a side panel: figures, workpapers, the prior occurrence, open notes.
- Works at phone width for the CFO between meetings.
Review queue
4 waiting on you · sorted by your due date
j k move · s sign · r return
- NWH
Operating cash reconciliation — October
Prepared by M. Alvarez · waiting 1 business day · 2
In review - ATL
Prepaid amortization — October
Prepared by J. Okafor · waiting 2 business days · 1
Due soonIn review - HBF
Payroll accrual — October
Prepared by S. Lindqvist · waiting 3 business days · 3
OverdueIn review - MER
Intercompany balances — October
Prepared by M. Alvarez · waiting Today · 1
In review
Sign-off
The sign button explains itself.
When sign-off is not allowed, RECON lists the unmet conditions instead of greying out a button. The rules the screen shows are the same rules the server enforces.
- Required workpaper, open prerequisite, tie-out over threshold, open review note.
- No self-review. Levels are assigned; nobody signs on someone else's behalf.
- An administrator's override needs a reason and lands on the Overrides report.
Northwind Holdings · 2026-10 · Reconciliations
Operating cash reconciliation — October
Level 1 · Preparer
- No workpaper attached; this item requires one.
- Tie-out difference 1,250.00 is over the 500.00 threshold.
- Prerequisite open: Bank statement import, October.
3 conditions unmet.
Evidence
Workpapers that survive the audit.
Every file is stored under one folder convention with a checksum verified on upload. Final files are superseded, never deleted, and closed periods lock.
- entities / entity / fiscal year / period / category, built by one function.
- Versions chained; a replaced final file keeps its reason and the old copy.
- The sign-off register and the close certificate are stored as workpapers at close.
Workpapers
entities / entity / fiscal year / period / category
- entities
- NWH
- 2026
- 2026-09Locked
- 2026-10
- reconciliations
- operating-cash-reconciliation-2026-10.pdfv2 · final
- operating-cash-reconciliation-2026-10.pdfv1 · superseded
- bank-statement-operating-2026-10.pdflinked to 3 items
- general
- close-register-2026-10.csvstored at close
- close-certificate-2026-10.pdfstored at close
How it works
A close week, start to finish.
Four moves. The first happens once; the other three happen every month, with less to remember each time.
01
Before the first close
Set up the entities and the templates
Add each legal entity with its ERP, fiscal year and close target. Build templates once: due date as BD+N, lead days, sign-off levels, the preparer and reviewer per entity, the GL account and threshold. Mark the holidays.
02
Nightly, automatically
Generate the close
RECON materializes one checklist per entity and period, dated on business days, with cross-entity dependencies resolved. Recurring bookkeeping outside the close is generated the same way, daily, weekly, monthly or on a custom rule.
03
BD1 to BD9
Prepare, review, sign
Preparers work from a dashboard of what is due, track time, attach workpapers, key the tie-out and flag blockers. Reviewers work the queue. Comments with mentions and an append-only timeline keep the conversation on the item.
04
Close day and after
Close, lock, certify
When every item is signed, close the period: the sign-off register and the close certificate are stored as evidence. Lock it when the auditors are done. Reopen a single item with a reason if you must.
Who it's for
Built for the people who close the books, and the people who check them.
Four roles, one system. Each person sees the work that is theirs, and only the entities they were given.
Staff accountants
Open the day with what is due, in order. Time, workpapers and the tie-out live on the item, so nothing is retyped into a tracker.
Controllers and accounting managers
Own the templates, the assignments and the calendar. See each entity's close against its target, who is behind, and who has room.
Fractional CFOs
Review and sign level 2 from a phone between meetings, with the evidence in the panel and the prior month one tap away.
Auditors and tax preparers
Read the checklist, the sign-off history and the workpapers for the entities and periods you were granted, and raise requests where the team will see them.
Controls
Built to be read as evidence.
Auditors read the system state, not a memo about it. RECON is designed so that what it shows is what happened.
One instance per customer
Your data, your database, your file store. No shared tenant.
Single sign-on for employees
Microsoft Entra ID, limited to your tenant and your email domains.
Two-step verification for everyone else
External users are invited, use an authenticator app, and get 8-hour sessions.
Append-only history
Sign-offs, overrides, comments and access changes are recorded, never rewritten.
Immutable workpapers
Checksummed on upload and held under object lock; a change is a new version with a reason.
Read-only ERP access
Balances and accounts are read through your own integration credentials. RECON never writes to the ledger.
Waitlist
Close your next month in RECON.
RECON runs today for the accounting team it was built for. We are opening it to a small number of teams next, one instance each, and setting up each one with you.