Toll back-office system for a US government programme

A tolling vendor needed the back-office system for a US government tolling programme. Every trip has to be recorded, matched to a vehicle and a driver, and turned into an accurate invoice, with a history that stands up to a dispute.

A microservices back office that integrates with multiple US government services for vehicle and driver verification, and handles invoicing, trip tracking and trip history. Batch workloads run on Spring Batch; services are built on Java and Spring Boot with an Angular front end, MS SQL for storage, and Docker on Azure.

We delivered the system module by module rather than as a single big-bang release. Trip tracking, vehicle and driver verification, invoicing and trip history each went to production as a self-contained service, so the programme could take each capability live, prove it under real traffic and build the next one on top of it.

As the programme grew, we scaled the platform to handle millions of trip records. High-volume ingestion and verification run as Spring Batch jobs that process records in parallel and can restart from the last checkpoint, so a failed run resumes rather than starting over. The same pipeline rolls each account's verified trips into its monthly invoice, generated on schedule for the whole customer base.

The system runs in production at state scale, processing millions of trip records and generating monthly invoices for the programme's customers. Each trip carries its full history, from capture through verification to the invoice line, so a disputed charge can be traced end to end. This is a capability reference: the client has not published further metrics, so we do not quote any.