Australian Fleet Card Statement to Excel: BP Plus, Caltex, Shell

Most Australian fleet operators run two or more cards because no single network covers every site or every driver. A tradie's BP Plus card sits in the ute alongside a Caltex StarCard for routes through Ampol-heavy regional towns; a small fleet adds Shell Card for sites BP Plus doesn't reach; an apprentice ends up paying cash at a country forecourt and brings the receipt back for reimbursement. Every month the bookkeeper opens the inbox to two or three different statement layouts and a couple of forecourt receipts on a personal card.

The shape that actually supports the downstream work — when converting a fleet card statement to Excel in Australia — is one row per transaction across every vendor, with vendor-of-card added as a column alongside transaction date, site, driver, vehicle ID, litres, ex-GST amount, GST, total, and any rebate or discount line. That unified shape supports per-vehicle and per-driver pivots, BAS GST recognised on the invoice date, and Fuel Tax Credit eligibility flagged at row level (diesel for eligible business activity, petrol excluded).

The pitches the searcher has likely just read elsewhere don't fit a real mixed-vendor fleet. Each vendor portal lives inside its own ecosystem — BP Plus exports BP Plus, Ampol exports StarCard, Motorpass exports Motorpass — and the consolidation problem doesn't disappear because one of them happens to offer Excel. "Switch to a single card" is a vendor pitch, not an operating reality, when site density and driver coverage drive multi-card setups. Generic PDF-to-Excel converters can pull a table out of any statement, but they don't preserve the columns a fleet bookkeeper needs: vehicle ID, FTC eligibility flag, rebate-line treatment, vendor-of-card. This article picks up where a generic fleet card statement to Excel walkthrough stops, with the AU vendor specifics and the multi-vendor consolidation shape as the spine.

Invoice Data Extraction handles this workflow directly: upload the month's mixed BP Plus, Caltex StarCard, Shell Card, and Motorpass PDFs together, write a single natural-language prompt describing the unified columns (transaction date, site, driver, vehicle ID, litres, ex-GST, GST, total, rebate line, vendor-of-card), and download a structured Excel, CSV, or JSON file — one input shape that lets you extract every fleet card PDF into a unified per-transaction spreadsheet, regardless of how many vendors are in the batch. The prompt is the configuration; the same prompt produces the same shape every month.

What follows walks the AU vendor landscape, the per-vendor portal-export realities (including what each export gets right and where each one falls short), the unified spreadsheet shape with vendor-of-card and card-source as the consolidation columns, the GST and FTC overlays at row level, and the per-vehicle and per-driver pivots that fall out of the unified shape without rework.

The Australian Fleet-Card Landscape: BP Plus, Caltex StarCard, Shell Card, Motorpass, FleetCard

Five vendors carry most of the fleet-card volume in Australia, each with a different network footprint and a different idea of what its statement looks like.

BP Plus is the BP-branded fleet card, accepted across BP service stations and the BP Plus partner network — independents and other branded sites that take BP Plus where there's no BP nearby. It runs the BP Plus Earn rebate programme and is the default for fleets that route through BP's metro and highway sites.

Caltex StarCard, now Ampol-branded since the rebrand from Caltex to Ampol, runs across the Ampol and AmpolCard / StarCard network with a wide regional footprint and the AmpolCash rebate sitting on top. Many statements still read as Caltex StarCard in older accounts, and operators tend to use both names interchangeably.

Shell Card in Australia is supplied through Viva Energy, which operates the Shell-branded retail network locally. The card opens up Shell sites and a smaller partner footprint, and is more common in fleets running highway routes where Shell's network has historically been strong.

Motorpass is a WEX-issued multi-network card that consolidates fuel purchases across BP, Caltex/Ampol, Shell, 7-Eleven, Liberty, and a long list of independents inside a single Motorpass invoice. It's the card fleets reach for when no single branded network covers their drivers.

FleetCard, also WEX-issued, carries similar multi-network acceptance and ships with deeper accounting-software integrations — Xero in particular — that push transactions into the general ledger rather than ending at a PDF or Excel export.

Most operators end up running more than one of these cards, and the reason is structural rather than a procurement oversight. Site density varies by region: a regional driver covering a route through New South Wales might pass a dozen Ampol sites and only two BPs, while a metro fleet might hit BP and Shell exclusively and never see an Ampol forecourt. Acceptance at independent and rural sites is patchy on the branded cards (BP Plus, StarCard, Shell Card) and broader but not universal on the multi-network cards (Motorpass, FleetCard).

