Set the method once
Coding rules, close steps, and approval thresholds - Spark learns how your firm works and applies it consistently, engagement after engagement.
For accounting firms
Spark prepares client close work the way your firm does it - drafts in Xero, workpapers with the formulas shown, and an audit trail your due-diligence team will actually like.
Now onboarding pilot practices.
We are building the multi-client tooling with a small group of firms. Bring one client's close; we run it approval-first, end to end, and shape the firm workflow around how your team actually works.
Draft bills and journals
ReadyClose workpapers
ReadyNamed approvals
1 waitingReview trail
ReadyCoding rules, close steps, and approval thresholds - Spark learns how your firm works and applies it consistently, engagement after engagement.
Bills, journals, and workpapers arrive as drafts with the working attached. Your staff approve in Slack; nothing posts without a named sign-off.
Who asked, who approved, what changed - recorded on every action, for every client. Due diligence stops being an archaeology project.
Built with pilot firms
These are in active development - pilot practices get them first and decide how they work.
A channel per client, bound to that client's Xero org
In developmentAutomated missing-document chasing
In developmentA firm console: close status across every client at a glance
In developmentFAQ
How Spark supports client context, repeatable workflows, and visible review.
Yes. Spark is designed around repeatable firm methods: coding rules, close steps, document requests, and approval thresholds can be rolled out consistently.
Each client engagement keeps its own Xero connection, approvals, and audit trail. Channel-per-client context is rolling out with our pilot firms.
Automated client chasing is in development with pilot firms. Today Spark prepares the work, shows what is missing from the ledger, and keeps the review trail current - the chasing stays with your team for now.