Professional Services

Run projects, billing, and resource planning together so utilization and profitability are always clear.

Who this page is for: Agencies, consultancies and engineering service firms billing by time, milestone or retainer, with overseas clients. If you also deliver physical goods, the operating side needs a separate system — this page covers the finance-and-delivery half only.

How the business actually flows

Seven steps every professional services system has to chain together. Software that breaks the chain at any point just moves the spreadsheet one step downstream.

  1. 1. Engagement and contract

    A signed scope with a fee basis: fixed fee, time and materials, milestone or retainer. The fee basis, not the feature list, determines which system can invoice correctly.

  2. 2. Rate card and staffing

    Roles carry rates that differ by client and contract, and people are assigned against forward capacity rather than whoever is free this week. Retrospective utilisation reporting is comfortable and nearly worthless.

  3. 3. Time and expense capture

    Every hour and every receipt is attached to a project and a task. This is the step that most implementations fail, because the constraint is human compliance rather than software.

  4. 4. Work in progress

    Cost incurred and time delivered but not yet invoiced is an asset. If the system cannot hold WIP at the rate that will actually be recovered, monthly profit is fiction.

  5. 5. Billing

    Fixed fee, milestone, time and materials, retainer — usually several at once. Billing method has to be a contract attribute, not a weekly manual decision.

  6. 6. Revenue recognition

    Revenue is matched to performance progress, so deferred revenue has to be released against milestones or measured completion rather than recognised at invoice date.

  7. 7. Collection and utilisation review

    Ageing in original currency where clients are overseas, and the three-number review: utilisation, realisation, collection. The gap between them is where margin disappears.

Common challenges

  • !Unbilled time and lost revenue
  • !Poor resource utilization
  • !Project overruns

How a modern ERP helps

  • ✓Time, expense & project billing
  • ✓Resource capacity planning
  • ✓Project profitability dashboards

Must-have functionality

If a product cannot do these, the rest of the demo is irrelevant.

  • ✓Billable time captured against project and task, at a rate determined by contract rather than typed in
  • ✓Work in progress and deferred revenue held as balances, not as spreadsheet adjustments
  • ✓Revenue recognised against progress, with an audit trail for the percentage applied
  • ✓Forward capacity planning: who is over-committed next month, not how busy people were last month
  • ✓Project budget versus actual, by person and by phase
  • ✓Multi-currency billing and collection where clients pay from overseas

Worth paying extra for

Optional only in the sense that the must-haves come first — in practice one of these is often the reason a project pays for itself.

  • ◇Retainer and recurring revenue schedules with automatic release
  • ◇Expense capture with invoice validation feeding straight to the ledger
  • ◇Subcontractor cost and margin pass-through
  • ◇Client portal for timesheet approval and invoice acceptance

Candidate products and why they are on the list

Every candidate is listed with the reason it is on the list and the limitation that could remove it. Fit is judged against the must-have list above, not against brand reputation, and it is a judgement about the shape of the requirement — not a statement that the features work.

Fit

Our judgement of whether the product covers the must-have list above — the shape of the requirement, not proof that any feature works. Evidenced means the capability question is also answered; potential — needs validation means the scenario matches but the deciding capability is still unproven, so the card is a possible candidate and never a recommendation.

Capability

Verified means we read it on the vendor’s own page on a stated date. Partly evidenced means some requirements are documented and the deciding one is not. Unverified means we found no evidence — which is not the same as unsupported.

Delivery

Confirmed would mean our sales side has confirmed we can contract for the product, the version and the implementation. Everything here is TBD, so no card is an offer.

Commercial disclosure. ERP Guide Hub is an editorial resource. We do not present ourselves as an authorised partner, reseller or distributor of any product named on this page. We may receive commission or referral fees on products we cover, Chanjet products included. That does not buy placement, a better position in a list, a softer verdict or the removal of a limitation. Nothing here is an offer to supply any product named on this page. Any figure or feature claim still needs checking against the vendor's current documentation. Read our editorial policy for the full terms.

This page specifically. Every candidate above is a fit judgement against the must-have list for Professional Services, not proof that the features work. Delivery is still TBD for all of them, so no card here is an offer to contract.

Fit: partial, potential — needs validationCapability: unverifiedDelivery: TBD

Chanjet HaoYeCai — project accounting

Verified for the project contract lifecycle: initiation approval, budget control, progress, subcontracting, profitability analysis and a project dashboard — on the same ledger as finance, which is the part most project tools get wrong.

