AX-Fiduciaire is itself an accounting firm, and it uses Odoo for its own operations. That's not a minor detail: it's what sets this page apart from a generic sales pitch. What follows describes what an accounting firm actually asks of its management tool, where Odoo answers well, and where it needs to be understood before committing.
The argument most often put forward for Odoo in a fiduciary context is that it handles accounting. That's true, but it isn't the decisive argument. The decisive argument is that the accounting firm and its client can work in the same environment: no more file exports sent by email at the end of every month, no more spreadsheet attached so the client can track turnover, no more gap between the version the accountant is looking at and the version the client believes to be accurate. Both look at the same data, at the same time, in the same system. It's this change in organisation, more than the accounting function itself, that justifies rethinking the tool.
What an accounting firm asks of its tool, which isn't what an SME asks
An SME uses an ERP to manage its own accounting, its own sales, its own stock. An accounting firm does the same thing, but multiplied: it keeps, in parallel, the books of dozens of distinct clients, each with different financial years, tax deadlines and levels of autonomy. The tool must therefore handle not just accounting, but portfolio management: who is handling which file, where each year-end closing stands, which deadlines are approaching, across all clients.
This is where the real difference from a standard corporate Odoo deployment lies. An Odoo implementation for an accounting firm must be designed from the outset for this multi-file operation, not bolted on afterwards to an architecture built for a single company.
Multi-file management and access segregation
Odoo allows several companies to be managed within a single instance, with access rights configurable per user and per company. For an accounting firm, this means a staff member can be authorised on a precise subset of client files, with no visibility over the others — a segregation principle that becomes essential as soon as a firm grows beyond a handful of staff.
This segregation must be checked every time a user is created, internal or external, and reviewed periodically: access granted for a one-off cover and never revoked is a silent gap, not a theoretical case.
At the level of the portfolio as a whole, a manager needs a cross-cutting view: which files are behind on their closing, which VAT deadlines are approaching, which clients haven't yet submitted their documents for the month. Odoo allows this type of dashboard to be built from data spanning several companies, but this aggregated view doesn't exist by default for fiduciary use; it requires specific configuration, designed for the structure of the portfolio rather than for a single company.
Document processing: digitisation, recognition, validation, reconciliation
The document flow is often what weighs most heavily on an accounting firm's daily work. An invoice received by email or scanned can be uploaded to Odoo, where automatic document recognition suggests a likely supplier, amount and account code. This suggestion remains an aid to data entry, not a final posting: a staff member must validate it, particularly for unusual documents or new suppliers.
Bank reconciliation — matching each bank statement movement to the corresponding accounting document — benefits from the same principle of partial automation: Odoo proposes a match when the correspondence is clear, and leaves the decision to the staff member in ambiguous cases. This is a genuine time saving on volume, never a complete removal of human oversight.
The point not to underestimate is exception handling: the poorly scanned document, the unknown supplier, the amount that matches nothing routine. A workflow designed only for the standard case, without a clear procedure for these exceptions, ends up piling them into a queue nobody prioritises — automation saves time on routine volume, but shifts the burden onto special cases if nobody has decided who handles them and how often.
Accounting production and year-end closings
Day-to-day bookkeeping — posting, matching, account checks — and periodic closing rely in Odoo on the same mechanisms as standard company accounting, but repeated file by file. Tracking the progress of each closing, across all clients, is what allows a portfolio manager to know where the delays are without having to open every file individually. For accounting work carried out on behalf of third parties, the question to settle is the same as for any accounting service: what level of interim validation before a financial year is finally closed.
VAT and returns
Odoo calculates VAT at the applicable Swiss rates — 8.1%, 2.6% and 3.8% since 1 January 2024 — as soon as the Swiss localisation (l10n_ch module) is activated for the company concerned, and prepares the data needed for the periodic return. For an accounting firm, the challenge isn't the calculation itself, but the consistency between the return method chosen by each client (effective method or net tax rate method, quarterly or half-yearly frequency) and the actual configuration of the file in Odoo. This consistency is checked file by file, not once for the whole portfolio.
A portfolio of files also means a portfolio of VAT deadlines staggered relative to one another. The cross-cutting view mentioned above takes on its full meaning here: without consolidated tracking of deadlines per client, the risk isn't a calculation error, but a missed filing on an isolated file somewhere in the portfolio, harder to spot than an error on a single file tracked on its own.
Payroll on behalf of clients
Payroll management is one of the most sensitive flows for an accounting firm, because it directly affects clients' employees. Odoo is listed on the Swissdec register at the "swissdec certified basic" level (certificate no. 1203.25, ELM 5.3 exchange standard), which covers the standardised exchange of payroll data with social insurance bodies for basic functions. For a complex payroll file, payroll management requires a specific check of the coverage expected against this certification level, before entrusting a portfolio of client payrolls to the tool.
Managing several clients' payrolls within a single system adds a requirement beyond what an SME managing its own faces: each payroll file must remain strictly isolated from the others, with its own scales, its own compensation funds and its own filing deadlines. This segregation relies on the same multi-company mechanism as accounting, but deserves a specific check on the payroll side, where confusion between two files has direct consequences for the employees concerned.
Time tracking and billing for the fiduciary's own services
Beyond the accounting kept on behalf of clients, an accounting firm has its own business model: staff time billed to files. Odoo allows hours spent per file to be tracked and the corresponding invoicing generated from the same system. This flow must be clearly separated, in the configuration, from the accounting kept for the client: one is a service sold by the firm, the other accounting kept in the client's name — mixing them creates confusion, both accounting and contractual.
Time tracking per staff member and per file has a second, often overlooked, use: it lets the firm measure where its own time actually goes, file by file, independently of what is billed. This is internal management data, useful for adjusting workload between staff or identifying a file that has structurally grown heavier than its mandate anticipated — a use turned towards managing the firm itself, not the client.
The client portal, and what is or isn't exposed there
This is the most decisive argument, often underrated: the accounting firm and its client can work in the same environment, via a dedicated portal, rather than through a constant exchange of exported files. The client uploads their documents directly, checks the status of their accounts or VAT without waiting for a mailing, and the firm no longer has to manually keep in sync what it sees and what the client sees.
This requires deciding, file by file, what is exposed to the client on the portal and what remains internal to the firm (working notes, exchanges between staff, items still pending validation). A poorly configured portal that exposes an unvalidated entry creates more confusion than it removes.
The concrete benefit is mostly felt at the margins: fewer back-and-forth exchanges to track down a document lost in an email inbox, fewer reminders to obtain a receipt, less time spent reconstructing a history when a client changes point of contact at the firm. These are ordinary frictions, rarely highlighted, but which represent a significant share of a file's administrative time — and it's precisely on this share that the portal changes day-to-day operation.
Security, access rights, professional secrecy
Fiduciary professional secrecy imposes requirements that go beyond a standard ERP configuration: who can view which file, where data is hosted, what traceability exists on access, what clauses bind the firm to its host. These are points to document explicitly for fiduciary use, not settings that can be assumed correct by default. The multi-company segregation mentioned above is the technical building block; the access policy and its periodic review are the organisational one, equally necessary.
The honest limits
Odoo is not a specialised multi-file accounting firm software, and this needs to be stated clearly. Dedicated fiduciary software natively offers certain cross-cutting functions — time-based invoicing consolidated across the entire portfolio, a single regulatory deadline tracker spanning all files, document templates specific to regulated fiduciary reporting — that Odoo doesn't cover out of the box and that require additional configuration or development.
This limit matters particularly for a firm managing a very large number of small files with highly standardised deadlines: the benefit of specialised software, built for that volume, can outweigh the advantage of a single tool shared with clients. Conversely, for a firm managing a tighter portfolio, with clients who genuinely benefit from the shared portal, the balance tips towards Odoo. The right decision depends on the actual structure of the portfolio, not a general preference for one tool over another — a point that a migration project from an existing fiduciary software must settle before starting, backed by support that knows both worlds.