BDI

Defense technology.
Buyers, markets, opportunities.

Why a German federal invoice needs the right Leitweg-ID

Use the recipient’s Leitweg-ID, the actual order reference and current OZG-RE route to connect a federal invoice with the customer’s processing office.

In this article
  1. Use the current federal platform
  2. Keep the routing and order references separate
  3. Read the buyer's own implementation instructions
  4. Connect the invoice with evidence of the work
  5. Check the route used by the company's software
  6. Follow up with the party able to resolve the issue
  7. Sources & evidence

A German federal invoice needs an accurate route to the organisation responsible for processing it and a clear connection to the underlying order. The Leitweg-ID supplies the buyer reference used for routing. The purchase-order reference identifies the transaction to which the invoice belongs. Getting one right does not compensate for getting the other wrong.

This is a practical handover issue between sales, delivery and finance. A supplier may have performed the agreed work while its invoice still lacks a reference already present in the customer's order document. Collecting those details when the order arrives is cheaper than reconstructing them after an invoice has been returned.

Use the current federal platform

The government's June 2026 consolidation review confirms that OZG-RE is the consolidated federal invoice-entry platform. The migration of the former ZRE recipients finished in September 2025, and ZRE closed at the end of that year. A supplier should update any internal instruction that still directs staff to choose between the two federal platforms.

The customer nevertheless remains the starting point for the particular invoice route. An organisation's participation and its order instructions should be established before transmission. Our explanation of German defence purchasing organisations provides context for identifying the contractual buyer; the invoice recipient and its internal processing unit must then be connected to the actual order.

Consider a hypothetical supplier providing office equipment maintenance at several government locations. Its technicians know the delivery sites, while finance invoices from a central office. The company needs the order's invoicing information to travel with the work instruction, so the person preparing the invoice does not substitute the technician's site address for the required buyer routing record.

Keep the routing and order references separate

The federal electronic-invoice FAQ identifies the Leitweg-ID with Buyer Reference field BT-10 and the order number with BT-13. It also distinguishes the structured invoice from an ordinary PDF image. The supplier sends the recipient's Leitweg-ID; it does not need to obtain its own identifier of that kind simply to invoice the federal customer.

For the maintenance supplier, the order record should preserve each reference in its own field. A generic box labelled customer number creates uncertainty when staff must decide which value belongs in the invoice. Use the buyer's terminology beside the internal label so the mapping can be reviewed without relying on the knowledge of one employee.

If the company supplies two locations under different orders, compare the relevant references rather than copying the last successful invoice. A correct earlier transaction demonstrates what worked for that order. It does not establish that another order uses the same recipient or purchasing reference.

This distinction also improves error investigation. A routing failure points towards the recipient information or transmission setup. A customer unable to match the invoice to an order may need the purchase reference or line allocation corrected. Finance can ask a much more useful question when it knows which relationship is missing.

Read the buyer's own implementation instructions

The Bundesnetzagentur's invoice guidance gives a concrete example. It uses several Leitweg-IDs and tells suppliers to take the applicable value from the order document. A specified order reference must also be included; the agency distinguishes a technical field requirement from a reference that becomes required because it was supplied with the order.

For a company maintaining equipment at several agency offices, that means a central customer record may need order-level detail. Finance should identify the processing office named in the order and retain any instruction relevant to older contracts. An agency-wide search result is less precise than the information supplied for the transaction.

The Bundesagentur für Arbeit provides a different operational example in its OZG-RE instructions. It distinguishes orders from its supplier portal from other purchasing routes, requires a separate invoice for each order and asks for the original order-line reference. These are buyer-specific requirements that should be carried into the company's billing process.

The examples show why the supplier should read the actual customer's instructions even when the transmission platform is familiar. The common infrastructure does not remove differences in the information needed by the organisation that processes the invoice.

Connect the invoice with evidence of the work

The maintenance company should identify which service visits and periods each invoice covers. A customer receiving several visits in one month needs enough information to connect the charge with the agreed service. Finance should obtain that delivery record from the operational system rather than infer it from a technician's expense claim.

Before billing, compare the completed work with the order and its permitted charging basis. If the invoice includes an additional visit or replacement part, establish the contractual reference supporting that charge. An accurate Leitweg-ID cannot resolve uncertainty about whether the customer ordered the extra work.

Supporting documents should follow the customer's submission instructions. The BA guidance, for example, treats supporting attachments differently depending on the ordering route. Its distinction should be reviewed when the supplier sets up that customer, rather than discovering it after sending a separate email containing material the invoice processor cannot associate with the request.

The commercial team can make this easier by preparing one order handover containing the invoicing references, expected billing period and required supporting evidence. The document should be short enough for finance to use and precise enough to avoid repeated clarification calls during delivery.

Check the route used by the company's software

A supplier may create the structured invoice in its own accounting software or use the platform's available capture route. Either way, finance should be able to inspect the values actually transmitted. A familiar printed layout can conceal a missing or incorrectly mapped field in the structured record.

For Peppol transmission, the federal FAQ distinguishes the recipient's transport identifier, which includes the relevant scheme prefix, from BT-10 inside the invoice, which contains the Leitweg-ID itself. The company's software provider should understand that distinction. The business owner can verify that the configured customer record reflects the documented values without needing to design the transport system.

When introducing a new customer, compare the first prepared invoice against the order before sending it. Check the recipient, purchase reference, service period, amount and selected supporting material together. This catches inconsistencies that separate checks by sales and finance might miss.

For recurring invoices, preserve the confirmed setup but review any changed order or customer instruction. Automation is most useful when it repeats an accurate mapping; it can otherwise reproduce the same error across many service periods.

Follow up with the party able to resolve the issue

Track submission evidence, the invoice's processing position and the actual receipt in the bank as separate records. The supplier needs to know whether a problem arose during transmission, during the customer's examination or after an amount became due. That determines the useful next action.

The BA separates technical platform support from substantive invoice questions to the customer. The Bundesnetzagentur likewise distinguishes its enquiry contact from its invoice-entry route. A supplier should send a focused question through the appropriate channel, identifying the order and invoice, rather than resend the billing document to every contact it knows.

Our guide to the federal tender workspace covers an earlier stage of the customer relationship. After award, keep that procurement record connected with the order and billing setup. Correct routing, clear transaction references and reproducible delivery evidence give finance a practical basis for obtaining payment and resolving exceptions.

Sources & evidence

  1. June2026 review of federal platform consolidationBeschaffungsamt des Bundes
  2. Federal electronic-invoice FAQBeschaffungsamt des Bundes
  3. Bundesnetzagentur invoice instructionsBundesnetzagentur
  4. BA OZG-RE invoice instructionsBundesagentur für Arbeit

June2026 federal consolidation report, federal invoice FAQ and BA/Bundesnetzagentur buyer instructions were read on6September2026. ZRE closure and OZG-RE current routing verified; buyer-specific rules kept distinct. Maintenance-company example is hypothetical.

Suggest a correction