XRechnung 2.1.0: CII validation rule changes

The rule requires that every invoice line allowance (BG-27), represented in UBL as cac:AllowanceCharge with cbc:ChargeIndicator false, and in CII as ram:SpecifiedTradeAllowanceCharge with ram:ChargeIndicator false, carries at least one of cbc:AllowanceChargeReason (BT-139) or cbc:AllowanceChargeReasonCode (BT-140) in UBL, or ram:Reason or ram:ReasonCode in CII. A document fails validation if the allowance charge has neither a reason text nor a reason code.

Add either the allowance reason text or the allowance reason code to the line allowance. In UBL, inside the cac:AllowanceCharge with cbc:ChargeIndicator false, add cbc:AllowanceChargeReason with the reason text, or cbc:AllowanceChargeReasonCode with a code. In CII, inside ram:SpecifiedTradeAllowanceCharge with ram:ChargeIndicator false, add ram:Reason or ram:ReasonCode. If using a reason code, ensure it is one the rule accepts; the rule does not list the allowed codes here.

Rule BR-37 requires each document level charge (BG-21) to have a Document level charge VAT category code (BT-102). In UBL, an AllowanceCharge with ChargeIndicator equal to true must contain a cac:TaxCategory whose cac:TaxScheme/cbc:ID is VAT (case-insensitive, surrounding whitespace ignored) and that TaxCategory has a cbc:ID element. In CII, a SpecifiedTradeAllowanceCharge with ChargeIndicator true must have a sibling ram:CategoryTradeTax with ram:TypeCode equal to VAT (case-insensitive) and that contains a ram:CategoryCode element. The test checks presence of these elements; it does not check their values. Because the severity is fatal, a document missing them fails validation.

For UBL, ensure the AllowanceCharge (where ChargeIndicator is true) contains a cac:TaxCategory with cac:TaxScheme/cbc:ID equal to VAT and a cbc:ID element. For CII, ensure the SpecifiedTradeAllowanceCharge has a ram:CategoryTradeTax with ram:TypeCode equal to VAT and a ram:CategoryCode element. The rule does not specify allowed category code values; use a value accepted by the applicable tax category code list.

The element ram:SpecifiedTradeSettlementPaymentMeans/ram:TypeCode must contain a payment means code from the UNTDID 4461 code list. The rule accepts only the specific codes listed in its test: 1 through 70, 74 through 78, 91 through 98, and ZZZ. The value must not contain any spaces after trimming surrounding whitespace. For example, '30' or 'ZZZ' are valid, while '4 2', 'ABC', or '71' would fail.

Set ram:SpecifiedTradeSettlementPaymentMeans/ram:TypeCode to exactly one of the allowed UNTDID 4461 codes, such as 1, 2, 30, 58, or ZZZ, with no internal spaces. If the current value is not in the allowed list, replace it with the correct payment means code for the invoice. If you are unsure which code to use, check the payment method and map it to the UNTDID 4461 list used by this rule.

BR-DEC-25 requires the invoice line allowance base amount (BT-137) to be expressed with no more than two decimal places. For UBL it checks cbc:BaseAmount on the line-level allowance charge; for CII it checks ram:BasisAmount under the corresponding specified trade allowance charge. A document fails if the value contains more than two digits after the decimal point, such as 10.345, because the portion after the . has length 3.

Ensure the cbc:BaseAmount or ram:BasisAmount value for the line-level allowance charge has at most two digits after the decimal point. For example, change 10.345 to 10.34 or 10.35. The value may also be a whole number or have one decimal place. If the document is generated by software, format the allowance base amount field to output no more than two decimal places.

Each Document level allowance (BG-20) must have at least one of a Document level allowance reason (BT-97) or a Document level allowance reason code (BT-98). In UBL, this means that within every cac:AllowanceCharge where cbc:ChargeIndicator is false, either cbc:AllowanceChargeReason or cbc:AllowanceChargeReasonCode must exist. In CII, within the ram:SpecifiedTradeAllowanceCharge whose ram:ChargeIndicator has udt:Indicator set to false, either ram:Reason or ram:ReasonCode must exist. This is a fatal rule, so a document that does not satisfy it fails validation.

