SaaS · Saas

Accounting Firm Management Vertical on Acumatica

Accounting Firm Management Vertical on Acumatica: a practical Acumatica fit review focused on project budgets, time capture, utilization, billing rules, and scope change control. It separates documented product capability from configuration, integration, and customisation work.

John Kihiu12 min read

An accounting or bookkeeping firm evaluating Acumatica is usually not shopping for a general ledger — they already know general ledgers cold. What they are actually testing is whether the Projects module can run their real business model: client engagements billed by the hour against a budget, recurring compliance work billed flat, and a partner group that wants realization and utilization numbers every Friday, not at month end.

Treat every engagement as a Project, not a customer

The instinct to model each client as an AR customer and stop there is the most common setup mistake I see. It gets you invoicing, but it throws away the one thing Acumatica's Projects module (PM301000, PM302000) is actually good at: tracking budgeted hours against actual hours per engagement, per task, per staff member. A tax return is a Project with a task per return type; a monthly bookkeeping retainer is a Project with a recurring billing schedule; an audit is a Project with tasks for planning, fieldwork, and review, each with its own budget.

This matters the first time a partner asks "are we losing money on the Henderson audit" — with engagements-as-projects that is a Project Status report (PM640000-class inquiry) pulled in thirty seconds. With engagements-as-customers-only it is a manual spreadsheet reconstruction from timesheets.

Billing rules: the actual decision that matters

Acumatica's Billing Rules (PM207000) support time-and-material steps and progress/fixed-fee billing on the same project, which maps directly onto how accounting firms actually price work — T&M for advisory and cleanup engagements, flat fee for recurring compliance:

PM207000 · BILLING RULE STEP
Step 1 — Time and Material
  Source: Time Activities (EP), Expense Claims
  Rate resolution order: Employee override rate
                          -> Project Task rate
                          -> Labor Item rate
  Markup: 0% (rate table already includes margin)

Step 2 — Progress (fixed-fee compliance work)
  Billing Method: Completed Percentage
  Trigger: Task marked Completed on task PM302000
  Amount: Contract line amount for the task

The gotcha that catches firms migrating off QuickBooks Online or a practice-management tool: Acumatica bills off the rate resolved at time-entry, not a rate you can silently change after the fact on the invoice screen. If a partner rate changes mid-engagement, back-dated time entries keep the old rate unless you explicitly rebill — which is usually the correct behavior for a firm, but it surprises people expecting Excel-style "just change the number".

Realization and utilization, not just billable hours

The metric partners actually care about is realization — billed amount divided by standard rate value of hours worked — and Acumatica gets you most of the way there because time activities carry both the billable rate and, if you configure a separate "value" rate on the Earning Type or Labor Item, the comparison is a GI away. Out of the box there isn't a dedicated "realization dashboard"; I typically build one Generic Inquiry joining PMTimeActivity to the billing rule's rate resolution and expose it on a dashboard widget per partner. That is a half-day of GI work, not a customization project.

Write-downs need a real workflow, not a delete

When a partner writes down an engagement's fees before billing, the correct move in Acumatica is a billing adjustment on the pro forma invoice (PM304500-class screen) that preserves the original time value for realization reporting, not deleting or editing time entries. Deleting time entries destroys the utilization numbers you need for the next comp review. Train staff on pro forma review before release, every time.

Where it doesn't fit cleanly

Trust accounting for client funds — if the firm also holds client money in a fiduciary capacity, which is more of a legal-practice pattern — is not something Acumatica models natively; see the legal-practice post for that gap and workaround, the same segregation problem applies if an accounting firm handles client trust funds. And practice-management niceties — engagement letters, PBC (prepared-by-client) request tracking, workpaper sign-off — live in dedicated tools (Karbon, Suralink, etc.); the sane architecture integrates those via the REST API rather than trying to rebuild them in Acumatica screens.

Wrapping up

For a firm with real project-costing needs — multiple staff levels, budgets that matter, mixed T&M and fixed-fee billing — Acumatica's Projects module is a legitimate, not a forced, fit. The setup work is mostly discipline: model engagements as projects with real tasks and budgets from day one, resist the urge to skip straight to invoicing, and build the one or two realization GIs the partners will actually look at every week.

John Kihiu
Acumatica ERP Developer · Laravel Engineer

Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.