Tradies running owner-operated work vehicles add another layer to the mix. The fleet card sits in the ute for the routine fills, but a personal card comes out at cash-only forecourts and on after-hours weekend jobs — which lands them in the mixed-source reality even before a second fleet card is issued.

The consolidation problem doesn't dissolve at the card level. Each vendor's portal lives inside its own ecosystem. Even Motorpass and FleetCard, which consolidate transactions across acceptance networks within a single card, only consolidate within their own card — a fleet running Motorpass plus a separately-issued BP Plus card still has two statements to merge, and a fleet running FleetCard plus a Shell Card receives data from two different systems that need to meet in the same spreadsheet.

The Australian ecosystem also doesn't carry across to the US one. The US fleet-card market runs through different vendors (AtoB, WEX US, Comdata, Fuelman) with different statement layouts, and US fleets work to different regulatory anchors — federal and state sales tax, IFTA fuel-tax reporting, no FTC equivalent. Operators handling fleets across both markets need a separate workflow on the US side; the AtoB fleet card statement workflow for the US ecosystem covers that ground specifically. The rest of this article stays in Australia.

Per-Vendor Statement Anatomy and What Each Portal Export Actually Gives You

Every AU fleet card produces a tax invoice for the statement period plus a transaction listing. The shape of that listing, and what the portal lets you do with it, varies enough that a multi-vendor fleet ends up handling each one differently. Here's what each looks like in practice.

BP Plus. The monthly statement lists transactions with date, site, vehicle / driver / asset ID where the account has those fields configured, fuel grade and litres, ex-GST and GST amounts, total, and rebate lines from BP Plus Earn where eligible. The portal does offer a real Excel transaction download, which is the strongest portal export of any of the AU fleet cards. The catch is that the export is raw: the column headings aren't embedded in the file. The column-name reference lives separately in the BP Plus FAQ, so a bookkeeper opening the export for the first time has either to map columns by hand or set up a saved column mapping that survives between months. Once the mapping is in place, the export is reliable; before it's in place, the file looks like a wall of unlabelled numbers.

Caltex StarCard / Ampol. The statement lists transaction date, site (Ampol-branded or partner), card-holder reference, fuel grade, litres, GST-inclusive amount with GST shown separately, and AmpolCash rebate lines on eligible accounts. The self-service download from the StarCard portal is capped at a 35-day window per request and ships as a .txt file rather than Excel. The 35-day cap is the operating constraint that catches people out: a year-end review, an audit-period reconstruction, or any historical lookback past a single billing month means stitching together a series of downloads. For periods past the self-service window the practical input most bookkeepers actually have is the monthly statement PDF, which makes extraction the path rather than the export.

Shell Card. Administered through Viva Energy in Australia. The statement lists transaction date, site, card and vehicle reference, fuel grade, litres, ex-GST, GST, total, and any volume-rebate line where the account has one. Portal access varies by account type — larger accounts get a portal with structured downloads, but many smaller accounts receive a PDF statement by email each month and never see an Excel export. For those accounts the PDF is the primary input the bookkeeper has in hand, and extraction from the PDF is the only path to a structured shape.

Motorpass. The WEX-issued multi-network card. Its statement consolidates transactions across BP, Caltex/Ampol, Shell, 7-Eleven, Liberty, and other accepting sites within a single Motorpass invoice — useful, and marketed as ATO-compliant consolidated billing. The constraint is that the consolidation is within Motorpass. A fleet running Motorpass plus a separately-issued BP Plus card still has two statements to merge, and the Motorpass invoice itself doesn't carry the BP Plus Earn rebate line because the BP Plus rebate sits on the BP Plus account, not on the Motorpass invoice that paid for the fuel.

FleetCard. Also WEX-issued, with established accounting-software integrations — most visibly Xero, where transactions can flow structured into the ledger as they post. For accounts running the integration on current periods, the data is structured at source. The PDF statement is still the fallback for accounts without the integration, for periods predating activation, and for the year-end reconstruction cases where structured data is needed in spreadsheet form rather than already-posted ledger lines.

Across all five, the portal exports — where they exist — share three gaps that the unified spreadsheet has to close after the fact:

• No row-level FTC eligibility flag. The exports record fuel type, but the eligibility decision (diesel for eligible business activity yes; petrol no; AdBlue separate) isn't a column in any vendor's export.
• No card-source distinction for the forecourt-on-personal-card overlay. The vendor's own export, naturally enough, only knows about its own card. The apprentice's cash forecourt receipt is invisible to it.
• No unified shape across vendors. BP Plus's column order differs from Caltex's .txt structure, which differs from Motorpass's consolidated invoice. Per-vehicle pivots that work across the whole fleet need a single column shape, which means deciding on it once and either re-mapping every export or extracting straight to the unified shape.

