Implementation perspective. A hardware wholesale company based in Gaborone needs an accounting system that produces reliable balances, not merely attractive dashboards. This guide addresses process design, controls, reconciliations and acceptance testing for operations supplying Francistown.
OTN Consulting Limited is a Nigeria-based accounting and systems consultancy. This article provides general guidance, not a representation that the firm is licensed to provide regulated services in Botswana.
Map the accounting process before configuring software
Document how the Gaborone business orders goods, approves purchases, receives inventory, transfers goods to Francistown, invoices customers and records settlement. Identify the documents supporting each transaction and who can authorise changes. Select three real examples, including one exception, for end-to-end testing.
Design the chart of accounts and reporting dimensions
Agree separate ledger treatment for trade receivables, payables, inventory, goods in transit, freight clearing, taxes and exchange differences. Do not create a separate general-ledger account for every warehouse if the system supports appropriate location reporting. Define the reports the owner and finance manager will sign off monthly.
Clean data and reconcile opening balances
Deduplicate customers, suppliers and item codes. Reconcile bank balances, customer statements, supplier statements and stock counts to the old trial balance. Investigate differences before import. Preserve evidence supporting opening fixed assets and historical tax balances.
Configure VAT invoicing only after local review
Confirm current requirements with the Botswana Unified Revenue Service and an appropriately qualified Botswana adviser. Document tax codes, invoice fields, credit-note rules and the reconciliation between the ledger and any required official electronic invoicing process. Configurable tax rates alone do not establish authorised integration or local compliance.
Test a complete Gaborone–Francistown transaction
- Enter a supplier invoice and record the goods receipt.
- Allocate eligible freight and import costs under the company’s accounting policy.
- Transfer stock to Francistown and record a quantity discrepancy.
- Invoice a customer, then process a return or credit note.
- Record a partial payment and reconcile the bank entry.
- Compare stock valuation, aged balances, tax reconciliation and trial balance.
Document expected and actual results, the responsible tester and evidence of correction before acceptance.
Set user responsibilities and period-close controls
Separate supplier creation, purchasing, payment approval and stock adjustment where staffing allows. Agree approval limits, a correction policy and monthly reconciliation responsibilities. Confirm what the selected system logs rather than assuming all edits are traceable.
Plan training, cutover and continuity
Train staff on their own transactions and exceptions. Agree a cutover date, a parallel reconciliation period, data-export procedures and a contingency for interrupted connectivity. Obtain formal sign-off from operations and finance before relying on the new ledger.
Define implementation acceptance criteria
Require balanced opening data, reconcilable sample transactions, agreed reports, documented user access and resolution of material exceptions. A successful login or posted invoice is not sufficient evidence of readiness.
Professional support and local scope
OTN’s system migration guide explains common cutover risks. For statutory interpretation or regulated representation in Botswana, engage appropriately authorised local professionals. Software choice should follow the documented business requirements, not a vendor’s marketing promises.
Frequently asked questions
When should the old ledger be retired?
Only after opening balances and representative transactions reconcile and responsible staff have signed off.
Who owns tax configuration?
The company should appoint a responsible finance lead and obtain local specialist review where necessary.
How should the project be closed?
Keep a signed acceptance register, unresolved-issues log, training record and export of configuration decisions.