Multi-entity, multi-client books
Keep a distinct ledger, chart of accounts, currency and reporting calendar per client entity, and move between them inside one signed-in session instead of opening and closing separate files.
CPAs & CAs Solution
One console for every client ledger you carry
A practice does not fail on bookkeeping. It fails on the forty small things around it: which return is due, who has the working papers, which draft the client approved, and how much of last quarter's time was ever billed.
Every client entity on one ledger structure, with the compliance calendar, working papers and audit trail attached to the transactions themselves.
Platform fundamentals
Built for a portfolio, not a single company.
One console
Every client entity opened from a single signed-in workspace
Filing calendar
Statutory dates tracked per entity with an owner and a status
Working papers
Schedules linked to the postings that support them
Recovery view
Time recorded, billed and written off compared per engagement
What it covers
The practice, not just the ledger.
Client accounting, statutory compliance, engagement documentation and the commercial side of the firm sit in one place, because in a practice they are the same job seen from different desks.
Compliance calendar
Track every statutory return, filing, renewal and board date per entity with an owner, a due date and a status, so nothing depends on one partner remembering it.
Audit trail and working papers
Every posting carries a user, a timestamp and a reversal history, and lead schedules link back to the transactions that support them so a review can follow the number to its source.
Document management
Hold engagement letters, statements, notices, queries and signed accounts against the client and the period they belong to, with version history and access control by role.
Time capture and practice billing
Record chargeable and non-chargeable time against client, engagement and staff member, then turn it into invoices, write-offs and recovery reporting without re-keying a timesheet.
Client portal
Give each client a controlled place to upload records, answer queries, approve drafts and download filed documents, so the exchange stops living in an email thread.
The real bottleneck
Context switching is the tax on a practice.
A senior who handles thirty entities does not lose the day to journal entries. They lose it to opening the right file, finding last year's schedule, checking whether the notice was answered and confirming which version the client signed.
Putting the books, the calendar, the papers and the correspondence behind one login removes most of that overhead, and it makes review possible without a handover meeting.
- Client, entity, engagement and period as a single navigable structure
- Statutory dates carried forward year on year with the owner attached
- Queries raised, answered and closed against the record they concern
- Partner review sign-off recorded on the working paper, not in an inbox
- Recorded time visible against the fee before the invoice is raised
Questions practices ask
Before you move the portfolio.
Each client entity holds its own ledger, chart of accounts, currency and reporting calendar. Staff see only the entities their role grants them, and every action is recorded against the user who performed it.
Yes. Switching between entities does not require signing out and opening a different file, which is the point: the time lost in a practice is usually lost between files rather than inside them.
Every posting carries a user, a timestamp and a reversal history rather than being silently editable, and working papers link back to the transactions that support them so a reviewer can trace any figure to source.
The client portal gives each client a controlled place to upload records, respond to queries, approve drafts and download filed documents, with access scoped to their own entities only.
Chargeable time is recorded against client, engagement and staff member, then converted into invoices with write-ons and write-offs recorded explicitly, so recovery per engagement is visible rather than inferred.
How a practice moves across
Migrate a portfolio without losing a deadline.
Practices move between filing seasons, not during them. The sequence below is built around that constraint, starting with the entities whose next deadline is furthest away.
01
Portfolio review
We map your client base by entity type, statutory calendar, engagement type and the staff who own them, and agree which cohort moves first based on when their next deadline falls.
02
Chart and calendar setup
Standard charts of accounts, engagement templates, working paper packs and the statutory calendar are configured once at firm level, then applied per entity.
03
Cohort migration
The first cohort of entities is migrated with opening balances, prior-period comparatives and open queries, and reconciled against the balances your team already signed.
04
Firm-wide adoption
Remaining cohorts follow between filing cycles, time capture and billing are switched on, and the client portal is opened to clients in a controlled sequence.
Related solutions
What your clients are running.
Practices that advise across industries can put clients on the same core they audit against, which shortens every year-end conversation.
Retail Solution
Multi-outlet point of sale, live stock across locations, promotions and margin reporting on one ledger.
Explore retail ERPManufacturing Solution
Multi-level BOMs, production planning, shop-floor capture and actual costing for discrete and process plants.
Explore manufacturing ERPEducation ERP
Admissions, attendance, fee collection, examinations and payroll on a single student record.
Explore education ERP
See it on your portfolio
Bring one client to the demo.
Pick an entity with a messy year-end and a deadline you nearly missed. We will walk the engagement through the platform, from records received to filing acknowledged.