XRechnung in Levora
Leitweg-ID, check digits and mandatory fields – checked before the file exists.
To the featureFree tool
Check the Leitweg-ID before the portal does
If the check digits are wrong, the invoice intake rejects the XRechnung before a human sees it – and payment slips by weeks. Here the check takes seconds.
Check
Enter the ID
Structure and check digits are validated against format specification v2.0.2 – the same document the invoice intake follows.
Try one:
- Coarse address
- Fine address
- Check digits
This tool failed its own test case and has been switched off. Please tell us – a checker that calculates wrongly is worse than none.
Without JavaScript this field checks nothing. The method is printed below the tool – it is the same one used for IBANs and can be done on a pocket calculator.
Structure and check digits are correct
Check digits are correct – but something stands out
An invoice will not get through like this
The ID is syntactically sound. Whether it is the RIGHT ID for your contracting authority is something this cannot tell you – only the body that issued it knows.
none (permitted)
Only digits, the letters A–Z and hyphens are allowed.
A Leitweg-ID is between 5 and 46 characters long.
A hyphen is missing. There is always one before the two check digits.
Too many hyphens: at most two are allowed – before the fine address and before the check digits.
The coarse address is digits only. Letters are allowed from the fine address onwards.
The coarse address has 2 to 12 digits.
The fine address may contain only digits and the letters A–Z.
The fine address is at most 30 characters long.
Exactly two digits follow the last hyphen – the check digits.
The check digits do not match the parts in front of them. The typo could be anywhere; changing the check digits until they fit does not produce a correct ID – only one that passes the syntax check and still goes nowhere at the authority. Ask the issuing body for the ID.
%s is not a documented code: 01–16 stand for the federal states, 99 for the federal government.
A coarse address of %s digits cannot be assembled from the elements in the specification (2, 3, 5, 8, 9 and 12 are documented). It need not be wrong – but it is worth a call to the authority.
The specification recommends starting the fine address with a letter: otherwise a misplaced hyphen goes unnoticed.
The check runs in your browser. The ID you enter does not leave your machine.
How a Leitweg-ID is built
Three parts separated by hyphens. Between 5 and 46 characters in total.
04011000-1234512345-06
│ │ └── Check digits: 2 digits
│ └── Fine addressing: optional, up to 30 characters
└── Coarse addressing: 2 to 12 digits
The coarse addressing says which administrative unit is meant. It is assembled from parts of the regional key: two digits for the federal state (04 is Bremen, 99 stands for the federal government), then optionally the administrative region, the district and the municipal association or municipality code. That yields possible lengths of 2, 3, 5, 8, 9 or 12 digits.
The fine addressing is the authority’s house number – which office, which department. It is optional and assigned freely by the federal government and the states; the specification recommends starting it with a letter so that a misplaced hyphen stands out.
The check digits are your protection against typos – and the reason this tool can check anything at all.
How the check digits are calculated
To ISO/IEC 7064:2003, procedure Modulo 97-10 – the same one used for IBANs. Using the specification’s own example:
- Join coarse and fine addressing without hyphens:
040110001234512345 - Replace letters by their position in the alphabet, A = 10 to Z = 35 (none here)
- Append
00:04011000123451234500 - Take
mod 97: remainder 92 - 98 − 92 = 06 – those are the check digits
Checking is shorter: divide the complete ID without hyphens by 97. If remainder 1 is left, it is correct. That is exactly what the field above calculates, on every keystroke, in your browser.
What valid check digits do not mean
They mean: there is no typo in here. They do not mean it is the right ID for your client. A syntactically flawless ID can point to a completely different administrative unit – or to none at all. Only the body that issued the ID can give binding information; it is usually stated in the tender documents or in the order confirmation.
This is also why the tool does not show what the check digits ought to be. The typo can just as easily sit in the coarse addressing. Swapping the check digits until they fit leaves you with an ID that passes the syntax check and still goes nowhere at the authority – the worst possible error, because it surfaces when nobody expects it any more.
Where the ID sits in the invoice
In an XRechnung the Leitweg-ID belongs in BT-10, the element cbc:BuyerReference. If it is missing there, or sits in the wrong field, the finest check digits will not help.
Next
What else the invoice needs
Test an XRechnung
Try an XML you already have against the points the portal rejects.
To the toolROI calculator
What billing costs per month – with your own numbers.
To the toolInvoices that no longer need this check
In Levora the XRechnung comes out of the job itself – with the stored Leitweg-ID, checked against the same specification, before the file leaves the house.