>
Contact Let's Talk
Home › Solutions › Project Management

Project management software for services firms: where task tracking ends and PSA begins

Most firms buy project management software to answer the question "what is everyone working on?" — and then discover the questions that actually pay salaries are different ones: is this project making money, can we staff the next one, and what can we legitimately invoice this month? A board full of cards answers the first. Only project accounting — the discipline that PSA software, or professional services automation, exists to carry — answers the other three. This page is about that gap: what a services business genuinely needs from project software, why it is not the same thing as task tracking, and when paying for the heavier tool is justified.

Ind AS 115
Recognition requirement
ETC
Not percentage spent
4
Platform families implemented
CMMI 3
Appraised delivery

Questions task tracking cannot answer

  • What was our utilisation last month, billable over available?
  • Is this fixed-price project going to land above or below cost?
  • How much delivered work is sitting unbilled in WIP?
  • What is the estimate-to-complete, and who signed it?
  • Which skills come off projects in six weeks, and against what pipeline?
  • Which change orders were absorbed rather than priced?
The category, not the product

Task tracking and project accounting are different problems

Work management tools are good at what they were built for. They make work visible, they let a team self-organise, they hold conversation next to the artefact, and they are cheap enough that a delivery lead can adopt one without a business case. If your problem is that nobody knows who owns which task, buy one and stop reading.

The trouble starts when the finance director asks a question the board cannot answer. A card moving to Done records that something finished. It does not record how many hours it consumed, at whose cost rate, against which contract line, or whether those hours were billable. So the firm ends up with two parallel realities: a delivery view in the work tool, and a commercial view assembled monthly in a spreadsheet from exported timesheets. The spreadsheet is where project margin is calculated, and the spreadsheet is nobody's job.

Professional services automation is the category that collapses those two views. The defining characteristic is not that it has a Gantt chart — work management tools have Gantt charts too. It is that the project is also a financial object: it carries a contract type, a rate card, cost rates by role or person, a budget in hours and in currency, recognised revenue, unbilled work in progress, and a forecast of what remains. Hours entered by a consultant hit the delivery plan and the ledger in the same transaction.

That is a heavier system, and it should not be sold as a universal upgrade. A product engineering team building its own software has no client to invoice and no utilisation target; for them, PSA adds ceremony and removes nothing. PSA earns its cost at the point where project profitability and utilisation become the questions leadership actually asks — typically when a firm bills time, runs a bench, or takes fixed-price work it can lose money on.

Margin known in arrearsProject profitability calculated three weeks after month end, when nothing can be changed
Bench invisible until payrollNo view of who rolls off when, so idle time is discovered rather than planned
Percentage-spent as progressSixty per cent of budget consumed reported as sixty per cent complete
Silent scope creepExtra work delivered goodwill-first and never written against the contract
What the category actually has to do

The eight capabilities that separate PSA from a task board

Each of these is a specific mechanism with a specific failure mode. We implement them on MJC WorkSuite ProjectSuite, on the project modules inside Oracle and SAP, and on Microsoft Project with Power Platform — and we will tell you when a lighter work-management tool is the honest answer. Delivered under our CMMI Level 3 appraised framework and ISO 27001 certified security.

Utilisation tracking, defined honestly

Utilisation — billable hours over available hours — is the number that runs a services firm. It is also the number most commonly reported in a way that flatters. Getting the denominator right matters more than the dashboard.

  • Availability defined explicitly: leave, public holidays, training and notice periods removed
  • Billable against chargeable separated, so written-off hours do not count as billed
  • Target utilisation set per role, since a delivery lead and a junior consultant cannot carry the same number
  • Bench time trended as a leading indicator, because idle hours today are a margin problem next quarter

Project accounting software and the cost side

A project board holds effort. Project accounting holds effort priced twice — once at cost and once at bill rate — which is the only way margin exists as a number rather than an opinion.

  • Cost rates per person or per role, versioned so historical months stay correct
  • Rate cards per contract, with client-specific discounts and out-of-hours rates
  • Expenses, subcontractor cost and travel attributed to the project, not to an overhead pool
  • Margin reported per project, per phase and per client, from the same hours finance bills from

WIP and unbilled revenue

Work in progress is delivered work not yet invoiced. It is where cash quietly disappears in services businesses: nobody objects to WIP, and nobody owns it, so it ages.

  • WIP aged by project, so work delivered two months ago and still uninvoiced is visible
  • Invoice-ready versus blocked WIP distinguished — missing approval, missing PO, disputed hours
  • Write-offs recorded as write-offs against a reason, rather than quietly reduced to nil
  • Accrued and deferred revenue reconciled to the ledger at each close, not estimated

Revenue recognition on projects

