Odoo Accounting Consultant, France

Journals, partner accounts and lettrage in Odoo

A French accountant expects to open the ledger and see receivables and payables broken down by third party, with each invoice matched to the payment that settled it. Odoo stores receivables on a common account and keeps the detail through the partner on each line. The information is the same; the presentation differs.

Decisions I settle early:

• Journal codes. Short, stable codes for each sales, purchase, bank and miscellaneous journal, chosen with the accountant. Renaming journals after go-live confuses everyone reading historical exports.
• Partner references. Each customer and supplier carries a reference that appears in exports as auxiliary information, so the accountant can follow a third party across periods.
• Dedicated accounts where needed. Some accountants want separate accounts for specific customer groups, such as intercompany or public sector customers. Odoo allows different receivable accounts per partner when that is justified.
• Matching. Odoo's reconciliation assigns matching numbers that play the role of lettrage. I check that partial payments, grouped payments and credit notes all produce a clear match.

Once the structure is set, I test it from the accountant's side: can they find a customer's balance, see what is open and trace a payment to its invoices, using their own tools on exported data? The product overview is on my Odoo Accounting consultant page.

Reviewing the FEC field by field

The accounting entries file used in French tax audits has a defined set of columns, and each must be filled consistently. Odoo's French localization can generate the file, but the quality of each column comes from configuration and daily practice. Rather than treat the export as a single pass or fail test, I review it column by column with the expert-comptable.

• Journal and entry identifiers. Do journal codes and labels make sense, and are entry numbers continuous within each journal?
• Account and auxiliary data. Do receivable and payable lines carry the partner detail the accountant expects, and are partners without references caught?
• Document references and dates. Does each line point to the invoice or supporting document, with document date and posting date distinct where they differ?
• Matching information. Are lettrage codes and dates exported for reconciled lines?
• Validation data. Are entries posted and validated, rather than left in draft, at the time of export?
• Currencies. For foreign currency transactions, are amounts and currency codes present?

Problems usually trace back to a handful of causes: manual entries created without references, imported opening balances with missing partners, or a journal set up hastily. Fixing them in the test phase is quick. The general French Odoo context, including the edition question, sits on my Odoo consultant France page.

TVA on receipts and protecting posted entries

In France, TVA on many services generally becomes due when payment is received, while on goods it generally follows the invoice or delivery. Your expert-comptable confirms the rule for your activities and any options you have taken. In Odoo, taxes due on payment are handled by posting the tax first to a waiting account and moving it to the TVA due account when the invoice is paid.

That mechanism works, but it needs testing in the situations where it tends to go wrong:

• an invoice paid in several installments across different TVA periods
• a credit note applied against an invoice that was partly paid
• a customer deposit received before the invoice exists
• a mixed invoice containing both goods and services

For each case we compare Odoo's TVA report with a manual calculation from the accountant.

Record integrity is the other French expectation. Accounting entries, once validated, should not change without a trace. Odoo offers period lock dates, invoice numbering controls and, in its French localization, features aimed at proving that posted sales records have not been altered. Requirements are strictest around cash registers and point of sale, which your accountant can confirm. I configure lock dates and access rights so that only defined roles can reopen a period, and test that a regular user cannot edit a posted invoice.

Intercompany flows and the edition decision

French groups often combine a holding company, an operating company and sometimes a property or services entity. Foreign groups may have a French sales subsidiary trading with a European parent. A single Odoo database can host all of them, while every company keeps its own French or foreign setup.

Design choices I make with finance:

• Which flows are automated. Odoo can create a mirror bill in the receiving company when an intercompany invoice is posted. Useful for recurring trade, less so for occasional recharges.
• Management fees and cost sharing. Invoiced on a schedule with keys documented for the accountant and, where relevant, for transfer pricing files.
• Cash pooling and current accounts. Balances between entities tracked on dedicated accounts and reconciled monthly on both sides.
• Group figures. Consolidation in Odoo or in a separate tool, decided before go-live.

These requirements feed the Community or Enterprise decision. Accounting reports, bank synchronization, some French localization pieces and several multi-company conveniences have historically sat in Enterprise. Rather than restate the general debate, I score your specific accounting needs against each option, including community modules that would need maintenance through upgrades. My multi-company ERP page looks at the same problem across platforms.

When Odoo Accounting is the wrong ledger for a French company

Odoo Accounting can run the books of many French distributors, light manufacturers and service companies. I recommend another arrangement when:

• The expert-comptable keeps the books in their own software and only needs invoices and bank data. Odoo can stay the operational system while bookkeeping remains outside.
• Group reporting runs on a Microsoft stack. A French subsidiary of such a group may be better aligned with Business Central in France.
• The company is small and service-based. Zoho Books in France may cover invoicing and TVA with less setup.
• Sector-specific accounting rules apply that dedicated French software handles natively, such as those of regulated professions.
• Nobody internal can own the accounting configuration after go-live, and no budget exists for an integrator to do it.

In each case I explain the trade-off in writing so the decision can be revisited later. To see how I compare platforms for French entities, read the ERP consultant France page; the France section of the site describes how remote work is organized. Odoo Accounting vs QuickBooks gives a neutral comparison for smaller firms.