That's where extraction earns its place. For multi-vendor consolidation, for out-of-window historical periods (Caltex's 35-day cap, Shell email-only accounts, end-of-year reconstructions), and for the PDF-by-email accounts that don't get a structured export at all, extracting directly from the statement PDFs into a unified column shape is faster and more reliable than chaining together vendor exports and re-mapping each one.

The Unified Per-Transaction Spreadsheet: Columns and the Vendor-of-Card Field

The shape that holds together across BP Plus, Caltex StarCard, Shell Card, Motorpass, and FleetCard is one row per transaction, with a fixed column set that every vendor's PDF maps into. Decide on the columns once, then run the same prompt against the next month's batch.

Recommended columns:

• Transaction date — the date the fuel was purchased, taken from the statement transaction line. Drives every analytical view downstream and the FTC consumption period.
• Statement period — the start and end dates of the parent statement. Useful for traceability back to the source PDF.
• Invoice date — the date the parent statement is invoiced. Drives BAS GST recognition (covered in the next section).
• Site / merchant — the branded forecourt or independent name as it appears on the line: BP Wagga, Ampol Tarcutta, Shell Coles Express South Yarra, an independent named on the receipt.
• Card holder / driver — the named driver where the account assigns transactions to a card holder.
• Vehicle / asset ID — the vehicle, asset, or unit number assigned to the transaction. Critical for per-vehicle pivots.
• Fuel type — diesel, petrol grade (91 / 95 / 98), AdBlue, LPG. Preserved separately because FTC eligibility hinges on it.
• Litres — the fuel volume on the line.
• Amount ex-GST — the pre-tax line amount.
• GST — the GST amount on the line.
• Amount total — the GST-inclusive line amount.
• Rebate / discount line — the AmpolCash, BP Plus Earn, or volume-rebate line as it appears on the parent statement, kept on its own row.
• Vendor-of-card — BP Plus, Caltex StarCard / Ampol, Shell Card, Motorpass, FleetCard, or "personal card – reimbursement" for the forecourt overlay rows. This is the column that makes the consolidation work.
• Card source — fleet card vs personal-card-reimbursement. A separate field from vendor-of-card so a Motorpass row and a personal-card row are both attributable cleanly: the Motorpass row shows vendor-of-card = Motorpass, card source = fleet card; the personal-card row shows vendor-of-card = personal card – reimbursement, card source = personal-card-reimbursement.

Two additional fields are worth keeping where the data exists: source file and page number (so each row points back to the exact PDF and page it was extracted from), and an FTC eligibility flag (covered in detail in the next section).

Rebate-line treatment is a deliberate choice the reader makes once and applies consistently. The two reasonable approaches:

1. Keep rebates as separate rows. Each AmpolCash, BP Plus Earn, or volume-rebate line becomes its own row with a negative amount, its own vendor-of-card, and the same site / driver / vehicle assignment as the parent transaction where the statement provides it. Audit-friendly, because the spreadsheet shape mirrors the source statement line for line.
2. Net rebates into the parent transaction. The rebate amount reduces the transaction's total in place, with no separate row. Cleaner per-vehicle KPIs, because the cents-per-litre figure already reflects the rebated price, but breaks the 1:1 correspondence with the source statement.

For any spreadsheet that feeds BAS or FTC work, the separate-row approach is the safer default. The rebate has its own GST treatment, the original statement carries it as its own line, and the audit trail benefits from matching that shape. The netted approach is reasonable for purely analytical reporting where audit traceability isn't the deliverable.

The forecourt-on-personal-card overlay merges into the same shape. The apprentice paid cash at a non-network site on Saturday morning; the owner used a personal card on a country run when no fleet-card site was on the route. Each receipt becomes one row in the unified spreadsheet:

• Transaction date, site, driver, vehicle ID, fuel type, litres, amount ex-GST, GST, and total taken from the receipt itself.
• Vendor-of-card set to "personal card – reimbursement", and card source set to "personal-card-reimbursement", so the row is attributable independently from the fleet card statements.
• The receipt scan stands as the substantiation for that row, in the same way the fleet card statement substantiates the fleet-card rows.