Ensure each document-level allowance contains at least one reason element. In UBL, add cbc:AllowanceChargeReason or cbc:AllowanceChargeReasonCode inside the relevant cac:AllowanceCharge. In CII, add ram:Reason or ram:ReasonCode inside the relevant ram:SpecifiedTradeAllowanceCharge. The rule only checks for the presence of one of these elements; it does not specify allowed code values, so if using a reason code, check the applicable code list.

In UBL, the buyer electronic address element cac:AccountingCustomerParty/cac:Party/cbc:EndpointID must have a schemeID attribute present; the test only checks that the attribute exists, not that it is non-empty. In CII, if ram:URIUniversalCommunication is present, the first ram:URIID/@schemeID must be non-empty; if ram:URIUniversalCommunication is absent, the rule is satisfied.

In UBL, add a schemeID attribute to cbc:EndpointID in the buyer party. In CII, if ram:URIUniversalCommunication is used, ensure the first ram:URIID has a @schemeID attribute with a non-empty value; if no ram:URIUniversalCommunication is present, no change is needed.

The rule is fatal and requires that each document-level allowance (BG-20) have a document-level allowance VAT category code (BT-95). In UBL, the allowance charge element cac:AllowanceCharge with cbc:ChargeIndicator = false() must contain at least one cac:TaxCategory whose cac:TaxScheme/cbc:ID is VAT and which has a cbc:ID. In CII, the allowance charge ram:SpecifiedTradeAllowanceCharge with ram:ChargeIndicator = 'false' must contain at least one ram:CategoryTradeTax with ram:TypeCode = 'VAT' and a ram:CategoryCode. For UBL, the comparison of the tax scheme ID is case-insensitive and ignores surrounding whitespace.

In UBL, for the allowance charge with cbc:ChargeIndicator = false(), add a cac:TaxCategory that has a cac:TaxScheme with cbc:ID equal to VAT and a cbc:ID containing the VAT category code. In CII, for the allowance charge with ram:ChargeIndicator equal to 'false', add a ram:CategoryTradeTax with ram:TypeCode equal to VAT and a ram:CategoryCode containing the VAT category code. The rule does not specify which codes are allowed, so use the correct code according to the invoice context.

The rule requires that the Invoice line charge amount (BT-141), as given in cbc:Amount for UBL or ram:ActualAmount for CII, has at most two decimal places. The test counts the characters after the decimal point; if there are more than two, the document fails validation.

Set the amount in cbc:Amount (UBL) or ram:ActualAmount (CII) to a value with no more than two digits after the decimal point, e.g. 10.50 or 10.5. If the original amount has more decimals, round or truncate it to two decimals before sending.

For a document containing a document-level charge with VAT category code AE (Reverse charge), this fatal rule requires both a seller identifier and a buyer identifier. In UBL, the charge is a cac:AllowanceCharge with ChargeIndicator true and TaxCategory/ID AE under VAT; seller must have cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID or cac:TaxRepresentativeParty/cac:PartyTaxScheme/cbc:CompanyID with VAT, and buyer must have cac:AccountingCustomerParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID with VAT or cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID. In CII, the charge is ram:SpecifiedTradeAllowanceCharge with ChargeIndicator true and CategoryTradeTax with CategoryCode AE and TypeCode VAT; seller must have ram:SellerTradeParty/ram:SpecifiedTaxRegistration/ram:ID with schemeID VA or FC, or ram:SellerTaxRepresentativeTradeParty/ram:SpecifiedTaxRegistration/ram:ID with schemeID VA, and buyer must have ram:BuyerTradeParty/ram:SpecifiedTaxRegistration/ram:ID with schemeID VA or ram:BuyerTradeParty/ram:SpecifiedLegalOrganization/ram:ID. If no such charge exists, the rule passes.

