法國¶
模組¶
The following modules related to the French localization are available:
名稱 |
技術名稱 |
說明 |
|---|---|---|
France - Accounting |
|
French fiscal localization package that applies only to companies based in mainland France and doesn’t include DOM-TOMs. |
France - Accounting Reports |
|
Export of the French VAT report, which can be sent to the DGFiP, an OGA, or a professional accountant. |
France - Payroll with Accounting |
|
Includes the necessary accounting data for the French payroll rules. |
France - Factur-X integration with Chorus Pro |
|
Adds fields needed for submitting invoices to Chorus Pro. |
France - FEC Export |
|
Generates the FEC file as defined by the Decree of July 29, 2013. |
France - FEC Import |
|
Import of standard FEC files, useful for importing accounting history. |
France - Adding Mandatory Invoice Mentions (Decree no. 2022-1299) |
|
Adds address fields required to comply with Decree 2022-1299. |
France - VAT Anti-Fraud Certification for Point of Sale (CGI 286 I-3 bis) |
|
備註
The localization’s core modules are installed automatically with the localization. The rest can be manually installed.
Localization overview¶
The French localization package ensures compliance with French fiscal and accounting regulations. It includes tools for managing taxes, fiscal positions, reporting, and a predefined chart of accounts tailored to France’s standards.
The French localization package provides the following key features to ensure compliance with local fiscal and accounting regulations:
賬目總表: a predefined structure tailored to French accounting standards
财政状况（税项和科目映射）: automated tax adjustments based on customer or supplier registration status
Taxes: pre-configured tax rates, including standard VAT, zero-rated, and exempt options
報表¶
Installing the France - Accounting
(l10n_fr) module gives access to some accounting reports specific to France, such as:
Bilan comptable (FR) (Balance Sheet)
Compte de résultats (FR) (Profit and Loss)
Rapport de taxes (FR) (Tax Report)
會計¶
E-Invoicing¶
The Chorus Pro portal, managed by the AIFE (Agence pour l’Informatique financière de l’État), is the official platform for submitting electronic invoices to French public entities. It allows businesses to send and manage invoices, track their processing status, and access payment updates. Since January 2020, electronic invoicing has been mandatory for all business-to-government (B2G) transactions in France. Odoo supports integration with Chorus Pro to submit invoices generated in Odoo.
配置¶
To send invoices to Chorus Pro, the following configuration is required:
Install the France - Factur-X integration with Chorus Pro (
l10n_fr_facturx_chorus_pro) module.Register with Peppol, as invoices are sent from Odoo to Chorus Pro via the Peppol network.
If you don’t already have a Chorus Pro account, go to the Chorus Pro page, click Créer un compte, and create one.
客戶¶
To submit invoices to Chorus Pro, configure the relevant customers』 contact form as follows:
Verify the Country and Tax ID fields are filled out.
In the Sales & Purchase tab, ensure the SIRET field is completed.
In the Accounting tab, fill in the following fields in the Electronic Invoicing section:
Format: Select BIS Billing 3.0.
Peppol e-address (EAS): Select 0009 - SIRET-CODE.
Peppol Endpoint: Type
11000201100044, the reference used by Chorus Pro.
Sending invoices to Chorus Pro¶
To send invoices to Chorus Pro, follow these steps:
Go to and open or create the invoice.
Make sure the following fields are filled in the Other Info tab:
Buyer Reference: Service Exécutant in Chorus Pro
Contract Reference: Numéro de Marché in Chorus Pro
Purchase Order Reference: Engagement Juridique in Chorus Pro
Confirm the invoice.
Click Send & Print and, in the Send window, enable Peppol Bis Billing 3.0.
Click Send & Print.
Once the invoice is sent, the Peppol status of the invoice is updated to Done.
也參考
FEC - Fichier des Écritures Comptables¶
An FEC Fichier des Écritures Comptables audit file contains all the accounting data and entries recorded in all the accounting journals for a financial year. The entries in the file must be arranged in chronological order. Since January 2014, every French company is required to produce and transmit this file upon request by the tax authorities for audit purposes.
FEC匯入¶
Install the France - FEC Import
(l10n_fr_fec_import) module to import FEC files from other software.
To enable this feature, go to . In the Accounting Import section, click Import and Import FEC. Then, in the FEC Import window, upload the FEC file and click Import.
備註
Importing FEC files from different years requires no particular actions or computations. However, if multiple files contain RAN Reports à Nouveaux with the starting balance for the year, these entries are automatically marked as unnecessary in Odoo and may need to be deleted.
文件格式¶
備註
FEC files must be in CSV format, as XML format is not supported.
The FEC CSV file is a plain text file structured as a data table. The first line serves as the header, defining the list of fields for each entry, and each following line represents a single accounting entry without any specific order.
FEC files must comply with the following technical specifications:
**** ：UTF-8、UTF-8-SIG 和 iso8859_15.
隔 ：以下任一项：“;”或“|”或“，”或“TAB”.
行终止** ：同时支持 CR+LF （
\r\n） 和 LF （\n） 字符组。期格 ：“%Y%m%d`
字段描述和使用¶
# |
字段名称 |
說明 |
使用 |
文字格式 |
|---|---|---|---|---|
01 |
日记代码 |
日志代码 |
“journal.code”和“journal.name”（如果未提供“JournalLib` |
字母数字 |
02 |
期刊图书馆 |
日记账标签 |
“journal.name` |
字母数字 |
03 |
EcritureNum |
特定于条目的每个日志序列号的编号 |
“move.name` |
字母数字 |
04 |
EcritureDate |
会计分录日期 |
|
Date （yyyyMMdd） |
05 |
CompteNum |
帳戶號碼 |
“帐户.代码` |
字母数字 |
06 |
CompteLib |
賬戶標籤 |
“account.name` |
字母数字 |
07 |
CompAuxNum |
辅助帐号（接受空） |
|
字母数字 |
08 |
CompAuxLib |
辅助帐户标签（接受空） |
“partner.name` |
字母数字 |
09 |
片材参考 |
参考文件 |
“move.ref”和“move.name”，如果未提供“EcritureNum` |
字母数字 |
10 |
片状日期 |
文件日期 |
|
Date （yyyyMMdd） |
11 |
EcritureLib |
帐户条目标签 |
“move_line.姓名` |
字母数字 |
12 |
借方 |
借方总额 |
“move_line.借记` |
浮點數 |
13 |
貸方 |
信用额度（不允许使用字段名称“Crédit”） |
“move_line.credit` |
浮點數 |
14 |
EcritureLet |
会计分录交叉引用（接受空） |
|
字母数字 |
15 |
日期让我们 |
会计分录日期（接受空） |
在日历年度结束时，未使用的应计费用将被 |
Date （yyyyMMdd） |
16 |
有效日期 |
会计分录验证日期 |
在日历年度结束时，未使用的应计费用将被 |
Date （yyyyMMdd） |
17 |
蒙坦特维斯 |
货币金额（接受空值） |
|
浮點數 |
18 |
伊德维塞 |
货币标识符（接受空值） |
“currency.name` |
字母数字 |
These two fields appear in the same order as the others, replacing them.
12 |
蒙坦特 |
金額 |
“move_line.debit”或“move_line.credit” |
浮點數 |
13 |
森斯 |
可以是“C”表示贷方，“D”表示借方 |
确定“move_line.debit”或“move_line.credit” |
字元 |
实现细节¶
The following accounting entities are imported from the FEC files: Accounts, Journals, Partners, and Moves. The module automatically determines the encoding, line terminator, and separator used in the file. Next, a check is performed to ensure that each line has the correct number of fields matching the header. If the check is successful, the entire file is read, stored in memory, and scanned. Accounting entities are then imported one type at a time in the following order.
項目¶
Each accounting entry is associated with an account identified by the CompteNum field.
代码匹配¶
If an account with the same code already exists, the existing one is used rather than creating a new one. In Odoo, account numbers follow the default digit length of the fiscal localization. Since the FEC module is tied to the French localization, the default account length is 6 digits. This means that trailing zeros in account codes are removed, and the comparison between the account codes in the FEC file and those already in Odoo is made based only on the first six digits of the codes.
Example
The account code 65800000 in the file is matched with an existing 658000 account in Odoo,
and the existing account is used instead of creating a new one.
可调和标志¶
An account is technically flagged as reconcilable if the first line in which it appears has the EcritureLet field filled out, indicating that the accounting entry will be reconciled with another one.
備註
The field can be left empty on the line, but the entry must still be reconciled with an unrecorded payment. The account is flagged as reconcilable once the import of the move lines requires it.
账户类型和模板匹配¶
Since the account type is not specified in the FEC format, new accounts are created with the default type Current Assets. After the import process, they are matched against the installed Chart of Account templates. The reconcile flag is also determined this way.
The matching is performed by comparing the left-most digits, starting with all digits, followed by 3 digits, and then 2 digits.
Example
名稱 |
程式碼 |
全面比较 |
3 位数字比较 |
2 位数字比较 |
|---|---|---|---|---|
範本文字 |
|
|
|
|
CompteNum |
|
|
|
|
(无结果) |
没有找到匹配 |
The account type is then flagged as payable and reconcilable based on the account template.
日記賬¶
Journals are checked against the existing ones in Odoo to avoid duplicates, even when importing multiple FEC files.
If a journal with the same code already exists, the existing journal is used instead of creating a new one.
New journals have the prefix FEC- added to their name. For example, ACHATS becomes FEC-ACHATS.
備註
Journals are not archived, allowing the user to manage them as desired.
日志类型确定¶
The journal type is not specified in the format (similar to the accounts) and is initially created with the default type general.
At the end of the import process, the journal type is determined based on the following rules regarding related moves and accounts:
- bank: Moves in these journals always include a line (debit or credit) impacting a liquidity account.cash / bank can be interchanged, so bank is assigned when this condition is met.
- sale: Moves in these journals mostly have debit lines on receivable accounts and credit lines on tax income accounts.销售退款日记帐项目是倒排的借方/贷方。
- purchase: Moves in these journals mostly have credit lines on payable accounts and debit lines on expense accounts.购买退款日记帐项目是倒排的借方/贷方。
- general: Used for everything else.
備註
A minimum of three moves is required to identify the journal type.
A threshold of 70% of the moves must meet the criteria for a journal type to be determined.
Example
Suppose we are analyzing the moves that share a certain journal_id.
移動 |
個數 |
百分比 |
|---|---|---|
具有销售科目行且没有采购科目行 |
0 |
0 |
具有采购科目行和无销售科目行 |
1 |
25% |
具有流动性账户行 |
3 |
75% |
合计 |
4 |
100% |
The journal type would be bank, because the bank’s move percentage (75%) exceeds the threshold (70%).
聯絡人¶
Each contact keeps its Reference from the CompAuxNum field.
備註
These fields are searchable based on previous FEC imports for fiscal/audit purposes.
小訣竅
Similar and potential duplicate contacts can be merged using the Data Cleaning App.
移動¶
Entries are posted and reconciled immediately upon submission, with the EcritureLet field used to match the entries.
The EcritureNum field represents the name of the moves, but it may sometimes be left empty. In such cases, the PieceRef field is used instead.
舍入问题¶
A rounding tolerance is applied based on currency precision for debit and credit amounts (i.e., 0.01 for EUR). If the difference falls under this tolerance, a new line is added to the move, called Import rounding difference, targeting the following accounts:
658000对增加的借项收取不同的费用758000Produits divers de gestion courante， for add credits
缺少移动名称¶
If the the EcritureNum field is not filled out and PieceRef field is not suited to determine the move name (it may be used as an accounting move line reference), it becomes impossible to identify which lines should be grouped into a single move, and effectively preventing the creation of balanced moves.
In such cases, a final attempt is made to group all lines by the same journal and date (JournalLib, EcritureDate). If this grouping generates balanced moves (sum(credit) - sum(debit) = 0), then each different combination of journal and date creates a new move.
Example
“ACH” + “2021/05/01” –>名为“20210501”的期刊“ACH”的新举措。
If this attempt fails, an error message is displayed, listing all the move lines that are considered unbalanced.
Contact information¶
If a line includes contact information, it is copied to the accounting move itself, provided the targeted journal is of type payable or receivable.
FEC Export¶
To download the FEC, install the France - FEC Export`(`l10n_fr_fec) module, then go to . In the FEC window, fill in the following fields:
Start Date
End Date
Test File: Enable this option to test the FEC file generation.
Excluded Journals
Then, click Generate.
Liasse fiscale¶
The liasse fiscale (tax returns) is a collection of standardized financial documents that businesses must submit annually to the tax authorities. It comprehensively summarizes the company’s financial activities and determines corporate taxes.
Teledec is a platform used to prepare and submit tax returns using data from accounting records. To synchronize your accounting data stored in Odoo with Teledec and electronically send your company’s liasse fiscale to the DGFiP (Direction Générale des Finances Publiques), follow these steps:
Teledec account creation¶
To create a Teledec account, access the Teledec account creation page and fill in the Adresse e-mail field with an email address. Choose a secure password, accept the general terms and conditions by checking the box, and click S’enregistrer to save. Then, enter the SIREN number of the company.
備註
If the account has already been created, click Déjà enregistré? (Already registered).
Company registration and fiscal year information¶
To register the company on Teledec, go to Vos entreprises (Your companies) and click Enregistrer votre entreprise (Register your company). Make sure to fill in the following company information in the Coordonnées de l’entreprise (Company’s details) and Représentant légal (Legal representative) sections:
Nom de l’entreprise: Company’s name.
Forme juridique: Select the company’s legal form.
Les comptes sont clôturés le: Closing date.
Régime d’imposition, choix de la liasse: Select the Tax scheme and tax return option.
Adresse du siège social: Head office address.
Nom du représentant légal: Legal representative’s name.
Agissant en qualité de: Legal representative’s function.
Numéro de téléphone: Phone number.
Click Sauvegarder (Save) to display the next step Informations générales sur l’exercice déclaré (General information about the declared fiscal year). Then, fill in information on the financial year, such as the fiscal year start and end dates or the closing date and duration of the previous fiscal period. After saving, the list of documents included in the liasse fiscale is displayed, including both standard tax forms and those customized for the company’s tax return.
小訣竅
The Etat (Status) column shows the progress of the document filing.
Click Compléter to fill out a document, then Sauvegarder to save.
To print a blank version of the declaration, click Imprimer la déclaration and select the Imprimer la déclaration avec les notices option.
Odoo synchronization¶
To enable Odoo to automatically fill in the data for the Liasse fiscale, click Autres actions (Other actions) in the top-right corner and select Synchroniser avec un logiciel tiers (Synchronize with third-party software), then Synchroniser cette liasse avec Odoo (Synchronize this liasse with Odoo).
In the Synchroniser cette liasse avec Odoo window, fill in the following information to complete the synchronization:
Nom / URL complète de la base de données Odoo: Odoo database name or URL. To provide the full URL of the database, enable Je voudrais donner une url complète hors .odoo.com option.
Nom de l’utilisateur: User name associated with the Odoo account.
Clé API: API key generated by the Odoo instance.
備註
In a multi-company setup, the following configurations are required in Odoo:
Next, click Importer to synch data from Odoo. In the Confirmation de la synchronisation de liasse avec Odoo window, review the amounts and make any necessary changes. Then click Importer la balance to confirm the synchronization of the liasse fiscale with Odoo and import the balance.
重要
Clicking Importer la balance may overwrite or alter any manual updates made previously.
To make payment and send the declaration to the tax authorities, click Paiement & envoi de la déclaration.
Point of sale¶
VAT anti-fraud certification¶
Since January 2018, new anti-fraud legislation has been in effect in France and its overseas territories (DOM-TOM). This legislation establishes specific requirements for the integrity, security, storage, and archiving of sales data. Odoo complies with these legal requirements by providing a module and a downloadable certificate of conformity.
Anti-fraud cash register software, such as Odoo (CGI art. 286, I. 3° bis), is required for companies taxable in France or DOM-TOM, where some customers are private individuals (B2C). This rule applies to all company sizes, but auto-entrepreneurs exempt from VAT are unaffected.
Odoo certification¶
The tax administration requires all companies to provide a certificate of conformity confirming that their software complies with anti-fraud legislation. In case of non-compliance, a €7,500 fine may be imposed.
備註
This certificate is granted by Odoo SA to Odoo Enterprise users.
To get the certification, follow these steps:
Install the France - VAT Anti-Fraud Certification for Point of Sale (CGI 286 I-3 bis) (
l10n_fr_pos_cert) module.Set the Country field on the company record to encrypt entries for the inalterability check.
Download the mandatory certificate of conformity delivered by Odoo SA.
反欺诈功能¶
反欺诈模块引入了以下功能：
Inalterability¶
All methods to cancel or modify key data in POS orders, invoices, and journal entries are deactivated for companies located in France or any DOM-TOM.
備註
In a multi-company environment, only the documents of such companies are impacted.
安全¶
To ensure inalterability, every order or journal entry is encrypted upon validation. This number (or hash) is calculated from the document’s key data and the hash of the precedent documents. The module introduces an interface to test the data’s inalterability. The test will fail if any information is modified on a document after its validation. The algorithm recomputes all the hashes and compares them against the initial ones. In case of failure, the system points out the first corrupted document recorded in the system.
Only users with administrator access rights can initiate the inalterability check:
For POS orders, go to ;
For invoices or journal entries, go to .
儲存¶
The system also processes automatic sales closings daily, monthly, and annually. Such closings compute the sales total for the period and the cumulative grand totals from the very first sales entry recorded in the system.
To access closings, either go to or .
備註
Closings compute the totals for journal entries of sales journals (Journal Type = Sales).
For multi-companies environments, such closings are performed by company.
POS orders are posted as journal entries at the closing of the POS session. Closing a POS session can be done anytime. To prompt users to do it daily, the module prevents them from resuming a session that was opened more than 24 hours ago. Such a session must be closed before selling again.
A period’s total is computed from all the journal entries posted after the previous closing of the same type, regardless of their posting date. Recording a new sales transaction for a period already closed will be counted in the very next closing.
小訣竅
For test & audit purposes, closings can be manually generated in developer mode. To do so, go to . In the scheduled actions list view, open the desired Sale Closing action and click Run manually.
工作內容¶
Uninstalling this module will reset the security hashes. This means the system will no longer guarantee the integrity of the past data.
Users are responsible for their Odoo system and must operate it carefully. Modifying source code responsible for ensuring data integrity is not allowed.
Odoo is not responsible for any issues with this module’s functionality if caused by uncertified third-party applications.