Why professional services firms struggle with month-end close delays
Unbilled time, WIP, and project revenue slow the close at professional services firms. Where the days go and how to get them back.
Part of the month-end close guide.
A product company closes its books on invoices, shipments, and subscriptions. A professional services firm closes on something much softer: hours that haven't been entered yet, projects that are 40% done according to one partner and 60% according to another, and retainers that cover work nobody has scoped. Professional services firms struggle with month-end close delays because their revenue depends on data that isn't final at month-end: unsubmitted timesheets, unbilled work in progress (WIP), estimates to complete on fixed-fee projects, and rebillable expenses. The accounting team can't close until the delivery team finishes its own paperwork, and that handoff is where the days go.
Key takeaways
• Revenue at a services firm depends on time and progress data owned by people outside finance. Late timesheets delay revenue, unbilled receivables, and the close.
• Different billing models need different revenue treatment under ASC 606: time and materials can often use the "right to invoice" expedient, fixed-fee work is usually recognized over time by measure of progress, and retainers start as deferred revenue.
• Unbilled WIP must be recorded at month-end as an unbilled receivable or a contract asset, not left for next month's invoice.
• In our worked example, one advisory firm recognizes $24,000 of June revenue across three billing models, and $19,000 of it had not been invoiced by month-end.
• Fractional CFO and advisory firms feel this acutely, because they close their own books and often their clients' books across many billing models.
• Loopfour, the deterministic finance workflow automation platform, automates the time-to-revenue handoffs so the close doesn't wait on manual exports and chasing.
Why the close is harder for professional services firms
A services firm's revenue is only as accurate as its time and progress data, and that data is rarely final on the last day of the month. Product companies can close on documents that already exist: invoices, shipping records, subscription schedules. Services firms have to wait for people to report what they did.
Four data dependencies drive most of the delay:
• Timesheets: consultants submit hours late, submit them to the wrong project, or leave them unapproved.
• Estimates to complete: fixed-fee projects need an updated estimate of remaining effort before revenue can be measured.
• Rebillable expenses: travel and third-party costs have to be matched to projects and marked billable before invoicing.
• Rate and contract changes: a change order agreed on a call doesn't reach the billing system until someone keys it in.
Every one of these lives with delivery teams, not accounting. That's why the close for a services firm is as much an operations problem as a finance one. For the general close sequence, see what month-end close is.
Where the days go: the services close, step by step
The services close adds three steps to a standard close: time cut-off, WIP valuation, and project revenue measurement. Each one sits on the critical path, because revenue and receivables can't be finalized without them.
| Close step | What it needs | Common delay |
|---|---|---|
| Time cut-off | All hours for the month submitted and approved | Consultants submit days late; managers approve in batches |
| Expense cut-off | Rebillable expenses tagged to projects | Receipts arrive after month-end; expenses coded to overhead |
| WIP valuation | Approved hours × billing rates, less amounts already invoiced | Rate cards out of date; hours on the wrong project |
| Project revenue measurement | Progress on fixed-fee work, based on updated estimates | Project managers haven't updated estimates to complete |
| Invoicing | Approved WIP turned into invoices | Partner review of every draft invoice |
| Reconciliation and review | Unbilled, deferred, and AR balances tied to the ledger | Differences between the time system and the ERP |
The pattern is a relay race where the baton is data. Finance can't value WIP until time is approved. Partners can't review invoices until WIP is valued. The controller can't sign off until invoices and unbilled balances tie.
How revenue works for each billing model
Professional services firms usually run three billing models at once, and each one follows a different ASC 606 pattern. Getting the pattern right is what makes the month-end entries correct.
| Billing model | How revenue is typically recognized | Month-end balance it creates |
|---|---|---|
| Time and materials (hourly) | As hours are worked, often using the "right to invoice" practical expedient | Unbilled receivable for hours worked but not yet invoiced |
| Fixed fee | Over time, by a measure of progress such as labor hours against total estimated hours | Contract asset when revenue exceeds billing; deferred revenue when billing exceeds revenue |
| Retainer billed in advance | Over the retainer period, as the firm stands ready to deliver | Deferred revenue for the unearned portion |
Time and materials: the right to invoice expedient
For hourly engagements, ASC 606 offers a practical expedient that lets you recognize revenue in the amount you have the right to invoice. ASC 606-10-55-18 allows this when your right to consideration "corresponds directly with the value to the customer of the entity's performance completed to date," and gives "a service contract in which an entity bills a fixed amount for each hour of service provided" as the example. That text is quoted in Deloitte's revenue roadmap on measuring progress.
The practical effect: approved hours × rate = revenue for the month, whether or not the invoice has gone out.
Fixed fee: measuring progress
Fixed-fee engagements are usually recognized over time using an input method, such as labor hours expended relative to total expected hours. ASC 606-10-55-20 lists labor hours as an example input. The catch is the denominator: if the estimate to complete is stale, the revenue is wrong. That makes the project manager's estimate a close input, not a nice-to-have.
Retainers: deferred revenue first
A retainer billed in advance is a liability until the firm delivers. It's released to revenue over the period covered. For how that liability behaves, see what deferred revenue is and why it's a liability.
Worked example: an advisory firm's June close
Here is one month for a small advisory firm with three client engagements, one per billing model. All entries balance.
• Client A, time and materials: 40 hours worked June 24 to 30 at $250 per hour = $10,000, invoiced July 3.
• Client B, fixed fee: $60,000 total fee, 400 estimated hours. 100 hours worked through May 31 ($15,000 recognized, $15,000 billed at kickoff). 60 more hours in June, so 160 of 400 hours are complete.
• Client C, retainer: $15,000 billed April 1 for April to June at $5,000 per month.
The revenue calculation
| Client | Method | Calculation | June revenue |
|---|---|---|---|
| A | Right to invoice | 40 hours × $250 | $10,000 |
| B | Input method (hours) | 160 ÷ 400 = 40% × $60,000 = $24,000 cumulative, less $15,000 recognized through May | $9,000 |
| C | Ratable | $15,000 ÷ 3 months | $5,000 |
| Total | $24,000 |
The June 30 journal entries
Client A: record unbilled receivable for hours worked but not invoiced. Under ASC 606, a receivable is a right to consideration that is unconditional, meaning only the passage of time is required before payment is due. The firm's right to payment here depends only on issuing the invoice, so the balance is a receivable. Deloitte's roadmap on receivables also notes that the standard wasn't meant to change existing practice on when receivables are recorded, so confirm your policy with your auditor.
| Account | Debit | Credit |
|---|---|---|
| Unbilled receivables | $10,000 | |
| Professional services revenue | $10,000 |
Client B: record a contract asset for revenue earned ahead of billing. The next billing milestone hasn't been reached, so the right to payment is conditional.
| Account | Debit | Credit |
|---|---|---|
| Contract asset | $9,000 | |
| Professional services revenue | $9,000 |
Client C: release one month of the retainer.
| Account | Debit | Credit |
|---|---|---|
| Deferred revenue | $5,000 | |
| Professional services revenue | $5,000 |
$19,000 of June's $24,000 in revenue had not been invoiced by June 30. A close that waits for invoices would push that revenue into July or later. When the Client A invoice goes out on July 3, the firm debits accounts receivable and credits unbilled receivables for $10,000, so no revenue is double-counted.
Every number above depended on data from outside finance: approved hours for Client A, updated hours and estimates for Client B. If those arrive on business day four, the close can't finish before day five.
Book a workflow review to see which of your delivery handoffs sit on the critical path of your close.
The fractional CFO firm's version of the problem
Fractional CFO and advisory firms carry the services close problem twice: once for their own books and once for each client they close. A firm managing 12 clients can run hourly, fixed-fee, and retainer arrangements for itself while closing clients on QuickBooks, Xero, and NetSuite, each with its own chart of accounts and deadlines.
That creates a specific set of pressures:
• Parallel closes compete for the same people in the first week of every month.
• Every client's stack is different, so there's no single system to standardize on.
• Client data arrives on the client's timeline, not the firm's.
Firms that close quickly tend to standardize the process even when the systems differ: one close calendar, one set of input deadlines, one exception-handling workflow, applied to every client. Our month-end close checklist is a good starting template.
How to reduce close delays at a professional services firm
The fix is to move time and progress data to finance continuously, and to make missing data visible before month-end. The same principles that speed up any month-end close apply, with a services twist.
| Delay | Fix |
|---|---|
| Late timesheets | Weekly time submission with automated reminders, and a hard cut-off on business day one |
| Unapproved hours | Manager approval inside the workflow, with a deadline and escalation |
| Stale estimates to complete | Estimate update required before month-end for every open fixed-fee project |
| Expenses coded to overhead | Project code required at submission; rebillable flag checked daily |
| Manual WIP valuation | Rate cards maintained in one place; WIP calculated from approved hours automatically |
| Partner invoice review bottleneck | Review only exceptions, such as write-downs or invoices above a threshold |
How to choose an approach
Choose the approach that connects your time system, billing, and ERP so the close doesn't depend on exports and email. The goal is fewer handoffs, not more dashboards.
Professional services automation (PSA) tools manage projects, time, and billing well. They're the right system of record for delivery data. The gap is usually the handoff to the ERP and the month-end entries for unbilled and contract balances.
Horizontal automation platforms can connect a PSA to an ERP. They're flexible, but someone on your team has to build and maintain every flow, and that person is usually also closing the books.
Loopfour handles the finance side of those handoffs. Loopfour Studio connects your time and billing data to QuickBooks, Xero, NetSuite, Sage Intacct, or Rillet, calculates WIP and unbilled balances from approved hours with deterministic rules, and posts the month-end entries. Missing approvals and hours on closed projects are flagged as exceptions and routed to the right manager in Slack. For fractional CFO firms, the same workflow runs across every client stack. Loopfour builds and maintains the workflows, and every run leaves an execution tree your auditor can follow.
Frequently asked questions
Why do professional services firms struggle with month-end close? Their revenue depends on timesheets, project progress estimates, and rebillable expenses that come from delivery teams, not finance. When that data arrives late or incomplete, finance can't value WIP, recognize revenue, or finish invoicing, so the close waits.
How is unbilled revenue recorded at month-end? Revenue earned but not yet invoiced is recorded with a debit to unbilled receivables or a contract asset and a credit to revenue. It's an unbilled receivable when payment depends only on issuing the invoice, and a contract asset when payment depends on something else, such as reaching a billing milestone.
How do you recognize revenue on time and materials contracts under ASC 606? Many firms use the practical expedient in ASC 606-10-55-18, which lets them recognize revenue in the amount they have the right to invoice when that amount corresponds directly to the value delivered. For hourly billing, that usually means approved hours multiplied by the contract rate.
How do you recognize revenue on a fixed-fee consulting project? Fixed-fee projects are usually recognized over time using a measure of progress, such as labor hours worked divided by total estimated hours. The estimate of total hours must be updated each period, because it drives the revenue calculation.
What is WIP in professional services accounting? Work in progress (WIP) is the value of billable work performed but not yet invoiced. At month-end, it is recognized as revenue with an offsetting unbilled receivable or contract asset.
Conclusion
Professional services firms struggle with month-end close delays because their revenue lives in timesheets and project estimates that finance doesn't own. Fix the handoffs from delivery to finance, and the close stops waiting on people outside the accounting team. Get the treatment right for each billing model, record WIP every month, and the numbers hold up to review.
Tell us the one workflow your team dreads. We will show it running: deterministic, permissioned, and auditable.
Book a demo.
Sources
• Deloitte DART: Roadmap, revenue recognition, 8.5 measuring progress for revenue recognized over time
• Deloitte DART: Roadmap, revenue recognition, 14.5 receivables
Related reading
• What is month-end close? The process, how long it takes, and soft vs hard close
• How to speed up month-end close: fix the handoffs, not the people
• The month-end close checklist: every step, owner, and control
• What is deferred revenue? Why it's a liability
• The AR aging report: how to read it and forecast collections from it