AI Email Parser that reads the whole message, body and PDF attachment, and lands the fields as spreadsheet columns
Manually opening each email, downloading the attachment, and typing its fields into a spreadsheet takes about 3 minutes per document. This parses the body and the attachment in 5-10 seconds.
5–10s per page · Up to 99% accuracy on printed text · Dedicated inbox address · No per-sender rules
What an Email Parser Pulls Out of Every Message and Its Attachments
An email parser turns unstructured messages into spreadsheet rows. ImageToTable.ai covers both halves of the message: the header fields every tool can see (sender, subject, received date), and the data that usually lives inside the attachment, where a vision model reads PDFs, scans, and photos the same way it reads any uploaded document. You type the column names, and every forwarded email lands as a row with those headers.
These are example column names. Body fields come from the message itself; fields like line items and totals are read out of the PDF or image attachment. You define the set once, and every forwarded email produces the same structured row.
The Data Is Usually Not in the Email. It Is in the Attachment.
Most of what ranks for this query is an email parser tool that reads the prose of the message and stops there. That design made sense when the email itself was the document, but for invoices, order confirmations, and bank notices the message is just an envelope around a PDF. Three structural problems follow from it, and they explain why so many parsing setups quietly decay.
Where Body-Text Parsing Falls Short
Body-only parsers stop where the data starts. An order confirmation email is two sentences of prose wrapped around a four-page PDF invoice. A body parser captures the prose, the subject line, and maybe a total mentioned in text; the invoice number, the line items, and the tax breakdown sit in the attachment it never opens. The Gmail and Sheets add-ons in this category parse "templated emails," not the documents attached to them.
Parsing rules are tied to one sender's layout, and the vendors' own docs admit it. cloudHQ's setup guide instructs you to filter to a single sender and subject because all messages must "have similar format" (source). Mailparser's own help center recommends building each rule around "a fixed position in the text" (source). When the vendor renames "Total" to "Amount Due" or reflows the template, the rule does not error out. It grabs the wrong span, or nothing.
Email noise defeats position-based rules. Signature blocks, legal disclaimers, and quoted reply chains mean "the text after Total:" can appear three times in one message, and the oldest copy usually sits in the quoted thread. A parsing-rules thread in r/ConnectWise puts it plainly: "The problem with parsing rules is that you can't always use them and it depends on the subject line of the email."
How Column-Name Extraction Handles It
The attachment is read as a document, not skipped. The vision model reads PDFs, scans, and photos the same way it reads any file you upload directly, at up to 99% accuracy on printed text. Password-protected attachments are covered too: save the passwords you commonly use in settings, and encrypted PDFs are tried automatically before processing. Body fields and attachment fields land in one row.
You define columns once; any sender fits. This is Custom Column Extraction: you type the column names you want (Invoice Number, Due Date, Total) and the AI locates each value by understanding what it means, not where it sits. A new sender, or an old sender with a redesigned email, needs zero reconfiguration. And because every account gets one dedicated inbox address, you forward everything to one place instead of maintaining one mailbox per layout the way rule-based tools require.
Semantic reading is immune to message chrome. Signatures, disclaimers, and quoted thread text are not confused with field values, because extraction runs on meaning rather than position: a disclaimer that contains the word "total" is not a total. When a forwarded chain does carry older versions of the same figures, review mode with bbox highlighting shows you exactly which occurrence each extracted value came from, so verification is a glance instead of a re-read.
The pattern behind all three problems is the same: rule-based email parsing prices every sender and every layout change as new work. Semantic extraction prices the schema once and absorbs the senders.
From Supplier Email to Spreadsheet Row Without Opening Your Mail Client
If you process supplier invoices that arrive by email, here is the full loop from message arrival to export.
Forward to your dedicated inbox address
Every account gets one inbox address. Share it with suppliers, or set a forwarding rule in your own mailbox so invoices route there automatically. Enable the sender whitelist to keep unrelated mail out of your queue, and turn on Auto-Process so extraction starts the moment a message arrives, using the column template you define in the next step. Attachments land in the processing queue on their own; nobody downloads or re-uploads anything.
One address, any mailbox, no upload step.
Name the columns once
Type the fields you want: Sender, Invoice Number, Invoice Date, Due Date, Total, plus attachment-side fields like line items. These names become the exact headers of your output spreadsheet. Save the column set as a template and Auto-Process reuses it on every arrival. The AI reads each message and its attachments and fills every column it can; fields a particular email does not contain are left empty rather than guessed.
Your column names are the output. No rules per sender.
Export the batch
Each email becomes one row, with body fields and attachment fields sitting side by side. Export the batch as XLSX, CSV, or JSON, or land the results directly in Google Sheets through the add-on. Dates and amounts are standardized during extraction, so the file is ready for your AP or reporting workflow without a cleanup pass.
| Sender | Invoice Number | Due Date | Total |
|---|---|---|---|
| [email protected] | INV-88213 | 2026-09-30 | $4,218.60 |
| [email protected] | VP-10427 | 2026-10-07 | $1,102.00 |
Example values. Sender comes from the message header; the rest comes from the attached invoice PDF.
What This Email Parser Does Well, and What It Deliberately Does Not Do
Parsing email content and attachments into columns is a bounded job, and it is worth being precise about where the boundary sits before you build a workflow on top of it.
When It Works Best
Emails whose real content is a PDF or image attachment. Invoices, purchase orders, bank statements, and delivery notes usually arrive as attachments. The attachment is parsed as a full document, so line items and totals survive, not just the covering note.
Recurring senders you can whitelist. With Auto-Process and a bound template enabled, extraction starts on arrival with no clicks. Whitelisting keeps the queue clean when the address is shared with vendors or clients.
Mixed senders and shifting formats. One inbox address and one column set cover every sender, so a vendor redesigning their email or a new supplier joining the rotation does not create maintenance work.
When to Be Cautious
It produces columns; it does not run your back office. This tool parses email content and attachments into structured data. It does not send replies, manage your mailbox rules, chase missing fields with vendors, or replace your CRM or accounting system. What happens to the spreadsheet afterward is your workflow.
Attachment quality still matters. A native digital PDF extracts far more reliably than a photograph of a screen. If a human would squint to read a field on the attachment, the model will likely struggle with it too, and handwritten or heavily degraded scans deserve a review pass.
Long forwarded chains deserve a verification glance. Extraction reads by meaning, but a chain that quotes several older versions of the same figures is the one scenario where confirming which occurrence a value came from is worth thirty seconds. Review mode with bbox highlighting exists for exactly this.
Frequently Asked Questions
Which mailboxes can I auto-forward from? Is there a Gmail, Outlook, or Zoho email parser setup?
Any mailbox that supports forwarding works, because the parser never logs into your mailbox. Every ImageToTable.ai account gets one dedicated inbox address, so searches like gmail email parser, outlook email parser, or zoho email parser all end at the same setup: a forwarding rule in Gmail, Outlook, Zoho Mail, or any other client that sends messages to that address. The parser only sees what you forward, and a sender whitelist keeps unrelated senders out of your queue. It parses email, not text messages; SMS forwarding is outside what this tool does.
Does it read attachments, or only the email body?
Both, and the attachment is usually the half that matters. Body-text parsers stop at the prose and the subject line, but on an invoice email the invoice number, line items, and total sit inside the PDF attachment. ImageToTable.ai reads the attachment as a document with a vision model, the same way it reads any uploaded PDF or scan, and lands body fields (sender, subject, received date) and attachment fields (invoice number, line items, totals) in the same spreadsheet row.
What happens when a vendor changes their email format?
Nothing breaks, because there are no per-sender rules to break. Template-based parsers tie every field to a fixed position or label in one sender's layout, so a renamed label or reflowed template returns the wrong value or nothing at all. Here you define output columns once and the AI locates each value by meaning, so a new sender or a redesigned email needs zero reconfiguration. The only time you touch your setup is when you want to capture a field you were not extracting before, and that means adding a column, not repairing a rule.
Can it pull invoice numbers and totals from PDF attachments into Excel automatically?
Yes. Define the columns you want (Invoice Number, Invoice Date, Due Date, Total Amount), bind them to a template, and turn on Auto-Process for your inbox. Every forwarded email carrying an invoice PDF then becomes a spreadsheet row without anyone opening the message. Password-protected attachments are handled too: save the passwords you use in settings ahead of time and encrypted PDFs are tried automatically before processing. Results export as XLSX, CSV, or JSON, or land directly in Google Sheets through the add-on.
Is there a free email parser to excel trial?
Yes. Signing up is free and includes credits to test with your own emails, so you can forward a sample message with an attachment, watch the columns fill, and judge the output before paying anything. The live demo on this page works without an account as well. Paid plans start at $9/month when you move beyond the free credits.
Read more about the workflows around email-driven extraction:
- The Google Sheets Invoice Pipeline: Supplier Email to Structured AP, the closest published story of turning supplier emails into AP-ready rows.
- Batch Extract Invoice Data to Excel, the attachment-side workflow when invoices pile up faster than the mailbox drains.
- API vs No-Code Document Extraction, architecture framing if you are evaluating parsers for a larger pipeline.