A Qualification That Expires 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. It is a good control, correctly built, and it tells nobody — not the supplier, not the buyer, not the person who approved them.
The best control in our supplier module runs before anybody is at their desk, does exactly the right thing, and leaves no trace anybody will see. On the day it fires, a supplier your buyer has used for three years simply stops 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.
It then writes a line to the log.
A control that acts and does not speak produces a mystery instead of a decision.
What that costs on the morning it fires
| Who needed to know | What they get | What they do instead |
|---|---|---|
| The supplier | Nothing | Finds out when they stop being asked to quote, which may be months |
| The buyer | Nothing | Discovers a supplier missing from a list and assumes a system fault |
| Whoever approved them | Nothing | Cannot renew in advance because nothing signalled the approach |
| Finance | Nothing | An open order with a now-inactive vendor is nobody's exception |
| The log file | A line | Nobody reads a log file |
The second row is 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, and they raise a support question or work around it. The control fired, and its effect reads as a defect.
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 identical field, on the identical table, attached to a supplier, produces nothing. 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.
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.
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 is 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.
- 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.
- Expiry dates stored against supplier documents, and a working document-expiry reminder job that runs daily on a thirty-day window.
What it does not do
- Any notification when a qualification expires — not to the supplier, the buyer, the approver or an administrator.
- Any warning before a qualification expires. There is no thirty-day horizon on this clock.
- Document expiry reminders for supplier documents. The reminder job is filtered to employee records and employment contracts.
- Any handling of open orders against a vendor that has just been deactivated.
- A renewal path that a supplier can start themselves before the date passes.
Not ours, by choice
- 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 gap is a filter on a working job rather than an absent capability, which is worth knowing because it changes the size of the fix.
- Nothing here is Ivorian. It is what a silent control does; this is where the annual documentation cycle makes lapses arrive in a queue.
What is not built for the CFA franc zone today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in the CFA franc zone. Kenya's eTIMS integration and its maintained payroll engine exist 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 your own operation needs that the standard one does not have, or a link to a system you already run 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
Do not rely on the system to tell you about a qualification. Keep a calendar of qualified-until dates outside the product, review it monthly, and start renewals sixty days out. Tell your buyers explicitly that a supplier vanishing from a selection list means a lapse rather than a fault — that single sentence in an induction saves more time than any feature on this page would.
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 does the first and not the second. 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. Expiry notification is merely an explanation after the fact.
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 stores the date and the reminder does not read it. A stored date with no reader is a diary nobody opens.
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.
Build the renewal calendar before the first lapse
A list of suppliers and qualified-until dates, reviewed monthly, closes almost everything on this page for the cost of a recurring meeting. We will help you extract the dates and set the rhythm.
Set up the calendarFrequently 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 right change is a warning before it happens, not a weaker rule.
Can the workflow engine notify on expiry?
The workflow engine acts on events, and the expiry runs as a scheduled job that logs rather than emitting one. So there is no event for a rule to hang off, which is why this is a build rather than a configuration.
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.
