Is This Invoice Really Ours?
A forged invoice looks exactly like a real one, because it was made from a real one. A second QR on every invoice, receipt and credit note opens a page that states what the issuer actually issued — number, date, total and whether it still stands — and nothing about the customer.
The accounts payable clerk at a Nairobi hospital has an invoice from a medical supplies company for KES 1,284,000. It has the supplier’s logo, their KRA PIN, an eTIMS QR that scans, and a bank account she has not paid before. The supplier’s real invoice for the same order was KES 1,128,400, payable to their usual account. Somebody in between had a PDF editor and an afternoon.
Why the tax QR does not answer this
The eTIMS QR on a Kenyan invoice confirms that an invoice with that number was filed with KRA. It is the right check for a tax question, and we wrote about it in eTIMS integration for Kenyan invoices. It is not designed to answer the clerk’s question: is this copy, with this total, the document the supplier issued? A forger who keeps the number and changes the total keeps a QR that still scans.
A second QR, for the reader
Every issued AWRA invoice now carries a Verify this document QR, printed beside the eTIMS one, never instead of it. Credit notes carry it on their printable copy, and payment receipts carry it in the receipt email. A draft, an invoice waiting for approval or a rejected one carries none: only a document that was actually issued can be verified.
Scanning it opens a page at /verify/ followed by a twenty-character code. The page states who issued the document, its type, number, issue date, currency and total, its current status, and a short fingerprint. If the paper in the clerk’s hand says KES 1,284,000 and the page says KES 1,128,400, the paper has been altered. A changed total is one forgery; a genuine-looking letter asking to change the supplier’s bank account is the other common one, covered in the email that changed the bank account.
| The page says | Which means |
|---|---|
| Valid | The document was issued with exactly these values. A copy that differs has been altered. |
| Valid, part credited | Issued with these values, and part of it has since been credited. |
| Credited | Issued, and since fully credited. Nothing is owed on it. |
| Superseded | This copy was issued, but the issuer has since changed it. Ask for the current version. |
| Voided | The issuer cancelled or withdrew it. It is no longer valid. |
The verification page tells the reader what was issued. It does not tell them who it was issued to.
What the page leaves out, on purpose
No customer name, no line items, no address, no phone number. The person verifying already holds the paper, so they need the values to compare, not a copy of the document. A verification link that showed the customer and the lines would turn every forwarded invoice into a way to read someone’s purchases, and the page is built so it cannot.
How a code maps to a piece of paper
A code belongs to one issued version of a document. The values a reader can check — issuer, type, number, issue date, currency and total — are fingerprinted together. Print the same invoice twice and both copies carry the same code. Correct an issued total and print again, and the new copy gets a new code, while the old code now reads superseded and still shows the values that were on the old paper. So a genuine old copy is told apart from the current one, and a forged total never matches anything.
Codes are random, twenty letters and digits, and stored rather than computed, so there is nothing to work out from an invoice number. An unknown code returns a plain not-found. The page is rate-limited per visitor and marked so search engines do not index it: a verification is a check, not content.
Checking without a camera
The public /verify page accepts a pasted link or the code typed from the paper. In the AWRA app, Tools has a verify scanner that reads the QR and opens the result.
What AWRA OpsHub does today
- A Verify this document QR on issued invoices, credit notes and payment receipts, beside the eTIMS QR.
- A public page showing issuer, type, number, issue date, currency, total, status and fingerprint.
- Five statuses: valid, part credited, credited, superseded and voided.
- One code per issued version, so a corrected document gets a new code and the old one reads superseded.
- No customer name, lines or address on the public page.
- Random stored codes, rate-limited lookups, and a scanner in the app.
More we can add to your workspace
- The same QR on purchase orders and delivery notes, so suppliers and gatekeepers can check your documents too. Commission it
- Verification on POS receipts. Commission it
- Verification on payslips, for banks and landlords checking an employee’s income. Commission it
- A log of verifications the issuer can read, showing when and how often each document was checked. Commission it
Where we point you to a specialist
- The page confirms what the issuer issued. Whether an invoice is a valid tax invoice is KRA’s question, answered by the eTIMS QR beside it.
The QR on purchase orders is the extension buyers ask for, because suppliers receive forged orders too.
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 needsWhere this leaves you
Your customers can check any invoice, credit note or receipt you issue against what you actually issued, in one scan, without learning anything about anyone else. A forged total does not match, a corrected document is told apart from the old one, and a cancelled one says so.
Three questions for your accounts payable desk
How do you check an invoice is the one the supplier sent?
What you will probably hear
It has their logo and PIN.
How to read it
So does every forgery made from a genuine invoice.
What do you do when the bank account on an invoice is new?
What you will probably hear
We pay it if the invoice looks right.
How to read it
Check the document against its issuer, and the account change against a known contact.
Can a customer check one of our invoices?
What you will probably hear
They would have to call us.
How to read it
A check that needs a phone call is a check that does not happen at 5 pm.
See document verification
A QR on every invoice, receipt and credit note that confirms what you issued, and nothing about the customer.
Explore document verificationFrequently asked questions
Is the AWRA verification QR the same as the eTIMS QR?
No. The eTIMS QR is KRA’s. The AWRA QR is printed beside it and confirms the document’s values against what the issuer issued.
What does the verification page show?
The issuer’s name, the document type, number, issue date, currency, total, current status and a short fingerprint.
Does the page show the customer’s name?
No. It shows no customer name, no line items and no address.
What happens if the issuer corrects an invoice after printing it?
The corrected copy gets a new code. The old code then reads superseded and still shows the values that were on the old copy.
Which documents carry the QR?
Issued customer invoices, credit notes and payment receipts. Drafts and documents awaiting approval do not.