ChargeBack comparison
Compare reimbursement approaches before you change driver policy.
The comparison tool will contrast settlement models and operational trade-offs. It is not interactive on this page yet.
In development
What is available on this page today
The interactive comparison is not built yet. This page explains the reimbursement decisions it is meant to structure so finance, HR, and fleet can prepare policy questions first.
What the comparison is meant to help with
Contrasting policy models
Compare flat allowances, tariff-based reimbursement, and settled energy costs without mixing the definitions.
Clarifying employer and driver split
See who carries which cost under each model and where exceptions usually appear.
Understanding evidence needs
Identify the session and tariff evidence finance needs before a model can run cleanly in payroll.
Anticipating change impact
Spot operational changes for drivers and administrators before a policy switch.
Where to go for reimbursement evaluation now
Until the comparison tool ships, evaluate ChargeBack through the reimbursement solution page or a specialist session with your current policy and payroll constraints.
Prefer to compare models with a specialist
Bring your current reimbursement rules and payroll constraints to a demo. A specialist can map them to how ChargeBack settles and reports today.
Schedule a demoReimbursement comparisons fail when models are undefined
Teams often compare “home charging reimbursement” options without agreeing what is being settled: a fixed allowance, a tariff table, or actual session energy. The ChargeBack comparison view is being built to keep those models distinct while showing operational trade-offs.
This page does not run side-by-side calculators and does not display simulated scores or winners. There are no comparison controls here. When the Phase 2 comparison tool ships, it will replace this landing page at the same URL.
Until then, read the reimbursement solution page for the ChargeBack operating model and bring your current policy to a demo. That is the fastest way to see whether a change is a finance configuration issue, a driver-experience issue, or both.