An invoice is filed. That does not mean it is paid.

Give each state its own meaning

An invoice can be sitting in an inbox, saved in a folder, recorded in a workspace and still be unpaid. Those are separate facts.

A useful admin workflow keeps them separate. Filing answers “where is the document?” Recording the bill answers “what does this invoice say?” Payment status answers a different question: “what has been confirmed about payment?”

Collapsing those steps into a single “processed” label can make the screen look tidy while leaving the actual position unclear.

Start with the right company

Before choosing a folder, identify which business or job the invoice belongs to. The sender’s email address alone may not settle it, especially when a supplier works with several companies in the same group.

Define the information the workflow should use. That might include the named customer on the document, a job reference or an agreed supplier mapping. If the records disagree, the exception should be visible for review.

One simple folder pattern is company, year, month and document type. The important part is consistency and the ability to retrieve the original, rather than a particular naming convention.

Capture the fields you need to check

Agree which fields should be extracted and reviewed for your process. A basic supplier-bill record could include:

• The supplier and invoice number.
• The company or job it belongs to.
• The amount and currency.
• The due date, where provided.
• A reference to the source document.
• A clearly defined payment status.

Unreadable fields should not be filled with guesses. Missing dates, unclear totals and suspected duplicates need a route back to a person.

If the same attachment arrives twice, the workflow should identify the repeat rather than quietly adding a second bill. The exact duplicate-checking rules need to fit the source data.

Keep payment confirmation separate

Saving a PDF does not confirm that money has moved. Neither does extracting an amount or approving the invoice for the next step.

Choose which record supplies the confirmed payment status and how updates reach the workspace. If this is a manual process initially, label it accordingly. If the status comes from an accounting connection, confirm what that connection actually provides before relying on it.

The same applies to totals. Show currencies separately unless there is an explicit conversion method. A list containing pounds and euros should not be summed and labelled entirely as pounds.

Make exceptions easy to spot

The smooth path matters, but the exceptions deserve a place on the screen too. A document might belong to an unknown company, have an unreadable amount or lack the information needed for the next step.

An exception is not a completed invoice workflow. Show what needs checking and keep the original document connected to the record so the reviewer can resolve it.

This is one possible workflow to scope with AskMace. Mailbox capture, extraction, storage and accounting updates must be configured and tested for the pilot; a connected account alone does not complete that chain.