Fleet Fuel Card Policy Template and What to Cover

Most fleets issue fuel cards long before they write a policy governing how they're used, and it usually catches up with them — a disputed personal purchase, a driver who's lost three cards in a year, or an odometer field nobody bothers filling in. A written fuel card policy closes these gaps before they become disputes, and it gives you something concrete to point to when a breach does happen. This guide sets out what a policy needs to cover and gives you a structured outline to adapt.

Why a written policy matters, even for small fleets

Some fleet managers assume a formal policy is overkill for a handful of vehicles, but the risk profile isn't really about fleet size — it's about the number of people with access to a payment method that isn't closely watched purchase-by-purchase. A written policy matters because it:

• Sets clear, consistent expectations so drivers aren't guessing what's allowed.
• Gives management and HR a documented standard to apply if a breach occurs, rather than an ad hoc decision that can look inconsistent or unfair.
• Reduces disputes about personal use, because the boundary is defined in advance rather than argued after the fact.
• Supports GST and FBT compliance by tying purchases to business use as the default position — see our related guide on fuel card reporting and BAS compliance for how this connects to your tax obligations.
• Protects the business if a card is used fraudulently, since a documented reporting process for lost or stolen cards limits financial exposure.

What a fleet fuel card policy must cover

At minimum, a policy should address the following areas. Each is covered in more depth below.

1. Card issuance and eligibility

Define who is eligible for a card (employees vs contractors, permanent vs casual), how a card is requested, and who approves issuance. Specify whether cards are allocated per vehicle or per driver — this decision affects both reporting and control, since a per-vehicle card can be used by multiple drivers, while a per-driver card follows the person across vehicles.

Also cover onboarding and offboarding: a new starter shouldn't be driving a company vehicle without a card sorted in advance, and a departing employee's card should be deactivated on their last working day, not whenever someone remembers.

2. PIN security

PINs should never be:

• Written on the card itself or stored with it in the vehicle
• Shared between drivers
• The same PIN reused across a driver's personal and work cards

The policy should state that PINs are personal and confidential, that sharing a PIN is itself a breach regardless of what it's used for, and what to do if a PIN is forgotten (typically a request through the fleet administrator, not a workaround at the pump).

3. Permitted and restricted purchases

This is usually the section with the most disputes, so it needs to be specific rather than general. Spell out:

• Permitted: fuel for the assigned vehicle, AdBlue, and — if your policy allows — minor consumables directly related to vehicle operation (screen wash, oil top-ups) up to a defined limit.
• Restricted or prohibited: fuel for personal vehicles, convenience store purchases (snacks, drinks, cigarettes), purchases for other people's vehicles, and cash withdrawals where the card network allows them.
• Approval required: anything outside the above list — for example, an unusual repair or consumable purchase — should require prior approval from a named manager, with the exception process documented.

Where the card platform supports it, product-type restrictions (fuel and AdBlue only, no general merchandise) should be configured at the account level rather than relying purely on driver compliance — a technical control is more reliable than a policy line alone.

4. Odometer entry requirements

If your card program supports odometer capture at the pump, the policy should make it mandatory, not optional, and explain why: it supports fuel tax credit substantiation, helps detect fuel card misuse (unusually high litres relative to distance travelled), and validates that the vehicle associated with the card is the one actually being fuelled. Make clear what happens if odometer entry is skipped repeatedly — a first reminder, then escalation if it continues.

5. Lost, stolen or damaged cards

Set out:

• Who to call and how quickly a lost or stolen card must be reported (immediately, not at the end of the shift)
• What happens to fuel purchased on a card between loss and reporting — this is where a clear, immediate reporting requirement genuinely limits financial exposure
• The replacement process and expected turnaround
• Whether repeated card loss (for example, three or more in a year) triggers a review or a small excess/contribution from the employee, if that's consistent with your employment terms

6. Personal use

State plainly whether any personal use is permitted. Many fleets adopt a zero personal use policy for simplicity — it's easier to enforce and keeps GST and FBT treatment straightforward. If limited personal use is allowed (for example, with a take-home vehicle), define exactly what's covered, how it's tracked separately, and how it's treated for tax purposes, since mixed-use vehicles have different GST and FBT implications than pure business-use vehicles.

7. Monitoring and reporting

Explain that transactions are reviewed regularly (weekly or monthly, depending on fleet size) against expected vehicle usage, and that this isn't an accusation of wrongdoing — it's standard practice across the fleet. Transparency here tends to reduce, not increase, defensiveness among drivers.

8. Breaches and consequences

Define a tiered response:

• Minor/inadvertent breach (e.g. missed odometer entry, minor purchase outside policy without approval): verbal reminder, recorded.
• Repeated breach: formal written warning, in line with normal HR process.
• Deliberate misuse (e.g. personal fuel purchases, PIN sharing leading to unauthorised use, falsified odometer entries): treated as a disciplinary matter, potentially serious misconduct depending on severity, handled through the same process as any other breach of company policy or fraud.

Make sure this section is consistent with your broader HR and disciplinary policies rather than creating a standalone process that could conflict with them.

