2. Semantic model
  3. Invoice number

Invoice number

請求書番号

A unique identification of the Invoice.
請求書の一意識別番号。

About

ID
ibt-001
Cardinality
Mandatory / Single (1..1)

Mandatory, minimum 1 occurence and maximum 1 occurrence of the information element (or group of the information elements) shall be present in any compliant instance document. (Source: EN 16931-1)
必須、最小1回および最大1回の出現。情報要素（または情報要素のグループ）は、標準に準拠するインスタンスドキュメントに存在しなければならない。

Semantic datatype
Identifier
Example
16

Syntax binding

Syntax binding
ubl:Invoice / cbc:ID
XPath
/ Invoice / 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.

VERSION 1.0 RULE

Unchanged
Same as 0.9.3
VERSION 0.9.3 RULE
JP PINT 0.9.3 Shared rule
ibr-002(fatal)
Unchanged
Same as 0.9.2
VERSION 0.9.2 RULE
JP PINT 0.9.2 Shared rule
ibr-002(fatal)
Still valid
[ibr-002]-An Invoice MUST have an Invoice number (ibt-001).
VERSION 0.9.1 RULE (Obsoleted)
Shared rule (0.9.1)
ibr-002 (fatal)
[ibr-002]-An Invoice MUST have an Invoice number (ibt-001).
JP PINT 0.9 RULES (Obsoleted)
Shared Rule (0.9)
ibr-02(fatal)
[ibr-02]-An Invoice shall have an Invoice number (ibt-001).
Basic Rules (0.9)
BASIC-00031(fatal)
Content must match "\w+".
BASIC-00030(fatal)
Content must contain minimum 3 characters.
BASIC-00003(fatal)
1 instance(s) of cbc:ID is mandatory.
PEPPOL BIS BILLING 3.0 RULE
EN16931 model bound to UBL rule
BR-02 (fatal)
An Invoice shall have an Invoice number (BT-1).