Revenue leakage in an IT consulting firm: the four places where billing gets lost before close
In a 50-person IT consulting firm, undetected billing gaps represent 1 to 3% of annual revenue on average. On €5M in revenue, that is between €50,000 and €150,000 in net losses per year, identified too late to be corrected. This figure is a floor: it does not account for amendments not reflected in billing, or discounts applied twice on certain accounts.
The distinctive feature of revenue leakage in an IT consulting firm is that it is structural rather than accidental. The gaps don't come from one-off errors. They come from the absence of line-by-line reconciliation between commercial data, staffing data and billing data. These three referentials are managed in different tools, by different teams, with different update logics. The link between them is almost always manual.
What revenue leakage means in this context
Revenue leakage refers to everything that should have been invoiced and wasn't. Or was invoiced at a lower amount than the contractual amount. In an IT consulting firm, this takes four concrete forms, each with its formation mechanisms and orders of magnitude.
Source 1: the sold budget incorrectly entered into the staffing tool
The salesperson negotiates a 150 man-day package with the client. The negotiation spans three weeks, the final contract has two pages of pricing appendices, and the version that arrives in the CRM is the correct one. But the operational team rarely reads the CRM: they read the purchase order or the summary sent by email, and that is the basis on which the project is configured in the staffing tool.
On a 150 man-day project, a 5 man-day reading error represents 3.3% of volume. At a day rate of €700, that is €3,500 lost on that project. Across 30 active projects per year, if the error occurs on 20% of them with an average gap of 4 man-days, the loss is €8,400. This figure is not alarming in isolation. It is when you add the four sources together.
Source 2: discounts applied twice
A 10% commercial discount is negotiated at the start of the year on the reference day rate. It is correctly integrated into the CRM: the day rate shown for this client already includes the discount. The salesperson moves on to the next project.
Three months later, a new quote is created for the same client. The person creating the quote in the billing tool knows there is a 10% discount on this account, because they remember the negotiation. They apply the discount manually in the quote. The discount is now applied twice: once in the reference day rate, once in the quote. The client pays less than the negotiated price, and nobody detects it until the annual close, when actual revenue is compared against forecast.
This case is particularly frequent in IT consulting firms managing multiple types of discounts: annual volume discount, loyalty discount, one-off commercial discount. When the rules are not centralized and documented in a single referential, double applications occur mechanically.
Source 3: amendments not reflected in billing
A 100 man-day project is extended by 20 additional man-days during the mission. The amendment is negotiated, signed, scanned and archived in the client folder on the shared server. The account manager sends it by email to accounting with the note "for information." Accounting has received it. But the billing tool has not been updated, because the amendment has no automatic update workflow.
The 20 additional man-days are consumed. The final billing is based on the original 100 man-day line. The amendment specified a slightly different day rate (the commercial context had changed between initial signature and extension). The invoice is issued at the initial day rate for 120 man-days instead of an adjusted day rate for the 20 additional man-days.
In this case, the gap can go either way: billing may be lower than contractually agreed (revenue leakage), or higher (client dispute). In both cases, the problem comes from the same place: the amendment did not trigger an update to the billing configuration.
Source 4: staffed days not correctly reported at period close
A consultant enters their days in the staffing tool every Friday. Their project manager validates with a two to three day lag. The month's billing is issued on the first business day of the following month, based on days validated at issuance date.
If three December days are only validated on January 4th, they don't appear in the December invoice. They will appear in the January invoice, mixed with January days, in a context where the client is doing their own reconciliation to validate the invoice. These lags create recurring disputes on early-month invoices, and discussions about days whose operational context has already been forgotten.
On a 15 man-day/month project, a 3-day validation lag represents 20% of monthly volume. This is not a net loss, but it is a recurring cash flow lag and a friction generator with the client.
Why these gaps are only detected at close
Each gap described above is detectable before invoice issuance, provided someone performs a line-by-line reconciliation between CRM data, staffing data and the invoice draft. This reconciliation is almost never done — not through negligence, but because there is no structured process for doing it and time is short.
Detection therefore occurs at monthly close, when actual invoiced revenue is compared against forecast. At this point, invoices have already been sent. Correcting a gap requires a credit note, a new invoice, a client exchange and an accounting correction. The cost of correction is significantly higher than the cost of prevention.
For net losses (revenue leakage proper), monthly close doesn't always reveal them: a discount applied twice may go unnoticed if the client line's revenue is broadly consistent with forecasts. These gaps often only surface at year-end, during the annual reconciliation or audit, when corrections are no longer possible.
What a reconciliation engine detects upstream
A pre-billing reconciliation engine connects the three sources (CRM for contractual terms, staffing tool for days delivered, billing tool for drafts) and applies the verification rules configured during the audit.
For each billing line, verification covers three points: is the amount consistent with the contractual rate for this client at this period, does the number of days billed match the days validated in the staffing tool, do the applied discounts match the discounts configured in the contractual referential.
Any deviation beyond a configurable threshold generates an alert before issuance. Billing is put on hold for the relevant line, presented with its context to the manager for validation or correction. The invoice is issued after validation, not before verification.
Order of magnitude on a portfolio of 50 active projects
On 50 active projects with an average basket of €100,000 per project (€5M revenue), if 15% of projects show a billing gap with an average magnitude of 3% of project value, annual revenue leakage is €22,500. Including discounts applied twice on 10% of accounts at 2% incorrect discount, the additional gap is €10,000. Total: €32,500 per year, not counting unreflected amendments.
This calculation is conservative. IT consulting firms working with complex contracts (variable day rate by profile, tiered discounts, different unit prices by project phase) have structurally higher gap rates because the number of billing rules grows faster than the capacity to verify them manually.
Where to start
Setting up a pre-billing reconciliation engine starts with mapping existing calculation rules: how are day rates configured by profile and by client, where do contractual discounts live, how are amendments formalized and archived, what is the validation lag for staffed days.
This mapping, done during the audit, produces two deliverables: a diagram of the billing process as it exists today (with its break points), and a diagram of the target solution (with verification rules and alert thresholds). It takes three weeks and constitutes documentation that generally didn't exist.
Engine implementation follows over three to eight weeks depending on source complexity and rule complexity. The process is then under a 12-month service guarantee, with a response within 24 hours in the event of outage.
If your IT consulting firm bills on fixed-price, time-and-materials or hybrid contracts, a 30-minute scoping call will verify whether your billing configuration is automatable. Book a scoping call