Telecom subcontractors: the 4 categories of statement discrepancies costing you money every month

In late July, the manager of a fibre connection company sits down one evening to do what nobody enjoys doing: comparing the production statement sent by his client with what his teams actually completed that month. Two hours later, the finding is clear: nine interventions completed, validated, photographed — missing from the statement. €4,310 that no one would ever offer to pay, because it was up to him to claim it.

That evening was nothing out of the ordinary. It's the standard mechanics of telecom subcontracting: the statement is drawn up by the client, from their own systems, and it stands as fact unless someone disputes it. The good news is that discrepancies aren't unpredictable: they always fall into the same four categories. Knowing them means already knowing where to look.

Why the statement is "always right"

In traditional construction, the company draws up its own work statements and invoices accordingly. In telecom subcontracting, the logic is reversed: the client does the counting. You're not paid for what you did — you're paid for what their statement says you did.

The system isn't dishonest, it's fallible. Between your technician's report and the line on the statement, the information passes through several tools and several people: a closure entered late, a task code misreported, a rework never coded, a duplicate reference. Each link loses a bit of information, and the loss is rarely in your favour.

The subcontracting agreement almost always includes a dispute deadline — often 30 to 60 days after receiving the statement. Once that deadline passes, a discrepancy is no longer a dispute: it's a straight loss. The monthly check isn't paperwork, it's a deadline.

Category 1 — missing interventions

The most frequent, and the most costly. The intervention was carried out, the report exists, the photos are timestamped — but the line appears nowhere in the statement. Typical causes: a closure left pending in the client's system, an "Act/Prod - ND" reference re-entered with a typo, or an intervention reassigned between two periods and lost in the gap.

As a rough order of magnitude: in the statements we see, missing interventions alone account for 2 to 5% of the monthly revenue of a company that doesn't check. On €80,000 of production, that's €1,600 to €4,000 a month sitting idle — not rejected, simply never counted.

Category 2 — underpaid interventions

The line exists, but at the wrong rate. Typical case: a connection billed under the "simple building" code at €78, when the report documents civil engineering rework that the price schedule codes at €210. Discrepancy: €132 on a single intervention — invisible if you only check that the line is present.

Underpaid lines are the hardest to detect by hand, because they require cross-checking each line against two sources: the field report (what was actually done?) and the contract's price schedule (what is it worth?). That's exactly the cross-check nobody has time to do line by line.

Category 3 — overpaid interventions

Counterintuitive, but real: some lines are paid twice, or at a rate higher than the price schedule. The temptation is to say nothing. That's a management mistake: the client almost always ends up noticing, and the adjustment then lands all at once, on a later statement, exactly when you're not expecting it — sometimes several thousand euros withheld in one go from your cash flow.

Spotting overpaid lines isn't about refunding them spontaneously: it's about setting money aside, so the adjustment never turns into a surprise cash flow gap.

Category 4 — orphan lines

The mirror image of missing lines: statement lines that don't correspond to any intervention by your teams. An unknown reference, a mutualisation point nobody visited, another subcontractor's intervention mistakenly assigned to your account.

A paid orphan line isn't a gift: it's a line you won't be able to justify the day the client audits their statements. Every orphan deserves a written clarification — this is the category that protects your business relationship more than your margin.

The method for detecting them by hand

Nothing magic, just rigour — and a non-negotiable monthly appointment:

• Export the list of completed interventions for the month from your tracking system, with the exact reference, date, task code and expected amount for each.
• Get the statement in spreadsheet format (insist on it from the client if necessary — a PDF can't be cross-checked).
• Cross-reference the two files by reference: what's on your side but not in the statement are the missing lines; the reverse, the orphans.
• Check the rate of common lines against the price schedule: underpaid and overpaid lines show up here.
• Quantify, write, send the claim before the dispute deadline expires, with reports and photos attached.

Let's be honest about the cost: for a team of ten technicians, this routine takes two to three hours a month when field data is clean — and much longer when references have been entered by hand on loose sheets. That's precisely why most companies don't do it every month. And that's precisely why the discrepancies persist.

What changes when the reconciliation is automatic

All the work described above rests on a single condition: having, on your side, a reliable record of every intervention — reference, tasks completed, evidence. That's the principle behind BL Next: the technician enters data once, on site, and the statement reconciliation happens automatically on import. The four categories come out sorted, each discrepancy is quantified, and the total to claim is ready before the dispute deadline expires.

The manager from the story at the start got his €4,310 back. Not because his client was acting in bad faith — but because, for the first time, he had the figures before the deadline.