2. Semantic model
  3. Invoiced object identifier

Invoiced object identifier

請求するオブジェクトID

An identifier for an object on which the invoice is based, given by the Seller.
請求書の根拠となるIDで、売り手が指定。請求書の根拠となるオブジェクトのIDで、売り手が指定したもの。

About

ID
ibt-018
Cardinality
Optional / Single (0..1)

Conditional,minimum 0 occurence and maximum 1 occurrence of the information element (or group of the information elements) may be present in any compliant instance document; it's use depends on business rules stated as well as the regulatory, commercial and contractual conditions that applies to the business transaction. (Source: EN 16931-1)
任意、最小0回および最大1回の出現。情報要素（または情報要素のグループ）は、標準に準拠するインスタンスドキュメントに存在する可能性がある。使用するかどうかは、記載されているビジネスルール、およびビジネストランザクションに適用される規制、商業、および契約条件によって異なる。

Semantic datatype
Identifier
Example
DR35141

Syntax binding

Syntax binding
ubl:Invoice / cac:AdditionalDocumentReference / cbc:ID
XPath
/ Invoice / cac:AdditionalDocumentReference [ cbc:DocumentTypeCode = '130' ] / cbc:ID
Restricted Syntax Cardinality
0..n
UBL 2.1
Element
cbc:ID
Cardinality
1
Datatype
UBL Definition
An identifier for this document, assigned by the sender.

Child element

  ID Business Term Card Definition
 ibt-018-1The identification scheme identifier of the Invoiced object identifier.
請求するオブジェクトIDのスキーマID		0..1If it may be not clear for the receiver what scheme is used for the identifier, a conditional scheme identifier should be used that shall be chosen from the UNTDID 1153 code list [6] entries.
受信者にとって、IDにどのスキーマが使用されているかが明確でない場合は、UNTDID1153コードリストから選択される条件付きスキーマIDを使用する必要がある。
Example: ABT

VERSION 1.0 RULES

Unchanged
Same as 0.9.3
VERSION 0.9.3 RULES
JP PINT 0.9.3 Shared rules
ibr-071(fatal)
Unchanged
Same as 0.9.2
ibr-072(fatal)
Unchanged
Same as 0.9.2
ibr-078(fatal)
Unchanged
Same as 0.9.2
ibr-cl-07(fatal)
Changed Message
[ibr-cl-07]-Object identifier identification (ibt-018) scheme MUST be coded using a restriction of UNTDID 1153.
VERSION 0.9.2 RULES
JP PINT 0.9.2 Aligned rule
aligned-ibrp-sr-43(fatal)
Removed
[aligned-ibrp-sr-43]-Scheme identifier shall only be used for invoiced object (ibt-018) (document type code with value 130)
JP PINT 0.9.2 Shared rules
ibr-071(fatal)
Still valid
[ibr-071]-An invoice should not include an AdditonalDocumentReference (ibg-24) simultaneously referring an Invoice Object Identifier (ibt-018) and an Attachment (ibt-125).
ibr-072(fatal)
Still valid
[ibr-072]-An invoice MUST not include an AdditionalDocumentReference (ibg-24) simultaneously referring an Invoice Object Identifier (ibt-018) and an Document Description (ibt-123).
ibr-078(fatal)
Still valid
[ibr-078]-Only one invoiced object (ibt-018) is allowed on document level.
Code list rule (Shared rule)
ibr-cl-07 (fatal)
[ibr-cl-07]-Object identifier identification scheme MUST be coded using a restriction of UNTDID 1153.
VERSION 0.9.1 RULES (Obsoleted)
Shared rules (0.9.1)
ibr-071 (fatal)
[ibr-071]-An invoice should not include an AdditonalDocumentReference (ibg-24) simultaneously referring an Invoice Object Identifier (ibt-018) and an Attachment (ibt-125).
ibr-072 (fatal)
[ibr-072]-An invoice MUST not include an AdditionalDocumentReference (ibg-24) simultaneously referring an Invoice Object Identifier (ibt-018) and an Document Description (ibt-123).
ibr-078 (fatal)
[ibr-078]-Only one invoiced object (ibt-018) is allowed on document level.
Code list rule (Shared rule)
ibr-cl-07 (fatal)
[ibr-cl-07]-Object identifier identification scheme MUST be coded using a restriction of UNTDID 1153.