A project business shortens month-end close by moving the work out of the last days of the month: approve time weekly, capture expenses and supplier costs as they occur, calculate work in progress (WIP) and accruals from project data by rule, and raise invoices from the same records. The close then becomes a review, not a rebuild in a spreadsheet.
Agencies, architecture firms, consultancies and engineering practices all share one close problem. The numbers that matter, such as billable hours, unbilled work, project cost and margin, live in people's timesheets and project managers' heads, and finance has to assemble them after the month ends. This guide shows how to restructure that process and what a system must do to support it. It sits between two existing guides: ERP project accounting explains how projects, budgets and costs are structured, and ERP for professional services firms compares PSA and ERP. This one is about the close itself. If you are weighing a build, see our custom ERP software page.
Key takeaways
- Most of a slow close is waiting for time and cost data, not accounting work. Fix capture and approval first.
- Approve and lock time weekly, and chase missing timesheets before month end.
- Calculate accruals and WIP by rule from project data, then review exceptions only.
- Raise invoices from approved time, expenses and milestones in a single billing run with a review step.
- Revenue recognition treatment depends on your contracts and accounting framework. Confirm it with your auditor.
- Report profitability by project, client and role monthly, and resource plans against actual hours.
Why is month-end close slow in a project business?
Close is slow because project data arrives late and in pieces. Timesheets are submitted after the month, expenses are in inboxes, supplier invoices for subcontractors have not arrived, unbilled work is estimated by hand and invoices wait for project manager approval. Each step is a dependency, so delay compounds.
| Cause | Symptom | Fix |
|---|
| Late or missing timesheets | Close waits for the last submitter | Weekly submission, automatic reminders, lock after approval |
| Unapproved time | Billable hours change after the books close | Manager approval with a cut-off |
| Expenses in email or on paper | Costs missing from the month | Receipt capture, claim by project, approval workflow |
| Supplier costs not received | Understated project cost | Accrue by purchase order or contract rule |
| Manual WIP spreadsheet | Rework every month, no audit trail | WIP calculated from project data |
| Invoices held for review | Revenue delayed, cash delayed | One billing run, review checklist, holds with a reason |
What does a faster close calendar look like?
A faster close moves tasks earlier. Time is approved weekly, expenses are claimed within a few days, billing runs on a set day and finance spends the first days of the month on accruals, WIP and review. The calendar below is a pattern to adapt, not a standard; the days are illustrative.
| When | Task | Output |
|---|
| Weekly | Submit and approve time; flag overruns | Locked weekly hours by project |
| Weekly | Submit expenses; approve and mark billable | Approved expenses |
| Two working days before month end | Chase missing time and expenses; review budget burn | Exception list |
| Last working day | Run billing for approved time, expenses and milestones | Draft invoices |
| Working day 1 | Post accruals (supplier costs received not invoiced, payroll items) | Accrual journals |
| Working day 1 to 2 | Calculate WIP and unbilled revenue | WIP schedule by project |
| Working day 2 to 3 | Review exceptions; project managers confirm percent complete | Approved WIP |
| Working day 3 to 4 | Reconcile subledgers to the ledger; review margins | Trial balance |
| Working day 4 to 5 | Management pack and KPIs | Report to leadership |
How should time approval work?
Time approval should require each person to submit weekly, route submissions to the project manager for approval, lock approved time against changes and alert managers to overruns against budget. Corrections after approval should be a logged adjustment with a reason, not a quiet edit.
Require these features:
- Time entered against project, task or phase, and a billable or non-billable flag.
- Rate logic: standard rate by role, client-specific rates, effective dates.
- Mobile or offline entry for staff on client sites with weak signal.
- Automatic reminders and a manager dashboard for unsubmitted time.
- A cut-off after which edits require finance approval.
Which accruals does a project business need?
A project business typically accrues for costs received but not yet invoiced (subcontractors, suppliers, reimbursable expenses), for staff costs not yet paid (leave, bonuses, overtime where relevant), and for revenue earned but not yet invoiced. Each accrual should come from a rule and a source record, with automatic reversal in the next period.
| Accrual | Source | Rule |
|---|
| Subcontractor or supplier cost | Purchase order, contract milestone, delivery record | Accrue value of work done not yet invoiced |
| Reimbursable expenses | Approved expense claims not yet paid | Accrue approved, unposted claims |
| Staff-related items | Payroll data, leave balances, bonus plans | Accrue per policy |
| Unbilled revenue | Approved time, milestones reached | Per revenue recognition policy |
| Deferred revenue | Invoices raised ahead of work done | Hold until earned |
Auto-reversal matters. An accrual posted on the last day and reversed on the first day of the next month keeps the ledger honest without anyone remembering to undo it.
What is WIP and how is revenue recognised for projects?
WIP in a project business is the value of work done and not yet billed, or billed ahead of work done, calculated project by project. The method depends on the contract type and your accounting framework, so use the general pattern below and confirm treatment with your auditor.
Revenue recognition for service contracts is governed by standards such as ASC 606 in the United States and IFRS 15 internationally. This guide does not interpret them. In practice firms commonly use one of these approaches by contract type:
| Contract type | Common practice | System needs |
|---|
| Time and materials | Revenue follows approved hours and expenses at billing rates | Approved time, rates, expense markup |
| Fixed fee | Revenue follows progress, often measured by cost to date against estimated total cost, or by milestones | Budget, estimate at completion, percent complete |
| Retainer | Revenue spread over the service period | Schedule by period |
| Milestone-based | Billing follows milestones; revenue follows how the performance obligation is satisfied, which may be over time or at a point in time | Milestone register, approvals and a link to the recognition policy |
Illustrative example. A fixed-fee project is contracted at 100,000. The estimated total cost is 60,000 and cost to date is 30,000, so the cost-to-cost progress is 50 percent. Revenue to date is therefore 50,000. If 40,000 has been invoiced, the 10,000 difference is unbilled revenue. If 60,000 had been invoiced, 10,000 would be billed ahead of work done. The system should produce this schedule per project, let the project manager revise the estimate to complete, and keep the history of each change. The figures are illustrative, and whether this method applies to your contract is a question for your auditor.
How should invoicing be handled in the close?
Invoicing should run from approved time, approved expenses and reached milestones, in one billing run with a review checklist. Each invoice should show the basis for charges and any holds, such as a disputed rate or missing purchase order number, with a reason that the project manager can clear.
Practical requirements:
- Invoice by contract type: hours at rate, fixed fee instalments, milestones, retainers.
- Pass-through of expenses with a mark-up rule where contracts allow.
- Credit notes and write-offs with approval limits.
- Tax, currency and client-specific invoice formats.
- Delivery by email or a client portal, and a link to payment status.
- Where staff work from sites with limited connectivity, offline capture of time and milestone evidence that syncs when connected.
What do professional services firms use for resource planning, billing and project profitability before ERP?
Many firms start with a spreadsheet for planning, a timesheet tool, accounting software for invoices and a CRM for opportunities. That works until the firm needs one view of utilisation, unbilled work and project margin. The signal to consolidate is when finance spends the first week of each month reconciling the tools.
| Stage | Typical toolset | Pain point |
|---|
| Starting | Spreadsheets, accounting package | Manual timesheets and invoices |
| Growing | Timesheet tool, accounting package, project tool, CRM | Data re-keyed between tools |
| Consolidating | Project-based ERP or professional services automation connected to accounting | Needs process change and data clean-up |
| Mature | One platform plus a BI layer | Governance of rates, roles and budgets |
A resource plan compares the hours you have by role with the hours sold. Require capacity by person and role, planned versus actual hours by project and a view of upcoming gaps and overload. Do not plan from titles only; plan from skills and the real calendar, including leave.
Which ERP systems for small architecture firms offer the most comprehensive KPI and project profitability tracking?
No ranking can answer this for every firm, because the right system depends on how you bill. Instead, check any option against the KPIs you read monthly: utilisation, realisation, effective rate, budget burn, margin by project and phase, WIP age and billed versus unbilled work. Test with one finished project.
Architecture and design practices usually bill by phase, often as a percentage of completion or as a fee schedule, so require:
- Phase-level budgets and percent-complete tracking by phase.
- Staff cost rates and billing rates by role, with history.
- Consultant and subcontractor costs linked to the project and re-billed where contracts allow.
- Profitability views by project, phase, client, office and project manager.
- Fee-to-date versus work-done views, so overspent phases are visible while still fixable.
For the reporting side, read our ERP reports finance teams need guide.
Can ERP software automate expense tracking and client billing for a professional services organization?
Yes. An ERP or professional services system can capture receipts, apply policy, route claims for approval, mark expenses billable to a project and add them to the next client invoice with the right mark-up. The value is in the controls: policy limits, duplicate detection, approver rules and an audit trail.
Check that expenses can be entered on a phone, that mileage and currency conversion are handled and that billable expenses appear on the invoice with supporting receipts if the contract requires it. Our ERP HR and payroll module guide explains how reimbursement connects to pay.
When this is the wrong approach
A project-based ERP is the wrong approach for a very small firm with few projects, simple fixed fees and a bookkeeper who closes in two days; a timesheet tool and good accounting software may be enough. It is also wrong to buy software before agreeing the process. If project managers do not agree on percent complete, or staff will not enter time, no system will shorten the close. Fix behaviour and policy first, then automate.
Glossary: WIP, work in progress; in a project business, a per-project schedule of cost incurred, revenue earned and amounts billed, whose difference is unbilled revenue (a contract asset) or billing ahead of work (a contract liability); accrual, a cost or revenue recognised before the invoice or payment; realisation, billed value as a share of the standard value of time; utilisation, billable hours as a share of available hours; percent complete, a measure of project progress used for recognition.
How Timeline Digital approaches project-based finance systems
A faster close starts with how time, costs and invoices are recorded. Timeline Digital, founded in Islamabad in 2013 and delivering remotely, can build custom ERP software that joins time, expenses, project budgets and invoices in one set of records. We build a free pilot of two to three key modules, such as time approval and WIP, that you test before the final agreement. Revenue recognition treatment is for your accountant to confirm, the schedule is set from your requirements in the Plan step and the code transfers on full payment.