For accounting firms
For a practice the hard part is never the first upload. It is the missing March statement, the transfer nobody can explain, and the export you have to stand behind. The Team area holds a tool for each.
Workspace, roles and client isolation
- A firm works in one workspace. Members are invited by email; invitations expire after 72 hours.
- Roles are Owner, Admin, Preparer, Reviewer and Viewer, each with a fixed set of capabilities (upload, edit, delete, export, approve, billing).
- Every client is a client workspace (an account holder). Client access is granted per person, and every query a person makes is scoped to the clients they may see.
- The page allowance is pooled across the workspace, with a usage policy the owner controls.
Coverage tracker
Team → Completeness. For each client and bank account, which months of the reporting period are received, partial, missing or awaiting review, and where statements overlap. One click turns the gaps into document requests pre-filled with the account and period.
Client upload portal
Team → Document requests. A document request emails the client a link. They upload from it without creating an account; the files land in that client's workspace and start processing at once. Reminders go out daily until the request is complete. The link is a one-off token — nothing about it is stored in readable form.
Questions to clients
From any transaction row, ask the client a question. It reaches them through the same portal; they answer and can attach evidence. Your decision on the answer is recorded against the row, and a confirmed category can become a client rule so it applies on every future statement.
Review queue and readiness
Review. Every blocker in one list, per client and per assignment:
| Exception | Meaning |
|---|---|
| Balance mismatch | the statement does not reconcile — see Reconciliation & review |
| Possible duplicate | rows that already exist elsewhere |
| Unmatched transfer | a proposed transfer match awaiting confirm / reject |
| Unassigned account or client | a statement not yet linked to an account or client |
| Uncertain date | a date that could not be read unambiguously |
| Missing statement | a gap found by the coverage tracker |
| Uncategorised | rows with no category |
| Ledger discrepancy | a difference found by the bank-versus-books diff |
An assignment is ready to approve when nothing is open. Each approval fingerprints the data it approved and starts a new version; exports are idempotent, so the same version cannot be delivered twice by accident.
Bank versus books
Ledger. Import the client's ledger as a CSV — the parser tolerates different delimiters, column orders and date formats — and see, per bank account, which bank rows match, differ in amount or date, exist only in the bank or only in the ledger. Match or unmatch rows by hand; unresolved differences appear in the review queue.
Handover pack
Team → Assignments. One PDF or Excel file per assignment: clean transactions, coverage, opening and closing balances, reconciliation results, confirmed transfers, open questions and the version and export history. Unresolved items are listed on the cover, never hidden, and the pack says plainly that it is not an audit opinion.
Pushing to each client's books
Team → Integrations. Map each client to its own connection in QuickBooks Online, Xero or another supported package, then preview before you push: what is already synced, what is new, what still needs an account mapping and what is waiting on a transfer decision. See Integrations, open banking & API for which connectors are available.