If the document contains such a charge, ensure at least one of the required seller identifiers is present (as listed above) and at least one buyer identifier. If the charge is not actually reverse charge, change its VAT category code from AE to the correct value.

The rule checks that the document level allowance amount (BT-92, German: "Dokumentenebene Nachlassbetrag") has no more than two decimal places. In UBL this is cbc:Amount inside an cac:AllowanceCharge where cbc:ChargeIndicator is false; in CII it is the ram:ActualAmount belonging to the specified trade allowance charge whose ChargeIndicator is false. The test counts the characters after the decimal point and fails if that number is greater than 2. Because the severity is fatal, the document is rejected if the amount has more than two decimal places.

Change the document level allowance amount to a value with at most two decimal places (e.g. round to two decimal places before output). In UBL set /ubl:Invoice/cac:AllowanceCharge[cbc:ChargeIndicator=false()]/cbc:Amount (or the CreditNote equivalent) to a numeric value with no more than two digits after the decimal point. In CII set the corresponding ram:ActualAmount in the specified trade allowance charge to a value with no more than two decimal places.

The rule requires that every document-level allowance (BG-20), represented in UBL as cac:AllowanceCharge where cbc:ChargeIndicator is false, contains at least one of cbc:AllowanceChargeReason (BT-97) or cbc:AllowanceChargeReasonCode (BT-98). The test passes if either element exists, so a document fails when both are missing from such an allowance. This is a fatal rule, so the invoice is rejected if it does not satisfy this condition.

For each document-level allowance (cac:AllowanceCharge with cbc:ChargeIndicator false in UBL, or ram:SpecifiedTradeAllowanceCharge with ram:ChargeIndicator false in CII), add either a cbc:AllowanceChargeReason (BT-97) or a cbc:AllowanceChargeReasonCode (BT-98), or both. Ensure the added element is not empty and contains a value accepted by the relevant format or code list.

The rule requires the cbc:TaxExemptionReasonCode element (in CII: ram:ExemptionReasonCode) to contain a value that appears in the CEF VATEX code list. The test first checks that the normalized value contains no space, then checks that the uppercase form of the value is present in the list provided by the rule. A document fails if the value contains a space or is not in that list.

Set the cbc:TaxExemptionReasonCode (or ram:ExemptionReasonCode) value to one of the codes listed in the rule's CEF VATEX code list, for example VATEX-EU-79-C or VATEX-FR-FRANCHISE. Ensure the value has no spaces; case is ignored by the test, but using the exact uppercase form is safest. If the current value is not in the list, replace it with the correct VAT exemption reason code.

The rule requires cbc:TaxCurrencyCode (UBL) or ram:TaxCurrencyCode (CII) to hold an ISO 4217 alpha-3 currency code from the list accepted by BR-CL-05. It passes only when the normalized value is exactly one of the 178 listed codes, for example EUR, USD, or GBP. A document fails if the element is empty, contains only whitespace, has an internal space, or uses a code not on that list.

Put a valid ISO 4217 alpha-3 currency code in the tax currency field, such as EUR, USD, or GBP. Ensure the value has no internal spaces (surrounding whitespace is ignored by the rule) and is not empty or only whitespace. Check that the code is present in the BR-CL-05 list; if the current code is something else, replace it with the correct three-letter ISO 4217 code.

The rule requires that the document level charge amount (BT-99), as given in the allowance/charge element where ChargeIndicator is true, must not have more than two decimal places. The test checks the number of characters after the decimal point in the amount value; if there are more than two, the invoice fails validation as a fatal error.

Change the document level charge amount (cbc:Amount in UBL or ram:ActualAmount in CII) to a value with at most two decimal places, for example 10.99 instead of 10.999. Ensure the system that produces this amount rounds or truncates it to two decimals for document level charges.