Time and materials recognises as delivered and is straightforward. Fixed-price work recognised over time needs percentage-of-completion, and percentage-of-completion needs a credible estimate-to-complete. Under IFRS 15 and Ind AS 115 that is an accounting requirement, not a management preference.

  • Contract type held on the project: T&M, fixed price, capped T&M, retainer or milestone
  • Performance obligations identified, with the transaction price allocated across them
  • Input or output method chosen and applied consistently, with the basis documented for audit
  • Onerous contract provision raised when estimate-to-complete exceeds remaining revenue

Project costing and estimate-to-complete

The most common costing error in services is treating budget consumed as progress made. They are unrelated. A project can be eighty per cent spent and thirty per cent complete, and only the delivery lead knows.

  • ETC re-forecast on a cadence by the person accountable for delivery, not derived from spend
  • Estimate-at-completion as actuals plus ETC, compared against the original approved budget
  • Variance surfaced while it is still recoverable, rather than confirmed at final invoice
  • Prior forecasts retained, so a project that has been ninety per cent complete for two months is obvious

Resource management software and the bench problem

Resourcing is a forecasting exercise against a sales pipeline, not a scheduling exercise against signed work. Firms that plan only against signed contracts alternate between a bench and refusing work.

  • Soft booking for pipeline and unsigned proposals, hard booking for committed delivery
  • Skills, certifications and seniority held per person so matching is not tribal knowledge
  • Weighted pipeline demand laid against forward availability to expose gaps early
  • Roll-off dates visible far enough ahead to place people, retrain them or slow hiring

Timesheet software and the discipline it depends on

Every number above is downstream of timesheets being submitted weekly and approved. This is the unglamorous truth of PSA: software cannot fix a culture that does not fill them in.

  • Weekly submission with a hard cut-off, and approval by the person accountable for the budget
  • Entry against a task on a contract line, not against a free-text project name
  • Non-compliance visible to delivery leadership, not buried in a finance exception report
  • Mobile and offline entry, because the friction of entry is the real driver of late timesheets

Change orders, milestone billing and the contract

Scope creep is rarely a decision. It is a sequence of small accommodations, each reasonable, none written down. The system's job is to make absorbing work a visible choice.

  • Change requests raised against the contract with effort and price, and an explicit approve or absorb
  • Absorbed changes still logged and costed, so goodwill is measurable at renewal
  • Milestone billing triggered by acceptance evidence rather than by a calendar date
  • Retention, advance drawdown and billing holds tracked against the contract, not in email
Choosing honestly

Work management, PSA, ERP project accounting or a spreadsheet

Work managementPSA softwareERP project accountingSpreadsheets
What question it answersWhat is being worked on, by whom, by whenIs this project profitable, and can we staff the next oneHow do projects post to the statutory booksWhatever was asked last month
Who uses itDelivery teams and project leadsDelivery, resourcing, sales and finance togetherFinance and controllers, with project managers as inputsOne analyst, and nobody else can maintain it
Financial depthTime logging and simple billable flagsCost and bill rates, WIP, margin, ETC, recognitionFull ledger integration, capitalisation, statutory reportingWhatever the formulas contain, unaudited
IntegrationGood with dev and collaboration tools; weak to financeBuilt to sit between CRM, HR and the ledgerNative to the ledger; project usability often the weak pointManual export, re-keying and version conflict
Best whenA delivery-only team with no billing or utilisation targetThe firm bills time, runs a bench, or takes fixed-price riskProjects are material to the statutory accounts and auditUnder about ten concurrent projects, and only briefly

Most firms do not replace one column with another — they end up with a work-management tool for day-to-day delivery and a PSA layer for the commercial view, integrated so hours are entered once. The mistake is running the third and fourth columns simultaneously and calling it a process.

How we deliver

How we implement project and PSA software

The sequence is deliberately financial-first. Configuring boards before the costing model is decided produces a system that looks finished and cannot close a month.

01

Contract and project taxonomy

We start by listing how you actually sell: T&M, fixed price, capped, retainer, milestone. That determines the project hierarchy, whether you need phases or contract lines as the billing unit, and how a multi-country engagement is split. Firms that skip this end up with one project per client and no way to report margin by phase.

02

Rates, costing and the utilisation definition

Cost rates and rate cards loaded and versioned, then a written definition of utilisation agreed between delivery and finance — what counts as available, what counts as billable, and the target by role. Agreeing this once, in writing, prevents the recurring argument about whose number is right.

03

Timesheet rollout and approval chain

Timesheets go live before reporting does, because the data has to exist before anything can be built on it. Weekly cut-off, approver mapped to budget accountability, and a first month treated as a discipline exercise with visible non-compliance rather than a technical one.

