Dynamics Community Forum Thread Details

Hi everyone,

We are encountering an error in an FR environment (FR localization) when running the Exchange Rate Adjustment process. The issue appears to originate from a trigger in the Microsoft French localization module “FEC Audit File” (Codeunit 10826).

Error message:

The Customer Posting Group does not exist. Identification fields and values: Code=''

Internal session ID:

549d0919-2eea-4278-8d23-02befe30b3b9

Application Insights session ID:

e625c766-5035-4286-b752-5d4d6290f31d

Client activity id:

9c1a5e34-d45d-47db-acaf-224112528d99

Time stamp on error:

2026-03-02T16:30:14.2874827Z

User telemetry id:

1d3778ca-68ed-43d2-bdc5-98539327ec5c

AL call stack:

"Generate File FEC"(CodeUnit 10826).GetCustomerReceivablesAccount line 7 - FEC Audit File by Microsoft version 27.0.38460.39927

"Generate File FEC"(CodeUnit 10826).UpdateDtldCustLedgerEntryCurrAdjmtAccNo line 2 - FEC Audit File by Microsoft version 27.0.38460.39927

"Exch. Rate Adjmt. Process"(CodeUnit 699).OnAfterInitDtldCustLedgerEntry(Event) line 2 - Base Application by Microsoft version 27.0.38460.46051

"Exch. Rate Adjmt. Process"(CodeUnit 699).InitDtldCustLedgEntry line 16 - Base Application by Microsoft version 27.0.38460.46051

"Exch. Rate Adjmt. Process"(CodeUnit 699).AdjustCustomerLedgerEntry line 64 - Base Application by Microsoft version 27.0.38460.46051

"Exch. Rate Adjmt. Process"(CodeUnit 699).ProcessCustomerAdjustment line 15 - Base Application by Microsoft version 27.0.38460.46051

"Exch. Rate Adjmt. Process"(CodeUnit 699).AdjustCustomers line 15 - Base Application by Microsoft version 27.0.38460.46051

"Exch. Rate Adjmt. Process"(CodeUnit 699).RunAdjustment line 5 - Base Application by Microsoft version 27.0.38460.46051

"Exch. Rate Adjmt. Process"(CodeUnit 699).OnRun(Trigger) line 27 - Base Application by Microsoft version 27.0.38460.46051

"Exch. Rate Adjustment"(Report 596).RunAdjustmentProcess line 28 - Base Application by Microsoft version 27.0.38460.46051

"Exch. Rate Adjustment"(Report 596).OnPreReport(Trigger) line 36 - Base Application by Microsoft version 27.0.38460.46051

"Exch. Rate Adjmt. Run Handler"(CodeUnit 599).RunExchangeRateAdjustment line 9 - Base Application by Microsoft version 27.0.38460.46051

"Exch. Rate Adjmt. Run Handler"(CodeUnit 599).OnRun(Trigger) line 2 - Base Application by Microsoft version 27.0.38460.46051

The failure originates here (Codeunit 10826, FR localization):

local procedure GetCustomerReceivablesAccount(CustomerNo: Code[20]): Code[20]

var

DetailedCustLedgEntry: Record "Detailed Cust. Ledg. Entry";

CustomerPostingGroup: Record "Customer Posting Group";

begin

DetailedCustLedgEntry.SetRange("Customer No.", CustomerNo);

DetailedCustLedgEntry.FindFirst();

CustomerPostingGroup.Get(DetailedCustLedgEntry."Posting Group");

exit(CustomerPostingGroup."Receivables Account");

end;

This code is executed through the following subscriber in the same localization:

[EventSubscriber(ObjectType::Codeunit, Codeunit::"Exch. Rate Adjmt. Process", 'OnAfterInitDtldCustLedgerEntry', '', false, false)]

local procedure UpdateDtldCustLedgEntryCurrAdjmtAccNo(var DetailedCustLedgEntry: Record "Detailed Cust. Ledg. Entry")

begin

DetailedCustLedgEntry."Curr. Adjmt. G/L Account No." := GetCustomerReceivablesAccount(DetailedCustLedgEntry."Customer No.");

end;

Based on this behavior, it appears that the localization code assumes that the first detailed ledger entry will always contain valid information, which is not guaranteed. Because the process relies on historical records that may not be complete or valid, the French localization introduces a failure in a standard periodic process. This seems to be a design issue in the localization, as the code should either use the Posting Group from the actual Detailed Customer Ledger Entry being adjusted, or apply filtering to ensure that only valid ledger entries with a Posting Group are considered. Without these safeguards, legacy data may block the execution of a core financial process that should not depend on the integrity of unrelated historical entries.

My question is whether Microsoft can confirm that this behavior constitutes a bug in the French localization, specifically in the FEC Audit subscriber logic. If it is indeed an issue, I would like to know whether a fix is planned and whether Microsoft can recommend a temporary workaround until an official correction is released.

Best regards.

Categories:

Dynamics 365 Business Central

Hi,

Looking at the code, it seems that the code is written to be failed and is running on the assumption. It need error handling or filter as you explained.

As you mentioned that this is standard code, it is best that you raise a support request with Microsoft and let them handle the scenario, considering there is no events to skip this error.

You can raise a support request following this guideline - https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/raise-support-case

✅ Tick the checkbox below to mark the answer as verified, if it helped resolve your question.

Regards,

Dhiren.

LinkedIn - https://www.linkedin.com/in/ca-dhiren-nagar-5079081b2/

Blog - https://dhirennagar.blogspot.com/

Community site session details

Exchange Rate Adjustment fails in FR Localization due to FEC Audit subscriber

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2025 Community Spotlights

Congratulations to the January Top 10 Community Leaders

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates