Project accounting workflow for professional services

The project accounting workflow for professional services firms runs through six linked steps: time and cost capture, approval, work-in-progress (WIP) tracking, revenue recognition, invoicing, and reconciliation. Each step depends on the one before it, so a breakdown anywhere in the chain, most often at the handoff between delivery and finance, delays or corrupts everything downstream, including the invoice and the numbers finance reports.

Most finance leads at professional services firms recognize the symptom before they can name the cause: month-end close takes days longer than it should, numbers get revised after they were supposedly final, and nobody can point to the exact moment things went wrong. That’s usually because the process was never written down as a process. It lives differently in every project manager’s head, runs through whatever spreadsheet each team happens to use, and only becomes visible to finance once it’s already broken.

One operations lead at a biostatistics consultancy described the result plainly: her team ended up with two different aging accounts receivable reports, one from the billing side and one from accounting, and neither could be fully trusted. That’s not a one-off data entry mistake. It’s what happens when the project accounting chain has a broken link between delivery and finance. This article maps the full chain, names where it typically breaks, and lays out what finance should expect from a system that runs it cleanly.

The project accounting chain: six steps

Step 1: Time and cost capture

Time and cost capture means logging billable and non-billable hours against the correct project and task, alongside any third-party or subcontractor costs tied to the same engagement. The billable team self-reports this data, which makes it the first and most fragile link in the chain.

The most common failure here is late or incomplete entry: people reconstructing a week’s work from memory on Friday afternoon instead of logging it as they go. Every downstream step, from WIP to the invoice, inherits whatever accuracy problem starts here. A clean version of this step looks like daily or near-real-time entry against project and task structures that already exist in the system, not a weekly reconstruction exercise. Whether that habit sticks is largely decided in the first 90 days after a new system goes live, not afterward.

Step 2: Approval

Approval means a delivery manager reviews and signs off on time and cost entries before they count as billable, reportable fact. This step exists to catch coding errors, misallocated hours, and out-of-scope work before any of it becomes an invoice line item.

Under deadline pressure, approval often becomes a rubber stamp, or gets skipped altogether. Once that happens, unreviewed errors flow straight into WIP and eventually the client’s invoice, where they’re far more expensive to fix. A clean version runs on a fixed weekly cadence rather than an ad hoc one.

Step 3: WIP (work-in-progress) tracking

WIP is approved, unbilled time and cost that has accumulated on a project: value the firm has already delivered but hasn’t yet invoiced or recognized as revenue. It’s the step most people outside finance rarely think about by name, even though it represents money the firm has effectively already earned.

The typical failure is tracking WIP in a separate spreadsheet, reconciled manually against delivery data that’s often days or weeks stale by the time anyone pulls it. A clean version keeps the WIP balance visible in real time, computed from the same approved time and cost data as every other step in the chain, not a parallel manual ledger someone updates once a week. How WIP diverges between fixed-fee and time-and-materials engagements is a distinction worth understanding on its own, since the two billing models accumulate WIP differently.

Two figures sit on top of a clean WIP balance and pull in opposite directions when the underlying data is stale: cost-to-complete, which tells a PM how much budget is left to burn, and estimate at completion, which tells finance where the project will actually land. Both depend on WIP being current, which is why a stale spreadsheet here quietly breaks two forecasts at once, not just one.

Step 4: Revenue recognition

Revenue recognition converts WIP into recognized revenue according to the engagement’s billing model and the firm’s accounting policy. For many time-and-materials and fixed-fee engagements this follows a percentage-of-completion approach; retainer engagements are typically treated differently. This is the step with real accounting-standard weight behind it, under the FASB’s ASC 606 revenue standard in the US, so the details depend on a firm’s specific policy and should be confirmed with an accountant rather than taken as a template.

The common failure is recognition calculated manually at month-end, disconnected from actual delivery progress. That’s especially painful on fixed-fee work, where an accurate percentage-of-completion figure depends entirely on clean WIP and milestone data from the steps before it. A clean version computes recognition from the same delivery data, time entries, milestones, budget-versus-actuals, rather than having finance re-derive it from scratch every month. This is the step most dependent on everything upstream being accurate, which is why the chain metaphor holds: a late timesheet approval in step 2 can quietly distort a recognized-revenue figure two steps later.

Step 5: Invoicing

Invoicing converts recognized or billing-model-appropriate amounts into a client invoice, matching the actual arrangement: time and materials, fixed fee, retainer, or a hybrid within the same client relationship.

