BT-149Item price base quantityBT-150Item price base quantity unit of measure code
Official rule text
[BR-TMP-3] If BT-149 (Item price base quantity) is present in both GrossPriceProductTradePrice and NetPriceProductTradePrice, the values must be identical. If BT-150 (unit of measure code) is present on the NetPrice path, it must also be present on the GrossPrice path and be identical.
Official text (German): Wenn BT-149 (Item price base quantity) sowohl in GrossPriceProductTradePrice als auch in NetPriceProductTradePrice vorhanden ist, müssen die Werte identisch sein. Wenn BT-150 (unit of measure code) auf dem NetPrice-Pfad vorhanden ist, muss es auch auf dem GrossPrice-Pfad vorhanden und identisch sein.
Why this error occurs
This rule only applies when another field has a certain value (for example a payment means code or an invoice type). Your file triggers the condition but does not provide the data that then becomes mandatory, or provides data that is then forbidden.
How to fix it
Either change the triggering value so the condition no longer applies, or add/remove the dependent elements as the rule text describes. Check the condition in the XPath test above to see exactly which value triggers it.
What the validator checks
Checked element (context):
CII
/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:IncludedSupplyChainTradeLineItemTest (XPath):
not(ram:SpecifiedLineTradeAgreement/ram:GrossPriceProductTradePrice/ram:BasisQuantity and ram:SpecifiedLineTradeAgreement/ram:NetPriceProductTradePrice/ram:BasisQuantity) or (ram:SpecifiedLineTradeAgreement/ram:GrossPriceProductTradePrice/ram:BasisQuantity = ram:SpecifiedLineTradeAgreement/ram:NetPriceProductTradePrice/ram:BasisQuantity and (not(ram:SpecifiedLineTradeAgreement/ram:NetPriceProductTradePrice/ram:BasisQuantity/@unitCode and ram:SpecifiedLineTradeAgreement/ram:GrossPriceProductTradePrice/ram:BasisQuantity/@unitCode) or ram:SpecifiedLineTradeAgreement/ram:GrossPriceProductTradePrice/ram:BasisQuantity/@unitCode = ram:SpecifiedLineTradeAgreement/ram:NetPriceProductTradePrice/ram:BasisQuantity/@unitCode))Check your invoice
Drop your XML or PDF on the validator and every failed rule is linked to its page here. Free, no account, the file is not stored.
Same check via API:
curl -F file=@invoice.xml https://einvoicechecker.com/v1/validateRelated rules
BR-TMP-2BT-124 "External document location" must contain an absolute URL with a valid schemeBR-TMP-4BT-123 "Supporting document description" (ram:Name) may occur at most once within…BR-TMP-5BT-125 "Attached document" (ram:AttachmentBinaryObject) may occur at most once within…BR-TMP-6Dates in UBL must be transmitted in the format YYYY-MM-DDBR-TMP-7Dates in UNCEFACT/CII must carry the attribute format="102" and be transmitted in the…
Frequently asked questions
What does BR-TMP-3 mean?
BR-TMP-3 is a xrechnung rule: If BT-149 (Item price base quantity) is present in both GrossPriceProductTradePrice and NetPriceProductTradePrice, the values must be identical. If BT-150 (unit of measure code) is present on the NetPrice path, it must also be present on the GrossPrice path and be identical.
Will my invoice be rejected because of BR-TMP-3?
Yes. BR-TMP-3 is flagged "fatal"; validators (KoSIT, Peppol access points, the German ZRE/OZG-RE portals) reject the invoice until it is fixed.
Which formats does BR-TMP-3 apply to?
XRechnung in UBL or CII syntax, including ZUGFeRD / Factur-X PDFs with the XRECHNUNG profile. Invoices to German public authorities (federal, state and municipal) must pass it. Syntax: CII.
Source: XRechnung 3.0.2, schematron 2.6.0 (KoSIT, September 2026). Catalogue generated from the official schematron on 2026-10-14.