UBL-DT-01:Amounts shall be decimal up to two fraction digits
Your invoice contains amount values with more than 2 decimal places. EN16931 requires all monetary amounts to have maximum 2 decimal digits (e.g., 100.00 not 100.001).
Engine Classification
Round all amount fields to maximum 2 decimal places per UBL data type rules
Confidence: 95% · Applied automatically in pipeline
What is UBL-DT-01?
UBL-DT-01 is a fatal validation rule defined in the EN16931 specification. It validates the * element in the UBL invoice XML.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Target path: //cbc:*[contains(name(),'Amount')]
Why This Error Matters
Invoice will be rejected. Monetary amounts must be rounded to 2 decimal places for proper processing and display.
UBL-DT-01 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.
Validator Behavior
- ·Causes invoice rejection
- ·Fails EN 16931 business rule validation
- ·Error returned: UBL-DT-01
- ·Specification: EN16931
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Missing or empty element triggers cbc:* error --> <cbc:*></cbc:*>
<!-- Provide the required value --> <cbc:*>VALID_VALUE</cbc:*>
Technical Reference
//cbc:*[contains(name(),'Amount')]Common Causes
- ·ERP system stores amounts with higher precision internally
- ·Currency conversion introduced extra decimal places
- ·Calculation rounding not applied before export
- ·Source data imported from system using different precision
- ·Manual entry included too many decimal places
Seeing this in production? The API handles UBL-DT-01 automatically. See the fix response →
See Also
Last updated: 21 February 2026
Handle UBL-DT-01 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.