Identifies the business process context in which the transaction appears, to enable the Buyer to process the Invoice in an appropriate way.
取引プロセスの名称。買い手が適切な方法で請求書を処理することができるように、取引が行われたビジネスプロセスを識別する。


About

ID
ibt-023
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
Text
Example
urn:peppol:bis:billing

Syntax binding

Syntax binding
ubl:Invoice / cbc:ProfileID
XPath
/ Invoice / cbc:ProfileID
Restricted Syntax Cardinality
0..n
UBL 2.1
Element
cbc:ProfileID
Cardinality
0..1
Datatype
UBL Definition
Identifies a user-defined profile of the customization of UBL being used.

VERSION 1.0 RULES

Unchanged
Same as 0.9.3

VERSION 0.9.3 RULES
JP PINT 0.9.3 Aligned rule
aligned-ibrp-002-jp(fatal)
Added
[aligned-ibrp-002-jp]-Business process type (ibt-023) MUST be in the format 'urn:fdc:peppol.eu:2017:poacc:billing:01:1.0'.
JP PINT 0.9.3 Shared rule
ibr-076(fatal)
Unchanged
Same as 0.9.2

VERSION 0.9.2 RULE
JP PINT 0.9.2 Shared rule
ibr-076(fatal)
Still valid
[ibr-076]-Business process (ibt-023) MUST be provided.

VERSION 0.9.1 RULES (Obsoleted)
Aligned rule (0.9.1)
aligned-ibrp-002-jp (fatal)
[aligned-ibrp-002-jp]-Business process MUST be in the format 'urn:fdc:peppol.eu:2017:poacc:billing:01:1.0'.
Shared rule (0.9.1)
ibr-076 (fatal)
[ibr-076]-Business process (ibt-023) MUST be provided.

JP PINT 0.9 RULES (Obsoleted)
Basic Rule (0.9)
BASIC-00002(fatal)
Minimum 1 and maximum 3 instances of cbc:ProfileID are allowed.