On this page
Every invoice has a clear reference.
Our collection service connects the amount being charged, the person or organisation paying it and the reference used to follow the transaction, giving the finance team a consistent record across payment channels.
An association can use the process for membership renewals, an institution for a permit or service fee, and an operator for repeated charges linked to its daily business.
From invoice to receipt
The process begins with an invoice and its reference, continues through the approved bank or mobile-money channel, and links the resulting payment to a receipt and the organisation’s reporting records.
Fee rules, payer notifications and payment-reference checks can be set around the organisation’s service, with duplicate-payment controls and review steps available for records that need attention before the process continues.
A membership renewal, step by step
In a membership-renewal workflow, the association issues the invoice against a member’s record, sends the payment instructions and uses the reference to connect the incoming payment with that renewal.
The member receives the resulting receipt and the association can see the collection in its reports, with any missing or unmatched reference passed to the team handling exceptions.
Start with your current receivables process.
Bring the invoice, the way transactions arrive today and the reports your finance team needs. The process can then be configured around the way your organisation already operates.
Current website capability record
Outcomes
- Standardised collections across channels
- Lower mismatch and dispute rates
- Clear settlement reporting and audit trails
Problems it resolves
Before
Separate bank, portal and manual records
After
One connected collection record
Before
References that do not match
After
Payments linked to the correct invoice
Before
Manual follow-up
After
Exceptions clearly identified
Before
Incomplete records
After
A complete transaction history
What is included
Core
- Standardised invoices and references
- Multi-rail payment collection
- Receipts and payer notifications
- Configurable fee rules
Controls
- Reference validation
- Duplicate payment prevention
- Role-based approvals (optional)
- Dispute-ready transaction logs
Reporting
- Collection reporting by channel
- Settlement statements
- Audit-ready exports
- Exception dashboards
Who it is for
Associations
Membership fees, renewals, and levies.
- Annual membership fees
- Event registrations
- Service charges
Government and public agencies
Permits, licences and public services.
- Permit fees
- License renewals
- Public service charges
Licensed operators
High-volume charges across logistics and trade corridors.
- Utility payments
- Logistics fees
- Trade corridor charges
Typical workflows
Member dues and renewals
- 01
Invoice issued
- 02
Payment received
- 03
Account updated
- 04
Receipt sent
Permits and levies
- 01
Charge set
- 02
Reference used
- 03
Transaction matched
- 04
Record closed
High-volume billing
- 01
Invoices issued in bulk
- 02
Transactions received
- 03
Exceptions identified
- 04
Statements produced