Three ways in, one inbox read by hand
Invoices came as attachments, as text in the email body, or sat in vendor portals that send no notification at all.
Aptus AI is an AI company in Pisa with 623 suppliers on its books, many of them outside the EU. Italian rules require every non-EU invoice to be rebuilt as an autofattura, a self-invoice that the buyer issues. The pipeline Ovidius built collects each invoice wherever it arrives, picks the tax path and registers it. The accountant then does one review before anything goes to SDI, the Italian tax exchange. It has run since November 2025.
Read, routed and registered in Fatture in Cloud with nobody keying them in.
Aptus’s own count for the month before the project. Typical volume ran 100 to 200.
Once spent collecting, converting and keying invoices. Now spent on review and sending.
Gmail is read every 5 minutes, and a browser agent visits 3 vendor portals each month.
In the month before the project, Aptus’s accountant uploaded more than 180 invoices by hand. A typical month ran 100 to 200. Aptus buys software and services from vendors in Europe, North America, Asia and Australia. Each non-EU invoice had to be rebuilt as an Italian autofattura before it could reach the tax system.
Invoices came as attachments, as text in the email body, or sat in vendor portals that send no notification at all.
For each one, the accountant looked up the Banca d’Italia rate, converted every amount to EUR, then created a new TD17 document, the e-invoice type for services bought from abroad.
A single accountant keyed every invoice into Fatture in Cloud, so each new supplier added hours.
However an invoice arrives, one AI step reads it, matches the supplier and sends it down the EU or non-EU path. The pipeline asks a person on Slack only when data is missing.
Early test runs converted Pinecone’s USD invoices at the latest available rate, and the totals drifted from the accountant’s figures. Banca d’Italia publishes each day’s rate after the day closes. Autofatture now wait a day for it, and weekends and holidays roll to the next business day.
See which day’s rate the request asks for, and when the autofattura is created.
GET tassidicambio.bancaditalia.it/terzevalute-wf-web/rest/v1.0/dailyRates
{
"referenceDate": "{{ invoice.date + offset_days }}",
"baseCurrencyIsoCode": "USD",
"currencyIsoCode": "EUR"
}
Request lightly trimmed from the delivered workflow. The week picker shows the weekend rule; Italian public holidays roll forward the same way.
Bulk runs of 170+ real invoices kept matching invoices to the wrong supplier. An audit of Aptus’s supplier list found most records missing key fields. That meant an invoice read correctly could still match the wrong supplier, or none. Aptus is now cleaning that source data so every supplier matches first time.
Real invoices run in bulk before go-live. The AI read them correctly. The mismatches came from the supplier list it matched them against.
From manual upload of every invoice to automated collection, conversion and registration.
Collected, converted and registered, across email, Drive and three vendor portals.
Once spent keying and rebuilding invoices. Now spent on review and sending only.
Aptus counts more than 180 invoices in the previous month.
Runs of 170+ real invoices show the rate timing problem and the gaps in supplier records.
Every invoice now enters through the mailroom.
Documentation and a recorded walkthrough, on Aptus’s own n8n.
Since go-live in November 2025, the untouched rate and the accountant hours have been reported, not measured by the system. Baseline volume is Aptus’s own monthly count from the discovery call: more than 180 invoices in the month before the project, typically 100 to 200. The 80% attachment share is Aptus’s estimate from the same call.
Nothing sits on an Ovidius server. Aptus received the workflows, the documentation and a recorded walkthrough at close.
Every workflow, credential and log stays inside Aptus’s account.
Each workflow, the routing rules and the Banca d’Italia query, written down.
Whoever takes over the mailroom can replay the walkthrough to learn how it works.
Bring the count and your accounting system. In a discovery call we map where your invoices arrive, which tax paths they take, and which steps a pipeline can run. See how it works on AI invoice automation.
We use Google Analytics cookies to see which pages visitors read, so we can improve the site. Accept to allow them or reject to keep them off. Privacy policy