Automated Email Attachment Processing
Every attachment is read, identified, renamed and filed where the case expects it – together with the rule that made that decision. Anything ambiguous does not go into the archive; it goes to a person.
Filing is not the slow part, deciding is
Saving a file takes seconds. The effort sits in front of that, and it starts again with every single message: is this PDF an invoice, an order confirmation or a quote? Does it belong to purchase order 8820 or to something else entirely? Should it live in the customer folder, in the accounting system, or in both? Today a person answers those three questions by opening the message, looking at the file and then switching between two systems.
The real difficulty is that attachments arrive the way the sender finds convenient, not the way your filing needs them. The same invoice is called “INV-4471.pdf” from one supplier, “scan001.pdf” from the next and “Document (2).pdf” from the third. Three documents turn up in one message, one document is split across two. The company logo from the signature block travels along as its own file, and a photo of the delivery note arrives instead of the delivery note. A rule set that only reads the file name fails on a sizeable share of the post – and rules that match too loosely are worse than none, because a misfiled document goes unnoticed.
So what we build is not the moving of files but the deciding: features that sit inside the document itself, a confidence threshold below which the automation holds back, and a log that records for every file which rule put it where it is. Otherwise a document in the wrong folder only surfaces when somebody goes looking for it – months later, in the middle of an audit or a complaint.
If the attachment is a customer purchase order, the path should not end in a folder. Order intake automation then validates line items, master data and exceptions before handing a draft to the ERP.
Which attachments are worth it
We start with the attachment type that arrives most often and has the clearest features. Further types later share the same recognition and the same log.
Supplier invoices
The most common starting point: consistent features, high volume, one clear destination – and the case where filing something twice costs real money.
Delivery notes and order confirmations
Matched to the open case through the order number inside the document rather than through the subject line of the message.
Completed forms and signed contracts
They come back as scans and need to reach the right file – recognisable from the form header and customer number, not from the file name.
Photos from service and site
Measurements, damage and installation photos taken on a phone. Here the link to the job matters more than the content of the file.
Certificates with an expiry date
Test reports, certifications and insurance confirmations from partners. The expiry date is read out as well and stored as a deadline.
Lists and price files
Spreadsheet and CSV attachments that are meant to be imported rather than filed – with a column check before anything is written.
An inbox with the decisions written beside it
A Tuesday morning in the invoice mailbox. For every attachment you see what it was recognised as, where it went and which rule decided that.
-
INV-4471.pdf Purchase invoice Accounts · case 8820 filed
R3Sender is on the supplier list; the PDF contains an invoice number, an amount and a VAT number.
logo-signature.png Signature image, 11 kB not taken over discardedR1Image under 20 kB, referenced from the signature block of the message – not a document.
-
scan001.pdf Delivery note Filing · goods receipt 2026 filed
R7Order number 8820 found in the document; folder and new file name come from that order.
-
Detail_North_v2.dwg File type without a rule Review folder · task to project lead person checks
R0No rule is defined for .dwg, and the sender is not linked to any open case.
-
INV-5518.pdf Purchase invoice Accounts · case 9014 filed
R3Same features as above; the duplicate check on invoice number and amount returned nothing.
Invoice_May_final(1).pdf Purchase invoice, identical not taken over duplicateR4Invoice number, amount and page count match INV-5518.pdf from the very same message.
The line that matters is the last one in each card. Without it, in six months nobody knows why a file sits where it sits – and nobody can change the rule on purpose.
The third message shows normal operation, not a failure: there is no rule for .dwg, so the automation files nothing and raises a task instead. Cases that keep coming back through the review folder become the next rule.
From the message into the case
-
Watch the mailbox
The workflow listens to one approved shared mailbox, or to a single folder inside it – never to a person's whole correspondence. Sender, subject, message body and each file are read separately.
-
Check the file and make it readable
File type, size and protection status are checked, archives are unpacked, scans and photos go through text recognition. Anything your security scanning rejects is isolated rather than opened.
-
Determine the attachment type
Sender, subject and above all the text inside the document produce the classification: invoice, delivery note, form, photo, signature graphic. The file name counts as one clue among several.
-
Match the case and rename
Customer number, job number or order number are read from the document and validated against your leading system. Only once that link holds does the file get its name under your scheme.
-
Hand over and log
The destination system receives the file and its key data, the message is marked as processed. Every decision is logged with its rule number; anything doubtful becomes a task for the responsible person.
What changes day to day
Today
- Every message is opened and every file saved by hand
- File names arrive exactly as the sender happened to write them
- The link to the case only exists in the head of one colleague
- The same invoice ends up in the filing system twice
- Nobody can say later why a file sits where it sits
With attachment processing
- Attachments are read the moment the message arrives
- File names follow your scheme, even for unnamed scans
- Customer, job and order number travel with the file
- Duplicates are caught before they reach the filing system
- Every filing carries the rule that triggered it
What this automation does not do
From the outside attachment processing looks like sorting. These four points decide whether it pays off in your case – we clarify them before quoting:
- Recognition stays a probability. With cleanly generated PDFs it is highly reliable; with photographed documents, handwriting or multi-page bundle scans it is markedly less so. So we agree a threshold with you: anything below it goes to the review folder instead of the destination system. That threshold costs throughput and is still the right call.
- Below a certain volume this is not worth buying. If you handle ten attachments a day you might save twenty minutes – which does not justify a rule set, an acceptance phase and ongoing operation. It gets interesting from a few hundred a month, or when several people repeat the same handling. If we do not see that case at your end, we say so in the intro call and advise against it.
- Without a leading system it stays filing. A file can only be matched to a customer or a job automatically if that case is maintained somewhere and we can identify it unambiguously. Where customer numbers are missing or order numbers are inconsistent, the automation sorts by sender and date and no further. This is the most common reason a project turns out smaller than planned.
- Security scanning stays with your IT. We bypass no filter and no quarantine; we sit behind what your mailbox already checks. Password-protected files and documents containing macros are isolated, and a password written in the message body is deliberately not read out. If you expect us to open everything that arrives, the answer is no.
Fits your mailbox and your filing
Scope and price
The entry price covers one mailbox with up to three attachment types and one destination system. What moves the price, we say before the quote.
- Connection to one approved shared mailbox or folder
- Rule set for up to three attachment types, documented
- Text recognition for scans and photographed documents
- Naming scheme, filing structure and duplicate check
- Handover to one destination: filing, CRM, ERP or ticket
- Review folder with a task for the responsible person
- Log per filing, documentation and 30 days of support
What increases the price
- More than three attachment types with their own features
- Several mailboxes or several destination systems in parallel
- Matching to cases in an ERP or industry-specific system
- Handwriting, bundle scans and multi-page documents
- An approval step before filing or before posting
Several mailboxes, more than three attachment types and matching into an ERP typically land in the range of our Workflow Advanced package from €2,490. We quote the binding fixed price after the intro call.
All prices excl. VAT · operation and further development optionally via a support package
What you get
-
Production attachment processing
Set up from inbox to destination system and signed off against two weeks of your real post
-
Documented rule set
Every attachment type with its features, destination and naming – changeable later without us
-
Review path for doubtful cases
Review folder, task and a named owner, so that no attachment quietly stops moving
-
Training for your team
How to spot a misfiling, how to correct it and how it turns into a new rule
Frequently asked questions about attachment processing
These solutions fit alongside
Automatic Document Filing
The step afterwards: consistent names, metadata and locations for everything that comes in.
Accounts Payable Automation
When the attachment is an invoice: matching against the order, approval and handover to accounts.
AI Document Processing
For documents whose content has to be extracted in full – not only their filing location.
AI Email Assistant
The message itself: sorting, summarising and draft replies in the shared mailbox.
How many attachments pass through your mailbox each day?
In the free intro call we look at two weeks of your real inbox and count which attachment types actually occur. Afterwards you know which three rules would cover the bulk of it – and whether the effort pays off at your volume at all.
Book a free intro callWhere email attachment automation creates value in everyday work
The automation checks sender, message and file, classifies the attachment and transfers it with a clear assignment to storage or a business system.
Three concrete operating scenarios to compare with your own process.Process purchase orders
PDF purchase orders are assigned to customer and order and prepared for the ERP process.
File completed forms
Completed forms receive a readable name and the correct case link.
Pre-sort invoices
Invoice attachments move into accounts payable with sender and intake data.
A strong fit when …
Recurring office tasks follow clear rules, consume small blocks of time every day and should run reliably without replacing existing systems.
- You handle recurring email attachments using repeatable rules.
- The intake, target system and accountable business role can be named clearly.
- Exceptions are allowed to remain visible and move to people deliberately.
Deliberate automation boundary
Unknown file types, malware warnings, password-protected files and unclear assignments are isolated and sent for review.
Explore the technical approach and platformsEstimate time savings with your own volume
The calculator uses 5 minutes today and 1 minutes after automation as fixed example assumptions. It does not replace process analysis.
Illustrative estimate based on the visible assumptions — not a guarantee.