The rule requires that every document level charge (BG-21) contains at least one of a document level charge reason (BT-104) or a document level charge reason code (BT-105), or both. In UBL this means each cac:AllowanceCharge with cbc:ChargeIndicator = true must have a child cbc:AllowanceChargeReason or cbc:AllowanceChargeReasonCode. A document fails validation when neither element exists.

Add cbc:AllowanceChargeReason or cbc:AllowanceChargeReasonCode (or both) to each cac:AllowanceCharge where cbc:ChargeIndicator is true. In CII, add ram:Reason or ram:ReasonCode under the applicable ram:SpecifiedTradeAllowanceCharge with ram:ChargeIndicator true. The rule only checks for the element's presence, not its content.

BR-41 requires every invoice line allowance (BG-27) to have an invoice line allowance amount (BT-136). In UBL, for each cac:AllowanceCharge with cbc:ChargeIndicator = false(), an cbc:Amount element must exist. In CII, for each ram:SpecifiedTradeAllowanceCharge whose ram:ChargeIndicator/udt:Indicator is 'false', the parent must contain ram:ActualAmount. Because this rule is fatal, an invoice missing that amount element in any line allowance fails validation.

Add the missing amount element to the line allowance: cbc:Amount in UBL or ram:ActualAmount in CII, with the allowance amount as its value. The test checks only that the element is present, not the value's format or sign.

This fatal rule applies when the invoice or credit note contains a document level allowance (BG-20) whose document level allowance VAT category code (BT-95) is "AE" (reverse charge). In that case, the document must include both a seller-side identifier and a buyer-side identifier. In UBL, the seller side is met by any cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID or by cac:TaxRepresentativeParty/cac:PartyTaxScheme/cbc:CompanyID where the tax scheme is VAT; the buyer side is met by cac:AccountingCustomerParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID where the tax scheme is VAT or by cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID. In CII, the seller side is met by ram:SellerTradeParty/ram:SpecifiedTaxRegistration/ram:ID with @schemeID VA or FC, or by ram:SellerTaxRepresentativeTradeParty/ram:SpecifiedTaxRegistration/ram:ID with @schemeID VA; the buyer side is met by ram:BuyerTradeParty/ram:SpecifiedTaxRegistration/ram:ID with @schemeID VA or by ram:BuyerTradeParty/ram:SpecifiedLegalOrganization/ram:ID. If no such allowance with reverse charge VAT category exists, the rule imposes no identifier requirement.

If the invoice has a document-level allowance with VAT category AE, add or ensure at least one of the permitted seller identifiers and at least one of the permitted buyer identifiers using the element paths above. In UBL, for the seller, add cbc:CompanyID inside cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme (or add a VAT tax representative cac:TaxRepresentativeParty/cac:PartyTaxScheme/cbc:CompanyID); for the buyer, add cbc:CompanyID under cac:AccountingCustomerParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID='VAT'] or under cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity. In CII, ensure the seller has ram:SpecifiedTaxRegistration/ram:ID with @schemeID VA or FC (or tax representative VA), and the buyer has ram:SpecifiedTaxRegistration/ram:ID with @schemeID VA or ram:SpecifiedLegalOrganization/ram:ID. If the allowance is not actually reverse charge, correct the cbc:ID / ram:CategoryCode from AE to the appropriate value.

The rule requires the invoice currency code to be a valid ISO 4217 alpha-3 currency code. It checks that the code contains no spaces and appears in the rule's list of accepted currency codes. A document fails if cbc:DocumentCurrencyCode (UBL) or ram:InvoiceCurrencyCode (CII) is empty, contains whitespace, or is not one of the listed codes.

Set the currency code element to a three-letter ISO 4217 code from the list allowed by the rule, for example EUR, USD, or GBP. In UBL use cbc:DocumentCurrencyCode; in CII use ram:InvoiceCurrencyCode. Ensure the value contains no spaces.

The rule requires that every document-level charge (BG-21) carries a document-level charge amount (BT-99). In UBL, each cac:AllowanceCharge with cbc:ChargeIndicator equal to true must contain a cbc:Amount; in CII, each SpecifiedTradeAllowanceCharge whose ChargeIndicator is true must contain an ActualAmount. A missing amount element causes this fatal validation error.

