Search
Image Pexels.com
Business Central: enabling the Payment Management FR extension for French bills of exchange
Business Central: enabling the Payment Management FR extension for French bills of exchange

French bills of exchange (LCR) in Business Central, moving from report 10880 to report 10840

Published on 11/19/2026  |  Project management  |  Post read 239 times  |  Read in 5,74 Mn  | Article 3 of 3  | Bill of exchange

Index toggle


The first remittance of French bills of exchange, the LCR (lettres de change relevé), after a version upgrade is a moment accounting teams watch closely. The printout comes out, then the file meant for the bank refuses to generate or does not contain what it should. In the French localization of Business Central, this scenario now has a clearly identified cause. Payment management has left the base application for a dedicated Microsoft extension, "Payment Management FR", which rebuilds payment slips, payment classes, statuses and steps identically, but under new object IDs.

The previous article in the series detailed the complete setup of a French bill of exchange flow, from LCR printing to posting the remittance. That setup remains valid. This one focuses on what changes with the extension: enabling it, migrating the data and, above all, replacing report 10880 with report 10840 in the step that creates the ETEBAC file.

What the extension really changes

In substance, nothing changes. The extension's tables mirror those of the former localization field by field: "Payment Class", "Payment Status", "Payment Step", "Payment Header" and "Payment Line" keep the same field numbers, the same options and the same checks. The report that creates the ETEBAC file is also a faithful copy of the old one. The format of the file sent to the bank therefore stays the same.

What changes are the identifiers. The former tables 10860 to 10870 become tables suffixed "FR", numbered 10831 to 10842, and every report is renumbered within the range reserved for the extension. A payment step does not call a report by its name, however, but by its number, stored in the "Report No." and "Export No." fields. A number left on the old value runs the old report, designed to read the base application tables. Once the migration is done, those tables no longer hold the current payment slips and the old report can no longer produce the right document.

Enabling the feature in Business Central

The "Payment Management FR" extension is provided by Microsoft with the French localization, and a look at the "Extension Management" page is enough to confirm it is there before going further. The feature is then enabled on the "Feature Management" page, on the line for payment management, whose technical key is "Payment". As long as it stays disabled, Business Central keeps using the base application objects.

Setting the "Enabled for" field to "All Users" is not enough, because the feature requires a data update. The wizard lets users review the data before starting the migration. It shows, table by table, the number of records that will be copied, down to the bank accounts whose RIB key and agency code move to new fields. The migration does not overwrite a record already present in the extension's tables, so it can be restarted after a failure without creating duplicates.

One detail is often missed during testing: the update runs company by company. An environment holding a production company, a test company and the CRONUS demonstration company must be processed in each of them, the others remaining pending. Microsoft also announces that the feature will be enabled by default from version 31, with the same forced migration. Enabling it in a sandbox before that deadline leaves time to validate the flows without schedule pressure.

Checking the steps of the French bill of exchange payment slip

The file step: 10840 instead of 10880

The migration does more than copy data. A dedicated routine then goes through every payment step and replaces the old report numbers with the new ones, according to a predefined mapping table. For a step whose "Action Type" is "File" and "Export Type" is "Report", the value 10880 in the "Export No." field becomes 10840, the new "ETEBAC Files FR" report.

This automatic mapping does not remove the need for a check. Open the LCR payment class, then its list of steps, and display the card of the file creation step. The "Export No." field must show 10840. If it still shows 10880, enter 10840 manually. The lookup displays the report name, which avoids validating a neighbouring number. The other fields of the step, starting with "Previous Status" and "Next Status", are not affected.

The printing step follows the same logic

The same check applies to the printing step, which the previous article set up with report 10865. In the extension, LCR printing uses report 10834 "Bill FR", entered in the "Report No." field. A complete French bill of exchange flow often relies on other reports, and here are the main mappings:

  • 10865 "Bill" becomes 10834 "Bill FR", for LCR printing;
  • 10880 "ETEBAC Files" becomes 10840 "ETEBAC Files FR", for the remittance file;
  • 10864 "Suggest Customer Payments" becomes 10849 "Suggest Cust. Payments", for suggesting customer payments;
  • 10843 "Recapitulation Form" becomes 10846 "Recapitulation Form FR", for the summary slip;
  • 10873 "Archive Payment Slips" becomes 10831 "Archive Payment Slips FR", for archiving;
  • XMLport 10863 for importing and exporting parameters becomes XMLport 10831.

