What Does a Standard ERP Balance Report Not Show About Project Cash?
A construction ERP shows the balance on each bill, retention and payable. A standard balance report on its own does not show how long a bill waited at each step, whose delay it was or what the wait cost. This guide lists six questions it cannot answer, the date fields each needs and how to check them by hand.
Last updated 9 min read
A construction ERP shows the balance on each RA bill, retention and payable. A standard balance report on its own does not show how long a bill waited at each step, whose delay it was or what the wait cost, unless someone rebuilds the answer from the date fields the ERP already stores.
This guide is general information. Sample figures are from Crestline's glossary and are not customer data. Field and report names differ between ERPs, and this guide makes no claim about any named ERP, so confirm the field names in your ERP.
What does a construction ERP report show, and what does it leave out?
A construction ERP report shows the current state of each record: what is billed, what is outstanding, what is held. A wait is the gap between two dates on the same record, so a report that shows one state at one moment leaves it out.
Crestline's glossary describes ERP reporting as answering "what is the current state of each record?" (glossary, process intelligence entry). Three examples from the same glossary show where that leaves a gap:
- The wait between submitting an RA bill and its certification sits outside receivables, outside DSO and outside the ageing report, because no invoice exists yet (certification lag).
- Retention carries no due date in most finance systems, so it shows as a receivable and is not tracked as owed until someone ages it from the completion certificate (retention money).
- Work done but not yet invoiced is the part of the receivable that DSO cannot see (unbilled revenue).
For the difference between the record and a reading of the record, see construction ERP vs process intelligence.
Which six questions can an ERP report not answer on its own?
Six questions about project cash need the dates between steps, not the balance at one step: how long a bill waited, how old retention is, whose delay it was, what the wait cost, which vendor credit went unused and which client pays late as a habit. The table gives the date fields each one needs.
| Question | Why a balance report misses it | ERP date fields needed (confirm the field names in your ERP) |
|---|---|---|
| 1. How long did a bill wait at each step? | The report shows where the bill is now, not the time spent at each earlier step. A resubmitted bill may carry only its new date, which erases the first pass | Work executed, bill submitted, returned for correction, resubmitted, certified, invoice date |
| 2. How old is the retention, counted from the completion certificate? | Retention has no due date in most finance systems, so it is aged from the invoice and looks permanently overdue or is ignored | Completion certificate date, defect liability period end, retention deducted on each bill, release date |
| 3. Whose delay was it, ours or the client's? | A status of "pending" does not say whose desk holds the bill | Submitted and certified dates, the contract's certification window, the user or team at each step |
| 4. What did each wait cost? | The ERP holds amounts and dates, not a cost per day of waiting | Amount and the two dates, plus a cost of funds you set |
| 5. Which vendor credit is unused? | A paid-invoice list may not carry the credit days the terms allowed; check your own report | Vendor invoice date, due date or credit terms, payment date |
| 6. Which client pays habitually late? | An ageing report is one moment in time. A habit needs the due date and the paid date of many bills | Invoice date, due date, payment date, per bill and per client |
Sources: question 1 and the resubmission point follow the Crestline glossary entries for RA bill and certification lag. Question 2 follows the retention money and defect liability period entries. Question 3 follows the client lens in Crestline's product brief, which splits days between the contractor's desk and the client's. Questions 5 and 6 follow the vendor and client views in the same brief. Field names in the last column are generic descriptions, not field names from any ERP. Reviewed 29 October 2026.
How can you check these six questions in your own ERP?
Export one row per event with a case id, an activity and a date, then subtract one date from the next within each case. Crestline's glossary names the minimum for an event log as a case id, an activity and a timestamp, with an amount added so a delay can be priced.
- Export the dated events for one process, starting with RA bills from the date the work was executed. Keep every rejected submission.
- Sort by case and date, then subtract each date from the next to get the wait at each step.
- Report the median and the P80 (the value 80 per cent of cases fall under), not the average. A median of 11 days with a P80 of 34 is a different problem from a median of 11 with a P80 of 14 (glossary, certification lag).
- Check how the dates were entered. Approvals keyed in bulk on a Friday for a week's work hide the real wait (glossary, event log).
The step-by-step method is in where cash is stuck in my projects and how to find it, and the RA bill case is in how to find working capital stuck in RA bills. For a few projects, a spreadsheet and one person who knows why each bill is late may be enough. This is a judgment, not a measured rule.
What does a wait cost?
A wait costs the cash held, multiplied by the cost of funds, for the days it is held. On the glossary's sample project, ₹2.15 Cr of retention still outstanding 14 months after handover costs about ₹24 lakh a year at 11% a year, or about ₹2 lakh a month. This is sample data, not a client figure.
| Line | Sample value | Basis |
|---|---|---|
| Retention outstanding 14 months after handover | ₹2.15 Cr | Crestline glossary, retention money entry (sample) |
| Cost of funds | 11% a year | Assumption used in the glossary's cost of delay entry |
| Cost of holding for one year | about ₹24 lakh | ₹2.15 Cr × 11% = ₹23.65 lakh |
| Cost of holding for one month | about ₹2 lakh | ₹23.65 lakh ÷ 12 = ₹1.97 lakh |
As of 29 October 2026. The rupee figure is a modelled cost used to rank waits, not an accounting entry, and changing the 11% to your own cost of funds moves it in proportion (cost of delay). Whether and when retention is released is set by the contract, so check your contract and current law.
Where does Crestline fit, and where does it not?
Crestline is process intelligence software for EPC and construction finance teams. Crestline reads the ERP event trail read-only, rebuilds the path each RA bill, retention release and vendor payment took, and prices each wait in rupees with the step and an owner named. Crestline fits a finance team that has the six questions above and no time to build them by hand.
- Grey Infra ERP is the only live connector today. SAP, Oracle, Tally and spreadsheet upload are not yet available; ask on the scoping call whether another system can be scoped.
- Crestline has no published go-live time. The timeline is set on the scoping call.
- Crestline syncs hourly, so it is not a real-time monitor.
- Your ERP reports remain the record. Crestline measures the gaps between the dates they hold.
The method is on the process mining for EPC finance page. To compare tools, read how to choose a process mining tool for an EPC company or the comparison of process intelligence software for construction. For the wider picture, read how a construction company frees trapped working capital. To see these six questions answered on your own data, book a Crestline demo.
What is Crestline not?
Crestline is not an ERP and replaces nothing you run. Crestline is also not:
- Accounting software. Crestline holds no ledger and issues no invoice.
- Project management or scheduling software.
- A write-back or automation tool. The connection is read-only, and Crestline never writes to your systems.
- A legal service. Crestline does not tell a contractor what a contract entitles it to.
Key takeaways
- An ERP report shows the state of each record. Stuck cash sits in the gaps between dates on the same record.
- Six questions need those dates: time at each step, retention age, whose delay, cost of the wait, unused vendor credit and habitual late payers.
- Confirm the field names in your ERP, then export the dates, subtract, and report the median and P80.
- On the glossary sample, ₹2.15 Cr held at 11% a year costs about ₹24 lakh a year.
- Grey Infra ERP is the only live connector today; SAP, Oracle, Tally and spreadsheet upload are not yet available, ask on the scoping call.
FAQ
Why does my ERP show a profit while project cash is short?
Where revenue is recognised as work is done, cash still arrives only when money is received. The gap sits in work not yet invoiced, bills awaiting certification and retention held, none of which is cash yet. Which of them holds the most on your projects is the thing to find.
Can I answer these six questions in a spreadsheet?
Yes, for a few projects. Export the dated events, subtract dates within each case and report the median and P80. The work grows with the number of bills and projects, and a spreadsheet will not catch a bill that went round twice unless every rejected submission was kept.
Does Crestline replace my ERP reports?
No. Crestline reads the ERP event trail read-only and replaces nothing. Your reports and ledger stay where they are, and Crestline adds the time each document waited at each step and what the wait cost.
- Process intelligence