Set up invoice intake to create a review task rather than approve a bill. TrekMail can supply the mailbox and permitted message access; another system must extract the document’s fields. Keeping intake separate from approval helps when a supplier resends a PDF or sends a corrected version.
You can pass emailed invoices into an external processing workflow through forwarding or API access. TrekMail provides the mailbox and authorized access to messages and attachments. A separate service or your own program handles document recognition, amount extraction, and creation of accounting records.
Define what counts as intake, extraction, and approval
Give each step a separate result. Intake means the relevant message or attachment has reached the chosen processing point. Extraction means another system has attempted to read fields from that document. Approval means the responsible person has checked what your business requires. The first two results should not silently be presented as the third.
For example, receiving an invoice PDF proves neither that it belongs to a current order nor that the amount was read correctly. Your integration can create a review task containing the source message and the extracted information. The person reviewing it should still be able to open the document and understand where the information came from.
Decide how incomplete cases will appear. A missing attachment, an unreadable image, and two conflicting versions need understandable descriptions. Do not replace an unknown field with a plausible value merely to make a record look complete. Route the case to the person who can examine the source or ask the supplier for clarification.
Keep the mailbox's role narrow in that description. It receives correspondence and provides the access you have authorized. The external processor's recognition, record creation, and error reporting need their own setup and verification. This makes it easier to identify which part needs attention when a message arrives correctly but no useful review task appears.
Gather documents in a clear place
A dedicated invoice address is useful. The integration then doesn't need to inspect a manager's entire correspondence or a general company mailbox.
If suppliers still use several addresses, select matching messages with conditions and forward copies to the intended destination. Conditional forwarding through email rules is available on Pro and Agency. You could combine a known sender's exact address with the subject. Test the conditions: the word “invoice” alone may also appear in a customer's question.
Follow the conditional forwarding guide. Keep the original correspondence during the initial rollout so you can compare processing results with it.
Forwarding does not recognize a file or verify that it is the correct invoice. It gathers incoming documents at a chosen point.
Connect an external processor
If your system has an email address for document intake, you can send suitable messages there using the agreed process. Processing capability depends on that system, so begin with one test document.
Another option uses the API. An external program gets authorized access to the mailbox, finds new messages, and retrieves the required attachments. TrekMail API access to message content requires Pro or Agency. Reading one selected mailbox is often enough for this task.
The processor then recognizes the PDF or image, extracts information, and creates a record or task in the destination system. Those steps are configured separately from TrekMail. The API overview describes the email access capabilities.
Decide when the external program checks email and how it reports errors. Connecting a mailbox does not automatically start the entire workflow for each new message.
Handle duplicates and unusual documents
A supplier may resend an invoice or provide a corrected version. The same document may also arrive through both forwarding and the original mailbox. The external system needs to distinguish these situations.
Keep a link between the source message, attachment, and created task. An employee can then open the original and understand why the item entered the queue.
Define the accepted formats first. If a message contains a link or archive instead of a PDF, the processor may need another step. Send these cases for manual review with a clear explanation.
Recognition results also need checking. One incorrect digit can change an amount or payment detail. Automatically transferring a file does not confirm the accounting information is correct.
Follow one document through repeated and corrected delivery
Use a harmless sample invoice and record the source message, attachment, and resulting review item. Check that the item leads back to the document you supplied. Then deliver the same sample again through the route you expect suppliers to use. The external process should handle that according to its documented duplicate policy, not assume that every new email is a new business bill.
Next, try a clearly corrected version. A repeat copy and a replacement with changed details are different cases. The reviewer needs enough information to distinguish them rather than seeing two identical-looking tasks with no source context. Decide that behavior with the processing system's owner before expanding to more suppliers.
Also interrupt one part of the test workflow in a controlled way. If retrieval succeeds but record creation fails, the follow-up should address that incomplete step. Keep the source correspondence while investigating so you can compare the document with the processing result. Connecting email alone does not establish how another program resumes work after an error.
Name the person who checks the exception queue and how they know a case is waiting. A technically successful transfer is of little use if unreadable or conflicting documents remain unattended. Begin with one destination, one known document type, and visible review responsibility; then broaden the flow when you can explain what happened to each sample.
Keep the pilot correspondence until it is reconciled
Don't delete messages immediately after the first successful run. First confirm that the destination record leads back to its source and another mailbox check does not create unnecessary tasks.
Introduce the real flow gradually once the path is tested. One address and one document type are enough to begin. Expansion is easier when you know where every invoice is and who handles cases automation could not process.
Use the API overview for message and attachment access. Choose and verify the external processor separately; TrekMail’s mailbox does not itself provide invoice OCR or accounting approval.