[BC Idea]: codeunit 37201 new integrations events for "PEPPOL30 Impl."

[AlperBekar]

BC Idea Link

microsoft/ALAppExtensions#29824

Description

Why do you need this change?

We would like to cover 2 case by this request:

The event is required to comply with PEPPOL requirements. Situations where a credit note is posted without being applied to a specific sales invoice are common, so we cannot populate Applies-to Doc. No. As a result, the UBL PEPPOL InvoiceDocumentReference tag remains empty, which causes a validation error on our providers. Therefore, we need the ability to populate this tag with the value dummy value NA.

The event is required to comply with PEPPOL requirements. Situations exist where special payment conditions are determined by business rules not directly related to the standard Payment Terms setup. For example, customer-specific payment arrangements, contractual agreements, or regulatory requirements may mandate specific payment notes that cannot be derived from the Payment Terms Code alone. As a result, the PaymentTerms field may need to contain custom text that differs from the standard Payment Terms.

Describe the request

Dear team,

On behalf of 4PS, I would like to implement the following integration events:

1. in the codeunit 37201 "PEPPOL30 Impl.": OnAfterGetCrMemoBillingReferenceInfo
2. in the codeunit 37201 "PEPPOL30 Impl.": OnAfterGetPaymentTermsInfo

It's part of PEPPOL app:

"id": "e1966889-b5fb-4fda-a84c-ea71b590e1a9",
"publisher": "Microsoft",
"version": "28.0.46665.47420",
"name": "PEPPOL"

Codeunit 37201 "PEPPOL30 Impl.": OnAfterGetCrMemoBillingReferenceInfo

---

Current code

procedure GetCrMemoBillingReferenceInfo(SalesCrMemoHeader: Record "Sales Cr.Memo Header"; var InvoiceDocRefID: Text; var InvoiceDocRefIssueDate: Text)
var
    SalesInvoiceHeader: Record "Sales Invoice Header";
begin
    if (SalesCrMemoHeader."Applies-to Doc. Type" = SalesCrMemoHeader."Applies-to Doc. Type"::Invoice) and
       SalesInvoiceHeader.Get(SalesCrMemoHeader."Applies-to Doc. No.")
    then begin
        InvoiceDocRefID := SalesInvoiceHeader."No.";
        InvoiceDocRefIssueDate := Format(SalesInvoiceHeader."Posting Date", 0, 9);
    end;
end;

Suggested code

procedure GetCrMemoBillingReferenceInfo(SalesCrMemoHeader: Record "Sales Cr.Memo Header"; var InvoiceDocRefID: Text; var InvoiceDocRefIssueDate: Text)
var
    SalesInvoiceHeader: Record "Sales Invoice Header";
begin
    if (SalesCrMemoHeader."Applies-to Doc. Type" = SalesCrMemoHeader."Applies-to Doc. Type"::Invoice) and
       SalesInvoiceHeader.Get(SalesCrMemoHeader."Applies-to Doc. No.")
    then begin
        InvoiceDocRefID := SalesInvoiceHeader."No.";
        InvoiceDocRefIssueDate := Format(SalesInvoiceHeader."Posting Date", 0, 9);
    end;
    OnAfterGetCrMemoBillingReferenceInfo(SalesCrMemoHeader, InvoiceDocRefID, InvoiceDocRefIssueDate);  // <-- New event
end;

[IntegrationEvent(false, false)]
local procedure OnAfterGetCrMemoBillingReferenceInfo(SalesCrMemoHeader: Record "Sales Cr.Memo Header"; var InvoiceDocRefID: Text; var InvoiceDocRefIssueDate: Text)
begin
end;

Codeunit 37201 "PEPPOL30 Impl.": OnAfterGetPaymentTermsInfo

---

Current code

procedure GetPaymentTermsInfo(SalesHeader: Record "Sales Header"; var PaymentTermsNote: Text)
var
    PmtTerms: Record "Payment Terms";
begin
    if SalesHeader."Payment Terms Code" = '' then
        PmtTerms.Init()
    else begin
        PmtTerms.Get(SalesHeader."Payment Terms Code");
        PmtTerms.TranslateDescription(PmtTerms, SalesHeader."Language Code");
    end;

    PaymentTermsNote := PmtTerms.Description;
end;

Suggested code

procedure GetPaymentTermsInfo(SalesHeader: Record "Sales Header"; var PaymentTermsNote: Text)
var
    PmtTerms: Record "Payment Terms";
begin
    if SalesHeader."Payment Terms Code" = '' then
        PmtTerms.Init()
    else begin
        PmtTerms.Get(SalesHeader."Payment Terms Code");
        PmtTerms.TranslateDescription(PmtTerms, SalesHeader."Language Code");
    end;

PaymentTermsNote := PmtTerms.Description;
   OnAfterGetPaymentTermsInfo(SalesHeader, PaymentTermsNote);  // <-- New event
end;
[IntegrationEvent(false, false)]
local procedure OnAfterGetPaymentTermsInfo(SalesHeader: Record "Sales Header"; var PaymentTermsNote: Text)
begin
end;

I will provide the implementation for this BC Idea

• I will provide the implementation for this BC Idea

[Groenbech96]

Hi @AlperBekar,

Thanks for the detailed write-up. Both scenarios — populating InvoiceDocumentReference with a fallback value and customizing PaymentTerms — are valid PEPPOL requirements.

The PEPPOL app was recently refactored to use an interface-based extensibility model instead of integration events. Both methods you want to customize are already exposed through public interfaces:

Method	Interface
GetCrMemoBillingReferenceInfo	"PEPPOL Document Info Provider"
GetPaymentTermsInfo	"PEPPOL Payment Info Provider"

The intended approach is to extend the "PEPPOL 3.0 Format" enum with your own value, implement the relevant interfaces, and delegate to the standard "PEPPOL30" codeunit for any methods you don't need to change. You then select your custom format on the PEPPOL 3.0 Setup page. The extensibility guide in the repo walks through this pattern with complete examples: extensibility_examples.md.

That said — you mention that an empty InvoiceDocumentReference causes a validation error on providers. If this is a general PEPPOL compliance issue (i.e. credit notes without a linked invoice fail validation for all users, not just in a country-specific scenario), then arguably the W1 standard implementation itself should handle it by defaulting to 'NA' or similar. Could you clarify whether this is indeed a validation failure in the general PEPPOL BIS 3.0 spec, or specific to certain providers/countries? If it's a general compliance gap we should address it in the base implementation.

[AlperBekar]

Hi @Groenbech96 ,

Thank you for your detailed response, after reading through the extensibility_examples I also see that it is also better to extend the interfaces instead of creating a new integration events for OnAfterGetPaymentTermsInfo and InvoiceDocumentReference.

About InvoiceDocumentReference, we don't know for sure if all countries are effected by this. Currently there are some scenario's where you want to send a credit memo, but you don't have a specific document to which it applies to. This should be possible since the PEPPOL BIS Billing 3.0 states about InvoiceDocumentReference that an invoice (applies to type) should always have an invoice number (applies to no.), because of the 1.1 cardinality if you don't have both the credit memo is still valid.