Fare and payment evidence

Finance Operator records fare components against the booking they concern. The charge type distinguishes a Base Fare from a Waiting Time Charge, Toll or other supported component. Keep the provider event identifier with the amount, currency and occurrence time so a colleague can locate the supporting event when a rider questions a charge.

Draft records give Finance Operator a place to prepare the evidence for review. Approved, Invoiced and Paid describe later evidence states. The team needs a clear operating rule for each state and the external confirmation that supports it. A completed trip supplies journey context; the payment provider supplies the evidence of a payment outcome.

• Explain the component. Choose the charge type that describes the amount and attach it to the correct booking. Keep separate components readable when the rider asks about a fare breakdown.
• Review before advancing. Finance Operator checks the provider event and the applicable currency convention before approving the evidence. Resolve a mismatched booking or unsupported amount before changing its state.
• Follow the payment outcome. Use Invoiced and Paid only when the connected billing or payment evidence supports that result. Retain the provider identifier for later reconciliation or correction.

Agree where fares are calculated and how the approved result reaches the desk. Fare calculation and payment processing are connections to set up with your chosen providers. Decide how Base Fare, Surge Fare and extra components will be represented so staff can explain the total without entering the same provider event again.

Set the meaning of the recorded currency and the USD amount before importing historical evidence. Do not combine unlike currencies in a report without an agreed conversion basis. Define who reviews a draft component, what supports a Paid state and how a voided draft remains identifiable. Use the provider’s own records when investigating refunds or payment reversals.

A completed airport ride has a Base Fare and a Toll. Finance Operator compares both components with the provider evidence and the linked booking. A toll event arrives again during a retry. Search the existing provider identifier before entering another component, and check whether the event details agree with the recorded amount and currency.

Later, the rider challenges a Waiting Time Charge. Finance Operator examines its fare breakdown evidence and asks Trip Coordinator for the relevant trip events. The reviewer should be able to explain the charge from the retained records. Any provider adjustment follows the agreed external process and its confirmation, while the original booking and ride evidence remain available for inspection.

• Draft fare evidence — Charge components awaiting review with their booking, amount and provider event identifier.
• Payment follow-up — Approved, Invoiced and Paid evidence for tracing the latest recorded outcome.

Rehearse fare evidence to payment review with a provider event and a disputed charge. Review integrations before loading live payment evidence.