The result is a single spreadsheet with one row per fuel transaction across every card, every receipt, every vendor — the column shape is the same for a BP Plus pump fill on a Tuesday and a personal-card forecourt receipt on a Sunday. That uniformity is what unlocks per-vehicle pivots, BAS GST extraction, FTC eligibility flagging, and driver expense reporting from the same input. The work to define the columns and tune the extraction prompt is one-time per format; the monthly cycle from then on is repeatable.

GST and Fuel Tax Credit Flags at Row Level, Plus Transaction Date vs Invoice Date

Two regulatory layers sit on top of the unified spreadsheet: the BAS GST that comes off the GST column every quarter, and the Fuel Tax Credit that comes off the eligible-litres rows. Both are easier to defend if the eligibility decisions live at the row level rather than getting reconstructed from raw statements at quarter-end.

Row-level FTC eligibility flag. Add a column that records the FTC status for each transaction. A three-state flag works well in practice: eligible-business-activity, ineligible (typically light-vehicle private use or non-business consumption), and excluded fuel type (petrol, which is not FTC-eligible). The decision logic, in outline:

• Diesel used in eligible business activity is the typical "yes" — for plant and machinery, off-road business use, and heavy vehicles (over 4.5 tonnes GVM) travelling on public roads at the road-user-charge-adjusted rate.
• Petrol is generally not FTC-eligible.
• AdBlue sits in its own category. It's not subject to fuel excise and isn't part of the FTC calculation, but it does carry GST and belongs on the spreadsheet for BAS purposes.

The flag is set per row at extraction time, not at quarter-end. The downstream FTC calculation consumes the eligible-litres column directly, applying the relevant FTC rate for the period. Forward to the dedicated workflow to calculate Fuel Tax Credits from extracted fuel records for the rate logic, the road-user-charge mechanics, and the BAS-line treatment — those mechanics are the FTC article's job, not this one's.

The substantiation argument for keeping the unified spreadsheet plus the source statements as the FTC record sits on solid ground: the ATO lists fuel card statements among the acceptable fuel tax credit records, and requires fuel tax credit records to be kept for five years. The unified spreadsheet is the working artefact; the source PDF statements (and the personal-card receipt scans for overlay rows) are the records the spreadsheet derives from. Together they meet the retention shape the ATO asks for.

GST at the row level. Every Australian fleet card statement breaks GST out per transaction line, because the statement itself functions as the tax invoice and the line-level GST is what makes that work. Pull the GST amount through into its own column on the spreadsheet rather than recalculating it at the column-sum level — fleet card transactions occasionally include zero-GST lines (overseas supplier transactions on a multi-network card, certain rebate adjustments) and recalculating from a flat GST rate produces incorrect totals on those rows. Sum the column for the BAS figure; reconcile back to the parent statement's invoice total as a check.

The transaction-date vs invoice-date distinction matters more than it first looks. They feed different downstream tasks:

• For BAS, GST is recognised on the tax invoice's invoice date — typically the statement period's invoice date, not the date of any individual fuel purchase. That date determines which BAS quarter the GST falls into, and it can move a statement period that crosses a quarter boundary into one quarter or the other depending on when the statement was actually invoiced. The spreadsheet's invoice-date column is what drives that recognition.
• For FTC and for analytical reporting (per-vehicle costs, driver expense reports, route variance analysis), the transaction date is what matters because consumption happens transaction by transaction, regardless of when the parent statement was invoiced.

Keeping both columns means neither task needs reconstruction. BAS sums GST by invoice-date quarter; FTC sums eligible litres by transaction-date period; per-vehicle pivots aggregate by transaction date. The spreadsheet feeds all three from the same row set without any reshaping.

