A NetSuite manufacturer with about ten approvers and a corporate card program processes a steady pile of shipping invoices, then trips on something smaller and stranger: airline receipts that arrive as email bodies with no PDF attachment. A transportation company on Great Plains or Business Central hits a cousin of the same problem: contracted driver invoices verified by an admin, then forwarded from the admin's address rather than from the vendor. In both cases the document is real. The attachment slot is empty, or the sender identity is the routing signal.
If your intake only reads attachments, airline style receipts never become bills. If your routing only reads vendor master email addresses, admin forwards never land in the right queue.
This matters most if corporate travel still produces HTML receipts, if admins verify third party invoices before finance sees them, or if you have already watched OCR tools sit idle because there was nothing to OCR until someone printed to PDF by hand.
Intake edges that do not look like AP strategy
These problems rarely make the RFP. They make Tuesday. Someone forwards a confirmation email. Finance prints it, or copies it into a Word doc, or saves a browser print to PDF, then uploads. The metadata is wrong. The duplicate detector may or may not recognize last week's forward. Approvers ask why the "invoice" looks like an email theme.
Sender based routing is the other half. When an admin mailbox is the trusted verifier for trucker invoices, the vendor domain is not who hit your AP address. Rules based on who the sender is decide whether the document is prechecked, needs coding, or should wait for a matching ticket. That is workflow design, not a capture party trick.
Fix attachment-only intake and the failure mode changes to silent loss. Emails without attachments disappear into a monitored inbox that your parser skips. Nobody opens an exception, because no record was created.
What travel documentation costs when nothing arrives cleanly
The GBTA Foundation's study on expense reporting estimated $58 and about twenty minutes to process an expense report, with 19 percent of reports containing errors that cost more time to fix. It is an older study and hotel skewed. Treat it as a reminder that travel documentation is expensive even when the dollar amount is small. Airline emails with no PDF are how those minutes hide: conversion labour before AP labour.
Ardent Partners’ Accounts Payable Metrics That Matter in 2025 puts average invoice cost at $9.40. A manually printed airline email can burn a chunk of that before extraction starts.
Build a tiny intake catalogue
List the last thirty non PO documents that were not clean vendor PDFs:
- Email body only (airlines, some bookings).
- Admin forward of a vendor PDF.
- Photo of a paper receipt.
- Multi attachment claim packs.
- Portal download links with no file.
For each category, write the rule you wish existed: convert body to PDF, route by sender, require attachment, or reject.
A test you can run without buying anything: for one week, tag every finance inbox item that needed a human to create a PDF before AP could start. That count is your business case.
How this shows up beside card feeds and SMS capture
Body conversion is not a replacement for receipt capture from employees who dine out. It is the sibling problem for documents that never touch an employee phone: carrier confirmations, booking engines, and admin verified vendor bills. Companies often buy an expense app for the first problem and still print the second problem to PDF by hand.
Sender rules also protect you from treating every forward as vendor truth. Write that difference down as policy before you automate it. Otherwise you will automate the wrong trust model.
Who this applies to: finance teams in manufacturing with corporate travel on NetSuite or similar, and transportation shops where dispatch or admin mailboxes are the real invoice gateway. If every vendor already sends clean PDFs to a locked AP mailbox, you may only need conversion for a handful of travel edge cases. Still worth doing. Those handful tend to sit with senior staff who hate print to PDF chores.
Pair this with duplicate detection. Forwarded airline emails get resent. Without content aware duplicate checks, you will pay the same itinerary twice under slightly different subject lines.
Reading the email body, and routing by who sent it
Finofo converts attachment less email bodies to documents so an airline confirmation becomes a reimbursable like any other, and applies sender based routing rules so admin versus vendor identity drives the path. For the manufacturer, the booking confirmation lands in the expense queue with merchant, date and amount extracted, no printing involved. For the transportation company, a driver invoice forwarded from the admin mailbox is recognised as prechecked and routed accordingly, while the same PDF arriving direct from a vendor takes the standard path. It pairs with the rest of intake: dedicated organisation addresses, trusted senders, and classification into invoices versus supporting documents.
We rejected waiting for airlines to standardize PDFs. They will not do it on your timeline. We also rejected forcing employees into an expense app solely because the receipt arrived as HTML. Finance still owns coding; intake should not invent a second mobile workflow just to capture a boarding confirmation.
Intake is the front of one engine, which is why an airline email and a trucker invoice can take different routes and still land in the same queue. Finofo runs accounts payable, expense management and purchasing on a single AI native platform, built in Calgary for the documents Canadian finance teams actually receive. A converted travel receipt gets the same Canadian tax handling, the same duplicate check and the same approval flow as a vendor bill, and posts through one path into NetSuite or Business Central.
What stays with your team
The judgment in this workflow stays with your team. That is a design decision, not a gap, and it shows up in a few specific places.
Trust is a rule you write. Which senders are treated as verified, which admin mailboxes count as prechecked, and what happens to a forward from an unknown address are policy decisions Finofo applies exactly as configured. Routing is a control, not an open relay, and it needs a quick review when admins change roles.
Review sits where conversion is imperfect by nature. Airline templates vary and email clients clip content, so a converted body that reads ambiguously is flagged for a person rather than posted on a guess. Finofo shows what it extracted and where it was unsure, which is the point of marking uncertainty instead of hiding it.
Portal links with no document are a chase, not a conversion. Finofo logs the email as an intake item so it is visible and aged, and the follow up to obtain the actual document stays with your team.
Bring this to any demo: process an HTML only booking email end to end, then process an admin forward of a vendor PDF and show different routing. If both paths look identical, sender based control is not real yet.
Keep an eye on classification after conversion. A body that contains both a receipt and a long marketing footer should still land as one reimbursable or bill, with junk held as supporting text rather than as extra invoices. Classification mistakes recreate SharePoint style clutter inside the new system. Finofo classifies the converted document the same way it classifies a PDF, so a marketing footer never becomes a second invoice.
The receipt was in the body the whole time. The system just refused to look there. Convert what you can. Route by who sent it when that is the control. Then airline confirmations and admin verified trucker bills stop being craft projects before they become accounting.
Frequently asked questions
**Does body conversion replace employee expense apps?**
No. It removes a conversion step for documents that already arrive as email. Coding ownership is a separate design choice, and in Finofo it stays with finance for converted receipts exactly as it does for texted ones.
**Can we trust any sender who forwards a bill?**
No. Maintain trusted senders and admin roles. Routing is a control, not an open relay. Finofo applies the sender rules you define and holds forwards from unrecognised addresses for review
**What if the email has both a body and a PDF?**
Prefer the PDF when it is the legal document, and keep the body as supporting context when it adds booking detail. Finofo attaches both to the same record so the reviewer sees the invoice and the context together.
About Finofo
Finofo is the AI native platform built in Calgary for Canadian finance teams. It brings accounts payable, expense management and purchasing onto one engine, on the cards, bank and ERP a business already uses, with line level extraction, Canadian tax handling and approval workflows designed for multi entity, multi province operations. Finofo does the verification. Finance keeps the judgment.
