[28.5] [FR E-Reporting] Add payment and invoice lifecycle messages - #10892
Merged
Milica Đukić (djukicmilica) merged 49 commits intoSep 2, 2026
Conversation
added 30 commits
September 1, 2026 13:45
# Conflicts: # src/Apps/FR/EDocument_FR/EReportingFR/test/src/FacturXCIIXMLTests.Codeunit.al
added 10 commits
September 1, 2026 13:51
# Conflicts: # src/Apps/FR/EDocument_FR/EReportingFR/test/src/FacturXCIIXMLTests.Codeunit.al
# Conflicts: # src/Apps/FR/EDocument_FR/EReportingFR/test/src/FacturXCIIXMLTests.Codeunit.al
# Conflicts: # src/Apps/FR/EDocument_FR/EReportingFR/app/src/Core/EDocHelpers.Codeunit.al
Milica Đukić (djukicmilica)
temporarily deployed
to
triage
September 1, 2026 11:55 — with
GitHub Actions
Inactive
Milica Đukić (djukicmilica)
enabled auto-merge (squash)
September 2, 2026 09:15
Anders (AndersLarsenMicrosoft)
approved these changes
Sep 2, 2026
Wenjie Fan (gggdttt)
approved these changes
Sep 2, 2026
Milica Đukić (djukicmilica)
merged commit Sep 2, 2026
754787d
into
microsoft:releases/28.5
40 checks passed
Milica Đukić (djukicmilica)
added a commit
that referenced
this pull request
Sep 3, 2026
…10946) Backport of #10892 to `releases/28.x`. ## Why French electronic invoicing requires lifecycle communication beyond the parent E-Document processing status. Eligible outgoing invoice payment applications and reversals must produce collected or negative-collected messages, buyers must be able to accept or refuse incoming invoices, and platform lifecycle messages must be correlated without overwriting the invoice's own state. This change models these exchanges as child E-Document messages and adds reusable transport, queuing, response polling, payment-occurrence, payload, and external-reference infrastructure to E-Document Core. ## Summary - **Added** a public E-Document message API with transport contracts, payload persistence, processing statuses, queued delivery, response polling, and retry support. - **Added** applied and reversed payment occurrences with replay protection and original-occurrence linkage. - **Added** French payment, buyer response, and incoming lifecycle messages with VAT allocation and PPF/CDV validation. - **Added** focused Core and French integration tests for transport, payments, responses, profiles, VAT allocation, and incoming messages. - **Fixed** test object ID collisions and Factur-X variable shadowing that blocked validation. Fixes [AB#648388](https://dynamicssmb2.visualstudio.com/1fcb79e7-ab07-432a-a3c6-6cf5a88ba4a5/_workitems/edit/648388) Co-authored-by: djukicmilica <milicadjukic@microsoft.com>
Milica Đukić (djukicmilica)
added a commit
that referenced
this pull request
Sep 4, 2026
## Why BCApps PR #10892 added 18 French E-Reporting files to `releases/28.5`, but that release still owns the E-Reporting FR app inline in NAV. Keeping the same FR objects in the BCApps validation overlay collides with the NAV-inline app and produces an invalid validation checkout, including a duplicate pageextension 10974. The FR files are represented by NAV PR 253681 for [AB#648388](https://dynamicssmb2.visualstudio.com/1fcb79e7-ab07-432a-a3c6-6cf5a88ba4a5/_workitems/edit/648388). The 32 W1 E-Document changes from #10892 belong in BCApps and remain unchanged. ## Summary - **Removed** exactly the 18 misplaced `src/Apps/FR/EDocument_FR/EReportingFR` files introduced by #10892 from the 28.5 release branch. - **Preserved** all W1 E-Document changes from #10892 in BCApps. - **Limited** the correction to `releases/28.5`; no files are removed from `main`. Fixes [AB#648771](https://dynamicssmb2.visualstudio.com/1fcb79e7-ab07-432a-a3c6-6cf5a88ba4a5/_workitems/edit/648771) Co-authored-by: djukicmilica <milicadjukic@microsoft.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #10822 to
releases/28.5.Why
French electronic invoicing requires lifecycle communication beyond the parent E-Document processing status. Eligible outgoing invoice payment applications and reversals must produce collected or negative-collected messages, buyers must be able to accept or refuse incoming invoices, and platform lifecycle messages must be correlated without overwriting the invoice's own state.
This change models these exchanges as child E-Document messages and adds reusable transport, queuing, response polling, payment-occurrence, payload, and external-reference infrastructure to E-Document Core.
Summary
IMessageSenderandIMessageResponseHandlerintegration contracts, payload persistence, processing statuses, queued background delivery, response polling, and retry support.CollectedandNegative Collectedmessages for payment applications and unapplications on approved or cleared Peppol BIS 3.0 FR and Factur-X FR documents with reportable unrealized VAT.AcceptedandRefusedmessages for incoming purchase invoices, with optional refusal reasons and validation that only one buyer response can be sent.Submitted,Accepted,Refused, andTechnical Rejectedstatuses, payload retention, transition validation, and deduplication.Fixes
AB#648388