Compliance & controls
Audit-grade, by default.
Aligned with TIMB and national data-protection rules, a tamper-evident ledger, and two people on every decision that moves money - built into the product, so compliance happens as part of the work.
Audit-grade, not audit-anxious
Compliance is how the book is kept - not a cost bolted on at the end.
SwiftlyGMS aligns with the regulators your business answers to, and keeps regulatory figures in configuration - so when the rules change, the platform doesn't need rebuilding. Compliance happens as part of the work.
Aligned with TIMB.
Built around the regulated stop-order recovery and the returns a tobacco merchant has to file - so what your business owes the regulator comes from the same record you run on.
Data protection, respected.
Built with national data-protection expectations in mind - data-subject requests, consent and retention handled inside the platform, in plain language.
Prove it later, yourself.
A tamper-evident trail records what happened and who did it - and your own team can read and filter it themselves, by action, entity and date, without waiting on us.
Regulatory figures in configuration.
The numbers the regulator cares about live in settings, not hard-coded - so a rule change is a configuration, not a rebuild.
Is this record intact?
Append-only - each entry is sealed to the one before it.
Intact
12,480 entries verified, no gaps and nothing altered.
Recovery posted
- Who
- A. Sibanda · Finance
- To
- T. Zulu · TIMB 0042918
Reallocation approved
- Who
- T. Ncube · Company Admin
- To
- Input reallocation · $1,250.00
Inspection captured
- Who
- R. Field Officer
- To
- Plot 14 · M. Dube
In-app guidance translates regulatory obligations into operator language - so smaller teams stay aligned without a specialist in every depot.
Segregation of duties, enforced
The decisions that move money need two people. The system makes sure of it.
Sensitive actions - input reallocation, input allocation, recoveries, money leaving the business, and changes to the settings that decide money - require a second authorised approver. The approver can't be the requester. Who may propose and who may approve is set through role permissions, no code deploy.
Every approval carries a named requester and a named approver.
Input reallocation
$1,250.00
Requested
R. Field Officer
- 2
Approved by a second person
T. Ncube · Company Admin
- 3
Posted to ledger
Balanced credit / debit, on approval
The approver can't be the requester - separation of duties, enforced.
Security & data protection
Security is built into the foundation.
Strong authentication, granular role-based access and a complete audit trail are part of the platform from the ground up - not bolted on afterwards.
Complete audit trail
Every sensitive action is recorded with who did what and when - a tamper-evident history your team can read and filter for regulators or internal review.
Strong authentication
Modern password policy, account lockout on repeated failures, configurable sessions, and second-factor support for office staff.
Isolated by tenant
Each merchant's data is isolated at the database, so one organisation can never see another's growers, inputs or books.
See it on your own season
Run a tighter book, recover more, and walk into audit ready.
Book a 30-minute demo and we'll show you the working platform against scenarios that match how your merchant runs today - registration, contracting, input credit, field work and recovery.
- Register
- Contract
- Fund
- Verify
- Recover
No commitment. No spreadsheet required to get started.
