Why I built this
This is a thought exercise.
I had a conversation scheduled with a CFO operating across 30+ African markets. Before our call, I wanted to make my thinking concrete — not pitch a product, but show how I think about the role of AI and automation in multi-entity finance operations.
So I built this in a few days.
It’s not a product. It’s a sketch. The sample data uses Flutterwave-themed entities because that’s the customer context I was thinking about. The validation logic is real but bounded — it handles the validation layer, not consolidation itself.
The sketch focuses on one specific workflow: the back-and-forth between subsidiary finance teams and group finance during the validation cycles that precede consolidation. In multi-entity environments, this work quietly compounds. A subsidiary submits a trial balance. Group finance reviews. Sends back questions. Subsidiary responds. Group finance reviews again. Across 30+ subsidiaries, those cycles stack.
This is one of the workflows where AI can credibly compress time — by catching the catchable issues before human review begins.
What this sketch demonstrates
- Pattern recognition for unmapped accounts and typos
- Period-over-period anomaly detection with materiality thresholds
- Intercompany transaction identification
- Classification consistency checks
- Suggested resolutions with confidence scoring
What it doesn’t do
- Replace consolidation software
- Handle currency translation
- Perform actual eliminations
- Replace controllers or accountants
The judgment work in finance still belongs to humans. The validation work is where AI assistance can move the needle.
— Isaac Olorode