InvoiceGlass

Separate advance payment block in the document header · UBL-CR-470

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

The EN 16931 core check flags a separate cac:PrepaidPayment block in the header of a UBL invoice. In the XRechnung Extension scenario for UBL invoices, KoSIT treats this finding as informational.

As of

Who can correct it?

The invoicing software provider can correct the export.

How to fix it

  1. Check the intended profile and the scenario name in the report. For XRechnung Extension, check the advance payment block against the extension rules.
  2. For a core export, map paid amounts to cbc:PaidAmount in cac:LegalMonetaryTotal and verify the resulting amount due.

Rule text and source

Paraphrase · The core test reports any cac:PrepaidPayment directly under the invoice root.

Message to the sender

Hello,

rule UBL-CR-470 was triggered when checking electronic invoice {invoiceNumber}. Could you check whether the separate advance payment block is intended for the selected profile? Could you check the export and send us a corrected file?

Kind regards

Example

A core export puts an advance payment in a separate cac:PrepaidPayment block. The corrected core invoice accounts for the payment in the document totals. A matching extension export may use the separate block.

Rule versions

CEN · EN 16931 (KoSIT) 1.3.16

CEN · EN 16931 1.3.17

Validate a file