Skip to content
Silverconne

TUTORIALS

The four problems every Zimbabwean system runs into.

Written for the person who has to make the system work, not for a search engine. Each one ends where the work actually gets hard, and says what to do there.

Start with fiscalisation

Free to read, no sign-up, and nothing gated behind an email address.

ALL TUTORIALS

Four guides.

WhatsApp business automation Zimbabwe

Connecting a WhatsApp Business number to an automated first response

What has to be true before you can automate WhatsApp replies, why the 24-hour window shapes the whole design, and what the first message should say so people keep talking to you.

8 min read · updated 30 July 2026

In one line

A number can be on the WhatsApp Business app or on the platform API, not both. Plan the move before you make it.

Related: Augustus AI

Multi-currency accounting Zimbabwe

Running USD and ZWG in one ledger without breaking your reporting

Two currencies do not break a ledger. Storing one amount per transaction does. What to record on every line, where the differences go, and which balances get revalued.

8 min read · updated 28 July 2026

In one line

Store the transaction amount, the rate used and the base-currency amount on every line. Three columns, not one.

Related: CheckERP

Mobile money reconciliation Zimbabwe

Reconciling EcoCash and ZIPIT payments against your sales ledger

Three payment rails, three different identifiers, and none of them is your invoice number. Here is a matching process that clears most receipts automatically and makes the rest somebody’s named job.

8 min read · updated 21 July 2026

In one line

Never auto-match on amount alone. It is the single most common cause of a customer being told they have not paid.

Related: CheckERP

ZIMRA compliant accounting software

ZIMRA fiscalisation: what it actually requires of your accounting system

Fiscalisation is usually explained as a device you buy. For anyone choosing accounting software it is better understood as a set of things your system has to do on every sale, and keep doing when the network is down.

9 min read · updated 2 July 2026

In one line

Fiscalisation is a data obligation on every taxable sale, not a printer you bolt on at the end.

Related: CheckERP

WHY THESE FOUR

Because nobody else is going to write them.

International software companies write excellent documentation about invoicing in general. None of it tells you what to do when the fiscal interface is unreachable and there are customers at the counter, how to match a wallet payment that carries no reference, or which balances to revalue when you run two currencies. That gap is where most of the local implementation pain sits, so it is what we have written about.

Something missing?

If you are stuck on something in this territory that is not covered here, tell us. It is usually a page we should have written.

NEXT STEP

Rather have this built than build it?

Everything in these tutorials is in CheckERP already — the queue, the match order, the two currencies on every line. Twenty minutes will tell you whether it fits.

Free 20-minute call. We will tell you honestly if we are not the right fit.