Questions firms ask before a pilot

No — reconciliation is one step of the close, and BreakZero covers the mechanical layer of all of it: pulling the data, matching every transaction, flagging each exception with the correction it implies, building the certified tie-out, assembling the close package, and tracking every client's close to done. What it deliberately doesn't take from you is judgment — accrual estimates, revenue-recognition calls, and final sign-off stay with your team, who now start them days earlier because the ticking and tying is already finished.

Any data source on the books side: QuickBooks Online and Xero connect in one click; SAP and Microsoft Dynamics via OData; SQL databases; Stripe; SFTP statement drops; and CSV exports from anything else; bank and credit-card activity by live bank feed (Plaid), statement exports (CSV/OFX), or SFTP statement delivery. If it can produce an export or a read-only connection, we can reconcile it — unusual formats are exactly the kind of thing we tailor during setup.

Access is read-only — BreakZero can never move money or write to your books. You can deploy it in your own environment so client data never leaves your infrastructure, or in ours. The live demo runs entirely in your browser — nothing is sent to us, and your free close verification runs on an anonymized export. Each client on the cloud platform lives in its own tenant behind database row-level security — one organization can never read another's data — with connector credentials encrypted at rest.

Your first client is usually reconciling within days. Rolling out across your full book — with match rules and reports tuned to how you work — takes weeks, not months.

Yes — every reconciliation produces a tie-out schedule: bank activity against the books, with each reconciling item listed and signed so the variance bridges to zero. Every close exports its package from the platform in one click — summary, certified tie-out schedule, exception detail with resolutions, and the close checklist, as an Excel workbook for your workpapers ( see the matching in the live demo ), and we tailor the format to your reporting package or your auditors' requests.

Keep using them — modern ERPs and ledgers are genuinely good at matching transactions, and we're not here to replace them. What they can't do is verify the close: catch a plugged reconciliation, a transaction deleted and re-fed, a rec quietly gone stale on one entity out of forty — or hand you a tie-out with the dollars at stake. Your systems match transactions. Nobody verifies the close. That's the job BreakZero does. On the platform, that proof is structural: the landing layer is append-only — nothing lands twice or disappears quietly — every action sits on an immutable audit log, and a close can only be certified when its exceptions are cleared, by someone other than the person who worked them (segregation of duties, stamped on the record).

No — and you can keep them. Those tools tell you what's wrong: a flag list your team still has to work through. BreakZero is the layer that makes the list disappear — we run the reconciliation, resolve the exceptions with you, and deliver the finished, evidenced tie-out. They flag; we resolve.

Yes — the platform has real accounts with roles: admins manage sources and people, preparers work the exception list on the client books they're scoped to, reviewers certify closes, and viewers get read-only dashboards. Access is enforced server-side per book, disabling someone kills their sessions instantly, and every sign-in and permission change lands on the audit log.

Isolation is structural, not policy: every record carries its organization, and the database itself enforces row-level security — a request scoped to one tenant physically cannot return another tenant's rows, even if application code had a bug. Book-level scoping inside a firm works the same way.

Reconciliation runs $40–75 per client book per month ($750/month minimum), starting with a paid pilot on a handful of clients — full pricing is published here. Founding clients get preferred pricing that stays with them. The first close verification is free either way.

Almost every firm's is, which is why customization is part of the service rather than an add-on. Match rules, materiality thresholds, exception categories, report formats, delivery — all fitted to your workflow during setup, and adjusted as your clients change.

Our core is the reconciliation and tie-out layer — making the numbers trustworthy. Once your clients' closes tie out every month, that same reconciled data can power tailored reporting: year-over-year comparisons, variance analysis, KPI packs, formatted to your firm's package. We build that as an add-on engagement for clients on the platform — and for multi-location groups it scales up to a full operator analytics suite (see the live demo) with data consolidation and verified migrations above it. (We deliberately don't do forecasting or projections — plenty of good tools exist for that; our job is making sure the actuals they start from are right.)

That's our flagship engagement. Every acquisition lands the same way: capture everything the target runs immutably, conform their accounts to your reporting lines, reconcile their history, and cut over to your stack with a tie-out proving completeness — opening balances equal closing balances to the penny, with lineage from new system back to old. The full playbook is here, and for groups that acquire on a rhythm, it repeats per deal.

Then your close is clean, and the free verification cost you nothing but the export. That's a good result — and you'll know it to the penny rather than assuming it.