Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Supplier invoices in by email. Draft bills out, for a person to confirm.
Your workspace gets its own bills address. An invoice sent or forwarded there — or uploaded on the web or from the app — is read, matched to a supplier and an open purchase order, checked against what was ordered and received, and laid out as a draft bill. Nothing is posted, approved or paid until a person says so.
- From [email protected]Sender verified by SPF/DKIMEmail
- Supplier · Kilimo Supplies LtdMatched on the tax PIN printed on the invoice0.96
- Purchase order PO-1182Number quoted on the invoice0.92
- Ordered · received · invoicedWithin your matching tolerance3-way
- Due date not found on the pageLeft empty for the reviewerCheck
Four steps, and the last one is always a person.
It arrives
By email to your bills address, up to ten attachments a message, or uploaded from Payables or the app. On Android you can share a PDF or photo straight into the inbox.
It is read
Supplier, tax PIN, invoice number, dates, currency, totals, tax, the order number and the lines — each with a confidence score. A field the reader could not see stays empty.
It is matched
The supplier from the PIN, the sender or the name; the order from the number quoted, the totals and the lines; then checked against ordered and received quantities with your own tolerances.
A person confirms
Correct anything, then create the draft bill — or reject it with a reason, or run the reading again. The draft takes the normal approval path.
Three ways to read, in order. The first that finds anything wins.
What comes out is a proposal shown beside the invoice itself. Every field carries how sure the reader was, so the reviewer knows where to look.
1 · AI, where you allow it
Only when your workspace allows third-party AI, the procurement AI switch is on and the month’s allowance has room. A PDF with text is sent as text; a scan or photo goes to a provider that reads images.
2 · The PDF’s own text
Read on our servers and matched with plain patterns — invoice number, dates, totals, PIN. Lower confidence by design, and no third party involved.
3 · The reviewer types it
A photo with AI switched off is shown as it is, and the reviewer fills the fields. Matching and duplicate checks still run on what they enter.
An address nobody can guess, and a draft nobody can skip.
Its own address
bills+ followed by 24 random characters. That token is the only thing that routes mail to your workspace. Regenerate it and the old address stops at once.
An optional sender list
Limit the inbox to named addresses or @domains. A listed sender counts only when SPF or DKIM vouches for the From domain, so typing an allowed address is not enough.
Duplicates caught twice
The same file already in the inbox, by its SHA-256; and, once supplier and invoice number are known, the same invoice already a bill or already waiting.
The same match rule as approval
Lines are checked against the order’s ordered, received and agreed figures with your workspace’s tolerances — the rule the bill’s approval applies later.
Never posts or pays
Confirming creates a draft supplier bill and nothing else. Approval rules, maker-checker and the purchase order ceiling decide what happens next.
On the web and in the app
The inbox, the file, the proposed match and Create draft bill are in the mobile app as well, under the same supplier-bill permissions.
What AWRA OpsHub does today
- A bills address per workspace, with a regenerate button that retires the old one at once, and an optional sender list checked against SPF or DKIM.
- Upload of PDF, PNG, JPEG and WebP invoices on the web, in the mobile app, and from the Android share sheet.
- Reading by AI where your workspace allows it, then by the PDF’s own text, with a confidence per field and empty fields left for the reviewer.
- Supplier matching by tax PIN, sender address, sender domain and name.
- Purchase order matching by quoted number, totals and lines, with a three-way check against what was received using your tolerances.
- Duplicate detection by file fingerprint and by supplier plus invoice number.
- Confirm, reject with a reason, or read again; confirming creates a draft supplier bill on the normal approval path.
More we can add to your workspace
- A connection to a shared accounts mailbox in Google Workspace or Microsoft 365, read directly instead of forwarded. Commission it
- Learning from corrections, so a supplier’s layout is read better after the first few invoices. Commission it
- Suggested ledger accounts and departments on each line of a bill with no purchase order. Commission it
- Supplier statements read from the same inbox and set against what you have on record. Commission it
- Automatic confirmation for a trusted supplier under a value you set, still landing as a draft for approval. Commission it
Where we point you to a specialist
- We will not post, approve or pay a bill from the inbox. A person confirms a draft, and your approval rules take it from there.
- We will not guess a figure the reader could not see. It stays empty until the reviewer fills it.
- We will not send an invoice to an AI provider when your workspace has switched third-party AI off. The PDF’s own text and the reviewer are used instead.
A direct mailbox connection and suggested ledger coding are the two items payables teams ask for first. Tell us how invoices reach you today and we will come back with a written spec, a timeline and a price.
Where a confirmed draft goes next.
Frequently asked questions
How do invoices get into the inbox?
Does AWRA post or pay the bill?
Is the invoice sent to an AI service?
How does it know which purchase order an invoice belongs to?
What stops the same invoice being entered twice?
Can anyone send mail to our bills address?
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.