The essentials

The product you envision

AiO demands seven technical capabilities that are rare on this market: an immutable double-entry ledger, idempotency over an unstable network, multi-partner reconciliation, cash and float management, KYC/AML, roles sealed per branch, and a degraded mode that never stops the counter.

We have already built most of these blocks in production: Mobile Money collections, payment ledger, sealed roles, operation over unstable 3G, accounting exports.

What AiO is — and what it is not

AiO does not move money: your partners do. AiO records, controls, reconciles and proves.

It is therefore not a till application with reports. It is an accounting system in double entry, multi-currency, multi-branch, multi-tenant, with external reconciliation and regulatory constraints. That distinction governs the whole architecture: the core of the product is not the entry screen, it is the ledger and the matching engine.

It also governs a decision that cannot be undone. Your §3.2 creates a "Super Administrator — Software Publisher" profile responsible for managing licences, and your chapter 25 asks for multi-company administration. Multi-tenant isolation is therefore not a version 2 feature: it is your business model. It is set in the database, at the first table created.

The principle that structures everything

You close your specification on a requirement marked non-negotiable: Zero Double Entry. An operation is captured once, and then feeds every process concerned without re-keying.

This is not a slogan, it is a verifiable constraint. When an operation is recorded — by API, file, email or at the counter — five things happen in the same database transaction: the cash movement, the ledger postings, the commission calculation, the compliance checks, the audit log entry. All five succeed together, or none applies.

What we deliver

• The modules of chapters 8 to 27 of your specification, plus Visa Cards and Banking Partners announced in chapter 4 without being specified there — excluding the iOS application, which your own §2.2 announces as a future version
• Two applications: the counter (web, installable, usable offline) and the supervision back office
• One partner module, configured per partner — Western Union, MoneyGram, Ria, JUBA, KORI
• Full general accounting: chart of accounts, journals, trial balance, bank reconciliation, financial statements, budgets, closings

Commitments

• No entry can be edited or deleted — UPDATE and DELETE rights are revoked in the database itself. A correction is a reversal.
• Code repository in your name, fed from the first week. Custom developments are assigned to you on full payment.
• Tooled security audit and performance testing at month 5, timed restore drill before production — reports delivered. The external penetration test is deferred to phase 2, of little relevance on a platform not yet exposed to real traffic.
• Training for the six audiences, full documentation, and six months of maintenance and support included.

Delivery

Go-live at month 6, then six months of included maintenance. Four instalments, each tied to a demonstration run in your presence against numbered criteria — of which only 5,000,000 FCFA are drawn from your working capital.