Most of what is written about ERP stops exactly where the real questions begin. You are told that Odoo handles consolidation, the three-way match, or electronic invoicing — rarely how, and never at what cost in terms of configuration, accounting constraints, or design debt.
This blog exists to fill that gap. Each article takes one problem — just one — and follows it to the end: the business need as a CFO would articulate it, the accounting standards and regulatory constraints surrounding it, and then the actual implementation in Odoo, with its models, its limits, and the trade-offs it imposes.
These texts are long. This is deliberate: the topics that deserve to be addressed cannot be compressed into eight hundred words. They are aimed at two readers at once — the financial director who wants to understand what the system can actually support, and the architect who will have to build it. Each can read their half; the value is in reading both.