A Qualification That Expired in Silence
At six every morning a job finds suppliers whose qualification has lapsed, marks them expired, and switches them off so they cannot be invited to quote. Until 1 October 2026 it told nobody. It now warns your buyers thirty days ahead and tells them on the day — and the supplier is the one party it still does not reach.
The best control in our supplier module runs before anybody is at their desk and does exactly the right thing. For a long time it also left no trace anybody would see: on the day it fired, a supplier your buyer had used for three years simply stopped appearing in the list.
What the job does
Prequalification here is a real workflow. A supplier applies, their documents are reviewed, they are approved, and the approval carries a date until which they are qualified. When that date passes, a daily job marks the application expired and deactivates the linked vendor.
Deactivation is the part that matters. An inactive vendor drops out of selection, so nobody can invite a lapsed supplier to quote by accident. The control does not depend on anybody remembering, which is the property that makes a control worth having.
Until 1 October 2026 it then wrote a line to the log, and that was all.
A control that acts and does not speak produces a mystery instead of a decision.
What it now says, and to whom
The same job now speaks twice. Thirty days before a qualification lapses it sends a warning — once per expiry date, so nobody is nagged daily — naming the supplier, the date and what will happen on it. On the day it lapses it sends a second notice naming the vendor it has just deactivated, and saying that requalifying them restores it.
Both go to the person who approved the supplier and to everyone in your organization who can add vendors, which is the permission that can requalify them. They arrive in the notification bell, and where your workspace has Slack or another channel connected, the same notice is forwarded there.
What the morning it fires looks like now
| Who needed to know | What they got before | What they get now |
|---|---|---|
| Whoever approved them | Nothing | A warning thirty days ahead, and a notice on the day |
| The buyers who manage vendors | Nothing | The same two notices, so a missing supplier is a known lapse rather than a suspected fault |
| The supplier | Nothing | Still nothing from us — your team has thirty days to ask them for renewed documents |
| Finance | Nothing | Still nothing specific: an open order with a now-inactive vendor carries on as before |
| The log file | A line | A line, which is now the least important of the four |
The second row was the practical one. A buyer who cannot find a supplier in a dropdown does not conclude that a qualification lapsed; they conclude something is broken. With a notice in their bell from a month earlier and another from that morning, they know exactly why.
The second silence, one layer down
There is a document expiry reminder in the product, and it is a complete piece of work: it reads expiry dates on stored documents, looks thirty days ahead, respects notification preferences, and runs daily.
It is filtered to employee records and employment contracts.
So the qualification as a whole now gets a warning, but the individual documents inside it do not. An employee's work permit gets a thirty-day warning. A subcontractor's insurance certificate, a tax clearance, a trading licence — same field, same job, no warning of their own. The one date that is watched is the qualification date, which is why it is worth setting that date to the earliest certificate that matters.
This is not a missing feature. It is a filter, and the distinction is worth making because it changes how you should read it: the machinery for the thing you want is running every day, on the same data, and has been told to look only at people.
Why an Ivorian buyer runs into this sooner
Because supplier documentation here has genuine annual rhythm to it — tax and trading documents that renew on a cycle, and buyers, particularly institutional and donor-funded ones, who require them current at the moment of award rather than at the moment of registration.
That combination means qualification lapses are not rare events. They are an annual queue, arriving in clusters, and every one of them is a supplier who could have renewed if anybody had said anything. The thirty-day warning is what turns that queue into a list of calls to make.
And the cost is asymmetric. A supplier deactivated in error is an inconvenience. A supplier who should have been deactivated and was not is an award you may have to unwind. The system is on the right side of that trade — it fails towards refusing — which is why the fix was a notification rather than a change of behaviour.
What AWRA OpsHub does today
- Prequalification as a genuine workflow — public application, document upload, review, approval, and conversion to a vendor.
- A qualified-until date on an approved application, and a daily job at six that expires lapsed applications and deactivates the linked vendor.
- A warning thirty days before a qualification lapses, sent once per expiry date, and a notice on the day it lapses naming the vendor that was deactivated.
- Both notices to the approver and to everyone who can add vendors, in the app and on any connected channel such as Slack.
- An inactive vendor dropping out of quotation selection automatically, so a lapsed supplier cannot be invited by accident.
- Blacklisting with a stored reason, date and actor, separately from qualification.
- A working document-expiry reminder job that runs daily on a thirty-day window, today wired to employee records and employment contracts.
More we can add to your workspace
- A notice to the supplier themselves, so they hear about an approaching lapse from you without anybody writing to them by hand.
- An expiry date on each supplier document, with the same thirty-day reminder the employee documents already get. Today a supplier document holds its type and a verified flag, and the one date is the qualification as a whole.
- Handling for open orders against a newly deactivated vendor. A prompt to reassign them, hold them or let them run, rather than leaving them to be discovered.
- A renewal path that a supplier can start themselves before the date passes.
Where we point you to a specialist
- The control itself is correct and we would not change its behaviour. Failing towards refusing is the right direction for a qualification check.
- The document reminder is a filter on a job that already runs rather than a capability to build from scratch, which is worth knowing because it changes the size of the work.
- This is market-neutral. It is what a silent control does; this is where the annual documentation cycle makes lapses arrive in a queue.
What we can build for the CFA franc zone on top of the standard product
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point for the CFA franc zone, not a limit on what AWRA OpsHub can do there. Kenya's eTIMS integration and its maintained payroll engine are in the product because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If a national e-invoicing pipeline, a French interface, a bank or mobile money feed, a statutory return format, a rule specific to how your operation runs, or a link to a system you already have is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
National tax pipelines and a clean handoff to your ledger
Electronic invoicing against your administration's published interface, and a defined monthly export mapped to your expert-comptable's chart of accounts — with retries, a failure queue and a reconciliation report rather than a black box. The statutory ledger itself stays with them, by design; what we build is the pipe to it.
Mobile money, banks and French interface
Wave, Orange Money and bank statement feeds into the Payments Register, plus French interface text and document templates.
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.
Payroll and statutory returns
National income tax and social security schedules produced in the layout your filing body expects, generated from live payroll records rather than rebuilt each month.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
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. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedOur position
Let the system tell your team about a qualification, and make sure the right people can hear it: anyone who manages vendors should hold the permission to add them, because that is who the warning goes to. Use the thirty days to ask the supplier for renewed documents, since the product does not write to them for you. And set each qualification date to the earliest certificate that counts, because the qualification date is the one the warning watches.
Four questions about supplier compliance clocks
What happens the day a qualification expires?
A good answer sounds like
A deactivation and a notification, named.
What it actually means
Ours now does both. Ask about both halves; vendors answer the half they have.
Who gets warned thirty days before?
A good answer sounds like
A named recipient.
What it actually means
Advance warning is the only part that prevents anything. Ours goes to the approver and to everyone who can add vendors.
Show me a supplier document expiring next month.
A good answer sounds like
A list, and the reminder that will fire.
What it actually means
Ours holds one date per supplier, the qualification, and warns on that. A date per document is the next build; until then a mandatory custom date field per certificate makes them listable, though nothing watches it.
What happens to an open order when the supplier is deactivated?
A good answer sounds like
A stated behaviour, either way.
What it actually means
Ours does nothing to it, which is probably correct — the goods are still coming — but it should be a decision rather than an accident.
Check who will hear the first warning
The warning goes to whoever approved the supplier and to everyone who can add vendors. We will help you check those are the right people, and set qualification dates that match the certificates you actually care about.
Review your supplier clocksFrequently asked questions
Can I stop the automatic deactivation?
It is the intended behaviour and we would argue against turning it off: a lapsed supplier who stays selectable is the failure this control exists to prevent. The thirty-day warning is what makes it workable, because a renewal can be collected before the date arrives.
Who receives the expiry warning?
The person who approved the supplier and everyone in your organization who holds the permission to add vendors. It arrives in the notification bell thirty days before the qualification date, and again on the day it lapses. Where Slack or another channel is connected, the same notice is forwarded there.
Is the supplier told?
Not by the system. The notices go to your own team, who then have thirty days to ask the supplier for renewed documents. A notice addressed to the supplier is something we can add.
Does an expired qualification affect an order already placed?
No. The vendor becomes inactive and therefore unselectable for new quotations, and existing orders continue — receipts, matching and payment all behave normally. Whether that is right depends on why the qualification lapsed, which is a judgement the system cannot make for you.
