Codeunit 6530 "E-Doc. Remittance Advice Mgt."

EDocument · Microsoft.eServices.EDocument.RemittanceAdvice · BC29-30 · source at ea08af5e · facts from BC29

Properties

Procedures

• CheckJournalPayment(AnchorGenJnlLine: Record "Gen. Journal Line") (internal): Validates an unposted vendor payment journal line (and its group) is fit to build a remittance advice buffer from. Buffer derivation lives in the PEPPOL app (Codeunit “Remit. Advice Buffer Mgt.”) so format apps can reuse it without a Core dependency.
• CheckPostedPayment(PaymentVendLedgEntry: Record "Vendor Ledger Entry") (internal): Validates a posted payment Vendor Ledger Entry is fit to build a remittance advice buffer from.
• FindEDocument(var EDocument: Record "E-Document"; RecRef: RecordRef): Boolean (internal): Finds the E-Document (of any type) whose “Document Record ID” matches the given record.
• FindGroupAnchor(SourceGenJnlLine: Record "Gen. Journal Line"; var AnchorGenJnlLine: Record "Gen. Journal Line"): Boolean (internal): Finds the lowest-numbered vendor line of the payment group (same journal template, batch, account no. and document no.) that the given journal line belongs to. The anchor is the group’s stable handle: e-documents are created against it and looked up through it.
• HasExportedGroup(AnchorGenJnlLine: Record "Gen. Journal Line"): Boolean (internal): Returns true when any line of the payment group is flagged as having a remittance advice e-document created. Deliberately flag-based, not Record-ID-based: Gen. Journal Line numbers are reused after delete, so a Record ID lookup could match an unrelated older e-document.
• MarkGroupExported(AnchorGenJnlLine: Record "Gen. Journal Line") (internal): Flags every line of the payment group as having a remittance advice e-document created.

Plus 1 local procedures.

Recent changes

• 2026-08-11 #9578 [E-Documents Core] - Enabling remittance advice export via E-Documents (payment journal + posted payments) (main, BC30, feature, added)

Ask your agent

Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "E-Doc. Remittance Advice Mgt."), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.