Cases the migration does not cover

The mapping only applies at migration time, and only to standard objects. Imported parameters cause the most frequent problem. Many partners keep an XML file of payment classes, exported from a reference company and re-imported for each new customer. That file contains the old numbers 10865 and 10880, and the import does not convert them. Each imported step must then be corrected by hand, unless the reference file is regenerated from a company that has already been migrated.

Custom developments are the other blind spot. A customized LCR report, an extension that adds a check on payment slip lines or an export to a banking platform relies on the base application "Payment Header" and "Payment Line" tables. The routine ignores report numbers it does not know: the step keeps its custom number, and the code must be adapted to the "Payment Header FR" and "Payment Line FR" tables before enabling the feature, not after.

That leaves the question of payment slips in progress. The migration copies headers and lines with their status, so a payment slip printed before the switch can continue its cycle in the extension. As a precaution, the switch is best scheduled right after a bank remittance, so that the first file produced by report 10840 can be compared line by line with the last file produced by report 10880.

Conclusion

This extraction changes neither the French bill of exchange flow nor the ETEBAC format, and that is what makes it misleading. Nothing prompts anyone to reopen step cards set up years earlier. The useful work is nonetheless limited: enable the feature company by company in a sandbox, check the "Report No." and "Export No." fields of every payment class, regenerate the reference parameter files and have the bank validate the first file produced by report 10840. These checks take half a day before version 31. Discovered after a bank rejection, they cost a cash deadline.

Virgile Petrantoni
Help the blogger by rating this post:
vote 1 vote 2 vote 3 vote 4 vote 5
Comments

No comments yet.

Feel like commenting on this article? sign up, it's free!


Other posts
From the V-model to agility

V-model and ERP projects: when milestones are passed on paper

The V-model did not fail because it planned. Its milestones were passed on signed documents, with no proof that anything worked. A fresh reading of Royce, the tunnel effect, shared responsibilities and what agility changes in the nature of proof, with a box on the requirements document approved before anyone has seen Business Central.

Calendar Icon  Published on 11/12/2026 | 
Project management | 
Views Icon  Views 0 times | 
Time Icon  Read in 0 min | 
Off Off Off Off Off
Master your depreciation rules and secure the accounting impact of your assets in Business Central!

Depreciation laws and accounting integration in Business Central

Asset management in Microsoft Dynamics 365 Business Central relies on the configuration of depreciation rules. This article details their role, rounding rules, and integration into general ledger accounting. It presents the duplication of entries, multi-rule calculations, depreciation methods, and the configuration of fixed asset accounting types.

Calendar Icon  Published on 11/18/2026 | 
Project management | 
Views Icon  Views 0 times | 
Time Icon  Read in 0 min | 
Off Off Off Off Off
A schedule that is too short is always paid for later

ERP projects: when the initial estimate becomes an untenable promise

A Business Central project priced too tightly creates, from the day the contract is signed, a pressure that sacrifices testing, data migration and training. This article describes how the overrun shows up, what it really costs, why it repeats from one project to the next and how to build a budget and a schedule that hold up in the field.

Calendar Icon  Published on 11/15/2026 | 
Project management | 
Views Icon  Views 0 times | 
Time Icon  Read in 0 min | 
Off Off Off Off Off
Changing ERP partners

Changing ERP partners: the takeover method, illustrated with Business Central

When a new partner takes over an ERP project, the company faces custom code with no source, batch jobs that fail silently and knowledge held by a handful of key users. Using a Business Central project as an example, this article describes the symptoms of a poorly prepared takeover, their causes and the conditions to demand before support changes hands.

Calendar Icon  Published on 11/08/2026 | 
Project management | 
Views Icon  Views 0 times | 
Time Icon  Read in 0 min | 
Off Off Off Off Off
0%