9. Sign-off and acknowledgement

Every driver issued a card should sign an acknowledgement that they've read and understood the policy, ideally as part of induction and refreshed periodically (annually, or whenever the policy is materially updated). Keep signed acknowledgements on file — they're useful evidence if a breach dispute ever escalates.

Structured fuel card policy outline (adapt for your fleet)

Below is a working outline you can adapt into your own document. Replace bracketed sections with your fleet's specifics.

[Company Name] Fuel Card Policy

1. Purpose — Brief statement: this policy governs the issuance and use of company fuel cards to ensure appropriate use, cost control and compliance with tax obligations.
2. Scope — Applies to all employees and contractors issued a company fuel card.
3. Card issuance

• Eligibility criteria
• Request and approval process
• Per-vehicle vs per-driver allocation
• Onboarding/offboarding procedure

4. PIN security

• PIN confidentiality requirement
• Prohibition on sharing
• Process for a forgotten PIN

5. Permitted purchases

• List of approved purchase types
• List of prohibited purchase types
• Approval process for exceptions

6. Odometer entry

• Mandatory at every transaction
• Escalation for repeated non-compliance

7. Lost, stolen or damaged cards

• Immediate reporting requirement and contact details
• Replacement process and timeframe
• Liability position for unreported loss

8. Personal use

• Statement of policy (zero tolerance or defined limited use)
• Tax treatment note, if applicable

9. Monitoring

• Frequency and method of transaction review
• Escalation triggers (unusual volume, location, frequency)

10. Breaches

• Tiered consequences (minor, repeated, deliberate)
• Link to broader HR/disciplinary policy

11. Review — Policy reviewed annually or upon material change to fleet, provider or regulatory requirements.
12. Acknowledgement — Employee signature and date confirming the policy has been read and understood.

Table: policy area vs primary control mechanism

Policy area	Primary control
Issuance	Approval workflow, onboarding/offboarding checklist
PIN security	Personal, confidential PIN issued separately from card
Permitted purchases	Product-type restrictions configured on the card account
Odometer entry	Mandatory field at point of sale, monitored compliance
Lost/stolen cards	Immediate reporting hotline, fast deactivation
Personal use	Written policy statement, monitored transactions
Breaches	Tiered disciplinary process aligned to HR policy

Rolling out or updating the policy

If you're introducing a fuel card policy for the first time, or updating an existing one:

• Communicate it at a toolbox talk or team meeting, not just by email — questions come up, and it's better to answer them upfront.
• Give drivers a grace period (one or two pay cycles) if you're tightening previously loose practices, particularly around odometer entry or personal use, so the change doesn't feel punitive out of nowhere.
• Review the policy whenever you change fuel card provider — this is also a good moment to reset any bad habits that built up under the old arrangement. If you're mid-switch, see our guide on switching fuel card providers for how to sequence this alongside the operational transition.
• Set a recurring annual review date so the policy doesn't go stale as fleet size, vehicle types or regulatory requirements change.

Frequently asked questions

Do we need a written fuel card policy for a small fleet?

Yes — the risk of undefined boundaries around personal use, PIN sharing and lost card reporting exists regardless of fleet size. A simple one-to-two-page policy is far better than none.

Should fuel cards be assigned to vehicles or to drivers?

It depends on your operation. Per-vehicle cards suit fleets where multiple drivers share vehicles and you want fuel data tied to the asset. Per-driver cards suit fleets where drivers move between vehicles and you want spend tracked to the individual. Some fleets use a mix depending on vehicle type.

What should happen if a driver loses a card multiple times?

Most policies allow for an escalation — a reminder after the first loss, a documented conversation after a second, and management review if it becomes a pattern, since repeated loss increases fraud exposure and replacement costs.

Is any personal use of a fuel card ever acceptable?

Some fleets permit limited personal use, particularly for take-home vehicles, but it needs to be explicitly defined and tracked separately, since it has different GST and FBT implications than business-only use. Many fleets simplify this by adopting a zero personal use policy.

How often should the fuel card policy be reviewed?

At least annually, and whenever there's a material change — a new fuel card provider, a change in fleet composition, or a regulatory change affecting GST, FBT or fuel tax credits.

Does the fuel card provider enforce the policy, or is that up to us?

Providers can typically support the policy through technical controls — product restrictions, spend limits, mandatory odometer capture — but the policy itself, communication and disciplinary follow-through remain the employer's responsibility.

If you'd like help thinking through which controls your card platform should be configured with to support your policy, book a 15-minute fuel spend review with FuelPoint, or use the [/#calculator] on our homepage to see how your current fuel spend and control settings stack up.

Keeping the policy practical, not just compliant

A fuel card policy that reads like a legal document but never gets referenced day-to-day isn't doing its job. The most effective versions are short enough that a driver can read the whole thing in under ten minutes, specific enough that there's no ambiguity about what's allowed, and paired with technical controls on the card itself so the policy isn't the only line of defence. Treat it as a living document — update it whenever your fleet, provider or reporting requirements change, and revisit it with drivers at induction and at least once a year after that.