Rebate-line GST treatment follows the same row-level discipline. AmpolCash, BP Plus Earn, and volume-rebate lines have their own GST treatment as adjustments to the original supply, which is precisely why keeping them as separate rows (per the prior section's rebate recommendation) produces a cleaner BAS picture than netting them into the parent transaction. The rebate row carries its own GST column entry; the BAS-quarter sum picks it up correctly without the bookkeeper having to think about it.

Per-Vehicle and Per-Driver Pivots from the Consolidated Spreadsheet

The unified spreadsheet earns its place when the analytical view falls out of it without further data work. Three pivot shapes do most of the work for an Australian fleet.

Per-vehicle pivot. Rows are vehicle / asset ID. Columns:

• Total litres for the period.
• Total ex-GST fuel cost.
• Total GST.
• Transaction count.
• Average cents-per-litre.
• FTC-eligible fuel volume (sum of litres where the FTC flag is eligible-business-activity).

The cents-per-litre column is where the operational variance surfaces. The Hilux that fills regularly at premium-priced regional sites runs visibly above the metro Ranger that fills at high-volume Ampol forecourts on a discounted card; once the variance is visible it's actionable, whether through route adjustment, a different card mix on that vehicle, or a conversation with the driver. The FTC-eligible volume column is what feeds the FTC calculation per vehicle and what supports a per-vehicle audit defence if one is ever needed.

Per-driver pivot. Rows are driver. Columns:

• Total fuel cost for the period.
• Transactions per month.
• Sites visited (count of distinct sites).
• Vendor-of-card mix (counts or percentages by vendor).
• Ratio of fleet-card transactions to personal-card-reimbursement transactions.

The fleet-vs-personal ratio is the one most worth watching. A driver running a high share of fills on the personal-card-reimbursement path is either covering a route the card mix doesn't reach (legitimate, and a signal to add a card or adjust the route) or sidestepping the card discipline (worth a conversation). The vendor-of-card mix surfaces the same picture from the other side: a driver whose Motorpass count is suspiciously low while their personal-card count is suspiciously high tells the story without needing to ask.

Per-route or per-month pivot. For fleet managers running regional routes, the same data pivots by route assignment or by month. Total fuel cost per route per month, fuel volume per route, vendor-of-card concentration per route — the latter often flags acceptance gaps directly (a route with 80% Motorpass and a 20% sliver of personal-card-reimbursement is a route the card mix doesn't quite cover, and the gap narrows once a complementary card is added).

Each pivot above falls out of the column shape from the prior sections without further data work. The vendor-of-card column is what makes the vendor-mix view possible. The card-source column is what makes the fleet-vs-personal ratio possible. The FTC eligibility flag is what makes the FTC-eligible-volume column possible. The pivot is trivial because the columns were preserved upstream — that's the whole argument for the unified shape.

Where the Spreadsheet Lands: BAS Posting, FTC Calculation, and the Monthly Workflow

The unified spreadsheet is the working artefact for the rest of the monthly cycle. It feeds BAS, it feeds FTC, and it sits between the raw statements and the accounting software as the single shape every downstream task pulls from.

BAS posting. The GST column is the BAS GST input. Sum it for the relevant quarter, recognising on the invoice-date column rather than the transaction-date column — that's the distinction the prior section established, and it's the one that catches operators out when a statement period straddles a quarter boundary. A BP Plus statement period running 21 March to 20 April with an invoice date in early April lands in the March quarter; the same period invoiced in late April lands in the June quarter. The invoice-date column resolves the question without the bookkeeper having to reread the source PDF.

For Xero users, the spreadsheet typically gets posted as a manual journal or reconciled against the fleet-card supplier bill that imports through bank feeds, depending on how the account is configured. The detailed mechanics — bill capture, contact setup, BAS line allocation, the GST codes that fit each line type — are the BAS preparation article's territory rather than this one's. Readers ready to take the unified spreadsheet into the next stage can prepare BAS in Xero for Australian businesses once the data is in shape.

FTC calculation. The eligible-litres rows feed the Fuel Tax Credit calculation directly. Eligible diesel litres at the applicable FTC rate for the period, with the road-user-charge adjustment applied where heavy vehicles travelling on public roads are involved. The unified spreadsheet's FTC eligibility flag plus its litres column is the input; the FTC article carries the rate logic and the BAS-line treatment for the credit itself.

The monthly rhythm. Once the unified column shape is defined and the extraction prompt is tuned to it, the monthly cycle is repeatable. Same prompt, same vendor-of-card mix, same column shape. The first month is a setup investment: deciding the columns, mapping each vendor's quirks (BP Plus's no-headings export reality, Caltex's 35-day window, the personal-card receipt overlay format), settling the rebate-line treatment. From month two onwards, drop the new statements and receipts into the same workflow and the spreadsheet comes out in the same shape, ready for the same pivots and the same BAS / FTC feeds.

That repeatability is what replaces the manual entry hours that would otherwise stack up for a multi-vendor fleet. The unified spreadsheet is the one place every fleet card transaction lives in a shape the downstream work can use, and it stays consistent as long as the prompt and column definition stay consistent.

Retention. ATO record-keeping for FTC requires fuel tax credit records to be kept for five years, which the unified spreadsheet plus the source statements meet directly: the spreadsheet is the working artefact, the source PDF statements and the personal-card receipt scans are the substantiation, and the row-level pointer back to source file and page closes the loop. Keep the source PDFs in the same retention store as the spreadsheets, organised by statement period, and the audit defence is in shape before it needs to be.