Speak the entry. Approve what matters.
A round is money in, money out, and where the officer went to do it. Vasool captures all three as they happen: collections and expenses dictated in the officer's own language, both tied to a GPS-tracked route. What posts immediately and what waits is the split that matters — a repayment posts on confirmation, while a rewritten loan or a new borrower can be held for an approver. The day closes on a per-route day book, officer performance and P&L. The same flow runs in all nine markets.
The whole round, one flow, two speeds
Most lending software makes you pick: gate everything and your officers stop using the app, or gate nothing and your book is whatever the last person typed. This is built to avoid that trade — and to record the money going out and the ground covered, not just the money coming in.
Voice to data, not voice notes
The officer speaks and Vasool writes a structured record — borrower, amount, mode, date — that is searchable and reportable like any typed entry. No audio clip anyone has to listen back to at month end.
The language the officer thinks in
Dictation works in every market Vasool supports, including mixed-language phrases where the sentence runs in one language and the number in another. Officers speak normally; the record comes out structured.
Maker-checker on what you choose
Hold a staff create, edit or delete until an owner or an assigned approver allows it. It covers customers, loans, chit and savings schemes, gold sales, expenses, staff, roles and routes — switched on per role and per resource.
Gated is the exception, not the default
Ordinary collections post straight through, so volume never queues behind an approver. Only the resources you have gated wait — which is what keeps the control in use instead of switched off after a week.
Both outcomes on the trail
Approval and rejection are both recorded, with who decided, when, and what the request contained. A change that quietly appears with no history is exactly what the trail exists to prevent.
Expenses dictated the same way
Petrol, fares and market fees are spoken like a collection and land in the income and expense ledger with a receipt photo. Both sides of the round are captured where they happen, so the cash bag reconciles against the book instead of against a memory.
Every entry ties to a route
Routes are planned daily or weekly, assigned to officers and tracked to completion with live GPS and location history. Collections and expenses carry their route, which is what makes end-of-day settlement per officer possible at all.
Reports that close the day
Day book per route, officer performance with collection efficiency and expense breakdown, collection summaries, overdue and DPD ageing, cash flow by account and P&L — exportable as PDF or CSV, and answerable by voice.
Works with no network
Voice entries keep working offline on the route and sync when coverage returns. Pending requests reach the approvals inbox once the device is back online.
From spoken word to approved record
The officer speaks
One tap on the mic, then the entry — borrower, amount, payment mode — in their own language. No menus, no account search.
Vasool confirms the match
The matched borrower and parsed amount are shown before anything saves. Wrong or ambiguous, and the officer picks from a shortlist with one tap.
Routine posts, gated holds
A collection posts immediately. A change to a gated resource becomes a pending request instead of an edit to your book.
The approver decides
The request lands in the approvals inbox on the dashboard or the app. Approve and it applies; reject and it never happened — both on the audit trail.
Why speed and control belong on different entries
The argument against approval workflows in field lending is a fair one: an officer standing in front of a borrower with a queue behind them cannot wait for a manager. Every gate you add is a gate someone eventually works around, and a control that gets worked around is worse than no control, because it also gives you false confidence.
So the question is not whether to gate, but what. A repayment happens eighty times a day and changes a balance by a known amount against a known schedule — the risk in it is mishearing, and the confirmation screen handles that at the doorstep. Rewriting a loan's terms happens rarely and changes what a borrower owes — the risk in it is judgement or intent, and no confirmation screen catches either. That one needs a second person.
Vasool is built on that split. Voice makes the high-volume half fast enough that officers stop keeping a parallel notebook, which is where reconciliation problems are actually born. Maker-checker makes the low-volume half defensible. Neither works alone: fast entry without control is a book nobody can audit, and control without fast entry is a system your field staff quietly abandon.
The same flow in nine markets
Voice entry is not an India-only feature with the other markets waiting. Officers dictate in India (Tamil, Telugu, Hindi, Malayalam, Kannada and English), Philippines (Filipino, Cebuano and English), Nigeria (English, Nigerian Pidgin, Hausa and Yoruba), Kenya (Swahili and English), Sri Lanka (Sinhala, Tamil and English), Indonesia (Bahasa Indonesia, Javanese and English), Cambodia (English), South Africa (English, Afrikaans and isiZulu), Colombia (Spanish). Khmer dictation ships alongside Cambodian company setup — neither is live yet, and the market page says so rather than listing a language you cannot use.
What differs by market is not the mechanism but what is worth gating. A Kenyan SACCO cares about who added a member to a chama and who rewrote a loan before the paybill sees the repayments. A South African credit provider cares about a borrower record edited after the affordability assessment was run on it. An Indonesian koperasi cares that a change to a member's savings scheme names whoever allowed it, because the money belongs to the members. Same inbox, different list of gated resources.
Each country page sets out what that market's buyers usually gate, alongside the currency, the payment rail and the regulator they answer to.
Money in, money out, and the ground covered
A collection app that records only repayments measures half a round. The officer also spends — fuel, a fare, a market fee — and if that side is written on a slip and typed up at night, the cash bag never quite matches the book. Expenses are dictated exactly like collections and land in the income and expense ledger with a receipt photo, so both directions are captured at the moment they happen.
Everything attaches to a route. Routes are planned daily or weekly and assigned ahead of the day, officers navigate them with GPS, completion is tracked live, and a location history records where staff actually went for visit verification. Because each collection and expense carries its route, the day book is per route and end-of-day settlement compares one officer’s cash against one officer’s recorded movements rather than against a pooled total nobody can decompose.
That is what makes the reporting worth reading. Officer performance shows collection efficiency, attendance, route stats and expense breakdown side by side, so a strong collection number earned by heavy spending stops looking like a strong month. Overdue and DPD ageing, collection summaries, cash flow by registered account, a cash book and period P&L round it out, each exportable as PDF or CSV — and any of them answerable by voice when asking beats navigating.
What this does not do
Maker-checker covers customers, loans, chit and savings schemes, gold sales, expenses, staff, roles and routes. It does not yet cover individual collection entries — holding a single repayment for approval is on the roadmap and is not a shipping feature. A spoken collection posts once the officer confirms the match, and corrections to it live on the audit trail rather than behind a gate.
Approvals are also not given by voice, deliberately. Dictation is for capture in the field, where speed is the whole point; approval is a considered action in the inbox, where the approver reads the request before allowing it. An approval you could give by talking is an approval you could give by accident.
And none of this is a compliance product. Vasool holds records and enforces the controls you configure. It is not a licence, a registration or regulatory approval in any market, and no workflow in it makes an unlawful loan lawful.
What you get, stated plainly
The voice-approval flow as it actually ships today:
- Voice dictation of entries in every country Vasool supports, in local languages
- Speech converted to a structured record — borrower, amount, mode — not an audio file
- A confirmation of the matched borrower and amount before anything is saved
- Maker-checker on customers, loans, chit and savings schemes, gold sales, expenses, staff, roles and routes
- Gating configured per role and per resource, so ordinary collections stay one-tap
- Requests routed to the owner or an assigned approver, applied only on approval
- Approvals and rejections both written to an immutable audit trail
- Expenses dictated the same way, posted to the ledger with a receipt photo
- Routes planned daily or weekly, assigned to officers, GPS-navigated and tracked to completion
- Staff location history for visit verification, and every entry tagged to its route
- Day book per route, officer performance, collection summary, overdue and DPD ageing, cash flow by account, cash book and P&L
- Every report exportable as PDF or CSV, and answerable by voice
- Offline voice entry that syncs when the network returns
- Not included today: holding an individual collection entry for approval, and approving by voice