One Oracle environment. Many countries.
France tab, Germany spreadsheet, Poland portal. Country by country compliance gets dangerous when every local solution creates its own version of the truth.
Please do not create many truths.
Picture the international tax manager. France tab open. Germany spreadsheet. Poland portal. Norway project folder. Belgium documentation. Someone asks about Spain. Another Teams message appears.
"Which number is correct?"
This is where country by country compliance becomes dangerous. Not because local rules are wrong, but because every local solution can slowly create its own version of the transaction.
The obligation changes. The source should not.
Our view is different. The obligations differ per country, but the underlying Oracle finance reality is one and the same:
- e Invoicing4itax
- e Reporting4itax
- e Filing4itax
- e Audit4itax
Different compliance outcomes. The same source.
And when something does not reconcile? Fix the source in Oracle and let it flow through again.
Simple does not mean simplistic. Sometimes simple architecture takes the most discipline. But it scales a lot better than another spreadsheet called FINAL FINAL VAT v7. 馃槈
Originally published on the itax4apps LinkedIn page on 27 October 2026.