Reference
Markdown exportBT-9 Payment Due Date
The date when the payment is due. This date is calculated based on payment terms and invoice date, providing clear payment deadlines for cash flow management.
BT-9 (Payment due date) is the calendar date by which the buyer must settle the amount due. Optional under EN 16931 but expected by most German B2G receivers. Provide in ISO 8601 (YYYY-MM-DD); may be omitted when BT-20 (Payment terms) carries the information instead. Example: 2024-04-26.
BT-9 · EN 16931 / XRechnung 3.x
BT Reference Card
Key EN 16931 and XRechnung facts for this business term.
- BT code
BT-9- Name
- Payment Due Date
- Cardinality
- Optional (O)
- Business group
- Document
- Data type
- Date
- Example value
2024-04-26
Delivery and payment
Delivery dates, payment means, and the operational context around settlement.
Quick actions
In plain language
The date when the payment is due. This date is calculated based on payment terms and invoice date, providing clear payment deadlines for cash flow management.
Essential for payment processing, cash flow management, and establishing clear payment deadlines. Helps buyers plan their payment schedules and suppliers manage receivables.
What you usually enter here
YYYY-MM-DD (ISO 8601 date format)
Typical valid values include: 2025-01-15, 2025-02-28, 2025-12-31, 2026-06-15
Optional but highly recommended for commercial transactions to establish clear payment expectations and support dispute resolution
Where the field sits
- Invoice
- cbc:DueDateBT-9
- rsm:CrossIndustryInvoice
- rsm:SupplyChainTradeTransaction
- ram:ApplicableHeaderTradeSettlement
- ram:SpecifiedTradePaymentTerms
- ram:DueDateDateTime
- udt:DateTimeStringBT-9
What goes wrong often
Avoid values like: 15.01.2025, 2025/01/15, 01-15-2025, 2025-13-01
Valid Examples
- 2025-01-15
- 2025-02-28
- 2025-12-31
- 2026-06-15
Invalid Examples
- 15.01.2025
- 2025/01/15
- 01-15-2025
- 2025-13-01
- 2024-02-30
XML mapping and field facts
Open the technical reference if you need XML paths, validator rule codes, legal wording, or schema-specific mapping details.
Field ID:
BT-9
Data Type:
date
Cardinality:
0..1
Requirement:
Optional
XML Implementation
/Invoice/cbc:DueDate/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerms/ram:DueDateDateTime/udt:DateTimeStringNext step
Create an XRechnung from your PDF
The converter reads the invoice and shows the fields it found before download, so you can check and correct the values. No PDF? Fill in the XRechnung directly in the form.
Download requires an account. Subscriptions from €10/month with annual billing (excl. taxes), or €5 per conversion (excl. taxes) without a subscription.
FAQ
How is the payment due date calculated?
The payment due date is typically calculated by adding the payment terms period (e.g., 30 days) to the invoice date. It can also be explicitly specified in the invoice.
Is the payment due date mandatory in XRechnung?
No, the payment due date (BT-9) is optional in XRechnung. However, it's highly recommended for clear payment management and is often expected in business transactions.
What happens if no payment due date is specified?
If no payment due date is specified, the buyer typically follows standard payment terms or legal defaults (usually 30 days from invoice date in German commercial law).
Can the payment due date be earlier than the invoice date?
Generally no. The payment due date should be the same as or later than the invoice date. Earlier dates would indicate prepayment scenarios which require special handling.