Supplier Invoice Email Workflow: From Inbox to Reviewed Bill

First, separate Bills from sales invoices

The word "invoice" describes the document, not its direction. An invoice you send to a customer is income and accounts receivable. An invoice a supplier sends to you is a cost and accounts payable. In Experi, the second type belongs in Bills.

Keeping that distinction visible helps users understand whether a total should increase revenue or cost. It also avoids treating a supplier reference as one of your own invoice numbers. For a wider explanation, see invoice vs receipt vs purchase order.

Why a shared inbox is not enough

A dedicated folder can stop supplier emails getting lost, but it does not create structured records. Someone still has to download the file, open it, read the supplier and reference, type dates and amounts, decide the category, and remember whether it has been paid.

The better pattern is a controlled intake route. Email and attachment processing should suggest the repetitive fields, while the review screen asks the questions that require business context.

The seven-step supplier invoice workflow

1. Receive through one controlled route. Forward supplier emails to a workspace-specific address rather than a public or guessed mailbox.
2. Validate the attachment. Check the real file signature, size and supported format before parsing it.
3. Extract suggestions. Read the supplier, invoice reference, issue date, due date, currency, subtotal, tax and total where the document provides them.
4. Match the supplier. Reuse an existing supplier where possible instead of creating spelling variations for the same company.
5. Review business context. Select the project, cost category, tax treatment, VAT handling, description and payment status.
6. Check for duplicates. Compare supplier, reference, amount and dates with existing Bills and other drafts.
7. Confirm deliberately. Only an authorised workspace user should turn the draft into a reporting record.

Fields every reviewer should check

Inferred values should look inferred. A suggested date or category is a prompt to review, not a fact that should be silently accepted.

Monthly Bills need speed without blind duplication

Software subscriptions, hosting, utilities and professional services often arrive every month from the same supplier. Reusing supplier, category, currency and business defaults saves time, and bulk entry can help when several periods need to be added together.

The invoice reference, issue date, total and payment date still need to be unique to the actual document. A recurring pattern should prefill context; it should not manufacture records or assume every amount stayed the same.

Attachment safety and retention are separate decisions

File extensions are easy to rename, so validate the underlying PDF or image signature before parsing. Processing should run with strict size, time and memory limits. If parsing fails, show a warning and do not let a half-read attachment quietly create a financial record.

Experi's Email-to-Bill mode processes supported attachments, keeps extracted information and a private sanitised preview where available, then discards the original attachment. Your original supplier email remains in your mailbox. HMRC guidance says businesses should keep accurate records and supporting proof, so decide with your accountant which source documents or copies your business must retain outside Experi.

What good duplicate protection looks like

Exact supplier references are the strongest signal, but suppliers can omit references or reuse patterns. A useful review combines reference, supplier identity, issue date, currency and total. It should warn the user and show the likely match rather than automatically deleting one of two legitimate Bills.

The same principle applies when the cost appears elsewhere. A purchase invoice and a linked expense should not become two costs in your P&L. Reconciliation connects representations of one event; it does not create another event.

How Email-to-Bill works in Experi

Each eligible Pro workspace has a unique, rotatable intake address. Supported PDF, JPEG, PNG and WebP attachments are validated and parsed, then the suggested information appears in Draft Bills. An authorised user checks the core fields and confirms the result into the same Bill workflow used for manual entry.

Once confirmed, the Bill remains the source of truth for costs and can appear in Financials. The email route removes repetitive typing; it does not remove review, classification or ownership.