A document arrives by email, gets downloaded and lands in a temporary folder. Later, someone renames it, forwards it to a colleague or stores it in a folder structure that only its creator fully understands. Once several people and inboxes are involved, a small manual step turns into a daily search and sorting task.

For many SMEs, the answer is not another folder or another piece of software. The important step is to treat the attachment as the start of a defined workflow. A solution can read the file, identify its document type, suggest the right customer or project and prepare the filing step. The business still reviews and approves the result.

Why email filing becomes difficult

Email is an important intake channel for many businesses. Invoices, orders, delivery notes, quotations, contracts and technical documents rarely arrive in the same format. Some files have clear names; others are called scan_0047.pdf. A document may also belong to a customer, a project, an order or several of these at once.

Manual filing usually has four recurring weaknesses:

The document type is assessed from scratch each time.
Customer, project or order details have to be inferred from the content, not just the filename.
The result depends on the knowledge of individual employees.
Nobody has a reliable view of which attachments are still waiting for review.

This does not always cause a serious error. It does consume attention, interrupt other work and create more follow-up questions. When the document is needed later, the search often starts in the inbox, on the file server and in several personal folders at the same time.

What a prepared workflow changes

A suitable solution does not simply move every attachment into another folder. It treats the incoming message as the first step in a defined process.

The workflow reads the attachment and prepares the information that matters. This may include the document type, sender, customer, project, order number, date or amount. The fields are not accepted blindly. Missing or uncertain information is made visible.

The system then creates a filing suggestion. It may propose, for example, assigning an order to the right customer and project and storing it in an agreed location. The responsible person sees the suggestion, corrects it if necessary and approves it. Only then is the final filing step carried out.

For an SME, this is often a more useful starting point than completely automatic filing. Repetitive preparation is reduced while responsibility and control remain understandable.

How the process works in practice

1. Define the intake

Start by deciding which inboxes and document types are part of the pilot. A limited first scope could cover orders received in one defined mailbox. Personal messages, unclear attachments and unusual cases remain outside the first version.

2. Read the content

The solution reads PDFs, scans or other agreed formats. A scan may require text recognition. The goal is not to extract every possible field. It is to identify the fields that are actually needed for the next decision.

3. Prepare the assignment

The sender, document content and available master data are used to prepare a suggestion for the customer, project or order. If several assignments are possible, the alternatives and open questions should be visible. A good solution does not hide uncertainty behind a result that looks more certain than it is.

4. Review and approve

A named person checks the suggestion. They can change fields, reject the process or add missing information. This approval step is part of the design: the software prepares the work while the business keeps decision authority.

5. File and keep a trace

After approval, the document is filed according to an agreed scheme. It should also be possible to see when the document was processed, which assignment was suggested and who approved it. Retention and deletion rules need to match the document type and the business.

What to measure in a pilot

A pilot does not need to prove that every file can be processed without human involvement. It should clarify whether one bounded workflow works reliably enough in everyday operations.

Useful measures include:

How long does it currently take from receipt to correct filing?
How often are customer, project or other required details missing?
How many suggestions are approved immediately and how many need correction?
Which documents still require a manual exception path?
Can employees find an approved document faster later?

These questions create a better basis for a decision than a general claim about model accuracy. They measure the whole path, including review and filing.

Where limits and rules still matter

Not every document is suited to the same level of automation. Handwritten notes, unusual attachments, conflicting master data or missing permissions still require review. The filing logic also needs to be understandable. If nobody knows why a document was assigned to a project, the business has only created a new black box.

Permissions, storage location, roles and exception cases therefore belong in the pilot scope. The same principle applies to an internal assistant connected to your own file server: documents should be searchable without giving people access to content they are not allowed to see.

A practical way to start

The first step can be one document type, one intake channel and one clearly named approval role. Together, you define the data sources, required fields, filing rules and exceptions. The workflow can then be tested with selected real examples.

Alpino AI connects these process elements to the mailboxes, archives and business systems you already use. The best solution is not the largest one. It is the one people understand and use. See our services for an overview of possible starting points.

If you want to check whether automatically filing one document type makes sense for your business, book a 30-minute first conversation. We start with the workflow that currently creates the most searching and manual transfer work.

Automatically archiving documents from email: from attachment to workflow