Fixed assets with 4asset & 4verify
The 4Sight group's fixed-asset management and physical-verification tools — an asset register that reconciles to the general ledger, and barcode-driven verification counts that stand up to audit. Particularly at home in parastatals and grant-funded organisations.

4asset and 4verify are purpose-built, locally developed tools from the 4Sight group rather than generic add-ons retrofitted for asset management. 4asset maintains the financial and physical asset register — custodian, location, barcode, serial number and depreciation detail all tracked against a single record — and is built to integrate with the general ledger through standard data-loading formats, so the register reconciles to the GL rather than living as a parallel spreadsheet nobody trusts by year-end. 4verify handles the physical side: counts run from Android devices rather than legacy barcode scanners, checking what's actually on the floor against what the register claims.
That reconciliation between physical count and GL balance is exactly what an external auditor tests, which is why these tools land particularly well in parastatals and grant-funded organisations, where asset registers face formal audit scrutiny and funders often require documented verification cycles. For an organisation already running Acumatica, Sage 300 ERP, or another core financial system, 4asset and 4verify sit alongside it rather than replacing it — solving the specific fixed-asset and physical-verification problem that general ledgers were never built to solve well on their own.
4asset
The financial and physical asset register — custodian, location, barcode, serial number and depreciation, reconciled to the GL.
4verify
Android-device-driven physical verification counts, checked against what the asset register claims.
We implement ERP end to end — process design, configuration, data migration, go-live and the support that follows — across Acumatica, the Sage range (Sage 300 ERP, Sage Intacct, Sage Evolution, Sage X3) and Microsoft Dynamics 365 Business Central, matched to your size and sector. The goal is not software installed; it is month-end that closes on time, numbers leadership can trust, and operations captured once instead of three times.
Implementation done properly
Requirements and process design before configuration; migration with reconciliations you can sign off; user training by role; a go-live plan with a rollback path.
Acumatica Cloud ERP
Modern cloud ERP for finance, distribution, projects and CRM — unlimited-user licensing and a full REST API for the integrations that come later.
Sage 300 ERP
The financial workhorse trusted by Botswana organisations for decades — we implement, upgrade, optimise and support it, and when the time comes, we migrate it to the cloud without drama.
The wider Sage stable
Sage Intacct for cloud financials, Sage Evolution for mid-market operations, Sage X3 for larger and multi-site enterprises — implemented and supported by certified Sage consultants who pick the edition that fits, not the one on special.
Microsoft Dynamics 365 Business Central
Microsoft's mid-market ERP, at home in organisations already living in Microsoft 365 and Azure — finance, operations and reporting inside the ecosystem your team uses daily.
After go-live
SLA-backed support from Gaborone, periodic health checks, and optimisation as your processes evolve — the system should keep fitting the business, not the other way around.
How much does an ERP system cost in Botswana?
No honest partner quotes a figure before scoping, because the cost is three things: software licensing, implementation services and ongoing support. The drivers are user and transaction volume, which modules you switch on, how much data migrates, and what integrates. Licensing models differ too — Sage 300 ERP, Intacct and Business Central price per user, while Acumatica prices on consumption with unlimited users, which suits businesses with many casual users. We scope first, then quote.
How long does an ERP implementation take?
A focused financials-only implementation runs six to twelve weeks; a typical mid-market project across finance, inventory and operations runs three to nine months. The single biggest schedule risk is the quality of your existing data — which is why our method reconciles migrated data early, not at go-live.
Should we choose cloud or on-premise ERP?
Cloud gives you predictable monthly cost, vendor-managed updates and access from anywhere; on-premise gives you capital ownership and full control. In Botswana two more factors matter: connectivity resilience and where your data lives under the Data Protection Act. We implement both, and can host locally on Replic8 Cloud or on Microsoft Azure — so the answer follows your situation, not our stock.
We run Sage Pastel or Sage 200 Evolution — what is the upgrade path?
Sage's own direction is Sage Intacct for cloud financials and Sage X3 for complex manufacturing and distribution. An upgrade is not starting over: master records and opening balances migrate, and transaction history is kept in a read-only archive. A typical Evolution-to-Intacct move lands in two to four months depending on data quality and integrations.
Sage 300 ERP or Acumatica — which is right for us?
We implement and support both, so this is a fit question, not a sales pitch. Sage 300 ERP is a mature multi-entity, multi-currency workhorse with a large Botswana installed base; Acumatica is cloud-native with unlimited-user licensing, mobile access and an open API. The right answer comes from a structured demo against your own processes — which is exactly how we run selection.
Platforms: Acumatica · Sage 300 ERP · Sage Intacct · Sage Evolution · Sage X3 · Dynamics 365 Business Central · 4asset & 4verify