Watch out: The professional-services core is not what this product evidences. Billable time against a rate card, utilisation, work in progress and revenue recognition are absent from the official pages, and there is no PSA module documented. Treat project costing as covered and PSA as unproven.

Verified capability sheet →
Fit: partial, potential — needs validationCapability: unverifiedDelivery: TBD

Finance-first platforms with project accounting (Sage Intacct class)

Multi-entity consolidation, dimensional reporting and automated revenue recognition against ASC 606 / IFRS 15 are core capabilities rather than add-ons — the right shape for a services firm billing several entities.

Watch out: Not a PSA: resourcing, utilisation and timesheet-to-invoice workflow normally come from a connected system. China statutory work and export-rebate-adjacent compliance are outside it.

Fit: partial, potential — needs validationCapability: unverifiedDelivery: TBD

Enterprise PSA suites (NetSuite SRP, Dynamics 365 Project Operations class)

Cover the full chain — resourcing, time, billing, revenue recognition — in one product, for firms with hundreds of consultants and multi-country delivery.

Watch out: Licence and implementation cost assume a large firm; below roughly one hundred billable staff the overhead usually exceeds the benefit. China localisation arrives through a partner.

Still unverified

These are commonly assumed but we found no official evidence. They are questions for the vendor, not selling points.

  • Timesheet capture tied to project tasks, and the rate-card logic that prices those hours
  • Utilisation and realisation reporting by person, team and client
  • Work in progress and deferred revenue as system balances
  • Revenue recognition by progress (ASC 606 / IFRS 15, or the PRC equivalent for service contracts)
  • Forward capacity planning and bench management
  • Zero-rating or exemption evidence for exported services, and the filings that support it

Ask the vendor this

Put these in writing during the demo. An answer that arrives only in the follow-up email is not an answer.

  1. 1Can a consultant's hours be priced by rate card rather than entered as an amount?
  2. 2How is work in progress valued, and at which rate?
  3. 3What recognition method does the system support for fixed-fee contracts spanning periods?
  4. 4Can capacity be viewed forward by month, by person and by skill?
  5. 5How are retainer drawdowns and unused hours treated?
  6. 6Does the system hold deferred revenue in a foreign currency, and post the exchange movement?

What is verified, what is partial, what is unknown

Each requirement is marked against what we could actually read on a vendor’s own page. “No evidence” means we could not verify it — not that the product cannot do it. Ask for a demonstration before you remove a product for that reason.

On a phone, swipe the table sideways to see the evidence column.

RequirementStatusEvidence
Project budget control and actual-versus-budget reportingVerifiedHaoYeCai project management — budget control, progress, profitability analysis, project dashboard. hyc.chanjet.com/xiangmujingli/, read 2026-10-29.
Project cost and profitability on the same ledger as financeVerifiedBusiness documents post to vouchers automatically, so project cost and the ledger share one dataset. hyc.chanjet.com, read 2026-10-29.
Subcontracting captured against the projectVerifiedHaoYeCai project module documents subcontracting within the project lifecycle. Read 2026-10-29.
Multi-currency billing for overseas clientsPartialMulti-currency quoting, settlement and FX gain/loss are documented under the export-trade package; whether the base edition includes it must be confirmed with the vendor.
Timesheet to rate card to invoiceNo evidenceNo timesheet or rate-card capability appears on the official pages reviewed. This is an absence of evidence, not evidence of absence.
Utilisation, realisation and forward capacity planningNo evidenceNo official evidence. Do not assume a project dashboard equals utilisation reporting.
Revenue recognition by progress with an audit trailNo evidenceThe capability matrix has no row for revenue recognition. For PRC service contracts confirm the method with the vendor and your auditor.

Where these projects actually go wrong

Four areas, the failure each one produces, and the control that prevents it. None of this is vendor-specific — it is what the projects have in common.

Implementation

Timesheet adoption fails and the system holds only the hours people remembered to enter, which makes every downstream number wrong.

Control: Make entry weekly and short, tie approval to invoicing so there is a reason to comply, and measure entry compliance from week one.

Integration

A PSA tool and a separate finance system diverge, so project margin in one disagrees with the ledger in the other.

Control: Decide which system owns revenue and WIP, then verify that postings are automatic and reconcilable monthly — not a manual journal.

Deployment

Consultants work on client sites and mobile networks; a system that only works in the office gets abandoned.

Control: Test time entry on a phone, on a poor connection, before rollout; keep the form to a few fields.

Regional compliance

Exported services are usually zero-rated or exempt rather than refundable, and the evidence requirements differ from goods exports.

Control: Keep contract, invoice and supporting documentation linked in one place, since the evidence is what gets examined.

