Why leaders wait weeks for their own numbers, and how to end the wait
Par JBS Praxis · Publié le samedi 7 novembre 2026
Résumé
When finance, stock and purchasing each keep their own system, consolidated figures arrive weeks after the period they describe. We connect the systems you keep to one database, with agreed definitions, so leaders read the same figures the teams work from.
Le problème
In many mid-sized and large organisations in Nigeria and Cameroon, each department runs its own system. Finance uses an accounting package. Logistics uses an application written years ago. Purchasing runs on spreadsheets sent by email. Each system is right on its own terms, and none of them agrees with the others.
So the consolidated picture is assembled by hand. Every month, someone exports, copies, reconciles and corrects. The board pack arrives weeks after the period it describes, and by then the business has moved on.
The delay is more than an inconvenience. The gaps between the systems are where stock losses go unnoticed, where purchasing irregularities hide, and where a cash shortfall appears with little warning. Meetings spend their time on which figure is right instead of what to do about it.
Ce qui a été fait
We do not replace the systems your teams rely on. We connect them to one source of truth.
1. List every source. We record each system and spreadsheet that holds a figure leaders use: who owns it, how often it changes, and how it can be read, whether by export, by database connection or through an API.
2. Agree the definitions. What counts as a sale, when stock counts as received, which exchange rate converts naira and CFA francs, and when a month is closed. Each definition is written down once and used everywhere.
3. Build the pipelines. Scheduled extract, transform and load (ETL) jobs copy data from each source into one relational database, usually PostgreSQL. Each load is checked: totals must reconcile with the source, and missing or duplicate records are flagged. The data is normalised so that each fact is stored once, and its history is kept.
4. Report from one place. Dashboards and the month-end pack read from that database. Every figure shows its source and when it was last refreshed, so anyone can trace a number back to where it came from.
5. Hand over the running of it. Your team owns the pipelines, with an alert when a load fails and documentation for each source.
Le résultat
Consolidated figures are ready as soon as the sources are refreshed, every figure can be traced to the system it came from, and meetings start from one set of numbers.