Interface "PEPPOL Remit. Advice Info Provider"
PEPPOL · Microsoft.Peppol
Across versions
- BC23-28not present
- BC29-30present
PEPPOL · Microsoft.Peppol · BC29-30 · source at ea08af5e · facts from BC29
Procedures
GetPayeePartyInfo(Vendor: Record Vendor; var PayeeEndpointID: Text; var PayeeSchemeID: Text; var PayeePartyName: Text)GetPaymentMeansInfo(RemitAdviceBuffer: Record "Remit. Advice Buffer" temporary; var PaymentMeansCode: Text; var PayeeFinancialAccountID: Text): Gets payment means information for the PEPPOL remittance advice from the buffer’s header row.GetDocumentIdentification(var CustomizationID: Text; var ProfileID: Text): Gets the document identification (CustomizationID/ProfileID) for the PEPPOL remittance advice header. No PEPPOL BIS profile exists for remittance advice yet, so the default implementation returns both empty (the elements are omitted); a localization can supply its own values by overriding this metho…
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: "interface", object_name: "PEPPOL Remit. Advice Info Provider"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.