Automatic processing of incoming invoicessample project
Invoices arriving by e-mail are read and checked against the order. Matching ones are posted to the ERP on their own, differences go to accounting for approval, and duplicates are caught.
Approval requestPower Automate · Outlook
Flow log
- Invoice arrived by e-mail
- PDF read
- Checked against the order
- Accounting approval (if different)
- Posted to ERP or returned
Still doing this by hand?Set this up in your company
- Stack
- Power Automate, Outlook, AI Builder, Logo / Mikro ERP
This is a sample flow, not real client work. The model shows how such a system works, and the companies and amounts in it are samples too.
Problem
Accounting teams download supplier invoices from e-mail, open them one by one, compare them with the order and type them into the ERP. Differences slip through and the same invoice can be posted twice.
Solution
- Invoice attachments arriving at a mailbox are picked up and read: supplier, invoice number, amount, due date.
- The data is checked against the matching order, and invoices already posted are caught.
- Matching invoices are posted to the ERP without waiting for approval. When there is a difference, the accountant gets an approval card that shows it.
- Returned invoices trigger an e-mail to the supplier with the reason. Every step is recorded.
How it would work in your company
- The mailbox, the fields to read and the matching rules (for example, whether tiny rounding differences can be posted without approval) follow the way you work.
- For invoices that arrive as Turkish e-invoices, the XML file can be read instead of the PDF. The data is already structured there, so the result is more reliable.
- Posting follows the route your ERP (Logo, Mikro, Netsis) offers: its official service, the database or an import file.
- You get a short walkthrough video at handover, and fixes are free for the first 30 days.
To look inside a Turkish e-invoice XML file: e-invoice XML viewer.