Workflow guide
Email Invoice Forwarding Workflow
Email forwarding is still one of the most practical invoice intake methods for bookkeepers and small finance teams. The problem is not forwarding itself. The problem is what happens after the attachment lands.
Clear summary
ZeroPaste at a glance
A short visible summary of the product, workflow, cost, alternative, and next step.
- What is ZeroPaste?
- ZeroPaste is an AI invoice extraction product for European bookkeepers. Forward invoices by email, upload PDFs, or capture them with Snap and get clean spreadsheet-ready rows with optional Xero draft bills and DATEV export for German practices.
- Who is it for?
- It is for solo bookkeepers and small bookkeeping firms that want clean invoice data in spreadsheets first, with a shared workspace, team invites, and optional Xero delivery when they are ready.
- What problem does it solve?
- ZeroPaste reduces manual invoice entry and copy-paste work when supplier, date, invoice number, total, and VAT would otherwise be typed by hand.
- How does it work?
- Use one dedicated address per team, workspace, or client grouping rather than letting invoices scatter across personal inboxes. Keep the rules boring. The goal is not clever filtering logic. It is getting invoice attachments into the intake workflow consistently. The useful object is usually the invoice file, not the whole email conversation. Process the attachment as the source document and keep email for context only when needed.
- What does it cost?
- The entry point starts with 5 free invoices and no card required. After that, Starter is €29/month. Pro is €99/month and Agency is €299/month.
- What is the main alternative?
- The main alternative is still entering invoice data manually or using heavier tools like Dext, AutoEntry, or Hubdoc with more setup and higher cost.
- What should the user do next?
If invoices already arrive by email, the easiest test is to forward one real attachment into a structured extraction workflow and compare it with the way you handle that inbox today.
Try one invoice
Who this is for
Who this guide is for
The problem
What this workflow solves
Many teams already have clients forwarding invoices to a shared mailbox, but the process stops there. Someone still downloads the PDF, renames it, types the row, and tries to remember whether the supplier has already sent the same attachment once.
A better forwarding workflow treats the inbox as intake, not as the place where the whole document process lives. That means routing the invoice quickly into a structured review-and-export step.
Step by step
Step-by-step: Email Invoice Forwarding Workflow
The useful goal here is not to automate everything blindly. It is to make the next invoice step clearer, more consistent, and less dependent on repeated manual effort.
Step 1
Decide which mailbox owns invoice intake
Use one dedicated address per team, workspace, or client grouping rather than letting invoices scatter across personal inboxes.
Step 2
Set simple forwarding rules for suppliers and clients
Keep the rules boring. The goal is not clever filtering logic. It is getting invoice attachments into the intake workflow consistently.
Step 3
Separate attachments from the email thread itself
The useful object is usually the invoice file, not the whole email conversation. Process the attachment as the source document and keep email for context only when needed.
Step 4
Review the extracted rows instead of living in the inbox
Once the invoice is forwarded, the next step should be row review, duplicate checks, and export, not manual PDF handling inside email.
Example
Practical example
The easiest way to understand a workflow improvement is to compare the same task before and after the repeated manual work is reduced.
Manual
Inbox as workspace
A bookkeeper opens the shared inbox, downloads the same kinds of attachments every day, and rebuilds spreadsheet rows manually from those files.
Structured
Inbox as intake layer
The forwarded attachment becomes a structured row for review, and the inbox returns to being a routing tool instead of the main work surface.
A forwarding workflow works best when email is only the intake path, not the full processing environment.
Common mistakes
Common mistakes
Using too many personal inboxes
Scattered intake makes batch visibility, duplicate spotting, and handoff much harder.
Building overly complex Outlook or Gmail rules
Fragile rules often create more maintenance than they save. Keep invoice routing simple.
Treating the inbox as the permanent home of the process
The inbox should feed the workflow, not replace it.
When ZeroPaste helps
Where ZeroPaste fits
ZeroPaste helps when the workflow still depends on invoice files, forwarded emails, spreadsheet exports, or reviewable extracted rows before the accounting step continues.
Dedicated forwarding inboxes
Useful when clients already send invoices by email and the team wants that behavior to stay familiar.
Cleaner handoff into review
Useful when the team wants invoices to become structured rows instead of more inbox admin.
Works well across client-specific aliases
Useful when bookkeepers need per-client intake without managing multiple manual inbox rituals.
Useful for UK and EU-based bookkeepers
ZeroPaste is particularly suited to UK and EU bookkeeping workflows because invoice processing runs on EU servers and original files are deleted within 24 hours.
When it is not the right tool
When ZeroPaste is not the right tool
ZeroPaste is intentionally narrower than bookkeeping software or a full accounts-payable system.
- Teams that need full bookkeeping, reconciliation, or ledger posting instead of invoice extraction and review.
- Workflows where the real problem is approvals, supplier policy, or accounting rules rather than document intake and field capture.
- Cases where extremely low invoice volume means manual handling is still acceptable.
FAQ
FAQ
These are the practical questions teams usually ask before changing an invoice workflow.
Should invoice forwarding rules be complex?
Usually no. The best forwarding rules are simple enough to maintain and reliable enough that the attachment reaches the right intake flow every time.
What is the main risk of an email-only process?
The inbox becomes the work surface. That usually means more downloading, more renaming, and more manual row building than necessary.
How does ZeroPaste fit?
ZeroPaste gives teams a dedicated invoice inbox and turns forwarded files into structured, reviewable rows before export.
Why is this especially useful for UK and EU bookkeepers?
Because many smaller firms want a practical forwarding workflow with clearer data-handling boundaries. ZeroPaste processes on EU servers and deletes original files within 24 hours.