How Accounting works in GwizaSuite.
Four steps that turn daily operations into a clean, filed-ready set of books — without a single hand-typed journal entry for routine work.
Every sale, payment, clearance, and adjustment posts to the ledger automatically. No manual journal entries for routine ops.
AR and AP always tie to invoices and bills. Bank balances match the payments ledger.
Lock a period when you’re done. Locked periods become tamper-evident. Reopening is audit-logged.
VAT summary, trial balance, P&L, balance sheet. RRA-accepted formats.
Everything Accounting does.
Per-customer, aged across 0–30 / 31–60 / 61–90 / 90+ buckets. One click to email, WhatsApp, or PDF — branded per branch.
Per-supplier, aged. See exactly who you owe, when the bill was cut, and which are overdue — before the supplier chases you.
Close once and the period locks at the database. Reopen needs a reason and writes an audit entry — auditors see the full chain.
Output VAT, input VAT, net payable — exported in the exact shape the RRA asks for. Ready to file in under a minute.
Every debit and credit traces to the invoice, payment, or adjustment that created it. One click opens the source document.
Multi-account management across cash drawers, banks, and mobile-money lines. Running balances that always tie to the ledger.
Record supplier bills, allocate payments to them, track due dates. AP ledger mirrors the sales invoice workflow — symmetrical.
Customizable, with sensible Rwandan defaults pre-loaded. Add sub-accounts, rename, or reorder — changes are audit-logged.
Period close that locks the books — tamper-evident.
In most accounting tools, “closing a period” is a polite suggestion. Somebody adds a flag to a spreadsheet tab, everybody agrees not to touch it, and a month later a well-meaning junior posts a correction against March anyway. By the time the auditor asks questions, nobody remembers what was real.
GwizaSuite does it differently. When you close a period, a database-level lock refuses every subsequent write against any transaction dated in that window. The lock is signed with a hash of every transaction included — a fingerprint you can verify offline. An audit event is written with your name, your IP, your timestamp, and the exact list of balances frozen.
If you genuinely need to correct something after close, you reopen the period explicitly. The reopen writes its own audit entry with your reason. The next close re-signs the window with a new hash. Auditors see a clean chain of custody — not a “trust me” spreadsheet.
- Locked periods refuse writes at the database level — not just in the app
- Reopening requires a reason, audit-logged with actor + timestamp
- Transaction hashes preserved for forensic offline verification
- 7-year retention on every close and reopen event, per RRA
Connects to the rest of GwizaSuite.
No module is an island. Here’s how Accounting flows into and out of your other books.
When an invoice is issued → it posts to AR and revenue automatically, with VAT broken out per line.
When a payment lands → it debits cash or bank, credits AR, and the customer statement recalculates live.
When stock is cleared or sold → cost of goods sold and inventory value post automatically, no manual journal.
Accounting FAQ.
Next up: the numbers you actually show people. Thirty-plus pre-built reports, RRA-accepted exports, scheduled emails — one click from these books to anything your auditor or owner asks for.
See ReportsLess than the cost of one mistake.
Start your 14-day trial. No card. Cancel anytime.