Framework contracts in road construction: billing hundreds of small jobs cleanly

What makes billing under a framework contract so laborious?

Not the individual job. A Rahmenvertrag is won once it is signed – it is earned through hundreds of individual call-offs a year, every one of which has to be evidenced separately.

The effort comes from the chain: every quantity belongs to an item, every item to a call-off, every call-off to a contract. If that chain breaks anywhere, the client comes back with a query – and the invoice sits.

The terms that have to be kept apart

The call-off is the anchor. Without it there is no way to show later on what basis the work was done.

The process in five steps

1. Import the contract. The bill of quantities arrives as a GAEB file and becomes the item base: numbers, texts, quantities, unit prices. The item numbers stay the ones from the contract – that is not a formality but the language of the later check.

2. Create the call-off. Every order becomes its own transaction under this contract, with date, location and the number under which the client records it.

3. Do the work and document it. The crew works and fills in the Zettel – by hand, signed.

4. Assign the take-off. The quantities are checked and hung on the items. Prices come from the contract, not from a list beside it.

5. Bill monthly. All approved call-offs of the month go out as one XRechnung.

The critical point: remaining quantities

A framework contract contains, per item, a quantity that can be called off. Once used up, the item is exhausted – further work then needs a separate order or a variation.

In practice this is often kept in an Excel file that one person maintains. That works as long as that person is there. If they are on holiday or leave the firm, it is usually the client who notices first that a quantity has been exceeded.

If only one person in the firm can answer any of these four questions, that is a risk – independently of the software in use.

Collective invoice or individual invoices?

Both are possible; the collective invoice is usual. It saves both sides work: you the producing, the authority the checking.

An exception is worthwhile for larger individual call-offs that should be paid earlier – a separate invoice can make sense there. Settle that with the case handler beforehand; some authorities have fixed requirements.

Variations: show them separately

Work the contract does not cover is a variation. Letting it run under the contract items is more convenient and comes to light at the check at the latest.

The clean way is: mark the variation as such, show it separately, document the order. That is more work in the moment and considerably less work in a dispute.

Where the check typically gets stuck

1. Missing call-off reference. The case handler cannot assign the work.
2. Quantity without evidence. The take-off sheet is not enclosed.
3. Item exhausted. The quantity called off exceeds the contract quantity.
4. Price deviation. A different unit price from the contract – usually a transfer error.
5. Wrong Leitweg-ID. The invoice does not reach the authority at all.

The first four can be avoided by making the chain hang together technically rather than organisationally. The fifth is described in the XRechnung details .

What it costs per month

Work it out on your own numbers:

At sixty call-offs, eight minutes each and two hours of remaining-quantity maintenance, that is around ten hours a month. Whether a changeover is worth it is decided by that figure – not by a brochure.

Frequently asked

We have framework contracts with several clients. Does that not get confusing? Only if call-offs are not unambiguously assigned to a contract. With clean assignment it makes no difference how many contracts run in parallel.

How long may we wait before billing? That is in the contract. Independently of it: the longer the gap between the work and the invoice, the harder the query – and the later the money.

What if a Zettel never arrives? Then the work cannot be billed. Which is why a working process makes open call-offs without a take-off visible.

We struggle to follow the German correspondence around orders. What should we do? Fix one thing: every call-off gets a number and a date. Even when the order comes by phone, confirm it afterwards in a two-line email – the elegance of the sentence does not matter, the date and the number being right does. Those two are what the check asks for, not the sentence.

A contract year, worked through

A framework contract over twelve months, as occurs in road maintenance. The figures are a worked example.

Two things stand out.

First, only 22 of 140 items are actually needed. That is typical: a contract bill of quantities covers everything that might occur. Daily work consists of a handful of items that repeat constantly. Anyone who has set up those 22 cleanly has done 95 % of the work.

Second, 640 call-offs face twelve invoices. The effort lies not in writing the invoice but in collecting, assigning and evidencing in between. Software that only speeds up the invoice writing attacks the wrong end.

Remaining quantities: where it gets expensive

An example for a single item across the year:

In August the contract quantity is exceeded. What happens now depends on when somebody notices:

• Noticed before the work: you speak to the client, there is an extension or a separate order. Awkward, but regulated.
• Noticed after the work, before the invoice: the additional order is obtained after the fact. Doable; costs time and explanation.
• Noticed only at the check: the excess quantity is cut. You have worked and are not paid for it.

The third case is the most common, because remaining quantities typically sit in a spreadsheet somebody maintains on the side. Which is why “how much is left on this item?” is the best test for any billing solution – including your own.

Handling variations cleanly

Work outside the contract is the second area where firms regularly lose money. The process that holds:

1. Report before executing. An additional service notified after the fact is hard to enforce, however justified it is.
2. Get the order in writing. A short email from the case handler is an order. A phone call is not.
3. Capture separately. Variation items get their own numbers and do not run under the contract items.
4. Show separately. Visible in the invoice as a variation, with reference to the order.

The widespread error is step 3: the additional service is added to the nearest similar contract item because it is quicker. At the check the deviating quantity stands out, and then it is not only the variation under discussion but the care taken over the whole account.

What the case handler at the authority sees

The other side is useful for your own arrangement. A collective invoice is processed there in this order:

Four of the five steps concern assignment, not the work. Supplying that assignment instead of making them ask for it shortens the payment period noticeably – and at sixty call-offs a month that is a liquidity matter, not an administrative one.

Contract end and extension

A framework contract runs out, and that regularly creates two avoidable problems.

First, the final billing. Jobs from the last weeks of the term are often billed only after the contract has ended. Formally that is usually unproblematic; practically it leads to queries – the case handler has already closed the file. Billing the last four weeks promptly saves that round.

Second, the follow-on award. Between the end of one framework contract and the start of the next there is often a gap. During that time reports come in, but there is no contractual basis. What helps:

The last line sounds obvious and is not in daily practice: when a familiar case handler rings and asks you to “just pop over”, work arises without a basis. A short email afterwards confirming the telephone order costs two minutes and, in a dispute, is the entire claim.

In summary

Framework contract work is small-job volume. The benefit of structured billing shows not on the individual call-off but after the thirtieth – when remaining quantities, open transactions and missing evidence are visible without anyone having to ask.

How Levora ties call-offs to the contract is on the page about framework call-offs .