Codeunit 6531 "E-Doc. Remit. Advice Export"
EDocument · Microsoft.eServices.EDocument.RemittanceAdvice
Across versions
- BC23-28not present
- BC29-30present
EDocument · Microsoft.eServices.EDocument.RemittanceAdvice · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
Procedures
ExportFromJournalLine(AnchorGenJnlLine: Record "Gen. Journal Line"; AllowReExport: Boolean): Boolean(internal): Resolves the document sending profile for the payment journal line’s vendor and exports. See the profile-taking overload for behavior details.ExportFromJournalLine(AnchorGenJnlLine: Record "Gen. Journal Line"; DocumentSendingProfile: Record "Document Sending Profile"; AllowReExport: Boolean): Boolean(internal): Validates the journal payment is fit to build a remittance advice from, creates/exports the E-Document, and flags the payment group’s journal lines on success. Returns false (without error) when the profile is not set up for the Extended E-Document Service Flow, when the group is already flagged and…ExportFromPostedPayment(PaymentVendLedgEntry: Record "Vendor Ledger Entry"; AllowReExport: Boolean): Boolean(internal): Resolves the document sending profile for the posted payment’s vendor and exports. See the profile-taking overload for behavior details.ExportFromPostedPayment(PaymentVendLedgEntry: Record "Vendor Ledger Entry"; DocumentSendingProfile: Record "Document Sending Profile"; AllowReExport: Boolean; var AlreadyExists: Boolean): Boolean(internal): Validates the posted payment is fit to build a remittance advice from and creates/exports the E-Document. Returns false (without error) when the profile is not set up for the Extended E-Document Service Flow, or when an e-document already exists for this entry and re-export is not allowed (in which …
Recent changes
- 2026-09-15 #10437 [FR E-Reporting] Add payment and invoice lifecycle messages (main, BC30, feature)
- 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. Remit. Advice Export"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.