Reconciliation for tolling and mobility payments
The passage is the unit of reconciliation, not the trip. Astridex reconciles passage events through rating, posting, settlement, and deposit.
Tolling and mobility revenue moves through roadside and host systems, vehicle classification and rate tables, back-office account posting, invoice-by-mail and violation processing, interoperability settlement, merchant/acquirer settlement, and the bank — each owned by a different team, each accurate on its own records. The reconciliation problem is not only volume: it is that the full event-to-cash chain, from passage to deposit, is never owned end to end. Astridex reconciles passage events, rating and posting records, settlement files, payment-processor activity, and bank deposits at the cadence each source actually supports, grouping exceptions by root cause and routing each to the operational or finance owner with a complete evidence trail.
Where Astridex moves the needle
Payment & Settlement Reconciliation
Match payment-processor and gateway settlement files to posted payments, fees, refunds, and chargebacks — then tie the net deposit to the bank.
Explore →Bank Reconciliation
Astridex matches bank transactions to your ledger continuously — cash, card, and multi-entity accounts — with a reason attached to every item that does not match.
Explore →Revenue & Billing Reconciliation
Astridex reconciles what was billed against what was used or contracted, and what was billed against what hit the GL — surfacing unbilled usage and revenue drift continuously.
Explore →The reconciliation problem in tolling & mobility payments
Tolling and mobility revenue moves through roadside and host systems, vehicle classification and rate tables, back-office account posting, invoice-by-mail and violation processing, interoperability settlement, merchant/acquirer settlement, and the bank — each owned by a different team, each accurate on its own records. The reconciliation problem is not only volume: it is that the full event-to-cash chain, from passage to deposit, is never owned end to end. Astridex reconciles passage events, rating and posting records, settlement files, payment-processor activity, and bank deposits at the cadence each source actually supports, grouping exceptions by root cause and routing each to the operational or finance owner with a complete evidence trail.
The source-to-cash lifecycle
Passage / read event
RFID, transponder, or plate read at the roadside or host system.
Image review / classification
Vehicle classification and rate-table lookup, including discounts and exemptions.
Rating
The passage is rated against the applicable toll schedule.
Posting / invoice-by-mail
Rated passages post to an account, or route to invoice-by-mail or violation processing.
Payment / collection
Account payment, violation payment, or collection-agency remittance.
Settlement
Agency/interoperability settlement and merchant/acquirer settlement — reconciled separately.
Bank & GL
Settlement deposits hit the bank and post to the ERP/GL.
Sources that never agree
Each system reports accurately on its own records — the reconciliation lives in the gap between them.
Roadside / host systems
RFID/transponder reads, plate reads, and rejected or low-confidence reads. API or file ingestion.
Vehicle classification & rate tables
Discounts, exemptions, rate changes, and post-period adjustments. API or file ingestion.
Back-office account system
Account-holder transactions and postings. API or file ingestion.
Invoice-by-mail & violation systems
Plate/owner lookup, notice delivery, dispute and payment-plan workflow. Custom implementation — workflows are agency-specific.
Interoperability settlement files
Agency- and region-specific settlement, reconciled separately from merchant settlement. Custom implementation — rules differ by region and agreement; not abstracted into a generic hub.
Payment gateways & acquirers
Card/ACH merchant settlement, fees, refunds, reversals, and chargebacks. Native connector for major processors already in the Astridex integration catalog.
Lockbox & bank
Deposit records for tie-out to posted payments. API or file ingestion.
Reconciliation matrix
| Source · record key | Expected timing | Exception owner | Resolution / impact | |
|---|---|---|---|---|
| Passage-to-posting | Transponder/plate read ID | Same-day to T+2, source-dependent | Tolling operations — Passage rated but not posted to an account or invoice | Route to account posting or invoice-by-mail queue |
| Interoperability settlement | Agency settlement file reference | Per agency settlement cycle | Finance — settlement — Settlement total does not reconcile to underlying passage events | Root-cause by classification/rate variance or unposted event |
| Merchant settlement | Processor batch/deposit ID | Daily to T+2 | Finance — treasury — Deposit does not reconcile to posted payments, fees, refunds, chargebacks | Net and match; escalate unidentified deposits |
| Violation / collection remittance | Notice / collection account ID | Per remittance cycle | Violations operations — Remittance does not reconcile to the underlying notice balance | Route variance to violations team with evidence |
Where the money leaks
- Passage recorded but never rated — the read exists but doesn’t reach a rate table decision.
- Passage rated but not posted to an account or invoice.
- Account charges posted, then reversed, adjusted, or disputed without the reversal flowing back to the original event.
- Interoperability settlement that doesn’t reconcile to the underlying passage events.
- Merchant settlement or deposits that don’t reconcile to posted payments, fees, refunds, and chargebacks.
- Violation payments or collection-agency remittances that don’t reconcile to the underlying notice balance.
- Bad debt, collection recoveries, and post-period rate adjustments that never flow back to the original events.
Worked example: a passage-to-settlement variance
An interoperability settlement file for a given cycle totals $2,000 less than the sum of the underlying passage events Astridex has already rated and posted for that agency.
Astridex isolates the variance to a batch of passages later reclassified from a standard to a discounted rate after the original settlement ran — a post-period rate adjustment — and routes the evidence to the settlement owner with the specific passage IDs affected, rather than a single unexplained variance figure.
Outcomes finance teams see with Astridex
Across collections, payables, close, and procurement — measured on real customer workflows.
Sources we reconcile
Native connectors where they exist today; API or file ingestion, or a custom implementation, elsewhere — ask your Astridex contact for the current status on any system not listed.
Integrates with 500+ tools your team already uses — anything with an API.
Tolling & Mobility Payments: frequently asked questions
What counts as a "passage" for reconciliation purposes?
Astridex reconciles at the individual passage or transaction-event level — a single RFID or plate read — because most reconciliations here are naturally one-to-many or many-to-many once passages are grouped into charges, invoices, and settlements.
Does Astridex handle interoperability settlement the same way everywhere?
No — interoperability settlement rules differ by region and agreement, so Astridex reconciles each agency’s settlement files on their own terms rather than forcing them into one generic model.
Can Astridex reconcile daily?
Astridex reconciles at the cadence each source actually supports — some feeds are daily, others follow a settlement cycle. We do not promise universal daily reconciliation across every source.
How are violations and account payments reconciled differently?
Account payments post directly against a transponder account; violation payments and collection-agency remittances are reconciled against the underlying notice balance, which follows a different workflow and timing.
What is "merchant settlement" versus "interoperability settlement"?
Merchant settlement is your card/ACH processor paying out net of fees, refunds, and chargebacks; interoperability settlement is the inter-agency exchange for passages made on another agency’s network. Astridex reconciles them separately.
Does Astridex support public reporting or audit requirements?
Astridex produces the reconciliation evidence trail your finance and audit teams need; we don’t claim built-in public-reporting features beyond that evidence trail unless specifically scoped.
See tolling & mobility payments reconciliation on your data.
Connect your systems read-only and watch Astridex reconcile — with a reason on every exception.
Bring agentic finance to tolling & mobility payments.
See Astridex on your actual systems and volumes — deployed in days.