Incoming invoices, processed without retyping.
Invoices arrive as eRačun e-invoices, PDFs and scans. We build an automation that reads them, checks them against rules you set and enters them into the system you already use. Your team handles only the exceptions.
Where the time goes today
- Someone opens every email and saves the attachment to the right folder.
- Supplier, amounts, VAT and due date are typed in again by hand.
- Each invoice is compared with its order or contract by eye.
- Approvals are chased by email, and invoices wait in someone's inbox.
- Typing mistakes surface later, at reconciliation or month end.
What the automation takes over
- Invoices are collected from the mailbox or a shared folder as they arrive.
- AI reads the supplier, tax number, amounts, lines and dates.
- Your rules check the data, for example a known supplier, a matching order and correct totals.
- Invoices that pass go into your system; the rest go to a person, with the reason attached.
- Every invoice keeps a record of what was read, what was checked and who approved it.
How it works
Collect
Invoices are picked up from the e-invoicing service they arrive through, a mailbox, or a SharePoint or OneDrive folder.
Read
An eRačun is read straight from its structured data. For PDFs and scans, AI pulls out the fields you need.
Check
Rules you set decide whether an invoice can go through, and send everything else to a person.
Enter
The data goes into your accounting or ERP system, through its API or, where it has none, through a software robot.
Example: one supplier invoice, from inbox to ledger
A typical setup for a small company that receives invoices by email and keeps its books in an accounting program without an API.
- Supplier
- Sample Supplies d.o.o.Known supplier
- OIB
- 12345678901Matches the register
- Order no.
- PO-0417Order found
- Issued
- 3 Nov 2026
- Due
- 3 Dec 2026
- Printer toner, 4 pcs160.00
- Copy paper A4, 20 reams100.00
- Net
- 260.00
- VAT 25%
- 65.00
- Total (EUR)
- Totals add up325.00
The invoice arrives
A supplier emails a PDF to the invoices mailbox. The flow saves it to the archive folder and starts.
The fields are read
AI extracts the supplier, tax number, invoice number, dates, net amount, VAT and total.
The checks run
The supplier is in the register, the order number exists, the totals add up and the invoice is not a duplicate.
Someone approves
The person responsible for that cost gets an approval request in Teams or by email, with the invoice attached.
It is entered
A software robot enters the approved invoice into the accounting program, and the record is saved next to the PDF.
An illustrative example of how such a workflow is usually set up, not a description of a client project. Your steps, checks and approvals are agreed with you during the analysis.
Built with tools you may already have
If you use Microsoft 365, Power Automate is usually the natural choice. Where an older program has no API, UiPath works through its screens, and n8n suits teams that want to host it themselves. We choose after the analysis, based on what you already run.
- Power Automate (opens in a new tab)
Collects invoices from the mailbox or SharePoint, runs the checks and moves each one along.
- Azure AI Document Intelligence (opens in a new tab)
Reads the supplier, amounts and lines from PDFs and scans, with a model built for invoices.
- Microsoft Teams (opens in a new tab)
Where the person responsible for a cost approves or rejects the invoice, without leaving the chat.
- UiPath (opens in a new tab)
Enters approved invoices into accounting programs that have no API, through their own screens.
- n8n (opens in a new tab)
The same flow on a server you host yourself, for teams that want to keep it in-house.
- OpenAI (opens in a new tab)
Handles the unusual invoices a fixed model misreads, such as handwritten notes or odd layouts.
Common questions
Do we have to change our accounting software?
No. The automation works with the system you already use, through its API where it has one and through a software robot where it does not.
What happens to an invoice the automation cannot read reliably?
You decide that when we design the flow. Usually it goes to a person for review, with the reason it was stopped.
What does Fiskalizacija 2.0 change for incoming invoices?
Since 1 January 2026, invoices between Croatian VAT payers are exchanged as eRačun, a structured electronic invoice rather than a PDF or an email attachment. Businesses outside the VAT system have to receive eRačun in 2026 and start issuing it on 1 January 2027. Porezna uprava's guide is the authority on the details.
Do we still need this if our invoices arrive as eRačun?
An eRačun saves the reading, not the rest. It still has to be checked against the order, approved and entered into your books. Invoices from suppliers abroad fall outside the obligation and can still arrive as PDFs or on paper, so one flow handles both.
How long does it take?
A quick pilot takes 1–3 weeks and a simple implementation 2–6 weeks. Larger projects are developed iteratively.
Background on the e-invoicing phases and what to check before 2027: Fiskalizacija 2.0: e-invoicing and preparing for 2027
Want to see where your time actually goes?
Send us the process that holds you back most. We will tell you whether automating it is worth doing, and how long it would take.