Skip to content

[EDI] [E-document] Remittance Advice XML has an incorrect line count and invalid element order #11802

Description

Description

The exported Remittance Advice contains an incorrect line count, emits a line element in an order that does not conform to the UBL 2.1 XSD, and uses the wrong identifier for the referenced vendor invoice.

Validated against:

Findings

  • cbc:LineCountNumeric is 0 while one cac:RemittanceAdviceLine is present. Emit the actual number of cac:RemittanceAdviceLine elements, or omit the optional cbc:LineCountNumeric element.
  • Line-level cbc:Note is emitted after amounts and cbc:InvoicingPartyReference. RemittanceAdviceLineType is an xsd:sequence in which cbc:Note, when present, must appear immediately after cbc:ID. Emit it in the required position.
  • cac:BillingReference/cac:InvoiceDocumentReference/cbc:ID contains the buyer's internal posted invoice number (108241), while the vendor invoice number (V10) is placed in cbc:InvoicingPartyReference. InvoiceDocumentReference/cbc:ID identifies the referenced invoice and should contain the supplier/vendor invoice identifier, normally External Document No., when available. InvoicingPartyReference has a different UBL meaning and must not be used to carry the vendor invoice number.

Steps to reproduce

  1. In the buyer company, create a vendor payment in the Payment Journal and apply it to a posted vendor invoice.
  2. Create the Remittance Advice E-Document through report 399 with Create E-Documents enabled.
  3. Open the E-Document logs and download the exported XML.
  4. Inspect cbc:LineCountNumeric, the position of line-level cbc:Note, and cac:BillingReference/cac:InvoiceDocumentReference/cbc:ID.

Fixes
AB#648724

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Team: IntegrationsGitHub request for Integrations area

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions