Reference
Markdown exportBT-13 Purchase Order Reference
An identifier issued by the buyer for a referenced purchase order. This reference enables automated invoice matching, procurement process tracking, and ensures invoices are linked to authorized purchases.
BT-13 (Purchase order reference) carries the buyer's purchase order number, mapped to cac:OrderReference/cbc:ID at document level. Optional under EN 16931, but many B2G portals and ERP-driven accounts-payable workflows require it so the invoice can be matched against its originating order before payment. Example: PO-2024-00815.
BT-13 · EN 16931 / XRechnung 3.x
BT Reference Card
Key EN 16931 and XRechnung facts for this business term.
- BT code
BT-13- Name
- Purchase Order Reference
- Cardinality
- Optional (O)
- Business group
- Document
- Data type
- Identifier
- Example value
PO-2024-00815
Quick answer
An identifier issued by the buyer for a referenced purchase order. This reference enables automated invoice matching, procurement process tracking, and ensures invoices are linked to authorized purchases.
Delivery and payment
Delivery dates, payment means, and the operational context around settlement.
Quick actions
In plain language
An identifier issued by the buyer for a referenced purchase order. This reference enables automated invoice matching, procurement process tracking, and ensures invoices are linked to authorized purchases.
An identifier issued by the buyer for a referenced purchase order. This reference enables automated invoice matching, procurement process tracking, and ensures invoices are linked to authorized purchases.
Critical for procurement process automation, three-way matching (PO, invoice, receipt), spend analysis, and financial audit trails. Enables automated approval workflows and reduces manual processing errors.
What you usually enter here
Alphanumeric text with common separators (hyphens, underscores)
Typical valid values include: PO-2025-001234, ORDER_DEF789, B2025/0456, 4711-2025-ABC
Optional but essential for public procurement compliance and corporate governance. Required for many automated procurement systems and ERP integrations.
What goes wrong often
Avoid values like: , PO, Order123456789012345678901234567890123456789012345678901234567890, PO/001/2025
Examples in context
Critical for procurement process automation, three-way matching (PO, invoice, receipt), spend analysis, and financial audit trails. Enables automated approval workflows and reduces manual processing errors.
Optional but essential for public procurement compliance and corporate governance. Required for many automated procurement systems and ERP integrations.
Valid Examples
- PO-2025-001234
- ORDER_DEF789
- B2025/0456
- 4711-2025-ABC
- PUR-MUC-2025-001
Invalid Examples
- PO
- Order123456789012345678901234567890123456789012345678901234567890
- PO/001/2025
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-13
Data Type:
text
Cardinality:
0..1
Requirement:
Optional
Max Length:
50 characters
Since Version:
Optional
XML Implementation
/Invoice/cac:OrderReference/cbc:ID/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeAgreement/ram:BuyerOrderReferencedDocument/ram:IssuerAssignedIDNext step
Fill in BT-13 when you create an XRechnung from your PDF
The converter reads the invoice and shows BT-13 with the other fields before download, so you can add or correct the value. 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.
Why the standard cares about this field
Business Context
Critical for procurement process automation, three-way matching (PO, invoice, receipt), spend analysis, and financial audit trails. Enables automated approval workflows and reduces manual processing errors.
Legal Requirement
Optional but essential for public procurement compliance and corporate governance. Required for many automated procurement systems and ERP integrations.
FAQ
Is a purchase order reference always required?
No, the purchase order reference is optional in XRechnung. However, many organizations require it for automated invoice processing and approval workflows.
What happens if the purchase order reference is incorrect?
An incorrect purchase order reference can cause invoice rejection, delayed payment, or manual processing. It may also prevent three-way matching in automated systems.
Can multiple invoices reference the same purchase order?
Yes, multiple invoices can reference the same purchase order, especially for partial deliveries or milestone billing. Each invoice typically covers different line items or delivery dates.
How does purchase order reference affect payment processing?
Purchase order references enable automated validation against approved purchase orders, speed up approval workflows, and ensure payment authorization. Missing references often require manual intervention.