When did you last redesign your finance processes?
Most often, never. They accumulated — every workaround had a good reason the day it was invented. For us, consulting rarely starts with Odoo: it starts with the needs of the business. We analyse, redesign and optimise your finance processes so that they work the way your business works — order to cash, procure to pay, expenses, record to report. We cost each gap, rebuild the sequence, and automate only what the repaired process makes safe to automate.
You recognise at least three of these
None of them is dramatic. It is their accumulation that costs.
- The same figures are re-keyed into a spreadsheet before anyone trusts them.
- Describing what happens between an order and its payment takes three people, and they do not agree.
- Errors surface at the close, never before.
- Nobody decided who approves what: it settled itself.
- An order crosses several systems before it reaches accounting, and nobody knows which one is authoritative.
- The close lands somewhere between day eight and day fifteen, and nobody can say why this month.
- The same expense is not posted the same way twice, depending on who enters it.
- The flows that worked at the start stopped fitting, and nobody has had the time to rebuild them.
- One person's absence delays everything.
None of this is a people problem. These are the signs of a process that grew rather than one that was designed.
What a process nobody designed actually costs
Not the hours spent on it — those are the visible part. The real cost is elsewhere, and the close is its clearest example: every decision taken between month-end and the close is taken without figures. Ten to fifteen days of flying blind, every month, forever. The other four flows each have their own version of the same bill.
- D+10 → D+3the close timeline we target after a process rebuild
- 1 → 0re-keying steps between the ERP and the reported figure
- Namedevery step has an owner and a deadline, visible to you
What we optimise
Five flows. Yours is one of them, or several.
- Order → CashInvoicing, collections, reconciliation. A connected bank account is not the same thing as a reconciled bank: left alone, you chase customers who have already paid — and not the ones who have not.
- Procure → PaySuppliers, approval, invoices, payments. Left alone, you pay twice or too late, and nobody can retrace who approved what.
- Expense managementSubmission, approval, control, posting. Left alone, VAT is under-recovered and the control happens after the payment.
- Record → ReportClose, analytical accounting, reporting. Left alone, the close gets longer and nobody can say what is doing it.
- Operations → FinanceSales, purchasing, stock and operations, connected to accounting properly. Left alone, a stock movement reaches the accounts only at inventory — and the difference no longer has an explanation.
How we do it
Six steps. The first five are a project — four weeks, typically, of which the first two are observation: we propose nothing before we have watched a real close. The sixth has no end date.
- 1AnalyseWe map the process you actually run, not the documented one — step by step, with the waits and the rework — and we cost each break.
- 2Target processThe sequence as it should run, inside Odoo, with the controls that make it hold.
- 3ScenariosTwo or three ways to get there, costed in effort and in weeks. You choose. We do not hand down a verdict.
- 4ImplementationWe write the accounting rules and their acceptance tests. Your integrator builds. We confirm it books correctly.
- 5TrainingWe train your team and document the process, so that it does not depend on us.
- 6Continuous improvementWhere we also keep your books, we are in the process month after month — we see it drift before you have to tell us.
What you receive
A decision document, not a slide deck.
- The AS-IS mapYour close as it actually happens, with every handover and every wait state visible.
- The ranked gap listEach one costed, so you can stop after the first three if that is all the appetite you have.
- The target modelThe rebuilt sequence, with the Odoo configuration and the controls it requires.
- A phased roadmapEffort estimated, owners named, quick wins separated from structural work.
When configuration is no longer enough
Sometimes the answer is not a better process inside the same shape. These are the situations where we work on the shape itself.
- Growth
- Reorganisation
- A change of business model
- A reporting framework that no longer fits
- Transforming the finance department itself
- Structuring a Finance/Odoo project
- Coordinating everyone involved
What we automate, once the process is right
- Invoice capture and codingSupplier invoices arrive, are read, and land on the right account and the right analytical axis — with the exceptions routed to a person rather than guessed.
- Bank reconciliationReconciliation models handle the repetitive matching. What does not match comes back as a short list instead of being buried in a statement.
- Expense handlingSubmission, approval and posting follow one set of rules you decide, rather than one habit per team.
- Recurring entries and closing tasksAccruals, allocations and the monthly checks are scheduled instead of remembered.
- The controls around all of itAutomating without a control is a faster way to be wrong. Every rule above ships with the check that tells you when it did not apply.
When this is not the answer
Process work fixes sequence and ownership. It does not fix these.
- Your data arrives wrong — that is Data & integrations, and it has to come first.
- You need more hands, not a better process. Sometimes the honest answer is headcount or outsourcing the bookkeeping.
- Your Odoo is not configured for finance yet. That is not a process problem but a setup one — chart of accounts, journals, accounting parameters, opening balances. We do that work, alongside your integrator who carries the system. It is a different project from this one.
Common questions
Typically four weeks: two of observation, two of design. We do not propose a target model before we have watched at least one real close from the inside.
Read access is enough for the mapping. We never need write access to produce the diagnosis, and we say so before you grant anything.
No. The observation phase is deliberately passive — we watch the close you were going to run anyway. Changes are proposed for the following cycle, never mid-close.
That is a legitimate outcome and we separate them for exactly that reason. The roadmap is phased so you can stop after phase one without the work being wasted.
Both are possible. The roadmap names which parts we can execute, which belong to your integrator, and which your team is better placed to do.
Find out whether it is the process or the tool
Twenty minutes on your Odoo, free, and you leave knowing which one it is.
Book the free diagnostic