Transport Railway

Reimbursement Platform: Passenger Claims Automation

The problem

Reimbursement platform workflow interface

A transport operator’s claims team processed every passenger reimbursement manually: intake of the form submission, validation against travel data APIs, applying decision logic, routing payment to bank or voucher systems, and notifying the passenger. Each claim touched four or five people. The team couldn’t handle peak demand.

What we built

An end-to-end agentic workflow:

  1. Form submission — structured intake via web form
  2. Automated validation — checks against Silverrail and Trafikverket APIs to verify travel data, delays, and eligibility
  3. Decision engine — applies reimbursement rules, handles edge cases (partial journeys, combined tickets, delay chains)
  4. Payment routing — outputs to bank transfer or voucher systems based on passenger preference
  5. Notification — automated passenger notification at each status change

The system generates a full audit trail automatically for compliance.

The accelerator architecture

The core pattern — claim intake → external API validation → decision engine → payment/fulfilment routing → notification — is reusable. If your process involves: receiving a request, validating it against external data, making a decision, and routing an output to a payment or fulfilment system, we’ve already built this. Deployment time for a similar system is materially shorter the second time.

Outcome

  • ~60% FTE reduction in claims handling team (staff redeployed to customer-facing roles)
  • Manual data entry errors eliminated by automated API sync
  • Claim processing time reduced from hours to minutes
  • Integrated with Silverrail, Trafikverket, accounting system, bank and voucher payment rails