Reference
Markdown exportBT-18 Invoiced object identifier
Identifier of the project, asset, case, or other business object the invoice belongs to.
Quick answer
Identifier of the project, asset, case, or other business object the invoice belongs to.
Invoice basics
Core document identifiers, dates, process identifiers, and high-level invoice context.
In plain language
Identifier of the project, asset, case, or other business object the invoice belongs to.
Identifier of the project, asset, case, or other business object the invoice belongs to.
Use this when invoice processing is organized around a non-order object such as a project ID, case ID, or asset number.
What you usually enter here
Business object identifier
Typical valid values include: PROJECT-7784
Optional according to EN 16931-1.
What goes wrong often
Avoid values like: , AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Examples in context
Use this when invoice processing is organized around a non-order object such as a project ID, case ID, or asset number.
Optional according to EN 16931-1.
Valid Examples
Use these points as the practical checks for this section.
- PROJECT-7784
Invalid Examples
Use these points as the practical checks for this section.
- AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
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-18
Data Type:
identifier
Cardinality:
0..1
Requirement:
Optional
Max Length:
50 characters
Since Version:
Optional
XML Implementation
/Invoice/cac:AdditionalDocumentReference[cbc:DocumentTypeCode="130"]/cbc:ID/CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeAgreement/ram:AdditionalReferencedDocument/ram:IssuerAssignedIDWhy the standard cares about this field
Business Context
Use this when invoice processing is organized around a non-order object such as a project ID, case ID, or asset number.
Legal Requirement
Optional according to EN 16931-1.