Judge us on your worst depot, not your head office

No. Our chart of accounts has no account-number field at all, so a numbered SYSCOHADA plan cannot be represented and a statutory presentation cannot be produced. This is a deliberate design decision rather than an unbuilt feature — maintaining a statutory plan across seventeen member states is an ongoing professional commitment, not a feature, and it is already well served locally. Your statutory books belong with a local accounting package or your expert-comptable, working from the operational records we hold. Confirm your obligations with them or the DGI.

No. English only, with no translation files in the product and no setting to enable one. All printed output — invoices, delivery notes, purchase orders, credit notes, receipts — is in English. Your data can be entirely in French, since item names, locations, customers, suppliers, projects and notes are free text we do not alter, but the frame around it is English. Test this at your least-trained site rather than at head office; it is the fastest way to a real answer.

Yes, provided the discipline is in place: lot identity created at receipt, consumption recorded against the production job at the time rather than reconstructed later, finished output carrying its own batch linked to its inputs, and the batch carried through dispatch. Forward trace is the harder direction and the one customer audits actually test. Bring a real lot to the demo and time us. We are not a quality management system and not a manufacturing execution system.

That is the right question to press every vendor on, including us, and it should be tested at the depot rather than in a demo room. What matters is whether a depot user can be given genuinely restricted access, what happens mid-capture when a connection drops, whether receipts can be entered as counts rather than as confirmations of a dispatch note, and whether a photo can be attached at the tailgate. Judge the system on the worst site you run.

Yes, both as built-in presets. The CFA franc is resolved automatically as the base currency and everything is stored, invoiced and printed in it, with no exchange rate anywhere inside the monetary union. An Ivorian value added tax rate ships as a maintained preset with net, tax and gross separated line by line on purchases as well as sales. Additional lines are configurable with their own rates and effective dates but are yours to maintain. Confirm current rates with the DGI or your adviser.

Not as turnkey statutory payroll. CNPS, the income tax scale and sector collective agreements are not maintained calculations in our product — Kenya is our only market where that is true. Employee records, contracts, leave with balances, attendance and posting payroll cost into projects and cost centres all work. The statutory computation and declarations belong with an Ivorian payroll provider or your expert-comptable, and we would rather lose that line item than have someone calculating contributions from a formula nobody has revisited since implementation.

When your operation is domestic, works entirely in French, and your complexity sits in accounting and payroll rather than in stock, procurement and multi-site operations. A good Ivorian or regional suite then gives you one accountable vendor, French documentation and support in your language, and the split we recommend would add coordination cost for no operational gain. We reach this conclusion on first calls regularly and prefer to reach it quickly.