Standardize the operating workflow across companies, but preserve company-specific charts, policies, evidence, permissions, and close decisions.
Design two levels: firm supervision and company books
The firm needs to know which companies are current, blocked, waiting on evidence, or ready for review. The underlying accounting work still belongs to separate companies with separate ledgers, bank accounts, statements, and owner relationships.
Do not turn a portfolio view into a shared accounting scope. A firm-level count should lead to the exact company and records that produced it.
- Firm portfolio and work signals
- Separate company accounting scopes
- Explicit selected-company context
- Access based on current membership
Standardize work states before standardizing staff behavior
A team cannot coordinate if “done” means coded to one person, posted to another, and reconciled to a third. Define the states for bank activity, statement coverage, requests, reconciliations, journal review, and reporting.
Once the states are stable, staffing and automation can route work consistently. Without them, a larger team creates more status meetings rather than more throughput.
- What is pending or blocked
- What is ready for a bookkeeper
- What needs senior review
- What produces close evidence
Assign ownership by exception, not only by company
Company ownership is useful, but a portfolio also benefits from specialist paths. One person may handle reconciliation differences, another migration cleanup, and another company-owner requests. An AI bookkeeper may handle repeat research across all accessible companies.
The handoff must retain the company, source record, evidence, and expected outcome. Otherwise specialization creates another inbox.
- Company owner or primary bookkeeper
- Exception specialists
- Tally duties and authority
- Escalation and waiting-on-human paths
Use operating cadence without inventing busywork
Daily review should focus on new workable activity and blockers. Weekly review should identify companies falling behind. Close review should confirm statement coverage, reconciliations, material journal activity, and report readiness.
A cadence is useful only when the source conditions require work. A scan that correctly finds nothing should report nothing rather than generating a decorative task.
- Daily workable queue
- Weekly stale-work review
- Period-end reconciliation and report review
- No-op results treated as valid
Measure capacity with outcomes and exception rates
Company count alone is a poor workload measure. A company with two stable bank accounts and good owner responses differs from one with many cards, late statements, ambiguous transfers, and frequent cleanup.
Measure workable transaction volume, exception mix, missing-evidence days, reconciliation effort, review changes, and delivery timeliness. Those measures show whether automation creates real leverage.
- Workable transaction volume
- Exception and warning rate
- Days waiting on evidence
- Reconciliation and review effort
Related reading
Put the workflow into practice