An ERP for a professional services firm connects time and expenses captured against projects to billing, revenue and the general ledger, so the firm can see work in progress (WIP), utilisation and margin per project, client and person. Consultancies, agencies, engineering and IT services firms need this more than inventory or manufacturing modules.
The first decision is usually not which ERP, but whether you need a professional services automation (PSA) tool, an ERP, or both.
What is the difference between PSA and ERP?
PSA runs delivery: projects, resourcing, time, expenses and often billing. ERP runs the firm's finances and back office: ledger, receivables, payables, payroll inputs, consolidation. Many firms run a PSA connected to an accounting system; larger or multi-entity firms often need ERP-grade finance behind the PSA.
| Capability | PSA | ERP (finance core) | Notes |
|---|---|---|---|
| Project setup, tasks, budgets | Yes | Sometimes | |
| Resource planning and skills | Yes | Rarely | |
| Timesheets and expenses | Yes | Sometimes | Time capture quality decides everything downstream |
| Billing (time and materials, fixed fee, retainer) | Often | Yes | Decide which system owns invoices |
| WIP and revenue recognition | Partly | Yes | Finance usually wants this in the ERP |
| General ledger, AR, AP, cash | Limited | Yes | |
| Multi-entity, inter-company recharges | Rarely | Yes | Important for firms with offices in several countries |
| Utilisation and margin reporting | Yes | With data from PSA |
A useful rule: if one system can own the project, time, billing and finance with acceptable depth, use one. If you need specialist depth in either resourcing or finance, run two and integrate them so time is entered once.
Firms whose delivery model or billing rules do not fit the packages can consider custom ERP software or ERP modules built around existing systems.
Why is time capture the most important feature?
Because everything else is calculated from it. Late, vague or missing timesheets produce wrong WIP, late invoices and unreliable utilisation.
What good time capture looks like:
- Entry against project, task or phase, with a billable or non-billable flag
- Daily or weekly entry with reminders, and fast entry on mobile
- Rates applied automatically by role, person, client or contract
- Approval by project manager before billing
- Locking of approved periods, with controlled corrections
- Expenses with receipts, marked as rechargeable or not
How should WIP and revenue recognition work?
WIP is the value of work done but not yet billed. The ERP should value it consistently and show it per project so partners and finance agree on the number.
- Time and materials. WIP equals approved time and rechargeable expenses at billing rates, less amounts billed. Write-ups and write-downs are recorded with reasons.
- Fixed fee. Revenue is usually recognised by progress (for example, a percentage of completion based on cost or milestones). WIP or deferred income is the difference between revenue recognised and amounts billed.
- Retainers. A fixed monthly charge, sometimes with a capped number of hours and overage billing.
- Milestones. Billing on delivery or acceptance of defined outputs.
Revenue recognition policies are set by your accountants under the reporting framework you use; the ERP should apply the agreed method consistently and keep the audit trail. Our guide to ERP project accounting goes deeper on the mechanics.
Illustrative example: one client, three contract types
A consultancy runs a fixed-fee discovery project, a monthly support retainer and a time-and-materials implementation for the same client. The ERP holds one client account and three contracts. Time is captured against each; the discovery project's revenue is recognised by milestone, the retainer bills monthly with overage hours billed separately, and the implementation bills approved time each month. The client sees one statement; finance sees margin per contract.
Which metrics should the system report?
Pick a small set and define each one precisely, because firms argue about definitions more than about numbers.
| Metric | Typical definition (agree your own) |
|---|---|
| Utilisation | Billable hours divided by available hours, per person or team |
| Realisation | Amount billed divided by the value of time at standard rates |
| WIP days | WIP balance relative to average daily billing |
| Debtor days | Receivables relative to average daily billing |
| Project margin | Revenue minus direct cost (time at cost rate plus expenses) |
| Forecast to complete | Remaining effort and cost estimated by the project manager |
For dashboard design, see business dashboard KPI design.
How should billing and invoicing run?
Billing should be a review step, not a data entry step. The system prepares draft invoices from approved time, expenses, milestones and retainers; the project manager or partner reviews, adjusts with a reason, and approves; finance issues.
Practical points to check in any option:
- Draft invoices grouped by client, contract or purchase order, as each client requires
- Narrative and time detail attached in a format the client accepts
- Write-downs at billing captured with a reason, so realisation analysis is honest
- Retainer drawdowns and overage hours calculated automatically
- Disbursements and rechargeable expenses billed at cost or with an agreed uplift
- Multi-currency invoicing for international clients, with exchange differences posted correctly
- Credit notes linked to the original invoice and project
What about resource planning and forecasting?
Resource planning answers who is free next month and whether the firm can take on a new piece of work. It sits naturally in a PSA tool, but the ERP needs its output to forecast revenue and cost.
A simple forecasting loop: project managers update remaining effort each week or fortnight, the planning tool turns that into booked hours by person, and finance converts booked hours into forecast revenue and cost by month. Comparing forecast against actual each month shows which projects consistently run over and which people are booked beyond capacity.
Firms with several offices or entities
When staff from one entity work on another entity's client, the ERP should raise inter-company recharges automatically at an agreed rate, so each entity's results are fair and the group consolidation eliminates them cleanly. Doing this by manual journal at month end is one of the most common reasons services firms move off entry-level accounting software.
Professional services ERP scorecard
Score 0 to 3 and weight by importance.
| Requirement | Weight | Option A | Option B |
|---|---|---|---|
| Fast, mobile-friendly time entry with reminders | |||
| Rate tables by role, person, client and contract | |||
| Approval workflow before billing | |||
| Multiple billing models on one client | |||
| WIP valuation and write-up or write-down tracking | |||
| Revenue recognition by milestone or progress | |||
| Resource planning or integration with a planning tool | |||
| Multi-entity and inter-company recharges | |||
| Utilisation, realisation and margin reporting | |||
| CRM integration for pipeline to project hand-off |
When is custom ERP not the right approach for a services firm?
For many small and mid-sized firms, a PSA tool plus a mainstream accounting package is the right answer, and a custom build would be over-investment. A packaged ERP with services modules suits firms whose billing and approval rules are standard.
Custom work fits when the firm's commercial model is unusual (complex rate structures, multi-party billing, outcome-based fees), when several entities recharge staff to each other, or when the firm needs project, CRM and finance data in one model and the packages force duplicate records. Read ERP vs custom development for the general trade-off.
What does a typical rollout sequence look like?
Most services firms get value fastest by starting where data is born. A common sequence, which you should adapt to your own priorities:
- Clients, projects, contracts and rate tables, so every hour has somewhere to go.
- Time and expense capture with approvals, run for at least one full billing cycle.
- Billing and WIP, once time data is trusted.
- Revenue recognition, inter-company recharges and consolidation.
- Resource planning and forecasting, fed by the clean history from earlier phases.
Implementation checklist
- Agree definitions for utilisation, realisation, WIP and margin before configuration
- List every contract type and billing pattern in use today
- Decide which system owns time, which owns invoices and which owns revenue
- Clean the client and project list; close dormant projects before migration
- Migrate open projects with budgets, WIP and unbilled time, not closed history
- Pilot time entry with one team for a full billing cycle
- Train project managers on approvals and forecasts, not only on timesheets
- Set a clear rule for late timesheets and enforce it from the first week
- Review realisation and write-downs with partners after the first two billing cycles
- Keep a short list of change requests and agree them before adding them to scope
A firm that gets time capture and approvals right in the first phase usually finds billing, WIP and reporting follow naturally. A firm that rushes to dashboards before time data is trusted spends months explaining numbers nobody believes.
How to start
Write down your contract types, rate structures, entities and the five reports partners ask for most. The software requirements brief template gives you a structure, and the ERP selection criteria checklist helps when comparing options.
Then discuss the project with us. Timeline Digital builds 2 to 3 key modules as a free pilot before the full project starts, for example time capture with approvals and billing, so you can run a real billing cycle before committing.