Setting up Localization for France
This compliance guide explains the setup tasks required for your French companies to use the Localization functionality and comply with France legislation. This guide also gives you access to the certificate held by Certinia of the NF 203 compliance in France. You can access the certificate from here.
To guarantee compliance, we recommend that the latest version of Accounting is installed in your org.
You must be signed in as an administrator, or equivalent, to complete these tasks. We recommend that you complete the tasks in the order shown.
Localization Setup
The following table lists the setup task required regarding the Localization Setup Feature Console feature.
| Task | Further Information |
|---|---|
| Enable the Localization Setup Feature Console feature. | Enabling Localization Setup |
Local Chart of Accounts and Mappings
The following table lists the setup task required regarding the local chart of accounts and mappings.
| Step | Task | Further Information |
|---|---|---|
| 1 | Enable the Local Chart of Accounts Mapping Setup Feature Console feature. | Enabling Local Chart of Accounts Mapping Setup |
| 2 | Import a chart of accounts and its corresponding mappings for the selected localization. | Loading Chart of Accounts and Mappings with Datastream |
| 3 | Enable the Currency Exchange Gains and Losses Feature Console feature. | Enabling the Currency Exchange Gains and Losses Feature |
Audit Files
The following table lists the setup task required regarding audit files.
| Step | Task | Further Information |
|---|---|---|
| 1 | Select a localization for your companies. | Selecting Localization at Company Level |
| 2 |
To ensure the sequence for transactions is continuous, include the year in the sequence:
If no sequence is created yet, refer to the related Help page to create one, considering the steps above. |
Creating a Sequence Format |
| 3 | Run the Generate Sequences job in Foundations. | |
| 4 | Enable the Audit File functionality. | Enabling Audit File Functionality |
| 5 | [Optional] Add custom fields to custom metadata to include them in your audit files. | Customizing Audit Files |
JET File
The JET (Journal d'Évènement Technique) file is not generated automatically. By enabling the history tracking functionality you can obtain the data required for JET codes 50, 60, and 410. For more information about obtaining data for other codes, see Reference Table for JET Codes. The following table lists the setup task required.
| Task | Further Information |
|---|---|
|
Enable the history tracking functionality for the following fields required for the following JET codes:
|
Tracking for JET File |
Financial Statements
Business Analytics and Report Builder include dashboards and reports that enable you to view the details of your financial statements. The following table lists the task required to properly use the dashboards and reports.
| Task | Further Information |
|---|---|
| Ensure that you have defined local balance sheet values and an order for those values on your GLA records. |
VAT Returns
To file your VAT returns, you can either:
- Use the Avalara VAT Reporting integration. For more information, see About the Avalara VAT Reporting Integration. This integration only supports the accrual basis accounting method.
- Hire an external financial advisory service, which can use tax-related data from your Accounting environment. You can extract this data using custom reports.
Data Archiving
If you use archiving to permanently delete data from your org, ensure you keep periods from six or less years. Data must be kept for six years according to France legislation. You can keep the data in your org or an archive. For this, you can do one of the following:
- Keep the data in your org by excluding the relevant periods when creating archive sets.
- Use an archive set to extract the relevant data from your org and copy it to an external storage system before deleting the archive set.
For more information, see Archiving Overview and Creating Archive Sets.
Currency
Remove the Salesforce Currency field, with API Name CurrencyISOCode, from the page layouts on the objects below to prevent the field from displaying on records. This field is not used by Accounting. Instead, each object uses its own custom currency field.
- Journal
- Sales Invoice
- Sales Credit Note
- Payable Invoice
- Payable Credit Note
- Cash Entry
Other Requirements
The following table lists the setup tasks necessary to comply with various requirements.
|
Step |
Task |
Further Information |
|---|---|---|
| 1 | Create a validation rule for the Tax Registration Number fields on the Account and Accounting Company objects to make these fields mandatory. | Creating Validation Rules for Tax Registration Number |
| 2 | Create a validation rule for the Number of Periods field on the Year object to set a maximum value of 23. | See the Salesforce Help. |
| 3 |
Create a validation rule for the following fields and objects to ensure that the document date falls within the period that you select when you create your documents:
|
|
| 4 |
Create a validation rule for the name of a GLA with a France localization to start with four digits. |
Creating a Validation Rule for France GLA Name Format |
Post-Setup Considerations
After you merge audit files, rename the resulting file name according to the following naming convention:
{nine digit SIREN number}FEC{YYYYMMDD}.txt
For more information, see Merging Numerous Files.
SECTIONS
|