Accounting, payroll and point-of-sale software for businesses operating in Zambia. One double-entry ledger, in kwacha, structured for ZRA Smart Invoice.
Revenue, cash, receivables, payables, payroll and stock, with the exceptions that need attention — rather than a list of journals to interpret.
Revenue is up 12% on last month, but outstanding receivables grew 21% — three customers account for 64% of what is overdue.
Payroll is 31% of operating expenses. Cash is healthy today, but projected reserves may fall below your K120,000 target within about 21 days if collection times hold. Prepared at 06:00 from the posted ledger, read-only.
Strong profitability and cash, held back by slower collections.
Their longest delay this year. K47,200 still open in total.
The same items cost K3,400 more this quarter than last.
Selling 40 bags a week; 34 left at the Lusaka warehouse.
It grew 30% this quarter and is 18% of revenue.
Illustration with sample data. Balances are read from posted entries, never recalculated for display. The briefing, health score and insight cards belong to the AI layer, which is in development.
Many businesses in Zambia keep their accounts in one place, their payroll in another and their stock separately, and only bring the figures together at year end — months after anything could be done about them. CloudEdge Finance holds all of it in one system, so the position of the business is available while it still matters.
The accounting engine is the system of record. Every invoice, bill, expense, till sale and payroll run posts a balanced double-entry journal — debits equal credits, or it does not post. Posted entries are immutable; corrections are made by reversal, credit note or adjusting journal, so the history stays auditable.
Payroll is a core module, not an add-on. Salaries, allowances, overtime, bonuses and staff loans feed a deterministic engine that pro-rates starters and leavers, calculates PAYE, NAPSA and NHIMA with both portions, issues payslips and posts the run to the ledger — the statutory liability standing until it is paid.
Tax is configuration, not code. VAT categories are effective-dated data mapped to nominated accounts, so a rate change is a setting rather than a release — and the same structure is what a ZRA Smart Invoice submission requires.
An AI layer sits above the engines, never inside them. It reads the same ledger under the same permissions, and its role is to explain, analyse, forecast and prepare work for review. It cannot post a journal, alter a record or approve its own work: financial actions proceed only once a person authorises them, and every step is recorded in the audit trail.
A question such as "can we afford another employee?" touches cash, payroll and collections at once. The answer is presented with its workings — assumptions, data used and confidence — because a recommendation that cannot be checked should not be relied upon.
The hire adds K12,720 a month including employer contributions, raising payroll from 31% to 34% of operating costs. Profit stays comfortably positive. The pressure is timing: an October start lands on the same weeks as the dip already in your forecast.
Salary K12,000 · start November 2026 · customers keep paying in about 38 days · revenue follows its last six months · no other hires or large purchases.
Sensitive to collections. If ABC Limited's K47,200 arrives a month late, even a November start dips below target for about a week.
Costs are calculated by the payroll engine. The AI layer explains them and does not alter any record.
Each capability operates at a level of autonomy set by the company, and actions taken by the AI layer are identified as such in the audit trail, with the approver named.
Reads the ledger, explains the figures and identifies what merits attention.
Drafts the reminder, purchase order or categorisation and submits it for review.
Financial actions are queued for authorisation, showing amount, reason and risk.
Permitted only within limits the company defines, tested by the policy engine.
Accounting, sales, purchases, payroll and point of sale are in production today. The AI capabilities shown here are in development — intended behaviour, not features available in the product at present.
Sales, purchases, payroll and stock post to the same ledger, so the reports describe the business itself rather than a record kept alongside it.
Chart of accounts, journals, trial balance, profit and loss, and balance sheet. Posted entries are immutable; corrections are made by reversal or adjustment.
Quotations, invoices, credit notes, receipts and statements as branded PDFs, with VAT applied by tax code and effective date rather than a fixed rate.
Suppliers, purchase orders, supplier invoices and expenses, with input VAT posted to the account mapped for each tax category.
Employees, salaries, allowances, overtime, bonuses and staff loans. Pay pro-rates for starters and leavers, and each approved run posts to the ledger.
Touch-screen till with tax-inclusive pricing, shifts and cash-ups. Sales continue during a loss of connectivity and synchronise when the line returns.
Invoice, customer and tax-category data structured to the ZRA VSDC specification. Submission is enabled once ZRA issues the device — no re-keying into a second system.
Payroll registers, statutory liability, VAT by category, and customer and supplier positions — each drawn directly from posted entries.
Statutory rates, tax categories and posting accounts are effective-dated configuration, so a change in the rules is a setting rather than a new release.
We set up your chart of accounts, opening balances, employees and stock, and support you through the first month-end on the system.
Get in touch