Selection checklist

Work through this before you accept a demo. It takes an afternoon and removes most of the avoidable risk.

  1. 1Write down your fee bases and how many contracts run on each — a firm on four billing models needs four configurations, not one.
  2. 2Ask how many hours per week each consultant would have to enter, and whether that has ever worked at your firm before.
  3. 3Decide whether revenue recognition is a system requirement or a year-end spreadsheet. If it is a spreadsheet, say so and budget for the audit conversation.
  4. 4Take one fixed-fee project spanning two accounting periods and trace it end to end: WIP, progress, recognition, invoice.
  5. 5Confirm how rates are determined when the same person bills at two rates for two clients.
  6. 6Check ageing in original currency if any client pays from overseas.
  7. 7Pilot with one delivery team for a quarter before rolling out to the firm.

What makes Professional Services ERP different

Utilisation is the only number that compounds

A services firm has one asset — billable hours — and it perishes nightly. Everything else in professional services automation exists to answer three questions: how much of our capacity was billable, how much of what was billable actually got invoiced, and how much survived payment disputes. Those are utilisation, realisation and collection, and the gap between them is where margins disappear.

Most firms measure the first and ignore the other two. Utilisation of eighty per cent sounds healthy until you discover write-offs of fifteen per cent and another five lost in discounting during collection. A system that only reports time booked will never surface that, which is why implementation priorities should start with linking every hour to a project budget and a rate card, not with prettier dashboards.

The second requirement is capacity planning that shows forward rather than backward: who is over-committed next month, which projects are staffed against people who have already resigned, and whether the pipeline justifies the hiring plan. Retrospective utilisation reporting is comfortable and nearly worthless; forward visibility is what protects both delivery dates and margins.

Revenue recognition is the hard part

Services revenue arrives in patterns that do not match the work. A twelve-month retainer billed monthly is straightforward; a fixed-fee project spanning two accounting periods is not, because recognising the full fee at invoicing overstates this month and understates next. Under generally accepted standards the revenue must be matched to performance progress, which means the system has to hold deferred revenue and release it against milestones or measured completion.

Work in progress adds the mirror problem: costs incurred and time delivered but not yet billable sit as an asset that must be recognised, valued at the rate that will actually be recovered rather than the headline rate. Firms that ignore this report excellent profit in the month before a large project starts invoicing and miserable profit afterwards.

Rate cards complicate matters further because the same person bills at different rates by role, client and contract. Choose a system where rate determination is configuration rather than manual override, and where every adjustment leaves a traceable reason. The posting structure behind all of this is described in our finance and ERP integration guide.

Servicing overseas clients: tax, currency and collection

Cross-border services are governed by different rules from cross-border goods, and conflating them causes real cost. Goods exporters think about refunds; service exporters usually deal with whether the supply qualifies as zero-rated or exempt from VAT, which typically requires specific contracts and filings to evidence the export. Ask your system to keep contract, invoice and supporting documentation linked, because the evidence requirement is what gets audited.

Currency is unavoidable when a Shanghai agency bills a Singapore client in USD and pays contractors in RMB. Beyond ordinary multi-currency handling, the trap is advance payments: money received before performance creates a deferred revenue liability denominated in foreign currency, so both the revenue release and the exchange movement need posting correctly.

Finally, collection discipline. International invoices age differently and disputes travel slowly, so ageing analysis in original currency plus documented escalation beats any reporting upgrade. The broader export capability checklist is laid out in our buying guide for Chinese export companies, which covers the full quotation-to-settlement cycle.

Frequently asked questions

What is professional services ERP (PSA)?

It combines project management, time and expense capture, billing, and resource planning so utilization and project profitability are always visible — not reconstructed from spreadsheets after the fact.

How does it prevent lost revenue?

By capturing all billable time and expenses and matching them to the right project, it stops unbilled work from slipping through and improves realization rates.

What billing models are supported?

Fixed-fee, time-and-materials, milestone, and retainer — typically configurable per client contract so finance and delivery stay aligned.

How do I improve resource utilization?

Capacity planning shows who is over- or under-booked, letting you balance assignments before projects slip and protecting both delivery and margins.

Can it integrate with accounting?

Yes — project billing and expenses flow to the ledger automatically, keeping finance and delivery in sync without double entry.

Ready to unify your global operations on one ERP?

Book a free scoping conversation with our ERP team. We help Chinese companies going global build a unified system across HQ, overseas factories, and international sales — finance, procurement, inventory, production, and operations in sync.

Book a Free Consultation