Payment before certificate: designing out bad debt
Many schemes still work the way they did on paper: the inspection happens, the certificate is issued and an invoice follows. It feels natural. It also means the scheme has handed over the thing of value before it has been paid, and every late payer becomes a job for the office.
There is a simpler model, and the right platform makes it easy.
Why billing after the event creates debt
Once a certificate is issued, the person who needed it has what they came for. Paying the invoice drops down their list. Multiply that across hundreds or thousands of certificates a year and the result is predictable: a long tail of small debts, hours of chasing and awkward conversations with the very members your scheme depends on.
The alternative: release on payment
In a payment-before-certificate model, the inspection and its result are recorded as normal, but the certificate is held until payment is made. The moment payment clears, the certificate is released automatically and appears on the public register.
Payment becomes part of getting the certificate, not an afterthought.
Keeping it fair and flexible
A good platform does not make this rigid. The details that matter:
Billing the right party. Decide who the scheme bills, whether that is the owner of the equipment, the business being certified or the inspection body, and let others settle on their behalf if they choose.
Group payments. Organisations with many items can pay for several certificates in one go.
Card payments online, so paying takes a minute, not a cheque and a phone call.
Accounting integration, so every payment flows into your accounts without re-keying.
Discretion to override. Your scheme can still release a certificate before payment when there is a good reason. The default protects you; the override keeps you human.
What changes for the scheme office
The biggest change is what disappears: credit control. Staff time goes back into supporting members instead of chasing them, and the scheme's income becomes more predictable month to month.
How 16i builds it
Payment rules are part of the scheme platforms we build, alongside registrations, inspections, certificates and the public register. We connect card payments and accounting systems, such as Stripe and Xero, so the whole flow from inspection to payment to released certificate happens in one place. see platforms for certification and inspection schemes
Share article: