The Promise to Pay That Nobody Wrote Down
Collections runs on promises made over the phone, and a promise nobody records is one the reminders do not know about. A collections workspace now keeps the promise, holds the reminders off until its date, and says the next morning whether it was kept.
The bursar of a secondary school in Machakos owed an office-supplies distributor KES 180,000. On a Monday the distributor’s collector rang, and the bursar was straightforward: the capitation money would land by the 15th and she would pay then. The collector wrote it on a sticky note. On Tuesday morning the automatic reminder went out anyway, a firm one, to the school’s principal. On the 16th nobody noticed that the money had not come, because the only record of the promise was on a desk.
Two failures, pulling in opposite directions. The system chased a customer who had already agreed a date, and then nobody chased a customer who had missed it. Both come from the same place: the promise was made to a person and never reached the record the reminders read.
A board of who owes what, one currency at a time
The Collections workspace shows customers in aging lanes: current, 1–30 days, 31–60, 61–90 and over 90. Each customer sits in the lane of their oldest overdue invoice, because that is where the collector’s attention belongs, with the split of their balance shown alongside. The board shows one currency at a time. A customer who owes in shillings and in dollars appears on both boards, never on one with the two figures added together.
Each customer can have a collector assigned, so the board filters to “mine”. From the customer’s collections page you can see every promise and its outcome, open follow-up tasks, and the reminder history — each dunning stage sent, with its channel, and every email logged to the customer’s address — and download a statement as a PDF or a CSV.
The promise, written down
-
Record it while you are on the phone
Amount, currency, the date, and a note: “capitation expected by the 15th.” The date must be today or later. One promise per customer and currency is live at a time; recording a new one replaces it. The collector can do this on the web or in the app.
-
The reminders hold off
While the promise is open and its date has not passed, the dunning ladder skips that customer: no email, SMS or WhatsApp reminder goes out. The bursar is not chased for a date she has already agreed.
-
The next morning, it is settled
After the promised date, the promise is marked kept if payments received in that currency, from the day it was recorded to the promised date, reach the amount. Otherwise it is marked broken, and the ladder resumes.
-
A broken promise stays visible
The board flags a customer with a broken promise for 90 days, so the collector who rings next knows what was said last time.
Kept is measured, not ticked
Nobody marks a promise kept by hand. It is settled from the payments recorded against the customer, in the promise’s currency, between the day it was made and the day it fell due. A part payment leaves it broken, with the amount actually paid stored beside it, which is the conversation the collector needs to have next.
When the customer says the invoice is wrong
Sometimes the customer is not late; they are disputing. The school says it was billed for 40 reams and received 30. Chasing that invoice before anyone looks at the delivery note is how a customer relationship ends.
An invoice dispute records the reason — pricing, quantity, damaged goods, wrong item, not received, duplicate billing, tax, service quality — the amount in question, the lines, and evidence, including a forwarded email saved as a file. While a dispute is open or under review, reminders stop for that invoice only; the customer’s other invoices are still chased. A dispute closes one of three ways:
- Resolved with a credit note. The credit note is drafted from the dispute, and returned goods can go back into stock or into a quarantine hold. Where the workspace has switched on credit-note approval, the note waits for someone other than its author, and the dispute closes only when the note is actually issued.
- Rejected, with a note. Reminders resume for that invoice.
- Withdrawn, with a note. Reminders resume for that invoice.
Every step goes on a timeline on the dispute and on its credit note: who raised it, who it was assigned to, each comment, each file, and the outcome. The person assigned is told in the bell and by email, and so is whoever has to approve the credit note.
The customer can raise it themselves
In the customer portal, a customer can dispute an invoice, attach their evidence, follow its status and add comments. One open dispute per invoice; a second concern goes into the first as a comment. Staff comments on a dispute are internal notes by default. Only a comment sent with Reply to the customer appears in the portal, so the team can argue about the delivery note among themselves before anyone answers the school.
A reminder sent during a dispute tells the customer nobody read their complaint. A reminder held during a promise tells them somebody did.
The step-by-step guides are the Collections Workspace guide and the Invoice Disputes guide. How the reminder ladder itself is set up is on the payments and collections page; the portal is described on the customer portal page. Credit holds that stop a customer like this from running up more debt in the first place are in The Credit Hold a Salesperson Cannot Click Past.
Four questions about your collections
Which customers promised to pay this week, and how much?
A good answer sounds like
A list, per currency, from one screen.
What it tells you
If the answer is “ask the collectors”, promises are not managed.
How many promises made last month were kept?
A good answer sounds like
A count of kept and broken, measured from payments.
What it tells you
Without it you cannot tell a good collector from a hopeful one.
Did any customer get a reminder while disputing the invoice?
A good answer sounds like
No, because a dispute pauses reminders on that invoice.
What it tells you
If you do not know, assume yes.
Who can see what your team wrote about a customer’s complaint?
A good answer sounds like
Staff only, unless someone deliberately replied to the customer.
What it tells you
An internal note that reaches the customer is a second dispute.
What AWRA OpsHub does today
- A collections board in aging lanes, one currency at a time, with a collector per customer and a filter for your own.
- Promises to pay with amount, currency, date and note, recorded on the web or in the app, that hold the reminders off until their date.
- Promises settled automatically as kept or broken from the payments received, with a broken promise flagged on the board for 90 days.
- Follow-up tasks assigned to a person with a due date, a reminder history per customer, and statements as PDF or CSV.
- Invoice disputes with reasons, lines, evidence and comments, which pause reminders on that invoice only and close by credit note, rejection or withdrawal.
- Disputes from the customer portal, with staff comments internal unless sent as a reply to the customer.
More we can add to your workspace
- Promises recorded by the customer in the portal, choosing a date and amount themselves, for the team to accept.
- Instalment promises, several amounts on several dates under one agreement, each settled on its own date.
- A kept-promise rate per collector over a quarter, to show who is collecting and who is recording optimism.
- A response clock on disputes, flagging any that have waited longer than your target without a reply to the customer.
Where we point you to a specialist
- How and when you contact a customer about a debt is yours to decide within the law where you trade. The workspace records the promise, holds the reminders and tells you when it was missed.
- Whether a dispute is upheld is a judgement for your team. The workspace keeps the evidence and the timeline; it does not decide the claim.
Portal promises and instalment promises each extend records the collections workspace already keeps.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsVerdict
Most money owed is collected by a phone call and a date. Write the date where the reminders can read it, and the system stops chasing people who agreed to pay and starts noticing the ones who did not.
Payments and collections in AWRA
Reminder ladders, the collections board, promises to pay and invoice disputes, on the same customer record as your invoices.
Read the feature pageFrequently asked questions
Does recording a promise to pay stop payment reminders?
Yes. While a promise is open and its date has not passed, the automatic reminders skip that customer. The day after the promised date it is settled as kept or broken, and if it was broken the reminders resume.
How does AWRA OpsHub decide a promise was kept?
From the payments recorded for the customer in the promise’s currency, dated from the day the promise was recorded up to the promised date. If they reach the promised amount it is kept; otherwise it is broken, with the amount actually paid stored on it.
Does an invoice dispute pause reminders for the whole customer?
No, only for the disputed invoice. Reminders continue for the customer’s other invoices while the dispute is open or under review, and resume on the disputed one if the dispute is rejected or withdrawn.
Can customers raise a dispute themselves?
Yes, from the customer portal. They can describe the problem, attach evidence, follow the dispute and add comments. Staff comments stay internal unless a staff member sends one as a reply to the customer.
Does the collections board add up balances in different currencies?
No. The board shows one currency at a time. A customer who owes in two currencies appears on both boards, each with its own figure.
