AWRA OpsHub Search

The Invoice That Arrived by Email

Supplier invoices arrive as PDFs in somebody’s mailbox and wait there until somebody re-types them. A Bills inbox address of your own reads each one, finds the supplier and the order, checks it against what was received, and hands a person a draft to confirm.

Procurement Insights Washingtone Aura 7 min read

The short version

Every workspace can switch on a Bills inbox with its own address. Suppliers email invoices to it, staff upload them, or the Android app shares them in. Each file is read for supplier, invoice number, dates, totals, tax and lines, matched to the supplier and an open purchase order, and checked against what was ordered and received using your own tolerances. Nothing posts: a person confirms, and the result is a draft supplier bill that then takes your ordinary approval path.

At a hotel supplies wholesaler in Kisumu, the accounts assistant starts each morning in a shared mailbox. Forty-odd supplier invoices a week arrive as PDFs, a few as phone photos of a carbon copy. Each one is opened, its PO number looked up in another tab, the delivery note found in a third, and the bill typed in by hand. The invoice that arrives twice, once from the supplier’s sales rep and once from their accounts office, is typed twice about once a month.

An address that belongs to the workspace

Switch the inbox on under Payables and it shows an address of the form bills+token@ followed by our inbound domain. The token is twenty-four random characters, and it is the only thing that routes a message to your workspace, so it cannot be guessed. If an address leaks, regenerate it and the old one stops working at once.

The inbound endpoint is public, because a mail provider has to reach it, and that makes its authentication the whole security story. Every delivery is signed by the provider; the signature is checked, must be less than fifteen minutes old and can be used once, and with no signing key configured nothing is accepted at all. Behind that, an optional sender allow-list of addresses or whole domains. A list that names a domain is only satisfied when that domain’s SPF or DKIM vouches for the message, because anyone can type an allowed address into a From line.

Way in Who uses it What arrives
The inbox address Suppliers, or your own staff forwarding Up to ten PDF or image attachments per email
Upload on the inbox page Accounts staff One or several files, with a note
Share to AWRA on Android Anyone with a PDF or photo on the phone Files sent to the inbox through the API
The API Your own integrations The same upload, under the bill permissions

Files are accepted by what their bytes are, not by what the name claims: PDF, PNG, JPEG and WebP, up to a size limit of ten megabytes by default. Each is stored privately and queued for reading, and the people who capture bills get a bell notice, and an email if the workspace keeps that channel on.

Reading the invoice, in three tiers

  1. AI, where your workspace allows it

    Only when third-party AI is permitted, the procurement AI module is on and the month’s allowance has room. A PDF with a text layer is sent as text; a scan or photo goes as the file.

  2. The PDF’s own text, read locally

    The text layer is extracted on our server and matched with plain patterns. Lower confidence by construction, but nothing leaves the platform.

  3. A person types it

    A phone photo with AI switched off has no text to read. The reviewer fills in the fields beside the image.

Every field comes back with a confidence between zero and one, and a field the reader could not see is left empty, never guessed. That is the rule the rest of the screen depends on: an empty due date is something the reviewer notices, and an invented one is something they do not.

Finding the supplier and the order

The supplier is proposed from the strongest evidence first: the KRA PIN printed on the invoice, then the sender’s address (given full weight only when SPF or DKIM vouched for it), then the sender’s domain, then the printed name. The order is chosen from that supplier’s open purchase orders by the order number quoted on the invoice or anywhere in its text, by the total against what was ordered and what was received, and by line descriptions.

Once an order is chosen, each proposed line is checked against its ordered, received and agreed figures with the same three-way matching rule and the same tolerances the bill’s approval will apply later. So “matched” on the inbox means the bill would match at approval, not a looser test that passes here and fails there. Those tolerances ship at zero, and what that strictness does to a supplier’s goodwill extra unit is in every tolerance ships at zero. When a delivery was short, the inbox says so before anyone types a number; what happens next is the subject of whose problem is the short delivery.

The supplier is clear, the number, date and total were read with confidence, and the order matches cleanly

Matched

The draft is ready to confirm. A person still presses the button.

