Case studies/Aptus AI
CASE 05Invoice and autofattura automation
180+→90%+

Aptus AI’s accountant keyed in 180+ supplier invoices a month by hand. Now nine in ten reach Fatture in Cloud untouched.

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.

One invoice, step by stepLive
Client
Aptus AI S.r.l.AI company, Pisa, Italy
Problem
180+ invoices a month, keyed by handEvery non-EU one rebuilt as an autofattura
Built with
n8n, on Aptus’s own instanceFatture in Cloud, Banca d’Italia rates, Airtop, OpenAI
Live
Since November 2025Discovery call mid-2025
Sponsor
Andrea TeseiCo-Founder and CEO, with Sina Farhang Doust and Tommaso Pagotto
90%+
Invoices untouched

Read, routed and registered in Fatture in Cloud with nobody keying them in.

180+
Invoices a month

Aptus’s own count for the month before the project. Typical volume ran 100 to 200.

25h
Accountant time a quarter

Once spent collecting, converting and keying invoices. Now spent on review and sending.

5min
Inbox check

Gmail is read every 5 minutes, and a browser agent visits 3 vendor portals each month.

01
The challenge

180+ invoices a month arrived three ways, and every non-EU one was rebuilt by hand.

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.

Scattered intake

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.

Autofattura rework

Every non-EU invoice built twice

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.

One-person bottleneck

Volume and workload moved together

A single accountant keyed every invoice into Fatture in Cloud, so each new supplier added hours.

02
The solution

One digital mailroom takes in every invoice and sends it down the right tax path.

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.

Collect
GmailThe purchasing inbox, checked every 5 minutes. The pipeline saves attachments and prints invoices written in the email body to PDF.
Vendor portalsA monthly Airtop browser agent logs into 3 portals that never send an invoice by email.
Drive drop folderAnything else, dropped in by hand, enters the same pipeline.

n8n On Aptus’s own instance

ReadOpenAI pulls the supplier, address, VAT number, date and amount from every invoice.
RouteDecides EU or non-EU from the supplier address, and finds the supplier in Fatture in Cloud.
ConvertConverts non-EU amounts at the official Banca d’Italia rate, then rebuilds each invoice as a TD17 autofattura.
3ways in
2tax paths
1human check
Register
Fatture in CloudRegistered through the API, with the original PDF attached to every autofattura.
Drive, Sheets, GmailEach invoice is filed in a year and month folder, logged in a Sheets index and labelled in Gmail.
SlackIf VAT or bank details are missing, the pipeline asks for them. The answer goes back into the index and the invoice carries on.
The pipeline does the keyingThe pipeline collects, reads, classifies, converts and files each invoice without anyone opening it.
The accountant keeps the last wordEvery autofattura waits for a review before it is sent to SDI, the Italian tax exchange.
Stackn8nGmailGoogle DriveGoogle SheetsFatture in Cloud APIBanca d’Italia daily ratesAirtopOpenAISlack
03
Deep dive

The official exchange rate isn’t published until the day closes, so the system waits.

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.

Pick the invoice date

See which day’s rate the request asks for, and when the autofattura is created.

The live query, from the delivered n8n workflow
GET tassidicambio.bancaditalia.it/terzevalute-wf-web/rest/v1.0/dailyRates
{
  "referenceDate": "{{ invoice.date + offset_days }}",
  "baseCurrencyIsoCode": "USD",
  "currencyIsoCode": "EUR"
}
Trimmed to the three parameters that matter. The reference date moves past weekends and holidays, so every conversion uses a rate Banca d’Italia has actually published.

Request lightly trimmed from the delivered workflow. The week picker shows the weekend rule; Italian public holidays roll forward the same way.

04
The obstacle

Most supplier records were incomplete, and that caused the mismatches.

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.

170+

Real invoices run in bulk before go-live. The AI read them correctly. The mismatches came from the supplier list it matched them against.

→ The fix is in the source: Aptus is cleaning the supplier records.
05
The results

90%+ of invoices now file themselves, and the accountant only reviews and sends.

90%+
Processed untouched

From manual upload of every invoice to automated collection, conversion and registration.

180+ / mo
Invoices handled

Collected, converted and registered, across email, Drive and three vendor portals.

25 h / qtr
Accountant time

Once spent keying and rebuilding invoices. Now spent on review and sending only.

Mid-2025

Discovery call

Aptus counts more than 180 invoices in the previous month.

Testing

Bulk runs

Runs of 170+ real invoices show the rate timing problem and the gaps in supplier records.

Nov 2025

Live

Every invoice now enters through the mailroom.

At close

Handover

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.

06
Handover

Aptus owns the pipeline, which runs on Aptus’s own n8n with full documentation.

Nothing sits on an Ovidius server. Aptus received the workflows, the documentation and a recorded walkthrough at close.

Infrastructure

Aptus’s own n8n instance

Every workflow, credential and log stays inside Aptus’s account.

Documentation

Full technical documentation

Each workflow, the routing rules and the Banca d’Italia query, written down.

Training

A recorded walkthrough

Whoever takes over the mailroom can replay the walkthrough to learn how it works.

How many supplier invoices does your accountant key in each month?

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.

Book a Discovery Call30 minutes with a senior partner. You bring the process.