In a working capital discussion the cash position often looks robust: the bank balance has climbed steadily through the year and short-term borrowing requirements have fallen. When the advance ledger is opened in the same meeting, however, a material portion of that balance turns out to relate to orders not yet delivered, another portion sits against jobs whose delivery dates have already passed, and a small but non-trivial residue remains from orders that were cancelled outright. Management rarely characterises this picture as a problem, since the money is in the account and no customer has yet asked for it back. What is actually in question in this line item, though, is not where the cash sits but under what conditions it stays with whom — a question that seldom appears anywhere in the company's own management reporting.
The first document requested at the review table is not the cash flow statement but a schedule of the contractual clauses that generate advances: what percentage applies to which customer, which event converts the advance into earned consideration, whether delay triggers a refund carrying interest, and whether a change in shareholding requires customer consent under contracts carrying advances. The typical answer to this request is not a document but an average — that advances of roughly thirty per cent are collected, that a standard practice exists. The average is itself a finding, because the existence of a policy is demonstrated through thresholds and exception records, never through central tendency. What the existence dimension tests is not whether advances are collected, but whether the advance has been constituted internally as a defined rule.
Taken on its own terms the mechanism is highly functional, which is exactly why it is so widespread. Collecting ahead of delivery reduces the working capital requirement directly, funds the fixing of input prices, distinguishes a serious order from a costless expression of intent and thereby protects production planning, and pulls collection risk forward of delivery. The difficulty lies not in the mechanism but in the fact that the rule does not move when the conditions under which it was built change: an advance easily secured while demand is strong becomes the first term relaxed once competition hardens, by which point the cash structure has already become dependent on it. As the advance stock grows, the company drifts toward a configuration financed by its customers' payment calendars rather than by its own margin — a configuration that inverts the moment order intake slows, with cash draining considerably faster than profitability deteriorates.
There is a structural reason why advance percentages are conceded so readily in negotiation. The decision-maker on the sales side is measured on unit price; a price reduction appears immediately in the gross profit report and must be explained, whereas moving the advance from forty per cent to fifteen leaves no trace in any margin report whatsoever. Payment terms being the only concession a salesperson can grant without touching their own performance indicator, every negotiation conducted under price pressure predictably surrenders that ground first. The choice is rational to the extent that it preserves the order in the near term; the institutional cost accumulates not in individual contracts but in the aggregate lengthening of the cash cycle produced by two or three years of that choice being repeated without record. This is precisely what the implementation dimension examines: how closely the written percentage tracks the percentages actually appearing in executed contracts.
The configuration typically observed on the ownership side is one in which the advance is split across functions. The customer relationship belongs to sales, the cash to finance, the delivery commitment to operations; the advance policy, sitting at the intersection of all three, belongs in practice to none of them. When an exception is requested, the decision emerges not from an authority matrix but from the seniority of whoever happens to be in the room, and the founder frequently fills that gap with a signature. The consequence is less the decision itself than its untraceability: six months later, neither finance nor sales can reconstruct which customer was granted a waiver and on what grounds. An unowned area of this kind produces not merely an implementation gap but a direct form of founder dependency.
The measurement dimension is usually the weakest link, since the indicators that could be constructed for advances have generally never been defined. Advance coverage by order, the ratio of the advance balance to the value of undelivered orders, the ageing of advances against overdue delivery dates, the elapsed time from advance to earned revenue, and the volume of exceptions granted in the period — none of these five appear in standard financial statements and each must be built deliberately. Without them the company cannot state how much of its own cash position is unencumbered, and a management team unable to answer that question is placed a grade lower on forecasting reliability. Where quantitative tracking is absent, the acquirer fills the gap with an assumption, and such assumptions are calibrated against the seller as a matter of course.
The channel through which this gap reaches valuation is largely a single one: the bridge from enterprise value to equity value. Unearned customer advances, in the standard form of the argument, are treated as debt-like rather than cash-like and are deducted in that bridge, on the reasoning that the acquirer assumes the cost of delivering those orders after closing without receiving the corresponding consideration. The same logic operates in the normalised working capital peg: a reference set against a period of unusually elevated advance balances flatters the seller in the closing accounts, but where seasonality cannot be evidenced the reference period migrates toward an average of the buyer's choosing, and the difference comes straight out of the price. A properly maintained advance ledger, reconciled to the delivery schedule, is the seller's only concrete argument in that negotiation.
The second channel concerns the security instruments issued against advances. In companies serving corporate buyers and public counterparties, advances rarely arrive unencumbered; advance payment guarantees are issued in exchange, and those letters consume the company's non-cash limit with its banks. Because the burden does not appear on the balance sheet, management reads the cash structure as stronger than it is, whereas the narrowing of available limits materially affects transaction structuring when post-closing investment financing is being arranged. A guarantee inventory that is not reconciled against contracts and delivery progress also results in letters not being retrieved on completed jobs, which translates into years of unnecessary commission payments and limit blocked to no purpose.
The third channel is contractual and affects the closing timetable. In a meaningful proportion of advance-bearing contracts the refund trigger is tied to delivery delay, in some the change of control requires customer consent, and in others the advance becomes earned only upon a unilateral declaration of acceptance. Individually these clauses appear minor; in aggregate they produce a measurable effect on conditions precedent, the scope of representations and warranties, and the escrow percentage. Where the contract inventory has not been extracted clause by clause, the acquirer prefers to wait rather than price the unknown, and that preference extends the timetable not by weeks but by months.
The intervention that neutralises these tendencies is built through institutional architecture rather than individual discipline, and separates into four components. The first is a written advance policy defining thresholds by customer segment and order size, with an explicit approval hierarchy for exceptions. The second is a single record, reconciled monthly, that maps each advance balance to its contractual clause, its delivery milestone, and its guarantee letter reference. The third is a narrow indicator set comprising coverage by order, the ageing of advances past their delivery date, and the periodic volume of exceptions. The fourth — routinely omitted — is that exceptions are logged at the moment of request rather than the moment of approval; in a system that records only approvals, rejected requests remain invisible, and the actual bindingness of the policy can therefore never be measured.
BEIREK typically structures its intervention here around three records and a single rhythm. We rebuild the advance ledger mapped to contractual clauses and delivery milestones, reconcile the guarantee letter inventory against that same ledger, and add to the management pack a bridge that separates total cash into the company's unencumbered cash and cash conditionally belonging to customers; that bridge is attached to the monthly close rather than run as a standalone exercise. Exception requests, whether granted or refused, are recorded at the point of request together with the rationale and the requester, and their volume and distribution are brought onto the management agenda at period end. In transaction preparation we additionally model the counterparty's likely position on how the advance balance will be treated within the net debt definition, since a line item argued for the first time at the negotiating table predictably closes at a worse price than one prepared in advance.
The test of the continuity dimension lies not in the existence of a policy but in whether the same exception request meets the same threshold on a day the founder is absent, and whether that response can be evidenced from a record six months afterwards. What determines a company's valuation is frequently not the cash generation performance itself but the demonstrability of that performance being reproducible independently of particular individuals; customer advances are among the line items where this demonstration is tested in its most exposed form, touching contract, collection, and delivery commitment simultaneously. A management team that cannot answer with documentation how much of the money in the account actually belongs to the company has, by that failure, assumed assumption risk across every remaining question as well.