[FR E-Reporting] Implement and send invoice lifecycle messages

[Milica Đukić (djukicmilica)]

Why

French e-reporting requires payment applications and reversals for accepted e-invoices to be captured as lifecycle occurrences and reported through the invoice's approved French service. The application needs end-to-end lifecycle processing, from immutable payment and VAT data through message creation, delivery, failure handling, and retry.

Summary

• Added immutable French invoice lifecycle and VAT records for collected payments and reversals linked to e-documents and customer ledger entries.
• Captured payment applications and unapplications automatically and allocated reported amounts across the invoice VAT rates.
• Built French CrossDomainAcknowledgementAndResponse lifecycle XML, including PPF context and regulatory identities when configured.
• Added synchronous outgoing E-Document message sending with payload, integration, and returned-status validation.
• Persisted deterministic French service routing and rejected nonaccepted or ambiguous service selections.
• Updated background processing to create and send lifecycle messages, track failures and Message Sent, and retry without creating duplicate messages.
• Added lifecycle pages, service configuration, permissions, telemetry, and focused automated coverage.

Fixes
AB#637593

[github-actions]

$\textbf{🟠\ High\ Severity\ —\ AppSource}$

This pageextension relies on the app's namespace for owned objects, but the new action identifier ViewFREInvoiceLifecycles is added to the base E-Documents page without the member affix pattern used elsewhere in this app's extension members. A namespace does not exempt pageextension actions from AppSource member-affix requirements.

Knowledge:

• microsoft/knowledge/appsource/two-level-namespace-replaces-object-affix-not-extension-member-affix.md

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.33.4}

[github-actions]

$\textbf{🟠\ High\ Severity\ —\ Error\ Handling}$

CheckSIRENNotEmpty, CheckSIRETNotEmpty, and CheckSellerCountryCode raise dead-end plain Error calls for recoverable setup problems even though the only fix is on Company Information. Use ErrorInfo with PageNo = Page::"Company Information", RecordId, and an AddNavigationAction so the user can jump straight to the missing setup instead of being blocked by a non-actionable dialog.

Knowledge:

• microsoft/knowledge/error-handling/prefer-errorinfo-for-actionable-errors.md

Line mapping was unavailable, so this was posted as an issue comment.

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.33.4}

[github-actions]

$\textbf{🟠\ High\ Severity\ —\ Privacy}$

The new FR Sender Platform ID and FR Sender Platform Name table-extension fields are classified as SystemMetadata, even though they store the approved platform's identifier and name. That under-classifies organization-identifying tenant data, so telemetry, GDPR exports, and admin reports will treat it as system metadata.

Knowledge:

• microsoft/knowledge/privacy/data-classification-required-on-pii-fields.md

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.33.4}

[github-actions]

$\textbf{🟠\ High\ Severity\ —\ Testing}$

Most of this new test codeunit calls Initialize(), and that helper unconditionally executes Commit() after writing setup data. Methods such as CaptureCollectedOccurrenceCreatesCapturedLifecycle therefore run the commit path under the default AutoRollback transaction model, which can fail with an infrastructure Commit error instead of producing the intended test verdict. These tests need AutoCommit (with an isolated runner) or the committing setup must be reworked so non-AutoCommit tests do not execute Commit().

Knowledge:

• microsoft/knowledge/testing/transactionmodel-attribute-governs-test-transactions.md

_{👍 useful · ❤️ especially valuable · 👎 wrong - reply with why · AL review agent v1.33.4}

[Milica Đukić (djukicmilica)]

Superseded by #10437, which is now the authoritative implementation for AB#637593.

The replacement uses a smaller, normalized E-Document message model, generic payment occurrences, queued delivery, and focused payment/buyer lifecycle coverage. Continuing review in #10437 avoids carrying forward this PR's long and conflicting commit history.