Codeunit 6172 "E-Doc. PEPPOL Validation"

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

Properties

Procedures

• CheckReminder(ReminderHeader: Record "Reminder Header"): Validates if a reminder meets PEPPOL requirements.
• CheckFinChargeMemo(FinChargeMemoHeader: Record "Finance Charge Memo Header"): Validates if a finance charge memo meets PEPPOL requirements.
• CheckPurchaseOrder(PurchaseHeader: Record "Purchase Header"; EDocumentProcessingPhase: Enum "E-Document Processing Phase"): Validates if a purchase order meets PEPPOL requirements before the outbound e-document is created.
• CheckRemittanceAdvice(GenJournalLine: Record "Gen. Journal Line"): Validates if a remittance advice built from an unposted vendor payment journal line meets PEPPOL requirements.
• CheckRemittanceAdvice(VendorLedgerEntry: Record "Vendor Ledger Entry"): Validates if a remittance advice built from a posted payment Vendor Ledger Entry meets PEPPOL requirements.

Plus 11 local procedures.

Recent changes

• 2026-09-25 #11745 Bug 648781: check the party identifier that the PEPPOL export will use (main, BC30, fix)
• 2026-08-11 #9578 [E-Documents Core] - Enabling remittance advice export via E-Documents (payment journal + posted payments) (main, BC30, feature)

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. PEPPOL Validation"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.