Every accountant has sent the chase email: "Can you send me the receipt for that one?" Every owner knows the quarter-end ritual: dig through Gmail, dump PDFs into a zip, hope nothing important is still on a phone.
Automating that handoff is really two jobs. First, collect every invoice. Second, deliver it in a shape they can use. Most "set a Gmail rule" advice only automates the second half for messages you already noticed.
Below are the four common paths, what bookkeepers actually want from each, and a privacy-first setup that captures vendor email without granting a tool your whole inbox.
Most people combine two of these, not all four:
accountant@….Only path 4 stays complete when subjects vary, HTML bodies have no PDF, and you forget to forward. TallyScan is built for that path: you forward vendor mail to a private address, AI extracts the fields, and your bookkeeper works from a shared folder or sheet instead of chasing you.
The failure point is memory. A receipt arrives, you mean to forward it later, and "later" becomes tax season. Shared Drive folders help, but someone still has to upload. The chase email is a symptom. The disease is that collection sits between you and clean books as unpaid labour.
IRS Publication 583 is a blunt reminder: business records need durable source documents, not a total you typed from memory. Your accountant is asking for the same thing: the file behind the number.
Daily is ideal and rare. Weekly slips. Monthly creates a catch-up weekend. Quarterly is where deductions disappear.
That debate only exists because sending is a chore you batch. When capture and delivery run as invoices arrive, frequency becomes continuous without another calendar reminder. Your accountant reconciles a trickle all year instead of excavating a zip in April.
| Method | Your ongoing effort | What it catches | What your accountant gets |
|---|---|---|---|
| Hand forward / monthly zip | High | What you remember | PDFs, often late |
| QuickBooks / Xero email-in | Medium | Attachments you forward | Drafts in their ledger |
| Keyword auto-forward rule | Low after setup | Subject matches only | Raw emails, mixed quality |
| Capture then share / sync | Low after setup | Vendor mail you route to capture | Source file + extracted fields |
Fine for five suppliers. At forty SaaS tools it fails in the same week every month.
QuickBooks uses @assist.intuit.com. Xero gives each org a unique bills email. Both turn attachments into reviewable drafts. Setup guides: email invoices to QuickBooks and email invoices to Xero.
You are still the person who must forward, and HTML-only receipts still fall through.
Filter on "invoice" or "receipt" to your accountant's address. Cheap and useful as a start. It misses "Your order," "Payment confirmation," and non-English subjects, and it forwards junk that is not an invoice. Your accountant becomes an unpaid spam filter.
A tool recognises invoice content, extracts fields, keeps the source document, then puts the result where the accountant already works: a shared Drive, a Sheet, or the ledger. That is the only pattern that stays hands-off and complete for email-heavy AP. Details on intake models: extract invoices from email automatically.
A rule cannot forward an invoice that never reached you. Common gaps:
Automating "send to accountant" without automating collect just accelerates incomplete packs. Solve collect first.
Ask a bookkeeper and the list is short:
A folder of random screenshots fails most of that list. Capture-plus-share can hit all five.
This path does not require full Gmail or Outlook OAuth.
Sign up and copy your dedicated TallyScan forward address.
Forward by hand at first, then add filters for known billing senders. Test with one Stripe and one supplier PDF.
Pick one primary delivery channel (many firms use two):
| Accountant prefers… | What you share |
|---|---|
| Spreadsheet review | Google Sheets sync (Starter+) |
| PDF archive | Google Drive or OneDrive folder access |
| Notion workspace | Notion database sync |
| Working in the ledger | QuickBooks or Xero sync (Beta on Pro) after you trust extraction |
Invite them to the Sheet or Drive folder once. New invoices keep landing without another zip file.
Automation removes the scramble. It does not remove review. Ten minutes on Friday beats two days in April.
Download Amazon / ad-portal PDFs when billed, upload or forward once. No email tool invents portal files.
Pro Tip: Ask your accountant: "Sheet + PDF folder, or drafts in Xero/QBO?" Match the destination to how they already close your books. Do not invent a third system they must learn.
Forwarding dumps mail on someone. Sharing a reviewed capture queue (Sheet rows + PDFs) lets them query vendor, amount, and date without pinging you. For solo freelancers, that is usually enough. Multi-client practices evaluating firm tools should still compare practice suites honestly; see our Dext alternative page if that is your buyer seat.
Real-world versions of this habit show up in our case studies.
Capture invoices as they arrive (dedicated address or ledger email-in), then deliver via a shared Drive/Sheet or accounting sync. A plain keyword rule to your accountant's inbox is only a partial fix.
Use each product's built-in forwarding address, then review drafts. Guides: QuickBooks and Xero. For HTML bodies and higher volume, capture with TallyScan first.
Yes. Share the Google Drive / OneDrive folder or Sheet where TallyScan writes files and rows. That is usually better than flooding their inbox.
Automate collection from vendor email, keep source PDFs with the data, and deliver continuously. Chase emails are almost always missing documents, not missing effort at month-end.
Email attachments and many HTML receipts can flow through a dedicated address. Portal-only invoices still need a download step. Teammate inboxes need either shared filters or a single AP mailbox.
As they arrive, if automation is in place. If you still send manually, weekly beats quarterly.
Original PDF or clear image, plus key fields. Ideally already in Sheets/Drive or as ledger drafts. Ask them once and standardise.
Prefer tools that do not demand full-inbox OAuth if that worries you. Forward only invoice mail, use shared Drive permissions deliberately, and review Beta ledger sync on a small batch first.
The goal is not a prettier zip file. It is a pipeline: vendor email → capture → shared archive or ledger draft → accountant reviews.
Start free on TallyScan, forward one real invoice to your dedicated address, invite your bookkeeper to the Sheet or Drive folder, and retire the quarter-end scramble. Pricing scales when volume does.
Upload invoice PDFs to OneDrive by hand, with the sync client, or via Power Automate, then automate capture-and-file with AI so Microsoft 365 teams stop dragging files every week.
Invoice capture and invoice data capture explained, plus tools compared by fit (not a fake #1). Field reference, Hubdoc vs Dext vs TallyScan, ROI math, and how to test before you buy.
Native PDF vs scan, five extraction methods compared, fields you need, accuracy checks, and when AI beats templates so you stop retyping invoices into Sheets or your ledger.