Reconciliation eats your controller’s month
Bank feeds, processor batches, and AR applications are three jobs pretending to be one close.
Bookkeeping and reporting · coming Q2 2027
Lender-ready books every month. On the software you already use.
Close on time. Hand a lender a pack they can read. Track covenants before they breach. The extraction layer is automated; a named practitioner reviews exceptions and signs every client-facing pack.
Coming Q2 2027
The problem
Your books are accurate. They’re just not persuasive.
Your statements aren’t structured the way a lender reads them
Accurate books that still require a reconstruction before a credit memo are not lender-ready.
You find out about a covenant breach after it happens
A monthly pack that does not track covenants is a surprise generator.
Automated reconciliation
Ingest. Match. Triage. Review. Report.
Infrastructure, not a product pitch. The model extracts and scores. A person decides.
01 — Ingest
Bank feeds · card settlement files · AP invoices · AR aging · payment processor statements
02 — Match
Multi-signal matching on amount, date proximity, reference strings, counterparty history, and historical coding patterns. Confidence-scored.
03 — Triage
High confidence → auto-posted. Low confidence → human exception queue. Nothing is posted silently that the model wasn’t sure about.
High confidence → auto-postedLow confidence → human exception queue04 — Review
Every exception reviewed by a human. Every client-facing deliverable signed off by a named practitioner.
05 — Report
Lender-ready monthly package · 13-week rolling cash forecast · covenant status · DSO and AR aging trend · debt schedule
The human boundary
The model extracts. A person decides.
| What the extraction layer does | What a person always does |
|---|---|
| Extracts and classifies documents | Judges whether a treatment is correct |
| Matches transactions and scores confidence | Reviews and clears every exception |
| Surfaces anomalies and exceptions | Signs off on every client-facing deliverable |
| Drafts recurring narrative and commentary | Owns the relationship and the monthly review |
| Tracks covenants and flags approaching breaches | Decides what to do about them |
Adverse-action reasoning obligations exist under lending and privacy regulation on both sides of the border. Automated systems that make credit-relevant determinations without explainable human review create real exposure — for us and for you. So we don’t build it that way.
QuickBooks reconciliation automation
We read your ledger. We do not replace it.
Two-way sync. No data migration. No change to the existing close workflow.
- QuickBooks Online
- QuickBooks Desktop
- Xero
- Sage 50
- Sage Intacct
- NetSuite
- Dynamics 365 Business Central
- Acumatica
- Epicor
Outsourced controller
Three layers. Pricing when it’s live.
Books
Coming soonReconciliation, monthly close, AR/AP management, monthly reporting pack.
Reporting
Coming soonAdds 13-week cash forecast, covenant tracking, DSO analytics, lender package.
Controller
Coming soonAdds quarterly review, capital planning, refinance trigger monitoring, named practitioner.
Who this is not for
- Firms that want a fully automated close with no named reviewer
- Firms looking to replace their general ledger
Security
Data residency, named accountability.
- Data residency for client files.
- Transfer disclosure as required.
- Named-practitioner accountability on every client-facing pack.
- Zone-based access control.
- SOC 2 alignment roadmap — published, not implied.
When is this available?
Coming Q2 2027. Early access members get founding pricing and onboarding priority.
Do you replace QuickBooks or Sage?
No. We read the accounting software you already use. Two-way sync. No data migration.
What is the human boundary?
The model extracts and scores. A named practitioner reviews exceptions and signs every client-facing pack. Nothing is posted silently that the model was not sure about.
What is in the monthly pack?
Lender-ready reporting, a 13-week cash forecast, covenant status, DSO and AR aging trend, and the debt schedule — depending on tier.
Where does data live?
Data residency for client files. Transfer disclosure as required. SOC 2 alignment is a published roadmap, not a claim of certification.
Who is this not for?
Firms that want a fully automated close with no named reviewer, and firms looking to replace their general ledger.
How is pricing shown?
Tiers are listed. Numbers wait until the product is live. No fake ‘from $X’ on a coming-soon page.
Is this live on payments or capital files today?
No. Payments and capital run without it. Bookkeeping is a separate layer, later.