Your Odoo project has technical consultants. Who owns Finance?

Add a finance specialist to your implementation team. doo.FINANCE is a firm of chartered accountants and Odoo financial consultants, not an integrator. On a joint proposal you remain responsible for the overall functional and technical delivery, and we take ownership of the finance-specific requirements and decisions inside it. We bid with you, never against you — and that line is in the framework agreement, not just on this page.

This page is for you if…

Every item below is a deal we have seen stall, or a go-live we have seen go wrong for a reason that was never the ERP's fault.

  • The client's accounting team keeps changing its mind, and nobody on your side can tell whether the new requirement is legitimate.
  • Inventory valuation, costing or intercompany came up in scoping, and it is not your trade.
  • The chart of accounts, the journals and the tax setup are being decided by whoever happens to be available.
  • UAT is approaching and nobody has written the finance test scenarios.
  • Differences appeared during implementation and no one can say whether they come from the data or the configuration.
  • The client's accountant, controller or CFO is blocking sign-off, and you do not speak their language.
  • Go-live is approaching and nobody can say who will keep the books afterwards.
  • Your client has entities in several countries and nobody on the team knows the local rulebooks.

What we bring to the network

Chartered accountants registered in ten countries, working inside Odoo every day — the finance side of a project, carried by people who also keep the books afterwards. That is the part an integrator cannot staff, and the part a pure consultancy does not stay for. We are also a Solution Partner of the BOP Alliance, for international financial consolidation in Odoo.

  • 10countries, with locally registered chartered accountants in each
  • 2signatures on one proposal — yours for the system, ours for the finance
  • 0ERP scopes we have ever competed for

The dividing line

Stated plainly, because a vague boundary is what makes a partnership expensive later.

  1. 1We bid togetherOne proposal, two signatures. You own the system, we own the finance inside it, and every deliverable has a named owner before anything is signed.
  2. 2The ERP scope is yoursArchitecture, configuration, development, deployment, hosting, application support. We do not compete for it and we do not second-guess it.
  3. 3We write, you buildWhen something must be developed, we write the accounting rule and its acceptance tests. You build it. We confirm it books correctly. Nobody ends up guessing what the auditor will want.
  4. 4The client stays yoursWe do not go looking for the next ERP project. Cross-referencing is written into the framework agreement, in both directions.

What we take on inside your project

Named scopes, so a bid can be priced and a plan can be built around them.

  • Opening balances and cutoverMigrating the trial balances, reconciling them, and proving the opening position before anyone books into the new system.
  • Consolidation model and group chart of accountsThe structure every entity aligns to, the intercompany rules, and the currency treatment — the design work behind the BOP label.
  • Local compliance in ten countriesVAT, statutory filings and local rulebooks, by chartered accountants registered in each jurisdiction rather than one team reading a summary.
  • Finance training for the client's teamSo the people who use the system every day understand what it is doing to their numbers.
  • The bookkeeping after go-liveOptional, and often the thing that saves the project — the client is not left looking for an accountant three weeks before the first close.

What we take on, item by item

The finance half of an Odoo project, named so it can be priced and put in a plan.

  • Accounting workshops with the client's finance team
  • Translating finance requirements into Odoo
  • Chart of accounts, journals and taxes
  • Inventory accounting, costing and valuation
  • Payment flows
  • Intercompany
  • Multi-company and branch structures
  • Opening balances and migration
  • Finance test scenarios and UAT
  • Finance training
  • Analysis of accounting differences during implementation
  • Alignment with accountants, controllers and CFOs

What we will never do

This list costs us occasional revenue. It exists so that you can put us in front of your client without checking first.

  • Compete for the ERP scope — including when the client asks us to. On a joint proposal we are on the same side of the table; we never present an alternative to your implementation.
  • Recommend that a client change integrator.
  • Invoice Odoo development, or take on application maintenance.
  • Approach your client about work outside the finance function.

What integrators ask us first

No. We bid with you, on the same proposal, and we never present an alternative to your implementation. What we do not do is pretend we are absent from ERP bids — we are on them, on your side, for the finance scope only. The distinction is written into the framework agreement.

We decline and we say why, in front of you. It has happened; it is the moment this whole arrangement is worth something, and it is why the line is in writing rather than in a conversation nobody remembers.

No. We work with the integrator in place, whoever it is. The BOP route is simply the fastest way to start, because the non-competing rule is already understood on both sides.

Whatever the agreement says. We can be a subcontractor on your engagement or contract directly with the client alongside yours — both work, and the choice is usually about who the client wants a single invoice from.

Same week, usually within forty-eight hours for a scoping question. If the answer is that we are not the right fit, you get that just as fast.

Ten, each with chartered accountants registered locally rather than a central team applying a summary of the rules. For a multi-country group that is the difference between a filing that holds and one that gets corrected.

Where this leads

Let's put the line in writing

A framework agreement takes one call to scope. It says what is yours, what is ours, and how we refer work in both directions.

Talk to us about a framework agreement