04

Recognition, WIP and the close

Contract types mapped to recognition treatment under Ind AS 115 or IFRS 15, the input or output method documented, ETC capture put on a cadence, and WIP ageing built. We rehearse a close on live data with your auditors' expectations in mind before you rely on it.

05

Resourcing, pipeline link and integration

Soft and hard booking configured, the CRM pipeline connected so weighted demand reaches the resource plan, and the ledger integration built so invoices and journals are not re-keyed. Skills taxonomy kept deliberately coarse at first — a fifty-attribute skills matrix nobody updates is worse than ten that stay current.

06

Handover to a monthly rhythm

The system only holds if it is embedded in a calendar: timesheets Monday, approvals Tuesday, ETC re-forecast fortnightly, project reviews monthly against margin and utilisation. We hand over that rhythm with the configuration, and can run it as a managed service where you lack a PMO.

Related

Related platforms and services

MJC WorkSuiteProjectSuite with sprint boards, Gantt, timesheets and resource allocation on one database Oracle servicesProject Portfolio Management within Oracle Fusion Cloud SAP servicesProject systems and professional services on S/4HANA Microsoft servicesMicrosoft Project, Dynamics 365 and Power Platform reporting DecisionPlanOptimisation where resourcing becomes a constrained allocation problem Staff augmentationCovering a demand peak the bench cannot absorb Managed servicesRunning the PMO and close rhythm on an ongoing basis Case studiesEngagements across ERP and transformation
Questions we get

Project management and PSA software, answered

What is the difference between project management software and PSA software?
Project management software tracks work: tasks, dependencies, boards and schedules. PSA software treats the project as a financial object as well — contract type, cost and bill rates, budget, work in progress, recognised revenue and estimate-to-complete. The practical test is whether one system can tell you both what is being worked on and whether that project is profitable. Most work-management tools answer only the first.
How is utilisation calculated, and what should the target be?
Utilisation is billable hours divided by available hours, where available excludes leave, public holidays and training. We do not publish a target rate, because a credible one depends on role mix, contract type and how much pre-sales and internal work your model assumes. What matters is that the definition is written down, agreed between delivery and finance, and applied consistently — and that billable is not confused with chargeable.
What is the difference between billable and chargeable hours?
Billable hours are hours a client can be invoiced for under the contract. Chargeable hours are hours booked to a client project, some of which will never be invoiced — rework, hours beyond a fixed-price budget, or time written off in a commercial concession. Reporting chargeable hours as billable overstates utilisation and hides the write-off, which is precisely the number a services firm needs to watch.
Why is percentage of budget spent not a measure of progress?
Because spend measures consumption and progress measures delivery, and nothing links them. A project can be eighty per cent spent and thirty per cent complete. Using percentage-spent as percentage-complete guarantees that overruns are discovered only when the budget runs out. The correct input is estimate-to-complete, re-forecast by the person accountable for delivery, with estimate-at-completion derived as actuals plus ETC.
Do we need PSA software to comply with IFRS 15 or Ind AS 115?
You do not need a specific product, but you do need the inputs. Fixed-price work recognised over time requires a defensible measure of progress, which in practice requires a maintained estimate-to-complete and documented input or output method. A firm that cannot produce ETC cannot close its books correctly on those contracts. Spreadsheets can hold this; they rarely hold it in a form an auditor accepts without extensive substantiation.
Can we just keep using our work-management tool and a spreadsheet?
For a while, and for some firms indefinitely. Below roughly ten concurrent projects with a stable team, the spreadsheet is cheaper than the implementation. It stops working when the calculation lives with one person, when margin is only known weeks after month end, or when resourcing decisions need a forward view the spreadsheet does not hold. Those three symptoms, not headcount, are the signal.
What is WIP in a services business, and why does it matter?
Work in progress is delivered work not yet invoiced — approved hours, completed milestones awaiting acceptance, expenses not yet passed on. It matters because it is cash you have funded and not collected, and because nobody objects to it, so it ages silently. Ageing WIP by project and separating invoice-ready from blocked WIP usually recovers more cash in the first quarter than any rate increase.
Will new software fix our timesheet problem?
Partly. Better software reduces friction — mobile entry, pre-populated assignments, sensible defaults — and friction is a real cause of late timesheets. But weekly submission is a management behaviour, not a feature. If approvals are not enforced and non-compliance is invisible to delivery leadership, the new system will produce the same incomplete data faster. We treat the first month after go-live as a discipline exercise for that reason.

Let's build what's next — together.

Whether it's setting up your India GCC, modernizing your enterprise stack, or hiring 50 engineers in 30 days — we'd love to scope it with you.

Schedule a Call → Email Business Team