Skip to content

BT-9: Payment Due Date

The date on which the payment is due.

BT-9Conditional RequirementEN 16931-1 / XRechnung 3.0 / ZUGFeRD 2.3

Technical Specification

Requirement & Cardinality
0..1(Conditional)

Conditional (0..1), mandatory unless prepaid or direct debit

Data Type
Date (ISO 8601: YYYY-MM-DD)

Semantic data format according to European Standard EN 16931-1

XML Syntax Mappings
UBL 2.1(XRechnung / Peppol BIS)
Invoice/cbc:DueDate
UN/CEFACT CII D16B(ZUGFeRD 2.3 / Factur-X)
rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerms/ram:DueDateDateTime/udt:DateTimeString

What does BT-9 mean?

The payment due date (BT-9) indicates the deadline for settlement. If a payment instruction is given and no prepayment has taken place, BT-9 is expected by automated accounting software and Schematron rules.

Practice Context: B2B vs. B2G (Public Procurement)

In B2G public procurement, platforms frequently require a concrete due date in BT-9.

XML Syntax & Code Example

OASIS UBL 2.1 (XRechnung)
<cbc:DueDate>2026-09-27</cbc:DueDate>

Business Rules & Schematron Checks

BR-CO-25

Payment due date (BT-9) shall not be earlier than Invoice issue date (BT-2).

Check BT-9 in your invoice

Use the XML paths above to locate BT-9. A snippet illustrates this field; it is not a complete invoice. After correcting a value in the source application, export and check the entire file again.

Official specifications and rule sets

Requirements depend on the invoice profile and version. Consult the matching specification for mandatory fields, code lists and rules; Peppol-specific requirements do not automatically apply to every ZUGFeRD invoice.

Create compliant E-Invoices easily

Create XRechnung and ZUGFeRD invoices in Billance and check the exported file locally. Use this guide to understand BT-9 and review your invoice details before sending.