Business Central Consultant, France

TVA posting setup and VAT due on payment

In Business Central, TVA is driven by pairing two codes: one describing the trading partner, set on customers and vendors, and one describing what is sold or bought, set on items, resources and accounts. Every pairing carries a rate, accounts and reporting behavior. For a French entity those pairings should be derived from the scenarios your expert-comptable lists, never copied from another client.

Typical French scenarios to cover:

• domestic sales of goods and services at the rates relevant to your activity
• intra-EU sales to companies registered for VAT elsewhere
• purchases of services from abroad on which you account for TVA yourself
• imports and exports, with the documentation your accountant expects
• intercompany flows with group entities in France and abroad

Services raise a specific point. Where TVA becomes due on payment, Business Central can use its unrealized VAT feature, which holds the tax on an interim account until the invoice is paid. It has to be enabled and set per combination, and it interacts with partial payments, credit notes and prepayments. I test each of those cases and compare the result with a calculation by your accountant.

Every combination is documented with its purpose, so later changes do not break the return. The general product view is on my Business Central consultant page.

Analytical sections, the FEC and period closing

Many French companies run analytical accounting alongside the general ledger, with sections for departments, sites, business lines or projects. In Business Central these become dimensions. The question is which to choose as global dimensions, available directly on entries, and which to keep as additional dimensions on documents and journals.

I work through this with your financial controller:

• which analytical views management reviews monthly, and which only occasionally
• which accounts must carry which dimensions, enforced by mandatory rules
• default values inherited from customers, vendors, items or employees
• how shared costs are allocated between sections

The accounting entries export for French tax audits is the next checkpoint. Business Central's French localization targets this file, yet the content depends on how journals, source codes, document numbers and customer and vendor data are set up. I export a test period, let your expert-comptable review it in their own tools, and fix configuration issues before the first live closing.

Period closing then needs discipline: allowed posting dates restricted per user, periods closed after review, and a checklist that confirms bank accounts, intercompany balances and TVA accounts are reconciled. The broader French Dynamics picture, including hosting and e-invoicing, is on my Dynamics 365 consultant France page.

Payment files, collections and bank matching in France

French finance teams pay suppliers mainly by SEPA transfer, collect from some customers by direct debit and, in certain sectors, still use bills of exchange. Business Central handles payments through payment journals and exports, but the exact file formats and any bill of exchange handling depend on your banks and on apps the partner proposes.

What I specify and test:

• Supplier payment runs. Suggested from due invoices, approved and exported as a transfer file your bank accepts, with release in e-banking by a second person.
• Direct debit collections. Mandate references stored on customers and used in collection batches, with a process for rejected debits.
• Bills of exchange. If you use them, the partner must show how they are created, sent to the bank and accounted for. This is a frequent gap in generic proposals.
• Statement import and matching. Bank files imported and matched with rules that recognize invoice references, so reconciliation stays current.
• Customer identifiers. SIREN and VAT numbers stored and checked, since structured e-invoicing will depend on them.

Each item becomes a test script with your bank's involvement before go-live. Where a capability depends on a third-party app, I record who supports it and how it is licensed.

Fixed price or time and materials: reviewing the partner proposal

French Business Central proposals come in two broad contract models: a fixed price for a defined scope, or time and materials billed as work is done. Both can work. Each hides a different risk, and the statement of work has to be read with that risk in mind.

• Fixed price. The risk is scope. Anything not clearly described becomes a change request. I check that every requirement is mapped to standard features, an app or an extension, and that exclusions are explicit.
• Time and materials. The risk is effort. Estimates per phase, assumptions about your team's availability and the rules for stopping or re-planning matter more than the daily rate.

In both models I review:

• apps and extensions included, their licensing and who maintains them through updates
• data migration responsibilities and the number of trial loads
• the acceptance phase: who writes scripts, how defects are classified and what signs off a phase
• French-language training and documentation, and who delivers it
• support after go-live and how changes are requested and priced

You leave the review with concrete points to raise with the partner before signature. My vendor proposal review page describes the general method, and testing and UAT covers the acceptance work.

When a French company should not choose Business Central

Business Central fits many French mid-sized companies and subsidiaries of Microsoft-centered groups. I suggest a different route when:

• The business is small and needs mainly invoicing and TVA. Zoho Books in France may cover it with less partner dependence.
• The company wants to adapt the system itself with in-house technical staff. Odoo Accounting in France deserves a comparison.
• The group imposes a larger ERP template the French entity must join, so a separate local system would only add reconciliation work.
• No budget exists for ongoing partner support, which most Business Central customers rely on for updates, apps and changes.
• Requirements are still unclear. Signing any contract before the French processes are written down tends to produce change requests rather than a working system.

When the answer is to wait, I say so; that advice is not tied to any sale. The method behind platform comparisons is set out on my ERP consulting for France page, and the France overview covers working arrangements. If partner choice is open, ERP vendor selection runs it with scripted demonstrations.