TechOneDigital Start a pilot

Finance & Documents

AI Finance Mailbox

A shared finance inbox that turns attachments into payment-ready data automatically.

Available now · Human approval · Complete audit trail

The operational problem

The attachment is only useful if its email history survives

A finance mailbox carries more than PDFs. Sender, arrival time, subject, thread and attachments explain where a document came from and whether it was already handled.

The service keeps that lineage while it separates documents, extracts agreed fields and routes exceptions. Payment-ready means the record passed the defined checks; it does not mean a payment was authorised.

Mailbox workflow

What has to stay connected from email to record

Mailbox event

New messages are received through an agreed notification or supported connection, not ad-hoc forwarding.

Message lineage

Sender, subject, arrival time and attachment remain linked to the resulting document record.

Document handling

Attachments are separated, classified and checked for the document types included in the pilot.

Payment fields

Supplier, amount, currency, due date, bank details and other agreed values follow a defined schema.

Exception queue

Missing, conflicting or low-confidence values wait for a person with the source visible.

Method

How an attachment becomes payment-ready data

  1. Receive onceThe message and attachments receive stable identifiers so retries do not create duplicate work.
  2. Separate and classifyBundles are split and document types resolved before field extraction begins.
  3. Extract the finance schemaThe agreed payment fields are read with field-level confidence and evidence.
  4. Apply finance checksRequired values, formats and available supplier or reference data are checked.
  5. Route exceptionsOnly uncertain or failed fields wait for review; ready records remain separate.
  6. Export with lineageApproved records move to the agreed export or delivery step while retaining their source email and attachment.

Example queue

Ready items and exceptions are separated

Illustrative daily mailbox queue — no customer documents

Mailbox
invoices@ (shared)
New today
9 attachments
Ready to pay
7
Needs a look
2 (missing bank details)
Export
CSV, API

Finance controls

The rules behind a dependable mailbox

One message does not equal one document

Attachments and bundled PDFs are resolved before downstream records are created.

Retries must be idempotent

A repeated notification may re-check work, but it must not create a second payable record.

Missing data is not guessed

A bank account or due date without sufficient evidence remains an exception.

Payment-ready is not payment approval

The mailbox prepares validated data; authorising a payment remains in the accounting or banking control process.

Fixed start

What the 14-day mailbox pilot delivers

  • Connected pilot mailboxOne agreed shared mailbox and supported notification path configured for the pilot.
  • Document and field schemaIncluded document types, payment fields, validation rules and review thresholds.
  • Working daily queueReady records and exceptions separated with source messages and attachments traceable.
  • Duplicate and exception reportThe pilot records retries, unsupported documents and missing or conflicting values.
  • Export recommendationA defined next step for CSV, API or accounting-system delivery.

Fit

When mailbox automation is—and is not—ready

A good fit

  • A shared finance inbox receives recurring documents and people retype the same fields.
  • The required payment-ready schema and review owner are known.
  • Source-email traceability matters for audit and exception handling.

Not the right fit

  • The mailbox contains mostly unstructured conversations with no repeatable document process.
  • Nobody can define what makes a record ready or who reviews exceptions.
  • The expectation is to authorise or execute payments directly from an email.

Where the human approves

You look at what is flagged. The AI works through a fixed list of allowed operations; every approval and result is logged.

Finance questions

Questions an accounts-payable owner should ask

Does the AI poll the mailbox constantly?

The preferred design uses a supported notification when a message arrives. The exact connection depends on the mailbox platform and permissions.

What if one email contains several attachments?

Each attachment and any bundled documents are separated into traceable records while keeping the original message relationship.

How are duplicate emails or retries handled?

Stable message, attachment and document identifiers make the workflow idempotent so reprocessing does not silently create a second payable record.

Does payment-ready mean automatically paid?

No. It means the agreed fields and checks are complete for the next accounting step. Payment authorisation remains in the customer’s control process.

Can it send data to our accounting system?

Yes, through a separately scoped delivery step using an agreed channel and confirmation behaviour. The mailbox pilot can begin with an export.

Experience behind the service

Built on the SmartDocto document pipeline

The service uses SmartDocto’s document intake, extraction, review and delivery patterns. The platform supports mailbox intake as one of four channels while preserving document history and human approval.

Technical stewardship: David Máj, Founder & Technology Consultant. Last reviewed 24 September 2026.