Add the missing amount element to the document-level charge. In UBL, add cbc:Amount inside the relevant cac:AllowanceCharge; in CII, add ram:ActualAmount inside the SpecifiedTradeAllowanceCharge that has the ChargeIndicator with value true. Set its value to the charge amount.

For each document-level charge (BG-21), the rule requires at least one of a charge reason (BT-104) or a charge reason code (BT-105). In UBL, a document-level charge is an cac:AllowanceCharge with cbc:ChargeIndicator = true(); it must contain either cbc:AllowanceChargeReason or cbc:AllowanceChargeReasonCode. In CII, the ram:SpecifiedTradeAllowanceCharge whose ram:ChargeIndicator has udt:Indicator='true' must contain either ram:Reason or ram:ReasonCode. Because the test uses or, having either element satisfies the rule; having neither fails validation with severity fatal.

In the invoice, for every document-level charge that currently lacks both elements, add cbc:AllowanceChargeReason with a text description of the charge, or add cbc:AllowanceChargeReasonCode with a valid reason code, inside the corresponding cac:AllowanceCharge. In CII, add ram:Reason or ram:ReasonCode inside the ram:SpecifiedTradeAllowanceCharge for that charge. If the producing system omits these fields, configure it to populate at least one for each document-level charge. Use only reason code values accepted by the applicable code list.

The rule requires the line-level allowance amount BT-136 to have no more than two decimal places. It applies to cbc:Amount inside cac:AllowanceCharge where cbc:ChargeIndicator is false (UBL), and to ram:ActualAmount inside ram:SpecifiedTradeAllowanceCharge where ram:ChargeIndicator is false (CII). The test counts the characters after the decimal point in that amount and fails if there are more than 2. A value without a decimal point passes.

Set the allowance amount to a value with at most two decimal places, such as 10.50 or 10. In UBL change cbc:Amount; in CII change ram:ActualAmount. If the amount is produced by a system, format it to no more than two decimals before generating the invoice.

The rule checks the item classification identifier scheme identifier in cac:CommodityClassification/cbc:ItemClassificationCode[@listID] (UBL) or ram:ClassCode[@listID] (CII). After surrounding whitespace is ignored, the value must not contain any internal space and must exactly match one of the 185 listed UNTDID 7143 codes, for example AA, AB, AC, EN, or ZZZ. A missing value, a value with internal spaces, or any value not in that list violates this fatal rule.

Set the listID attribute to a valid UNTDID 7143 code from the rule's list, e.g. AA, AB, AC, EN, or ZZZ. The value may have leading or trailing whitespace, but after trimming it must be exactly one of those 185 codes and contain no internal spaces. If you do not know which code applies to the item classification, check the UNTDID 7143 list for the correct scheme identifier.

The rule requires that a coded charge reason (cbc:AllowanceChargeReasonCode in UBL or ram:ReasonCode in CII) on a charge (ChargeIndicator = true) be a single code from the UNCL 7161 list given in the rule. Ignoring surrounding whitespace, the value must not contain internal spaces and must exactly match one of the listed codes, for example AA, AAA, AAC. If the value is not one of the listed codes, or contains internal spaces, the document fails this fatal rule.

Set the charge reason code element to a valid UNCL 7161 code from the rule's list. In UBL, this is cbc:AllowanceChargeReasonCode inside cac:AllowanceCharge where cbc:ChargeIndicator is true; in CII, it is ram:ReasonCode inside ram:SpecifiedTradeAllowanceCharge where ram:ChargeIndicator is true. Replace any free-text description or unknown code with the appropriate single code from the list, and ensure no multiple codes or internal spaces are entered. Check your code mapping or configuration for the correct charge reason code.

