Setting up invoice forwarding for Xero and DATEV: best practices

Forwarding only helps if the intake path stays predictable

Most firms do not struggle because forwarding rules are technically hard. They struggle because forwarding gets bolted onto a messy intake setup. One client sends PDFs directly. Another sends bills to a shared finance inbox. A Xero-generated address forwards something else. Someone on the team forwards the whole email as an attachment instead of preserving the original PDF. The result is not one process but a collection of tiny exceptions.

The safest approach is to choose one canonical intake layer and make every forwarding rule serve that layer. For ZeroPaste users, that means deciding which ZeroPaste inbox or alias is the destination of record. Xero, Outlook, Gmail, shared mailboxes, and mobile capture should all converge there. Review and export happen after that, not inside five separate channels.

Step 1: decide the routing model before you add rules

Start with the destination design, not with the mail rule. Solo bookkeepers can often keep one personal ZeroPaste inbox for all incoming supplier invoices and assign clients during review. Multi-client firms usually benefit from client-specific aliases because it reduces later routing work. Shared inbox teams often want both: one catch-all inbox for uncategorised traffic and explicit aliases for high-volume or high-risk clients.

This matters for DATEV and Xero firms alike. DATEV-heavy practices often care about a clean client-to-export path. Xero-heavy practices often care about preserving a familiar email intake habit. In both cases, the routing question is the same: where should this supplier PDF land first so review stays consistent and downstream handoff is easy?

• Use one catch-all inbox for uncategorised or low-volume intake.
• Add client-specific aliases when shared inboxes or large client books create routing noise.
• Keep the alias pattern documented so the team does not invent its own versions.

Step 2: preserve the original supplier PDF

The most common failure mode is not DNS or OCR. It is forwarding the wrong thing. ZeroPaste works well when the original supplier PDF remains attached as a normal PDF attachment. It is much less useful when the mail client forwards the whole message as an .eml file or wraps the invoice in another message format that the intake layer was never meant to process.

That is especially relevant for Xero-related forwarding. If a user is already receiving supplier documents through Xero-style email addresses, the operational rule is simple: preserve the original PDF attachment. Forward the message normally if that keeps the PDF as a PDF. Avoid forwarding methods that turn the email itself into the attachment. The same rule applies to shared inbox workflows in Outlook or Gmail.

Step 3: make the exceptions queue part of the design

Forwarding should not be designed as if every incoming invoice is trustworthy by default. Build the review expectations in from the start. Shared inboxes create client-matching mistakes. Forwarded chains can confuse supplier context. Mobile photos can create lower confidence on VAT or invoice numbers. The answer is not to avoid forwarding. It is to let forwarding feed a queue that already knows how to surface duplicates, unusual totals, missing invoice numbers, and suspicious VAT.

This is where the combination of intake and review matters. A forwarding rule is only as good as the review layer behind it. If the team can see why a document was flagged, who corrected it, and what export preset is about to be used, forwarding becomes operationally safe. If the forwarded invoice disappears into a black box, the rule may save ten seconds and cost ten minutes later.

Step 4: align forwarding with the export destination

The intake path should reflect the downstream handoff. If a workspace mainly exports to Xero-friendly CSV, make that the default. If a German mandate needs DATEV-friendly output, set the DATEV preset as the workspace default and keep the same forwarding route for that mandate. The forwarding rule itself is not where export logic belongs, but the workspace receiving the document should already know which export shape is most likely.

That sounds minor, but it removes one more repetitive decision. A bookkeeper forwarding invoices from a shared inbox should not also need to remember whether this client wants generic CSV, Xero-friendly CSV, or DATEV-friendly output every single time. Intake, review, and export presets work better when they are configured together.

A practical checklist for firms

Before you roll forwarding out to every client, test one live path end to end. Forward one ordinary supplier PDF from Gmail or Outlook. Forward one Xero-style email that still contains the original PDF. Try one shared inbox route. Confirm that the attachment arrives correctly, the correct workspace or alias receives it, the exceptions queue shows anything suspicious, and the export preset is what you expect.

If that path is clean, document it in one short internal note. Tell the team which inbox to use, when to use aliases, what not to do with .eml forwards, and how to recognise a successful result in the review queue. That kind of operational clarity is what keeps forwarding useful after the first enthusiastic week, especially in practices juggling Xero, DATEV, QBO, and spreadsheet clients at the same time.