Roughly half the firms in our own discovery-call corpus described invoicing as a manual, day-long exercise each month, usually because it means assembling numbers across disconnected systems. Clients on mixed billing models make this worse: the time-and-materials portion and the fixed-fee portion of the same relationship often get invoiced through separate, unsynced processes. A clean version generates the invoice directly from approved time, WIP, and recognition data instead of rebuilding it from a fresh export every cycle.

Step 6: Reconciliation

Reconciliation matches invoiced amounts against the accounting system, tracks payments, and investigates any variance between what delivery recorded and what accounting shows.

This is where the two-different-aging-AR problem shows up in its clearest form: a billing system and an accounting system that don’t talk to each other produce two versions of what a client owes, and nobody fully trusts either one. It’s also why QuickBooks integration is the single most requested integration among the firms in our corpus, ahead of Salesforce, HubSpot, and Power BI combined; a two-way sync between the project system and the accounting system is what turns reconciliation into a quick check instead of a manual rebuild every month.

Where the chain actually breaks

The chain almost never breaks inside a single step. It breaks at the handoff between two people or two systems, most consistently at the seam between delivery and finance.

Two handoffs cause the most damage. The first is between approval and WIP: delivery data reaches finance late, incomplete, or in a format that has to be manually re-keyed before it’s usable. The second is between invoicing and reconciliation: the billing process and the accounting system run independently, so what finance eventually reconciles doesn’t match what delivery believes was billed.

A useful diagnostic for any finance lead reading this: which step in your own process currently involves exporting something from one tool and retyping it into another? That step is where the chain is breaking.

A sample month-end close, mapped to the chain

A close that runs cleanly looks like this in practice: time entered daily, approvals completed weekly rather than batched at month-end, WIP visible continuously rather than assembled once a month, revenue recognition calculated from that already-clean WIP balance, invoices generated within a few days of close instead of requiring a dedicated invoicing day, and reconciliation completed as a same-week check against the accounting system rather than a rebuild.

Contrast that with the common broken version: recognition and invoicing both wait on a manual data-gathering exercise that itself consumes most of a week, which means the “close” isn’t actually closed until well into the following month, and every number produced during that gap carries a caveat.

What finance should require from a project accounting system

The requirement is the same six-step chain, running on one connected data source instead of six disconnected tools stitched together by exports and re-entry. In practice, that means:

• Time and cost capture that flows into WIP without manual re-entry
• A WIP balance visible in real time, not reconstructed from a spreadsheet
• Recognition logic that reflects the firm’s actual billing models, not just time-and-materials work
• Invoice generation pulled from the same approved data used everywhere else in the chain
• A two-way accounting sync, not a CSV export, closing the reconciliation loop

This is the finance-specific slice of a broader evaluation. A full requirements checklist covers the criteria across delivery, resourcing, and reporting as well, for firms evaluating a system end to end rather than just the accounting piece.

The bottom line

Six linked steps, most of the damage happening at the handoffs between them, and a clean version of the chain running on one connected data source instead of six. Firms that map their own close against this chain usually find the break within a few minutes, because it’s almost always the step where someone is exporting a file and retyping it somewhere else.

Walking through a current close process against this chain, link by link, is the fastest way to find that step. A Birdview PSA demo can do that live, against a real project, rather than in the abstract.

FAQ

What is project accounting in professional services? Project accounting is the process of tracking a project’s costs, billable time, and revenue against its budget and its accounting treatment. In professional services it runs as a chain of six steps, from time capture through reconciliation, because each figure depends on the one calculated before it.

What is WIP in project accounting? WIP, or work in progress, is approved time and cost that has been delivered on a project but not yet invoiced or recognized as revenue. It’s easy to lose track of because it usually sits in a separate ledger or spreadsheet rather than being visible alongside delivery data.

How does revenue recognition work for professional services firms? Revenue recognition converts WIP into recognized revenue according to the engagement’s billing model, typically percentage-of-completion for time-and-materials or fixed-fee work under the FASB’s ASC 606 standard, with different treatment for retainers. Specific policy should be confirmed with an accountant.

Why doesn’t project billing match the accounting system? This usually happens when the billing process and the accounting system run independently, producing two versions of what a client owes: one from delivery’s records, one from finance’s. A two-way sync between the two systems, rather than manual exports, is what keeps them aligned.