NDX Fleet Automation Live
Upload the notice. NDX Fleet Automation reads the plate, the date and time of the violation, the amount and the issuing authority out of the document itself, finds the rental contract that was active at that exact moment, and prepares the notification letter for your renter.
Built for any rental or fleet business — whatever you rent out.
What it reads: the digital PDF issued by the authority, as it arrives by PEC or from an authority portal, up to 10 MB. A photograph or a paper scan has no text inside it to read, so the application refuses it with a clear message instead of guessing For those, ask the issuing authority for the digital copy: there is no screen for typing a notice in.
One notice, four steps
Illustrative exampleUpload the digital PDF
Up to 10 MB. Nothing to type in first.
Fields read from the document's own text
Matched inside the violation's time window
Rental start ≤ violation time ≤ rental end.
Renter notification prepared
Generated from the matched contract, ready to send.
Input
The reader works on the text layer inside the file. That is what makes it exact, deterministic and free of any per-document reading cost, and it is also what draws a hard line around the formats it accepts. We would rather tell you where that line is than have you find it after signing up.
For a notice that only exists on paper, ask the issuing authority for the digital copy. There is no image-reading feature on any plan and no date on which one arrives, and there is no screen for typing a notice in — a paper-only notice is handled outside the application.
Why this exists
A notice arrives, and from that moment the work is the same every time: read it, identify the vehicle, find the contract that covered that minute, write to the renter. It is repetitive, it is time-boxed, and getting it wrong is worse than being slow.
30 days to identify the driver — or the rental company pays the fine itself
Every design decision in the product follows from that sentence. Nothing is allowed to block your work, and nothing is allowed to guess at who was driving.
The plate identifies the vehicle, never the driver. The answer is a time-window question: which contract covered this plate at 14:22 on that date. That is the one thing a spreadsheet is worst at doing reliably, at volume, under a deadline.
The contract says AB-123-CD, the import file says AB123CD, and the notice says something else again. Compared as raw text, one vehicle becomes three. Plates are therefore canonicalised before anything is compared — and confusable characters are deliberately left alone, because European plates really do mix O with 0 and I with 1.
Sending a demand to someone who was not driving is not a clerical error you apologise for. It is a legal and reputational problem for the rental company, which is why anything ambiguous is handed to a person with the original document attached.
How it works
No integration project, no template to configure before the first notice. You bring the PDFs; the product brings the reading, the matching and the letter.
Drag in the notice as it arrived, up to 10 MB. There is nothing to fill in first, and nothing to convert afterwards. The upload refuses any file that is not the digital PDF, and says why.
Fine number, plate, date and time of the violation, amount and issuing authority are extracted from the PDF's text layer. The reader prefers values sitting next to a language-specific label (“Targa:”, “Matrícula:”) over a bare pattern match, and reports a field as unreadable rather than picking between candidates.
The plate is canonicalised, then tested against your rental records inside the violation's time window: rental start ≤ violation time ≤ rental end. One clean match, or it goes to review.
The notification documents are generated from the matched contract, so recovery begins the day the notice arrives rather than weeks later, and every figure traces back to the original notice.
Contracts and vehicles are imported from a CSV file. The import reads your column headings to work out which column holds the plate and which hold the start and end dates, and normalises the plates on the way in, so the matching has clean data to work with on day one.
Features
Every point below is behaviour you can reproduce in the application after signing up.
Extraction runs on the text the document already carries, inside our own deployment. There is no image-conversion step, no third-party AI service in the path and no per-document reading cost that grows with your volume — which is part of why the plans are priced per fine allowance rather than per page read.
Italian, Spanish, English and French. Labels, month names and amount formats are handled in each, including the Italian habit of writing “EURO 150,00”. You never tell the product which language the notice is in.
AB-123-CD, AB123CD and “AB 123 CD” become one value before anything is compared. Confusable characters are not silently “corrected”: a plate one character away from a known vehicle is surfaced for review instead.
The plate finds the vehicle; the window finds the contract. Two contracts overlapping the violation instant is an ambiguity, not a coin toss, and it is routed to a person rather than resolved alphabetically or by whichever record was created first.
The notification documents come out of the matched rental record, ready to send, with every figure traceable to the notice. No retyping between two screens, which is where digits drift.
Overlapping contracts, no contract at all, a near-miss plate, an unreadable field: each is recorded and queued for review with the original document attached, so your team decides with the evidence in front of them.
Pricing
Monthly subscription, billed per company. Every plan starts with a 14-day free trial that begins at sign-up — no card required, because the trial is enforced by the application and not by a payment authorisation.
Up to 50 vehicles
€49 / month
Includes 50 fines a month, and covers up to 3 users.
Up to 300 vehicles
€149 / month
Includes 300 fines a month, and covers up to 10 users.
Up to 2,000 vehicles
€499 / month
Includes 2,000 fines a month, and covers up to 50 users.
Up to 6,000 vehicles
€999 / month
Includes 6,000 fines a month, and covers up to 150 users.
For groups, franchise networks and multi-country operators running vehicles and fines in more than one country. There is no published price: the agreement is scoped with you, and the terms we commit to are the ones written into it.
Exceeding the fine allowance never blocks your work. Additional notices are accepted, processed and counted, then billed at €1.00 each. The running total is always visible in your dashboard, and you are warned at 80% and again at 100% of the allowance. Every notice a customer sends back to manual handling is a deadline you have to meet by hand, and rental companies have 30 days to identify the driver or pay the fine themselves.
The €1.00 rate is set above the per-fine rate of every tier, so once your volume reaches the next plan up, moving up costs less than the extra fines it replaces — the dashboard says so at the moment you cross the allowance.
Prices are in euros and exclude VAT. Subscription billing is handled by Stripe; cancel at any time. Users and vehicle counts are stated as what a plan covers — only the monthly fine allowance is measured. Compare all plans in detail.
Limits
Stated plainly, because a customer who signs up on a promise the product cannot keep will ask for a refund — and will be right to.
Questions
No. The reader works on the text layer of a digital PDF. A photograph, a scan and a screenshot contain no text layer, so the upload refuses them with a clear message instead of guessing. That is a deliberate limit, not an unfinished feature: the reading is exact precisely because it never has to interpret a picture.
No — and the app tells you so plainly. A scanned PDF is an image wrapped in a PDF container, so there is no text for the reader to extract. Upload the digital PDF the authority issued instead; there is no way to type the notice in.
Then it does not guess. Two contracts overlapping the violation instant is an ambiguity, and the notice goes to the review queue with the original document attached. The same applies when no contract matches at all, or when a plate is one character away from a known vehicle — a near miss is worth a human look, not an automatic correction.
Yes. The product is built for rental and fleet businesses of any kind, and matching uses the plate and the rental window rather than a vehicle category. In Italy cars, vans, scooters, e-bikes and kick-scooters all carry plates, so all of them can be registered and matched. If it has a plate, a contract and a rental window, it works the same way.
The 14 days start when you sign up and require no card. When the trial ends you choose a plan to keep processing notices; until you do, nothing is charged, because no payment method was ever taken. Subscription billing afterwards is handled by Stripe, and you can cancel at any time.
Yes. Contracts and vehicles are imported from a CSV file. The import reads your column headings to work out which column is the plate and which are the start and end dates, and plates are normalised on the way in, so a contract typed as AB-123-CD and a notice that says AB123CD resolve to the same vehicle.
On infrastructure NDX operates. Notices and generated letters contain names, addresses, tax codes and plates, so they are stored privately outside the web root and every read goes through an authorised route rather than a public link. Records are separated by company at the query level, and the database is not reachable from the internet.
Sign up, upload one digital PDF, and see the match and the letter for yourself. Fourteen days, no card, no implementation project.