Anything is uncertain: a weak supplier match, an unread total, an order that differs from the receipt

Needs review

The invoice opens beside the proposed fields and lines, with the issues listed.

The same file is already in the inbox, or the same supplier invoice number is already a bill or waiting

Duplicate

It is held apart with the reason, and nothing is drafted.

Caught twice

Duplicates are checked on the bytes, so the PDF the sales rep and the accounts office both sent is recognised as one file, and again on supplier and invoice number once those are read, so a re-scanned copy of the same invoice is recognised too.

What the inbox never does

It does not post, approve or pay. Confirming creates a draft supplier bill through the same service that creates one by hand, and the draft then meets your approval rules, the maker-checker split and the order ceiling exactly as a typed bill would. Rejecting asks for a reason and keeps the file. The inbox is a faster way to arrive at the draft, and the controls after the draft are the ones you already set.

24
random characters in each inbox address token
10
attachments read per email
0
bills posted without a person confirming

At the Kisumu wholesaler the assistant now starts on the inbox page instead of the mailbox: a list of invoices already read, the matched ones at the top, the ones needing review flagged with why. More on the screen on the Bills inbox page.

The straight answer

What AWRA OpsHub does today

  • An inbox address per workspace, regenerable, with an optional sender allow-list checked against SPF and DKIM.
  • Signed delivery from the inbound mail provider, refused when the signature is missing, stale or reused.
  • Upload on the web, Share to AWRA on Android, and the API into the same inbox.
  • Reading in three tiers: AI where allowed, the PDF text layer locally, or a person typing.
  • Supplier and purchase-order matching with the three-way rule and your own tolerances.
  • Duplicate detection on the file bytes and on supplier plus invoice number.
  • Draft bills only, confirmed by a person and then approved as usual.

More we can add to your workspace

  • A second inbound mail provider, alongside the one used today. Commission it
  • Automatic drafting of cleanly matched invoices, so the reviewer starts from a list of drafts rather than a list of proposals. Commission it
  • Supplier statements read the same way, matched line by line against your open bills. Commission it
  • Invoice intake from WhatsApp, for suppliers who send a photo rather than an email. Commission it
  • A separate inbox address per branch, each routed to its own reviewers. Commission it

Where we point you to a specialist

  • Whether a supplier invoice meets KRA’s requirements for an input VAT claim is a question for your tax adviser. The inbox reads what is printed; it does not rule on its validity.

Automatic drafting of matched invoices is the extension most accounts teams ask for once the inbox is trusted.

More we can add to your workspace

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 needs

Three questions for whoever captures your supplier bills

How do you know an invoice has not already been entered?

What you will probably hear

I search for the number.

How to read it

That catches the careful days. A duplicate check should run on every file, every time.

When you type a bill, how do you check the delivery?

What you will probably hear

I find the goods received note.

How to read it

The match should be done before the typing, with the same tolerance approval uses.

Who decides a bill is real before it is in the books?

What you will probably hear

Whoever types it.

How to read it

A reading tool should propose; a person should confirm; approval should still follow.

See the Bills inbox

An email address for supplier invoices, read, matched to the order and the receipt, and turned into a draft when you confirm.

Explore the Bills inbox

Frequently asked questions

Does the Bills inbox post or pay supplier invoices?

No. Confirming an inbox item creates a draft supplier bill, which then goes through your usual approval rules. The inbox never posts, approves or pays.

What file types can a supplier send?

PDF, PNG, JPEG and WebP, checked from the file itself rather than its name, up to ten attachments per email and ten megabytes per file by default.

What if AI is switched off for our workspace?

A PDF with a text layer is still read on our own server with plain patterns. A photo with no text layer is shown to the reviewer to type in.

Can we stop strangers emailing invoices to the address?

Yes. Add the addresses or domains you accept to the sender allow-list. A domain on the list must be vouched for by SPF or DKIM, so a typed From line is not enough.

How are duplicate invoices caught?

Twice: identical files are recognised by their bytes, and once the supplier and invoice number are read, the same invoice already captured or waiting is recognised too.

Share this article

LinkedIn X WhatsApp

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center