For each invoice line charge (BG-28) in CII, represented by a ram:SpecifiedTradeAllowanceCharge containing ram:ChargeIndicator with udt:Indicator = true, the rule requires at least one of ram:Reason (BT-144) or ram:ReasonCode (BT-145) as a child of that same ram:SpecifiedTradeAllowanceCharge. A document fails if neither element is present. Because the severity is fatal, such a document does not pass validation.

Add at least one of ram:Reason or ram:ReasonCode to the ram:SpecifiedTradeAllowanceCharge that carries the true ram:ChargeIndicator. For ram:Reason (BT-144), supply the reason text; for ram:ReasonCode (BT-145), supply a valid reason code from the applicable code list (the rule does not specify the allowed codes).

The rule requires the invoice line charge base amount (BT-142) to have at most two decimal places. In UBL it checks cbc:BaseAmount of a line-level cac:AllowanceCharge with cbc:ChargeIndicator = true(); in CII it checks ram:BasisAmount for a corresponding ram:ChargeIndicator with value true. A value such as 1.234 fails because there are three digits after the decimal point.

Set the affected charge base amount to a value with no more than two decimal places. In UBL, change cbc:BaseAmount in the line allowance charge; in CII, change ram:BasisAmount in the corresponding allowance charge. For example, round or format the amount to two decimals before output, e.g. 1.23 instead of 1.234.

BR-CO-24 requires every invoice line charge (BG-28) to include at least one of cbc:AllowanceChargeReason (BT-144) or cbc:AllowanceChargeReasonCode (BT-145), or both. In UBL this applies to cac:InvoiceLine/cac:AllowanceCharge[cbc:ChargeIndicator = true()] and to cac:CreditNoteLine/cac:AllowanceCharge[cbc:ChargeIndicator = true()]; in CII it applies to the corresponding SpecifiedTradeAllowanceCharge with ChargeIndicator true. A document fails when a line charge has neither element, because the test exists(cbc:AllowanceChargeReason) or exists(cbc:AllowanceChargeReasonCode) is false.

For each line charge in the invoice or credit note, make sure at least one of cbc:AllowanceChargeReason or cbc:AllowanceChargeReasonCode is present. In a producing system, configure the line charge to output a reason text or reason code; for UBL, add e.g. <cbc:AllowanceChargeReason>...</cbc:AllowanceChargeReason> or <cbc:AllowanceChargeReasonCode>...</cbc:AllowanceChargeReasonCode> to the charge. For CII, add ram:Reason or ram:ReasonCode to the ram:SpecifiedTradeAllowanceCharge that has ram:ChargeIndicator with indicator value 'true'.

The rule requires that the document level allowance base amount (BT-93) in cbc:BaseAmount (UBL) or ram:BasisAmount (CII) for an allowance charge with ChargeIndicator = false has at most two digits after the decimal point. A value fails if it contains a decimal point and more than two decimal digits; values with no decimal point or with one or two decimal digits are valid.

Set the document level allowance base amount to a value with at most two decimal places. For example, 100 or 100.50 are acceptable, while 100.505 is not. In the invoice generator, round or format cbc:BaseAmount/ram:BasisAmount for document level allowances to a maximum of two decimal digits.

The rule requires that the @currencyID attribute on amount elements (UBL) or on ram:TaxTotalAmount (CII) contains an ISO 4217 alpha-3 currency code from the list accepted by the rule, and that the code contains no spaces. Because the severity is fatal, an invoice that does not satisfy this condition is rejected with message [BR-CL-03]-currencyID MUST be coded using ISO code list 4217 alpha-3.

Set the currencyID attribute to a valid three-letter ISO 4217 alpha-3 code that appears in the rule's list, for example EUR or USD. Ensure the value is not empty and contains no spaces. In UBL this applies to amount elements such as cbc:TaxAmount; in CII it applies to ram:TaxTotalAmount[@currencyID]. If the current value is not a valid code, correct it in the source system.

