Implementing fuel software means moving live tax tables, open loads, and customer balances while the trucks keep delivering. A generic onboarding checklist misses the parts that hurt. This guide covers the standard steps and the four fuel-specific traps that turn a clean switch into a three-month cleanup.
The standard steps
Every implementation runs the same arc: configure the system to how you operate, import your data, connect it to your POS and fuel systems, train the team, and cut over. The data import carries the most weight. You typically bring over customers and vendors, open balances, the pricebook and products, tax setup, and the historical detail audits will ask for. Plan the export from the old system early.
The four fuel-specific traps
1. Tax tables that change under you. Many states adjust motor fuel rates on January 1 and July 1: EIA counted 26 states that changed gasoline taxes between the start of 2025 and the start of 2026. Florida moved its state motor fuel rate from 21.5 to 22 cents per gallon on January 1, 2026, and Illinois indexes its rate to CPI every July 1 (a 2.68% bump for July 2026). Time your go-live so you load one rate set, and pull the current figures from each state bulletin rather than copying last year's table. Our state fuel tax overview lists where to look.
2. Open BOLs mid-cycle. On cutover day you will have loads lifted at the rack under the old system that get invoiced under the new one. Decide in advance which system owns each in-transit BOL, and keep a one-page list of them. Orphaned loads are the most common source of missing gallons in month one.
3. The NAXML feed cutover. If stores send POS data through Conexxus NAXML files, repoint each feed on a planned date and capture one day of data in both systems so you can prove the new feed matches the old.
4. The first month-end. Reconcile your first close against the old system line by line: gallons by tax jurisdiction, AR aging, and fuel margin. Differences you catch in month one are corrections; differences you find in month four are amended tax returns. This is the point where vendor support matters most, and it is the part FastDragon staffs with its own onboarding team (you can price the full setup on the pricing page first).
The go-live checklist
- Cut over at a month-end, after returns for the prior period are filed.
- Freeze the pricebook and tax tables a few days out, then load final versions once.
- Spot-check migrated balances against the old system before invoicing from the new one.
- Train the team on live screens before day one, with your own customers and products loaded.
- Keep the old system readable until the first close reconciles.
This is the same discipline as a smart switch: preparation does the heavy lifting.
What to expect from the vendor
A written plan with dates, help with migration and configuration, training, and support staff who can talk rack pricing and tax jurisdictions without a translator. Two questions sort vendors fast: who answers the phone in week two, and has that person ever closed a fuel month.
Frequently asked
How long does it take to implement fuel jobber software?
For a single-entity jobber with clean data, plan on roughly six weeks; cloud vendors such as FleetPanda advertise five-to-six-week go-lives, and AIMS runs new customers in test mode for several weeks before importing beginning balances. Multi-entity operators with multiple POS feeds and years of history should budget two to four months. The phases are the same either way: configuration, data migration, integration testing, training, then a verified cutover.
Can we switch fuel software mid-year, or do we have to wait for January?
You can switch at any month-end. Motor fuel tax returns and most customer billing run monthly, so a clean month boundary gives you a natural break for balances and filings. Mid-month cutovers cause most reconciliation headaches, since deliveries in transit on the switch date end up split across two systems.
How much does fuel software onboarding cost?
Most vendors charge a one-time implementation fee separate from the monthly subscription, and migrating historical transactions is often billed by the hour or by the year of history. Get three things in writing: what the flat fee covers, whether training is included, and which data work bills hourly. Two quotes are only comparable once those three answers match.
Do we lose access to our old records after switching?
Plan to keep them. IFTA requires four years of fuel records from the return due date or filing date, and state motor fuel tax audits commonly reach back a similar span, so either keep the old system in read-only mode or export full transaction and BOL detail before the license lapses. Decide this before cutover, since exports get harder once the old vendor relationship ends.