Mobility

# How to integrate fine lookups into a fleet operation

When to look up each plate, how to assign each fine to the right driver and what to store so that a dispute is settled with data rather than memory.

![](/img/autores/enrique-orione/photo-240.2526eefb2549.webp)By [Enrique Orione](https://apinitro.com/en/authors/enrique-orione/)September 16, 2026

![An empty fleet yard at blue hour with wet parking lines and a warm light](/img/articulos/integrar-multas-en-flota/hero-1200.29378b3134dc.webp)

A fleet does not lose money on the fine itself but on discovering it late: once the voluntary-payment discount has expired, once the driver who was at the wheel no longer works for the company, or once the fine blocks a licence renewal. Integrating the plate lookup into the process, rather than into a spreadsheet someone checks when they can, changes that outcome. This guide describes the model that works for delivery fleets, rent-a-cars, school transport and service companies, with any of the fine APIs for [Argentina](https://apinitro.com/en/apis/traffic-fines-argentina/), [Brazil](https://apinitro.com/en/apis/traffic-fines-brazil/), [Chile](https://apinitro.com/en/apis/traffic-fines-chile/), [Mexico](https://apinitro.com/en/apis/traffic-fines-mexico/) and [Uruguay](https://apinitro.com/en/apis/traffic-fines-uruguay/).

## Which events trigger a lookup

The plate lookup is best scheduled by event and not only by calendar. There are four moments in the life of a unit when an unknown fine costs more than at any other: onboarding into the fleet, the return of a rental or the close of a contract with a driver, every licence or technical inspection expiry, and the disposal or sale of the unit. At each one, the lookup result has a clear recipient and a deadline to act.

-   Onboarding: the unit enters with a known history; whatever appears later belongs to the operation.
-   Return or contract close: the fine is charged to whoever was driving while the trip record exists.
-   Licence or inspection expiry: a forgotten fine does not block the procedure.
-   Disposal or sale: the buyer receives the unit with its debts settled and no surprises.

## The monthly batch

Beyond the events, a monthly batch over the whole fleet captures the fines that reach the sources late, above all speed-camera fines, which can appear weeks after the fact. The batch is scheduled at a low-load hour, sent in parts and reconciled against the previous result: new items are assigned, items that disappeared are marked paid or voided and unchanged items generate no work. The guide on [integrating asynchronous APIs](https://apinitro.com/en/articles/asynchronous-api-retries-without-duplicate-work/) explains how to retry without duplicating lookups.

## Assigning each fine to the right driver

The key data point is not the fine but the date and time of the event: with them you match the trip log, the shift or the rental contract and identify who was driving. That match must be stored together with the source result, because a driver’s dispute months later is settled by showing the record, not by rebuilding it. Fines that cannot be assigned go to a review queue with the discount expiry date, so that someone decides before the amount rises.

The API response splits the result by source and shows whether any failed to answer: a source with no answer is queried again, never interpreted as an absence of fines. The [vehicle lookup quality](https://apinitro.com/en/articles/vehicle-data-quality/) guide details that handling.

## What to store

-   The complete result per source, with the date and time of the lookup.
-   The authority, fine number, event date, amount and status, exactly as the source publishes them.
-   The driver assignment with the record that justifies it.
-   The decisions: paid, defence filed, transferred to the driver, unassigned.

## What to look for in the results

With three months of lookups, the fleet has its own indicators: which units accumulate fines, in which jurisdictions, of which type and with what delay between the event and its appearance at the source. That delay defines how far back each batch must look and how much margin remains for voluntary payment. The per-jurisdiction articles, such as the one on [Buenos Aires province](https://apinitro.com/en/articles/traffic-fines-buenos-aires-province/), publish aggregated data that helps compare with your own.

## How to start

1.  Choose the operational events that trigger the lookup and the day of the monthly batch.
2.  Define where the result is stored and who assigns ownerless fines.
3.  Integrate the POST per plate and the result by status or webhook.
4.  Measure the delay between event and source during the first quarter and adjust the batch.

## Sources and further reading

-   [Ley Nacional de Tránsito 24.449 — texto actualizado](https://www.argentina.gob.ar/normativa/nacional/ley-24449-818/texto)
-   [Agencia Nacional de Seguridad Vial — Consulta nacional de infracciones](https://consultainfracciones.seguridadvial.gob.ar/)

Related API

## [Argentina traffic fines API](https://apinitro.com/en/apis/traffic-fines-argentina/)

Bring vehicle fine checks into fleet operations, vehicle transactions and document review workflows.

[Ask about this API](https://apinitro.com/en/contact/?api=ar.mobility.traffic-fines&ref=article:integrar-multas-en-flota)

## Related articles

[

Integrations

## Asynchronous APIs: retry without duplicating work

A connection can fail after work has already started. Designing around the operation makes recovery clearer for users and integrations.

Read article ↗](https://apinitro.com/en/articles/asynchronous-api-retries-without-duplicate-work/)

[

Mobility

## How to assess the quality of a vehicle lookup

A useful vehicle lookup explains what was observed, where and when. These questions help teams turn records into clear product decisions.

Read article ↗](https://apinitro.com/en/articles/vehicle-data-quality/)

[![](/img/articulos/ar-traffic-fines-ar-b/hero-640.e7b8a039b11b.webp)

Mobility

## Traffic fines in Buenos Aires Province: what the API returns and what the data shows

Two layers of authorities, one plate: how to look up provincial and municipal fines through the API and what a year of our data shows.

Read article ↗](https://apinitro.com/en/articles/traffic-fines-buenos-aires-province/)

[← All articles](https://apinitro.com/en/articles/)
