Bill every hour, licence and milestone you deliver.
IT services firms, software companies and shared-service centres lose money between the timesheet, the contract and the invoice. We join them up and show what to bill, what to stop and what to forecast.
マネーラインHours billed, licences recovered and costs cut, by client, project and centre.
02Twelve use cases
Twelve use cases across delivery, contracts, spend and shared services
DELIVERY AND BILLING
- Unbilled hoursTimesheets, contracts, invoices
- Milestones delivered, not billedProject plans, sign-offs
- Rate card driftRate cards, invoices
CONTRACTS AND REVENUE
- Price escalations not appliedContracts, indices, invoices
- Revenue forecast by contractPipeline, backlog, billing
- Service credits paid outSLAs, tickets, credits
SPEND AND CLOUD
- Unused software licencesLicence registers, login data
- Idle cloud resourcesCloud billing, usage
- Subcontractor overbillingSubcontractor invoices, timesheets
SHARED SERVICES
- Manual journals near closeJournal entries, users
- Intercompany mismatchesIntercompany ledgers
- Payments released without approvalPayment runs, approval logs
Each use case names the data it needs. Timesheet, ticketing and cloud billing data usually sit outside the ERP.
03One case
One case: a forecast you can explain
IT services: the forecast was a spreadsheet. The answer was in the contracts.
- Situation
- An IT services firm built its revenue forecast from project managers’ estimates, updated each month.
- What a sample misses
- Each estimate looks reasonable. The gap is between what the contracts say will be billed and what the teams expect.
- Data and technique
- Contracts, timesheets, backlog and billing joined by project; a forecast built from the contracts, with the reason for every change.
- Typical findings
- Milestones delivered but not invoiced; rate increases due but not applied; projects billing below their contracted run rate.
- Control fix
- A weekly list of unbilled work sent to delivery heads; rate changes applied from the contract, not from memory.
A forecast you can’t explain is a forecast nobody acts on.
Illustrative composite case, read-only access.
04Tests to run first
Billing, spend and shared services: 12 tests to run first
| Billing and contracts | Spend and shared services |
|---|---|
| Hours on timesheets with no invoice | Licences with no login in 90 days |
| Milestones signed off but not billed | Cloud resources running with no owner |
| Rates below the contract or the rate card | Subcontractor hours above the client hours billed |
| Escalations due but not applied | Manual journals posted in the last days of close |
| Service credits paid without a breach | Intercompany balances that don’t match |
| Discounts given outside approval limits | The same person creating and paying a vendor |
Thresholds are set for each business unit and tuned on the results.