For each invoice line allowance (BG-27), represented by a cac:AllowanceCharge with cbc:ChargeIndicator set to false (or the equivalent CII structure), the rule requires at least one of cbc:AllowanceChargeReason (BT-139) or cbc:AllowanceChargeReasonCode (BT-140) to be present. Because the test uses or, either element alone is sufficient; both is also allowed. The severity is fatal, so an invoice missing both in any line allowance does not pass validation.

Add a cbc:AllowanceChargeReason element or a cbc:AllowanceChargeReasonCode element (or both) inside each line-level cac:AllowanceCharge where cbc:ChargeIndicator is false. In CII, add ram:Reason or ram:ReasonCode within the corresponding ram:SpecifiedTradeAllowanceCharge. The rule only checks for the presence of at least one of these elements, not its value or content.

For UBL, if any invoice or credit note contains a line with cac:ClassifiedTaxCategory[cbc:ID='AE'] and cac:TaxScheme/cbc:ID equal to VAT (case-insensitive), then the document must include at least one of: seller cac:PartyTaxScheme/cbc:CompanyID or seller tax representative cac:TaxRepresentativeParty/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID='VAT']/cbc:CompanyID; and at least one of: customer cac:PartyTaxScheme[cac:TaxScheme/cbc:ID='VAT']/cbc:CompanyID or customer cac:PartyLegalEntity/cbc:CompanyID. If no such line exists, the rule passes. For CII, on each line with ram:ApplicableTradeTax[ram:CategoryCode='AE' and ram:TypeCode='VAT'], the test requires at least one of: seller ram:SpecifiedTaxRegistration/ram:ID[@schemeID='VA' or @schemeID='FC'] or seller tax representative ram:SpecifiedTaxRegistration/ram:ID[@schemeID='VA']; and at least one of: buyer ram:SpecifiedTaxRegistration/ram:ID[@schemeID='VA'] or buyer ram:SpecifiedLegalOrganization/ram:ID. Severity is fatal, so a document that does not satisfy this check fails validation.

If the invoice has a reverse charge line (VAT category code AE), add the missing identifiers. In UBL, ensure the seller side has either cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID or cac:TaxRepresentativeParty/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID='VAT']/cbc:CompanyID; and the buyer side has either cac:AccountingCustomerParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID='VAT']/cbc:CompanyID or cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID. In CII, ensure the seller has ram:SpecifiedTaxRegistration/ram:ID with @schemeID VA or FC, or ram:SellerTaxRepresentativeTradeParty/ram:SpecifiedTaxRegistration/ram:ID with @schemeID VA; and the buyer has ram:SpecifiedTaxRegistration/ram:ID with @schemeID VA or ram:SpecifiedLegalOrganization/ram:ID. If no reverse charge line exists, the rule passes; check that the AE code is not incorrectly applied.

The rule requires that every document-level allowance (BG-20) also carries a document-level allowance amount (BT-92). It is fatal, so an invoice that does not satisfy it fails validation. In UBL, the allowance is an cac:AllowanceCharge with cbc:ChargeIndicator set to false, and the amount must be present as a child cbc:Amount. In CII, the allowance is a ram:SpecifiedTradeAllowanceCharge whose ram:ChargeIndicator has udt:Indicator = false, and the amount must be present as a sibling ram:ActualAmount. The test checks only that the respective element exists, not its value.

For each document-level allowance, ensure the amount element is present in the XML. In UBL, add a cbc:Amount child inside the cac:AllowanceCharge where cbc:ChargeIndicator is false and populate it with the allowance amount. In CII, add a ram:ActualAmount sibling after the ram:ChargeIndicator whose udt:Indicator is false and populate it with the allowance amount. If an allowance is present but no amount is available, check the source data or mapping: the amount must be supplied as part of the allowance. The rule does not specify a minimum or format for the amount, only that the element exists.

For a document level charge (BT-100), the base amount in the UBL element cbc:BaseAmount or the CII element ram:BasisAmount must have no more than two decimal places. The test checks the digits after the decimal point; if there are more than two digits after the decimal point, e.g. 12.345, the rule fails. This is a fatal rule, so such a document fails validation.

