InvoiceGlass

The third-party payment amount has too many decimal places · BR-DEX-13

  • Severity · Error
  • Applies to · UBL
  • Editorial review pending

This rule checks the decimal places in the XML field for a third-party payment amount. A third digit counts even if it is zero.

As of

Who can correct it?

The sender can correct the invoice.

How to fix it

  1. Ask the sender to export the actual third-party payment amount with at most two decimal places.

Rule text and source

Paraphrase · In the UBL binding of the XRechnung extension, a third-party payment amount may have at most two characters after the decimal point.

Message to the sender

Subject: Invoice {invoiceNumber} – decimal places in third-party payment

Hello,

Thank you for your invoice {invoiceNumber} dated {issueDate}. The check found more than two decimal places in the XML amount for a third-party payment (BR-DEX-13). Could you check the amount to be billed and resend the invoice XML with at most two decimal places in that field?

Kind regards

Example

The XML writes the amount as 19.960. Exporting 19.96 preserves the monetary value and meets the length check.

Rule versions

KoSIT · XRechnung Schematron 2.6.0

Validate a file