Platform admin
Build and assign the operation
Create staff and client accounts, create companies, assign one bookkeeper and one QC reviewer, monitor workload, configure report access, and reopen a locked period with a required reason.
White-label bookkeeping operations
Give clients a focused portal while admins, bookkeepers, and QC reviewers move every month from source documents to approved, locked reports.
One platform, your front door
Each white-label partner is designed around a branded tenant address. Your end users see your identity, your portal navigation, and the reports and actions you make available.
Subdomain, tenant routing, TLS, and brand configuration are completed during launch. The current demonstration portal still uses the Bookkeeping Puppy label.
Clear responsibility at every step
The platform uses distinct permissions so preparing the books and approving the books are not treated as the same job.
Platform admin
Create staff and client accounts, create companies, assign one bookkeeper and one QC reviewer, monitor workload, configure report access, and reopen a locked period with a required reason.
Bookkeeper
Import statement rows, review duplicates, categorize and post transactions, collect documents, resolve client questions, reconcile accounts, complete FX work, and submit the month to QC.
QC reviewer
Work from an assigned QC queue, inspect reports and transactions, fix items during review, confirm the required checklist, then approve and lock the month.
Client
Upload documents, answer bookkeeping questions, and view company reports only after the relevant months have passed QC and are locked without an active re-QC flag.
The full monthly system
Every stage has an owner, a visible status, and a rule for moving forward. The month cannot reach the client simply because someone says it is done.
Set the accounting basis, base currency, bookkeeping start date, standard chart of accounts, users, and staff assignments.
Receive statements, receipts, invoices, and supporting documents through controlled company access.
Map a bank CSV, preview rows, reuse saved formats, detect repeated files and possible duplicate rows, then place every row into a review queue.
Turn each staged row into a balanced double-entry transaction. Attach evidence and keep uncategorized items visible until resolved.
Ask transaction-specific questions, exchange supporting documents, and clear the waiting-for-client work before submission.
Reconcile every active bank account to an exact zero difference, confirm FX rates, clear all staged rows, remove uncategorized activity, close questions, and verify the trial balance.
The platform blocks submission until every accounting and workflow readiness check passes, then moves the month into the assigned QC queue.
Inspect reports and transactions, correct issues inside the active review, confirm the seven-point QC checklist, and lock the approved month.
Clients see approved reports. If an admin reopens an earlier month, a reason is recorded and every later locked month is flagged for re-QC.
Human-controlled AI intake
The current platform already supports mapped CSV imports, saved formats, duplicate controls, previews, and staged row-by-row review. The planned AI layer extends that intake to PDF and image statements without bypassing the approval queue.
Bookkeeper workspace
Bookkeepers work only on assigned companies. The workflow connects bank imports, double-entry transactions, documents, client questions, A/R and A/P, multi-currency activity, reconciliation, and the final submission gate.
Independent quality control
The assigned reviewer claims the submitted month, reviews its transactions and reports, makes controlled fixes, and must confirm every checklist item before approval can lock the period.
✓ All bank accounts imported
✓ All transactions categorized
✓ All exchange rates entered
✓ No unanswered client questions
✓ Bank accounts reconciled
✓ Debit equals credit
✓ Balance Sheet balances
Branded client experience
End users enter through your branded tenant address. They can upload supporting documents, answer bookkeeping questions, and view reports for periods that have been approved, locked, and cleared for release.
Controls beneath the workflow
The system is designed for accountable bookkeeping operations, not a shared spreadsheet with a new logo.
Staff only access companies assigned to their role. Clients receive explicit read access to individual companies.
Approved months become immutable. Only an admin can reopen one, and a reason is required.
Reopening an earlier period flags every later locked month so downstream reports cannot silently stay approved.
Logins, workflow transitions, document events, accounting changes, approvals, locks, and reopen reasons are recorded.
API access included
The commercial model includes API access. The endpoint contract, allowed actions, tenant boundaries, and integration scope are finalized during launch planning.
{
"tenant": "yourcompany",
"company": "client-1042",
"period": "2026-05",
"status": "ready_for_qc",
"bookkeeper": "complete",
"qc": "pending",
"client_reports": "locked"
}Simple platform pricing
One predictable user price for the branded bookkeeping platform. Shape your own client offer around the service, reporting, and support you provide.
A repeatable white-label model
Each partner receives an intentionally scoped tenant, brand, access model, workflow, and integration plan.
Confirm your partner key, branded subdomain, identity, users, client offer, and support destination.
Map admins, bookkeepers, QC reviewers, clients, assignments, report permissions, and escalation rules.
Finalize the API contract and any AI statement-extraction provider, confidence rules, data handling, and approval boundary.
Set branding and routing, test role isolation and the complete monthly workflow, then invite users at $10 each per month.
Straight answers
The platform is working bookkeeping software. Tenant routing, API endpoints, and AI intake are deployment layers that must be scoped honestly.
The intended model is yourcompany.genericdomain.com. The tenant hostname, TLS, and brand resolution are configured during launch; they are not active on the current Evo marketing host.
An admin creates user accounts with explicit roles, creates the company, then assigns an active bookkeeper and an active QC reviewer to that company. Staff access is limited to companies assigned to their own role.
No. A bookkeeper prepares the month and submits it only after readiness passes. An assigned QC user claims the review, completes the required checklist, and performs the approval and lock.
Not yet. The live intake workflow uses mapped CSV files, duplicate checks, previews, staged rows, and human posting. PDF/image AI extraction is a planned launch integration that must preserve the same human approval boundary.
Only after every month in the selected range is approved and locked with no active re-QC flag. Core reports are available by default; additional operational reports can be enabled for each customer access record.
An admin must reopen it with a reason. The period returns to work in progress, and later locked months are flagged for re-QC before their reports can remain available.
White-label Evo Accounts is $10 per user per month. API access is included; the actual endpoint and integration contract is finalized during launch planning.
Your brand. One operating system.