Ensure the document level charge base amount (BT-100) has at most two decimal places. In UBL, set cbc:BaseAmount to a value with no more than two digits after the decimal point, such as 12.34; in CII, set ram:BasisAmount accordingly. If the value is generated automatically, adjust the precision or rounding to two decimals.

The rule requires every invoice line charge (BG-28) to include an invoice line charge amount (BT-141). In UBL, any cac:AllowanceCharge with cbc:ChargeIndicator = true() inside an cac:InvoiceLine or cac:CreditNoteLine must contain a cbc:Amount. In CII, any ram:SpecifiedTradeAllowanceCharge with ram:ChargeIndicator equal to 'true' inside a ram:SpecifiedLineTradeSettlement must contain a ram:ActualAmount. A document that does not satisfy this fatal rule fails validation.

For UBL, add a cbc:Amount element inside the charge cac:AllowanceCharge (the one with cbc:ChargeIndicator true) for each affected line. For CII, add a ram:ActualAmount element inside the ram:SpecifiedTradeAllowanceCharge with ram:ChargeIndicator true. Populate it with the monetary amount of the line charge. The rule only checks that the element is present, not the currency or the value.

The rule requires that the Seller electronic address (BT-34) must have a Scheme identifier when provided. In UBL, the element cac:AccountingSupplierParty/cac:Party/cbc:EndpointID must have a @schemeID attribute. In CII, if any ram:URIUniversalCommunication element exists under the SellerTradeParty, its first ram:URIID must have a non-empty @schemeID attribute; if ram:URIUniversalCommunication is absent, the rule is satisfied.

In UBL, add a schemeID attribute to cac:AccountingSupplierParty/cac:Party/cbc:EndpointID with a value accepted by the rule. In CII, if ram:URIUniversalCommunication is present, ensure its ram:URIID has a non-empty schemeID attribute. If the electronic address is not provided, no change is needed.

The rule checks that in ram:ApplicableHeaderTradeAgreement the ram:SellerTradeParty has at most one ram:URIUniversalCommunication child. The test counts these children and requires the count to be <= 1; a count of 0 is allowed. If more than one is present, the document is rejected because the rule is fatal.

In the CII invoice, look under /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeAgreement/ram:SellerTradeParty and ensure there is no more than one ram:URIUniversalCommunication element. Remove any extra ram:URIUniversalCommunication elements, or configure the producing system to emit only one.

In CII, under /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement, the rule requires that the total number of ram:TaxPointDate elements directly inside any ram:ApplicableTradeTax element is at most one (count(...) <= 1). The message says "Only one TaxPointDate shall be present"; the test accepts zero or one, so the presence of two or more TaxPointDate elements under ApplicableTradeTax causes a fatal validation error.

Check the ram:ApplicableHeaderTradeSettlement section for ram:ApplicableTradeTax elements and count their ram:TaxPointDate children. Reduce the total to at most one. In the producing system, ensure that no more than one TaxPointDate is emitted for the trade settlement; if multiple ApplicableTradeTax entries each contain a TaxPointDate, remove all but one or map the data so only a single TaxPointDate is used.

In CII, the rule allows either no ram:DueDateTypeCode under any ram:ApplicableTradeTax, or exactly one distinct value for all such ram:DueDateTypeCode elements. A document fails when there are at least two ram:DueDateTypeCode elements with different values.

Ensure that all ram:DueDateTypeCode elements under ram:ApplicableTradeTax contain the same value, or remove all of them if no due date type code is needed. If multiple different codes are present, change them to the intended single code according to the relevant code list.

The rule requires that within ram:BuyerTradeParty under ram:ApplicableHeaderTradeAgreement, the element ram:URIUniversalCommunication occurs at most once. An invoice fails if the buyer trade party has more than one ram:URIUniversalCommunication element.

Ensure that the ram:BuyerTradeParty element contains no more than one ram:URIUniversalCommunication. Remove any additional occurrences so that only one remains, or none if not needed.