# Crestline See where your project cash is stuck. Get it back. > Crestline is process intelligence software for EPC and construction companies. It reads the event log your ERP already writes, rebuilds the real path every RA bill, purchase order and vendor invoice takes, and prices each delay in rupees, naming the step, the owner and the next move. Category: process mining / process intelligence software. For CFOs and finance teams at EPC and construction companies. Read-only · Live in 15 days · Works with your ERP. Offices: Pune. Markets: India · GCC. ## What Crestline is NOT - Not an ERP, and not accounting software. Crestline holds no ledger and issues no invoice. It reads what your ERP already recorded and replaces nothing you run. - Not project management or scheduling. It does not plan the work or hold the programme. It measures what happened to the money after the work was done. - Not a general-purpose process mining platform. It is built for EPC and construction finance: RA bills, retention, variations, subcontractor payments. For a manufacturing shop floor or a call centre, a general platform such as Celonis or a PM4Py-based build will fit better. - Not a write-back or automation tool. The connection is read-only by design. Crestline raises the finding and tracks the ticket; the change is made by your team in your systems. ## How it works 01. We connect to your ERP Read-only. Your data and processes stay exactly as they are. 02. We show where money waits Every RA bill, vendor payment and approval: how long it sits, and with whom. 03. We tell you what to fix A weekly list ranked by rupee impact, tracked until the cash comes in. ## The five lenses ### 01 · Working capital The money a project eats before it pays you back. Cash spent but not yet collected, and when you will need the bank to cover it. What the AI reports: Funding need peaks in December. Action: Chase Client A's two oldest certified bills this week. (owner: Commercial head) ### 02 · Order-to-cash From work done on site to money in the bank. Measure → RA bill → certify → invoice → collect → retention. What the AI reports: Certification takes 23 days against 14 in the contract. Action: Escalate Client A's 6 oldest bills; attach measurements to every RA bill. (owner: Commercial head) ### 03 · Procure-to-pay From a site's material request to the vendor getting paid. Indent → PO → GRN → bill → match → payment. What the AI reports: Vendor payments leave before they are due. Action: Hold every vendor payment to its due date from the next run. (owner: AP lead) ### 04 · Client Which clients pay slow, and why. Contract terms against how each client actually pays. What the AI reports: Client A pays 88 days past terms, every month. Action: Move Client A to a monthly statement and escalate at 30 days. (owner: Commercial head) ### 05 · Vendor Which vendors cost more than their rate. Price and credit, priced together at your cost of funds. What the AI reports: Vendor B is 1.4% cheaper once credit is priced in. Action: “Ask Vendor A to match the 60-day credit it gives your other site on TMT bar.” (owner: Procurement head) ## Inside the app What your finance team sees every day. The real process, where it waits, and a short list of what to do next. The process map shows frequency, duration, cash for every step, and each panel carries its own actionables with a named owner. Pages: Process Map, Overview, Working Capital, P2P · Cash Out, Vendors, O2C · Cash In, Client, Alerts & Tickets, Performance, Project Hierarchy. ## Crestline AI An AI CFO auditor that never makes up a number. Every figure is computed from your ERP. The AI reads it, names the owner, and follows up until it moves. - AI CFO auditor: Finds where the process leaks, and whose desk it's on. A finding becomes a ticket, and a ticket closes only on re-measurement (Ticket raised → Reminders → Re-measured → Verified). - Ask any chart: answers a question about a chart from that chart's own figures. - Cash cycle simulator: Computed, not AI Test the fix before you make it. - Vendor deal advisor: Buy on total cost, not the quoted rate. ## Security We read your books. We never write to them. Your ERP stays exactly as it is. - Read-only access (Enforced): No postings, approvals or edits. The login simply can't. - Every sync on record (Hourly): Hourly syncs, listed in settings for your IT team. - ISO 27001:2022 (In progress): Certification in progress with an accredited body. - Where data lives (Your choice): [Hosting region and options for India and the UAE.] ## Pricing Custom Let's talk. One plan, shaped to your company the processes you run, the systems you use, and the scale you need. Tell us about your setup and we'll design the best-fit scope and price. Included: Unlimited processes; Conformance checking + root-cause; Real-time alerts & monitoring; Custom KPI builder + query console; Realized-Impact Ledger · REST API; Simulation & scenario analysis; SSO / SAML + SCIM · advanced RBAC; Audit logs · data residency; SDK / notebook · dedicated support; Custom process & connector scope; Custom integrations & data pipelines; Bespoke security & compliance reviews; Dedicated solutions engineer; Volume & multi-year pricing; Unlimited analyst seats & free viewers. ## Questions **What is Crestline?** Crestline is process intelligence software for EPC and construction companies. It reads your ERP read-only, rebuilds how work actually flows through billing, approvals and payments, and prices every delay in rupees with a named owner. **What is process mining, in plain words?** Process mining rebuilds the real map of how work flows by reading the timestamps your software already records, rather than by asking people how they think it works. Crestline mines your ERP's event log and then prices what each delay costs. **Does Crestline replace SAP, Tally or our ERP?** No. Crestline is read-only and replaces nothing. It sits on top of the systems you already run, reads the trail they write, and never writes back to them. **How long does it take to go live?** About 15 days from the read-only connection being approved. The first process map and the first ranked list of delays come out of that first sync. **What does Crestline actually find?** Where cases wait longest, which stretches get repeated, which controls get skipped, which clients pay slowest and where cash leaves earlier than the agreed terms required. Each one is priced from your own volumes and waiting times. **Who is Crestline not for?** Crestline is built for EPC and construction finance: RA bills, retention, variations, subcontractor payments. For a manufacturing shop floor, a contact centre or a global multi-process rollout, a general process mining platform will fit better and we will say so on the call. **What does it cost?** One plan, scoped to your processes, systems and scale. There is no list price, because the scope decides it. Tell us your setup on the call and we will price it there. **Is our data safe?** The connection is read-only throughout, and data is held per tenant with separate encryption. Crestline never writes to your systems and never moves data between customers. ## Talk to us Bring one question about your cash. We'll answer it from your own data. With Rajat Kate, founder. For CEOs and CFOs of EPC and construction companies. - Book a call: https://www.crestlineintelligence.com/book-a-demo - Email: info@crestlineintelligence.com ## Process mining and process intelligence, defined **What is process mining?** Process mining is a technique that rebuilds the real map of how work flows through a business by reading the timestamps its software already records, instead of by asking people how they think it works. Every system stamps a time on what it does: an RA bill submitted on the 3rd, certified on the 19th, paid on the 27th. Collected together, those stamps are an event log, and the log shows the path each case actually took including the detours, the rework and the steps that were skipped. The diagram on the wall shows six steps; the mined map usually shows sixty paths. **What is process intelligence?** Process intelligence is process mining plus the money: it rebuilds how work actually flows and then prices each delay, so the output is a ranked list of what to fix rather than a diagram to admire. Process mining answers 'what is the real process'. Process intelligence answers 'what is it costing, who owns it, and what happens next'. Crestline joins the same event log to volumes, contract values and a cost of delay you set, so each slow or repeated step earns a figure and the worst ones sort themselves to the top. **How is process mining different from a BI dashboard?** A dashboard shows the numbers you already track; process mining shows the number nobody is tracking: where work quietly stalls, gets redone or skips a step, and how long each case waited there. A dashboard is built from a question somebody already thought to ask, and it aggregates. Process mining starts from the journey of a single case and works up, so it surfaces the paths nobody designed and nobody is reporting on. The two are complements: the dashboard tells you receivables are up, the mined map tells you that certification is where they are sitting. ## What process mining surfaces on a project - **Bottleneck** The step where cases wait longest, which sets the speed of the whole process. Certification on order-to-cash; approval on procure-to-pay. - **Rework loop** A stretch the same case travels more than once: rejected, corrected, resubmitted. Measurement sheets returned at client review. - **Skipped step** A case that bypassed a control the process requires. A payment released before the goods receipt was entered. - **Hidden handoff** An exchange between two teams that no document records, visible only as an unexplained wait. Site to billing, and billing to finance. - **Early payment** Cash leaving before the agreed terms required it, for no discount in return. Vendor payments cleared well inside terms. ## More questions **Does Crestline replace SAP or my ERP?** No. Crestline is read-only and replaces nothing. It sits on top of the ERP you already run, reads the event trail it writes, and never writes back to it. **Which systems can Crestline read?** Anything that can export an event log with a case, an activity and a timestamp: SAP, Oracle, Tally, Zoho, a project accounting system, or a plain spreadsheet export. The column mapping is done once during setup. **How long does it take to see results?** Crestline is live in about 15 days from the read-only connection being approved. The first process map and the first ranked list of delays come out of that first sync. **Do I need a data team to run it?** No. The work in setup is getting read access approved and confirming which fields mark a case, a step and a time. There is no data warehouse to build and no model to train. **How accurate are the rupee figures?** The map is exact, because it is rebuilt from your real events. The rupee figures are grounded estimates: they use your real waiting times and volumes with a cost of delay you set, so they rank the list reliably but should never be read to the rupee. **Is process mining the same as process intelligence?** Process mining is the technique that rebuilds the real process from event data. Process intelligence is that map plus the money and the ownership: the priced, ranked list of what to fix. Crestline does both, and the second is what finance acts on. **Where is our data stored?** Data is held per tenant with separate encryption, and the connection to your ERP is read-only throughout. The full detail is on the security section of the homepage and in the security policy. **Is Crestline an alternative to Celonis?** For EPC and construction finance, yes. Crestline is built around RA bills, retention, variations and subcontractor payments, and is priced and scoped for a single business rather than an enterprise programme. For manufacturing, shared services or a global multi-process rollout, Celonis is the better fit and we will say so. ## Writing (5) ### Mobilisation Advance in EPC Contracts: Recovery, Guarantees and Cost https://www.crestlineintelligence.com/blogs/mobilisation-advance-epc A mobilisation advance looks like free cash at the start of a project. This guide covers CPWD and central government rules on interest, recovery from RA bills and bank guarantee cover, the GST position, and a worked example of what the advance really costs. ### DSO for Construction Companies: Why the Standard Formula Hides Your Real Collection Time https://www.crestlineintelligence.com/blogs/dso-for-construction-companies Standard DSO starts at the invoice, but on an EPC project measurement and certification happen before an invoice exists. This guide shows contractors how to calculate DSO from work execution, separate retention, and find the days they can actually remove. ### How to Find Working Capital Stuck in RA Bills: EPC CFO Guide https://www.crestlineintelligence.com/blogs/find-cash-stuck-in-ra-bills Most trapped working capital in an EPC company sits inside the running account bill cycle, before an invoice exists. This guide shows EPC CFOs how to measure each stage and find it. ### Retention Money in Construction: Cost and Early Release https://www.crestlineintelligence.com/blogs/retention-money-construction-india Retention money is earned revenue the client holds until the defect liability period ends. This guide covers typical rates, release rules under CPWD conditions, the accounting treatment, and how to stop it going unchased. ### Process mining for construction: what it is, where it pays https://www.crestlineintelligence.com/blogs/process-mining-for-construction Process mining rebuilds how RA bills, purchase orders and vendor invoices actually move through an EPC company, from the timestamps the ERP already records. Here is what it needs, where it pays, and which tool fits which contractor. ## Glossary 28 terms ### Process mining (also: process discovery, automated process discovery) https://www.crestlineintelligence.com/glossary/process-mining Process mining is a technique that rebuilds the real map of how work flows through a business by reading the timestamps its software already records, rather than by asking people how they think it works. Every system stamps a time on what it does: an order raised at 09:14, an invoice approved at 16:02 on Thursday, a payment released eleven days later. Process mining collects those stamps into an event log and draws the path each case actually took. The result is the process as it happened, including the detours, the loops and the steps that were skipped. Why it matters: The map on the wall shows six steps. The mined map usually shows sixty paths, and the cash is sitting in the ones nobody drew. You cannot fix a delay you have never seen. Where it misleads: Process mining only sees what a system recorded. Work that happens over WhatsApp, on site, or in an inbox leaves no stamp, so it appears in the map as one long unexplained wait rather than as the three approvals it really was. That gap is a finding, not a failure but it has to be read as one. ### Process intelligence (also: process analytics) https://www.crestlineintelligence.com/glossary/process-intelligence Process intelligence is process mining plus the money: it rebuilds how work actually flows and then prices each delay, so the output is a ranked list of what to fix rather than a diagram. Process mining answers 'what is the real process'. Process intelligence answers 'what is it costing, who owns it, and what happens next'. The same event log is joined to volumes, rates and cost of delay, and each slow or repeated step earns a figure in rupees. Why it matters: A process map is a poster. A priced process map is a budget conversation. Finance acts on the second one. Where it misleads: The map is exact; the money is a grounded estimate. It uses your real waiting times and real volumes, but the cost of a day's delay is an assumption you set, and a different assumption moves the ranking. Any tool that presents the rupee figure as measured rather than modelled is overselling. ### Event log https://www.crestlineintelligence.com/glossary/event-log An event log is the raw material of process mining: a table where every row says which case moved, which step happened, and when. Three columns are enough. The case is the thing travelling: an RA bill, a purchase order, a vendor invoice. The activity is the step that happened to it. The timestamp is when. Everything else is optional colour: amount, owner, vendor, project. Formula: case id + activity + timestamp. Anything that can export those three columns can be mined: SAP, Oracle, Tally, a ticketing system, or a spreadsheet. Why it matters: Your systems have been writing this log for years whether or not anyone reads it. It is the only record of what actually happened that nobody edited afterwards. Where it misleads: A log is only as honest as the moment the stamp is written. If an approval is entered in bulk on Friday for work done all week, the log shows one Friday spike and the real waiting time is invisible. Backdated entries are the single most common reason a mined duration is wrong. ### Case (also: case ID) https://www.crestlineintelligence.com/glossary/case A case is the single thing whose journey is being followed through a process: one RA bill, one purchase order, one vendor invoice, identified by an ID that stays the same from first step to last. Choosing the case decides what the map is about. Follow the purchase order and you see procurement. Follow the invoice and you see payment. Follow the RA bill and you see how site work turns into money. Why it matters: Most arguments about a process map are really arguments about the case. Two teams looking at the same delay from different case IDs will describe two different problems. Where it misleads: A case that changes identity mid-flight, say a requisition that becomes a PO with a new number, breaks the trail, and the journey appears as two short processes instead of one long one. The join has to be made explicitly or the waiting time in between simply disappears. ### Bottleneck https://www.crestlineintelligence.com/glossary/bottleneck A bottleneck is the step in a process where cases wait longest, so the speed of the whole process is set by it and by nothing else. Waiting time is measured between steps, not inside them. A step that takes two minutes to perform but sits four days in someone's queue is a four-day bottleneck. Making the rest of the process faster changes nothing until that queue moves. Why it matters: Effort spent anywhere other than the bottleneck produces no improvement at all. It is the one place where a week of work returns a week of cash. Where it misleads: The longest wait is not always the most expensive one. A step that holds ten cases for thirty days matters less than one holding four hundred for six. Rank bottlenecks by total value held, not by duration, or you will fix the slow step that no money passes through. ### Rework loop https://www.crestlineintelligence.com/glossary/rework-loop A rework loop is a stretch of a process that the same case travels through more than once: sent back, corrected and resubmitted. It is usually the largest single source of hidden delay. In the map it appears as an arrow pointing backwards: measurement sheet rejected, corrected, resubmitted. Each pass costs the full waiting time again, and the case that goes round three times takes three times as long as the plan assumed. Why it matters: Rework is invisible in every status report, because the status is correct each time it is reported. Only the journey shows that the case has been at that status before. Where it misleads: Not all loops are waste. One extra check on a high-value certification may be cheaper than the dispute it prevents. The loop worth removing is the one that repeats for the same cause, such as a missing document or a wrong rate, and that cause is the finding, not the loop. ### Conformance checking https://www.crestlineintelligence.com/glossary/conformance-checking Conformance checking compares the process as it actually ran against the process as it was supposed to run, and lists every case that departed from it. The intended path is defined once: request, approve, receive, match, pay. Every case is then replayed against it. Cases that skipped a step, ran steps out of order, or added one appear as named deviations with a count and a value. Why it matters: A payment made before the goods receipt is not a process opinion, it is a control failure with an amount attached. Conformance turns policy into something that can be counted. Where it misleads: A high deviation rate is often a sign that the written process is wrong rather than that the people are. Before treating deviations as violations, check whether the majority path is the one the business actually intends. ### Throughput time (also: cycle time, lead time) https://www.crestlineintelligence.com/glossary/throughput-time Throughput time is the total elapsed time from the first step of a case to its last, including every queue, weekend and rework pass, not just the time somebody was working on it. It is measured on the clock, not on the timesheet. If an invoice arrives on the 2nd and is paid on the 27th, its throughput time is 25 days regardless of the forty minutes of actual work inside it. Formula: throughput time = timestamp of last activity − timestamp of first activity. Report the median as well as the mean. One case stuck for a year moves the mean and tells you nothing about the typical case. Why it matters: Working capital is throughput time wearing a currency sign. Every day a case is open is a day the cash behind it is unavailable. Where it misleads: Throughput time says nothing about where the time went. A 25-day invoice with one 23-day queue and a 25-day invoice with five 5-day queues need completely different fixes, and the headline number cannot tell them apart. ### Cost of delay https://www.crestlineintelligence.com/glossary/cost-of-delay Cost of delay is what one more day of waiting costs at a particular step, and it is what turns a process map into a ranked list of things worth fixing. It is built from what the delay actually causes: cash borrowed to cover the gap, early-payment discounts missed, penalties incurred, work redone. Multiply that daily cost by the waiting time and the volume of cases passing through, and each step carries a figure. Formula: cost of delay = days waited × cases affected × cost per case per day. The last term is the assumption. State it, and let anyone who disagrees change it and see the ranking move. Why it matters: Without it, every bottleneck looks equally urgent. With it, the top three are obvious and the rest can wait. Where it misleads: It is a modelled figure, not a measured one, and it should never be reported to the rupee. Its job is to order a list correctly, which it does robustly; its precision beyond that is false. ### Working capital https://www.crestlineintelligence.com/glossary/working-capital Working capital is the money tied up in running the business day to day: what customers owe you and what you hold in stock, less what you owe suppliers. On a project it is mostly three things: work done but not yet certified, bills certified but not yet paid, and material bought ahead of need. None of it is lost. All of it is unavailable. Formula: working capital = receivables + inventory − payables. On an EPC project, unbilled work in progress and retention money belong in receivables even where the balance sheet parks them elsewhere. Why it matters: A profitable project can still run out of cash. Working capital is the difference between the two, and it is the number that decides whether the next mobilisation is funded by the client or by the bank. Where it misleads: The balance-sheet figure is a single photograph taken on the last day of a period, which is exactly when everyone is pushing to make it look better. The daily average across the period tells the truth; the closing figure tells the story. ### Cash conversion cycle (also: CCC) https://www.crestlineintelligence.com/glossary/cash-conversion-cycle The cash conversion cycle is the number of days between paying for something and being paid for the work it went into. It is the length of time your own money is funding the project. It combines three waits: how long stock sits, how long customers take to pay, and how long you take to pay suppliers. The third one is subtracted, because a supplier waiting is a supplier financing you. Formula: CCC = DIO + DSO − DPO. Days inventory outstanding, plus days sales outstanding, less days payables outstanding. Why it matters: Every day of the cycle is a day of borrowing. Taking ten days out of a 70-day cycle on a project turning over ₹100 crore a year frees roughly ₹2.7 crore of cash permanently, without selling anything more. Where it misleads: A cycle can be shortened by simply paying vendors later, which improves the number and damages the business: worse rates, slower mobilisation, disputes. Read the cycle with its three parts visible, never as one figure. ### Days sales outstanding (also: DSO) https://www.crestlineintelligence.com/glossary/dso Days sales outstanding is the average number of days between billing a client and receiving their money. It measures the gap on the receivable side alone. On a project, the meaningful version starts at the point work was completed rather than at the point the invoice was finally raised, because the delay before billing is delay all the same. Formula: DSO = (receivables ÷ revenue for the period) × days in the period. Calculate it per client as well as overall. The average hides the one client who is funding themselves with your cash. Why it matters: It is the single clearest measure of whether your clients' payment behaviour is getting better or worse, and it is the number a lender looks at first. Where it misleads: A DSO measured from the invoice date rewards you for billing late. If certification takes three weeks before an invoice can even be raised, a healthy DSO can sit on top of a badly delayed cycle. ### Days payable outstanding (also: DPO) https://www.crestlineintelligence.com/glossary/dpo Days payable outstanding is the average number of days you take to pay a supplier after their invoice is due for payment. It is the mirror of DSO. A longer DPO keeps cash in the business for longer, which is why it is subtracted in the cash conversion cycle, but it is the supplier's working capital that funds it. Formula: DPO = (payables ÷ cost of sales for the period) × days in the period. Compare it against agreed terms, not against zero. Paying at 45 days on 45-day terms is correct; paying at 20 is a gift. Why it matters: Paying earlier than terms is one of the most common and least noticed ways a project leaks cash: money leaves the business before it had to, and nothing is received for it. Where it misleads: A rising DPO looks like an improvement and can be a warning. If it is rising because approvals are stuck rather than because terms were renegotiated, you are not financing yourself, you are accruing a dispute. ### Order-to-cash (also: O2C) https://www.crestlineintelligence.com/glossary/order-to-cash Order-to-cash is the whole run from work being done to the money arriving: on a project, from site execution through measurement, certification and invoicing to receipt. It is the process the receivable lives inside. Mining it end to end shows which of its stages holds the cash: usually certification rather than the client's payment run, which is where everybody looks first. Why it matters: It is the largest single pool of trapped cash on most projects, and the one where a fortnight can be recovered without asking a client for anything. Where it misleads: Order-to-cash is often measured from invoice to receipt, which is the last third of it. Measured that way, the two thirds where the delay actually is never appear. ### Procure-to-pay (also: P2P) https://www.crestlineintelligence.com/glossary/procure-to-pay Procure-to-pay is the run from a site asking for material to the vendor being paid for it: requisition, purchase order, receipt, invoice, match, payment. Mining it shows two things at once: where material requests stall before they reach a vendor, and where payments leave earlier or later than the terms that were agreed. Why it matters: Both ends cost money. A slow front end delays site work; a fast back end spends cash before it needed to be spent. Where it misleads: Purchase orders raised after the invoice has arrived are common and will make this process look fast when read from the PO date. Mine it from the requisition, or the delay before the PO is simply not in the data. ### RA bill (also: running account bill, progress bill, IPC, interim payment certificate) https://www.crestlineintelligence.com/glossary/ra-bill An RA bill is the periodic invoice a contractor raises for work completed so far on a project, measured on site and certified by the client before payment. Running account billing exists because a project takes years and nobody waits until the end to be paid. Each bill covers the quantities executed since the last one, valued at contract rates, less retention and any advance being recovered. Why it matters: The RA bill cycle is the heartbeat of project cash flow. Its length, far more than the client's payment terms, decides when money arrives. Where it misleads: The date on an RA bill is usually the date it was accepted, not the date the work was done or the date it was first submitted. Rejected and resubmitted bills often carry the new date only, which erases the very delay you are trying to measure. ### Retention money (also: retention) https://www.crestlineintelligence.com/glossary/retention-money Retention money is the share of every certified bill, commonly 5 to 10 per cent, that the client holds back as security, releasing it only at completion and after the defects liability period ends. It accumulates across every bill on the project. Half is typically released at practical completion and the remainder at the end of the defect liability period, which can be a year or more later. Why it matters: It is real earned revenue sitting outside the business, often the largest single block of trapped cash on a finished project, and it is the one most often forgotten once the site has closed. Where it misleads: Retention releases are almost never chased automatically, because the project team has moved on and the finance system shows the amount as a receivable with no due date. Ageing it from the completion certificate rather than from the invoice is the only way it surfaces. ### Variation order (also: change order, VO, EOT claim) https://www.crestlineintelligence.com/glossary/variation-order A variation order is work outside the original contract scope that the client has instructed, priced and agreed separately. Until it is agreed, it is work being done for nothing. Variations arise constantly: a design change, a site condition, an instruction given verbally on a Tuesday. Each needs to be notified, priced, agreed and then billed, and each of those steps has its own queue. Why it matters: Unagreed variations are the quietest form of trapped cash on a project. The cost has already been incurred; only the entitlement is missing. Where it misleads: A variation's real clock starts at the instruction, which often exists only in a site diary or an email. Measured from the day it entered the system, the delay looks like weeks when it has actually been months. ### Goods receipt note (also: GRN) https://www.crestlineintelligence.com/glossary/grn A goods receipt note is the record that material actually arrived on site, in what quantity and condition. It is the middle document of the three-way match. It links the purchase order to the invoice. Without it, a payment is being made against a promise and a bill with nothing confirming that anything was delivered. Why it matters: A late GRN is the most common single cause of a delayed vendor payment, and the vendor is usually blamed for it. Where it misleads: GRNs entered in batches at month end make every delivery look as if it arrived on the same day. Where that pattern appears, the material delay in the process map is an artefact of data entry, not of the supply chain. ### Three-way match https://www.crestlineintelligence.com/glossary/three-way-match A three-way match is the control that releases a payment only when the purchase order, the goods receipt note and the supplier invoice agree on what was ordered, what arrived and what is being charged. Any two of the three agreeing is not enough. The match is what stops paying for material nobody received, or paying a rate nobody agreed. Why it matters: Where the match fails, the invoice stops, so mining match failures by cause tells you exactly which vendors, sites or rates are jamming the payment run. Where it misleads: A tolerance set too wide turns the control into a formality; set too narrow it produces hundreds of exceptions that get waved through by habit, which is worse than having no control at all. ### Mobilisation advance (also: advance payment, mobilization advance) https://www.crestlineintelligence.com/glossary/mobilisation-advance A mobilisation advance is money a client pays a contractor before any work has been billed, to fund site establishment and early costs, and it is recovered out of later running account bills rather than being kept. It is a loan dressed as a payment. The contractor gets cash at the start, usually against a bank guarantee, and every subsequent RA bill is reduced until the advance is repaid. On most government contracts it also carries interest. Formula: net payable on a bill = value certified - retention - advance recovery. Recovery is normally a fixed percentage of each bill, so the advance repays itself faster on a project that bills quickly. Why it matters: Taken as free cash it is the most expensive money on the project. Taken as a priced loan it is sometimes the cheapest, because the alternative is working capital at a bank's rate. Where it misleads: Recovery is invisible in revenue. The bill shows the work certified; the cash shows the work certified less recovery. A project that looks like it is collecting well can be collecting almost nothing while the advance unwinds. ### Bank guarantee (also: BG, performance guarantee, advance payment guarantee) https://www.crestlineintelligence.com/glossary/bank-guarantee A bank guarantee is a bank's undertaking to pay the client a stated sum if the contractor fails to meet an obligation, and on an EPC contract there are usually two of them: one securing the mobilisation advance, one securing performance. The bank does not lend money; it lends its promise, against the contractor's credit limit and a fee. The advance payment guarantee covers money already handed over. The performance guarantee covers the job being finished. Why it matters: Guarantees consume the contractor's banking limit, which is the same limit that funds working capital. A guarantee left open after its obligation ended is borrowing capacity sitting idle. Where it misleads: Nobody chases a guarantee's release, because releasing it saves a fee rather than producing cash. Guarantees routinely stay open months past the event that discharged them. ### Security deposit (also: SD) https://www.crestlineintelligence.com/glossary/security-deposit A security deposit is the name Indian government works give to money deducted from each bill and held as security, which is the same mechanism private contracts call retention money. Different word, same cash: a percentage comes off every running and final bill and sits with the client until a release condition is met. The difference is in the detail of the rate, the cap and the release, which are set by the contract rather than by the name. Why it matters: Finance teams track retention and miss security deposit, or the reverse, because the ledger uses one word and the contract uses the other. The money is identical and so is the recovery work. Where it misleads: Do not assume the government rate. CPWD caps the deposit at 2.5% of tendered value, which is far below the 5 to 10 per cent a private EPC contract will deduct, and relief orders have moved these figures before. ### Defect liability period (also: DLP, defects liability period) https://www.crestlineintelligence.com/glossary/defect-liability-period The defect liability period is the stretch after completion during which the contractor must make good defects at its own cost, and it is the clock that decides when the second half of retention is released. Completion does not end the contract. For a defined period afterwards, usually a year, the contractor stays responsible for defects that appear. Only at the end of it does the remaining retention or security deposit fall due. Why it matters: It is the release trigger for the largest block of trapped cash on a finished project, and the only one nobody is watching, because the project team has moved to the next job. Where it misleads: The period runs from a certificate, not from a date in a plan. Where the completion certificate is issued late, the defect liability period starts late and the retention release moves with it, which is a delay the contractor pays for and did not cause. ### Price variation clause (also: escalation clause, price adjustment) https://www.crestlineintelligence.com/glossary/price-variation A price variation clause adjusts the contract rate when the cost of labour, fuel, steel or cement moves during the contract, so that a multi-year project is not priced on the day it was tendered. The clause names the inputs it covers, the index each one is measured against and the period between adjustments. On a long project it is the difference between a margin and a loss, and it is claimed, not granted. Why it matters: The adjustment is only paid if it is claimed, with the index figures, inside the window the contract allows. An unclaimed escalation on a three-year job is a straightforward loss on work already done. Where it misleads: The formula, the indices and the covered inputs differ between contracts, and a clause can be excluded entirely. There is no standard rate to assume; the clause itself is the only source. ### Unbilled revenue (also: unbilled WIP, contract asset, work in progress) https://www.crestlineintelligence.com/glossary/unbilled-revenue Unbilled revenue is work a contractor has done and recognised as revenue but has not yet been able to invoice, because the contract makes billing conditional on measurement or certification rather than on time passing. Under Ind AS 115 it is a contract asset: the entity has performed, but its right to payment is conditional on something other than the passage of time. Once the bill is raised and only time stands between it and payment, the same amount becomes a receivable. Formula: contract asset = revenue recognised to date - amounts billed to date. Read it per project. Netted across a portfolio, a project that is badly behind on billing is hidden by one that is ahead. Why it matters: It is the part of the receivable that standard DSO cannot see, because no invoice exists yet. On an EPC project it is often the largest single pool of trapped cash and the one least discussed. Where it misleads: A growing unbilled balance can mean the site is ahead of the billing team, or that measurement is stuck, or that revenue has been recognised on work the client will dispute. The number alone does not say which, and the three have very different consequences. ### Contractor DSO (also: DSO from execution, true DSO) https://www.crestlineintelligence.com/glossary/contractor-dso Contractor DSO is days sales outstanding measured from the day work was executed rather than from the day the invoice was raised, which is the only version that reflects how long a contractor actually waits for money. On a project, measurement, joint certification and client review all happen before an invoice can exist. Standard DSO starts after all of that, so it reports the last stretch of the wait and calls it the whole thing. Formula: contractor DSO = standard DSO + days from execution to invoice. The second term is the one nobody reports. It is also usually the one the contractor can shorten without asking the client for anything. Why it matters: A healthy standard DSO sitting on top of a three week certification wait is the most common way an EPC business convinces itself its collections are fine. Where it misleads: It is not a published benchmark and no lender will ask for it. Its value is internal: compared against your own standard DSO, the gap is the part of the cycle you control. ### Certification lag https://www.crestlineintelligence.com/glossary/certification-lag Certification lag is the time between a contractor submitting an RA bill and the client certifying it, and it is the stretch of the cash cycle that no standard finance report measures. The bill exists, the work is done, and nothing can be invoiced until somebody signs. Because no invoice has been raised, the wait sits outside receivables, outside DSO and outside the ageing report, which is why it survives for years unexamined. Formula: certification lag = date certified - date submitted. Measure the median and the P80. A median of 11 days with a P80 of 34 is a different problem from a median of 11 with a P80 of 14. Why it matters: It is usually the largest single wait on an EPC order-to-cash process, and unlike the client's payment run it can often be shortened by fixing what gets submitted rather than by asking the client for anything. Where it misleads: This is a measure, not a contractual term; a contract will talk about a certification period or a review window instead. And a resubmitted bill often carries only its new date, which erases the rejected pass and makes the lag look shorter than it was. Every figure shown on the site is sample data, labelled as such. Crestline prices delays from your own ERP; a figure nobody computed is a figure nobody prints.