Extract Fuel Tax Credit Data from Fuel Invoices

To extract fuel tax credit from fuel invoices, capture one structured row for every fuel purchase: acquisition date, supplier, invoice or receipt number, fuel type, litres, GST amounts, vehicle or plant ID, use category, and the source file reference. For BAS label 7D, those rows need enough detail to apply the ATO rate for each purchase date, split purchases across mixed rate periods, and keep supporting records that can be reviewed later.

The weak point in many Fuel Tax Credit claims is not the BAS form itself. It is the spreadsheet, folder, or shoebox of fuel records that sits before the calculation. A quarterly total copied from a pile of receipts does not show which purchases belong to which rate period, which litres relate to heavy vehicles, which litres were used off-road, or which source document supports a disputed row.

For Australian bookkeepers, BAS agents, and fuel-heavy businesses, the practical job is to turn fuel tax invoices and fuel receipts into a defensible dataset before using the ATO calculator, a BAS worksheet, Xero, MYOB, or any internal workbook. The ATO remains the authority for eligibility, rates, and the final calculation rules. The extraction workflow is the data-prep layer that makes those tools usable.

That distinction matters for trucking, agriculture, construction, mining, marine, and mixed-fleet businesses. The same docket can show litres and dollars, but it usually does not prove what the fuel was used for. The extracted row needs to preserve the purchase details from the document, then make room for the business records that support the use category and rate applied.

Build the minimum fuel invoice extraction schema

A fuel tax credit spreadsheet should be built at purchase level, not supplier-summary level. The minimum schema is:

• Source file and page
• Supplier name
• Supplier ABN where shown
• Invoice or receipt number
• Acquisition date
• Fuel type
• Litres
• GST-inclusive total
• GST amount
• Vehicle or plant ID
• Cost centre or client
• Use category
• Rate period
• Notes or exception flag

Some of those fields come straight from the fuel document. BP, Shell, Ampol, Caltex, 7-Eleven, United, Liberty, On The Run, and other fuel retailers use different receipt and invoice layouts, but the recurring extraction targets are usually the date, supplier, document number, fuel description, litres, and payment or tax amounts. If the document is being used as GST evidence as well as FTC support, the finance team should also check it against Australian tax invoice requirements, especially where the purchase value means a valid tax invoice is needed.

Other fields are not usually on the receipt at all. Vehicle or plant ID may come from the driver, docket notes, fuel-card metadata, a job sheet, or a fleet register. Cost centre and client allocation may come from the accounting file. Use category should be added from operational evidence, not guessed from the supplier name or suburb.

The source file and page column is worth treating as a control field, not admin clutter. If a BAS agent later filters for a high-value diesel purchase, a duplicate docket, or a row with missing litres, the workbook should point back to the exact PDF page or receipt image. That is also where repeatable extraction tools help: Invoice Data Extraction lets users upload PDFs, scans, or receipt images, prompt for the fields they need, reuse saved prompts for recurring jobs, and download structured Excel, CSV, or JSON files with source references. For fuel-heavy clients, the practical goal is to extract fuel invoice data into a clean BAS spreadsheet without losing the evidence trail behind each row.

Exception flags should be part of the schema from the start. Use them for unreadable receipt images, missing ABNs, no litre quantity, ambiguous fuel type, duplicate document numbers, or purchases that look private or mixed-use. A clean FTC file is not one where every row pretends to be ready. It is one where the review work is visible.

Separate rate periods before calculating BAS label 7D

Fuel Tax Credit rates are tied to when the fuel was acquired and how it was used. That is why the acquisition date needs its own column and why a quarterly litre total is not enough. If a BAS period crosses a rate change, March litres and April litres cannot be merged first and rated later.

The ATO rates page and fuel tax credit calculator should be the rate authority. The extraction file should make their job easier by preserving the purchase date, fuel type, litres, and activity category for every row. A rate-period column can be as plain as "before 1 April 2026", "1 April to 30 June 2026", or whatever grouping matches the current ATO table. The value is not the wording. The value is that the reviewer can filter the workbook and see which purchases were calculated under each period.

The 2026 relief window shows why this matters. The Department of Infrastructure reported that from 1 April 2026 for three months, fuel excise was reduced from 52.6 to 20.6 cents per litre and the heavy vehicle road user charge was reduced from 32.4 cents per litre to zero, according to its update on April 2026 fuel excise and road user charge relief. A June-quarter claim can therefore include purchases before and after 1 April, and those rows need to be split before the FTC amount is calculated.

That window also breaks a common shortcut carried over from the 2022 excise reduction. For the 2026 three-month period, the road user charge is temporarily zero, so an on-road heavy vehicle calculation should not assume the RUC swallows the fuel tax credit. The safer workflow is to keep the acquisition date and use category intact, then check the ATO rate for the exact fuel and activity at calculation time.

The same discipline applies to omitted claims. Fuel tax credits generally need to be claimed within 4 years, and when earlier fuel purchases are claimed later, the original acquisition date still controls the rate period. A file that only says "diesel, June BAS, total litres" forces someone to reconstruct the rate logic months or years later. A row-level file keeps the heavy vehicle fuel tax credit calculation auditable.

Add use-category evidence the fuel document cannot prove

A fuel invoice proves that fuel was bought. It rarely proves how the fuel was used. For FTC work, that gap is where many review problems start.

The extracted document fields should be joined to a controlled use-category column before the calculation is finalised. Common categories include heavy vehicle travelling on a public road, off-road business use, auxiliary equipment, fuel used in plant or machinery, marine use, rail, generators, and private or ineligible use. A mixed-fleet business may need several of these in the same quarter. A construction company might have diesel for trucks, excavators, site generators, and utes. A farm might have tractors, pumps, and light vehicles. A transport operator might need to separate public-road travel from auxiliary equipment use.

The receipt alone will not settle those distinctions. The support may come from logbooks, odometer readings, GPS or telematics data, job records, equipment registers, contracts, worksheets, fuel issue records, or driver notes. The extraction file should either include the supporting reference directly or include a column that points to where the evidence sits.

Use categories should be controlled values, not loose notes. "Truck", "semi", "Kenworth", "delivery", and "road" may all describe the same activity to the person typing the row, but they are poor calculation categories. A controlled list makes it easier to filter the workbook, review edge cases, and apply the same treatment across BP receipts, Ampol invoices, depot fuel logs, and scanned dockets.

This is not a place to improvise tax advice. Borderline light-vehicle treatment, mixed-use allocation, and changes in intended use should be escalated to the BAS agent or tax adviser. The extraction workflow should preserve enough facts for that adviser to make the call without rebuilding the document trail.

Keep fuel tax credit records review-ready for five years

Fuel tax credit record keeping for 5 years is more than keeping a PDF folder. The records need to support the amount of fuel acquired and used, the business activity, the rate applied, and the calculation that reached the BAS label 7D amount.

A review-ready FTC file usually has several layers:

• The original fuel tax invoice, receipt, docket, or statement
• The extracted row with source file and page reference
• The workbook, ATO calculator output, or worksheet used to calculate the credit
• The use-category evidence, such as logbooks, odometer readings, GPS data, job records, or equipment registers
• Notes explaining exceptions, adjustments, or judgement calls

That structure matters because the reviewer is not only checking whether the business bought diesel. They are checking whether the litres, date, fuel type, activity, rate, and calculation support the credit claimed. If the file cannot support a row, the business may have to repay part or all of the credit received.

The same source-to-workpaper discipline applies to other Australian tax records. If the same finance team is capturing staff or client meals, a meal entertainment receipt extraction workflow for FBT workpapers can keep those records separate from fuel evidence while still preserving the review trail.

Exception flags make the review work manageable. Flag missing ABNs, receipt images that cannot be read confidently, documents with dollars but no litres, duplicate receipt numbers, purchases that look private, and rows where the rate period does not match the acquisition date. A row with an exception flag is not necessarily wrong. It is a row that should not flow silently into the BAS total.

Document type also matters. This article is about individual fuel tax invoices and receipts. Consolidated fuel-card PDFs, portal exports, and monthly card statements are a related but different extraction problem because the useful data may sit in transaction lines rather than invoice headers. For those files, use a fleet fuel card statement extraction workflow so each card transaction can still be reviewed by date, litres, fuel type, vehicle, and driver or account. Where the goal is an FTC-ready output rather than a general transaction register, a dedicated workflow for turning a monthly BP Plus, StarCard, Shell Card, or WEX Motorpass statement into a per-vehicle, rate-period-split FTC worksheet can slot directly into the BAS 7D preparation step below.

Export the data for spreadsheets, Xero, MYOB, or the ATO calculator

The extracted file should stay calculation-friendly after the documents have been processed. Keep one purchase per row, use numeric litres and amounts, standardise dates, keep use categories consistent, and make the rate-period column filterable. If the workbook has to be cleaned again before the calculation can start, the extraction step has only moved the manual work downstream.

Excel is often the review layer because it lets a bookkeeper filter exceptions, pivot litres by fuel type or vehicle, and compare subtotals by rate period. CSV may suit import or working-paper systems. JSON may suit teams feeding the data into an internal workflow. The format matters less than preserving the controls: source reference, date, litres, fuel type, use category, and notes.

The ATO calculator or worksheet then needs the right inputs, not a perfect-looking but unsupported total. For example, the workbook should let the preparer group eligible diesel litres by acquisition date and activity before entering or calculating the claim. If a row is missing litres, has an unclear activity, or falls into a mixed-use category, it should be resolved before the BAS label 7D amount is posted.

Xero and MYOB can support BAS preparation and posting, but they do not remove the upstream data problem. A fuel tax credit Xero MYOB workflow still needs the source-document detail behind the calculation, especially where a business has multiple vehicles, rate periods, or off-road and on-road use. Readers who need the full Xero BAS context can pair the FTC working paper with a broader Xero BAS preparation workflow.

Invoice Data Extraction can fit at the document-to-dataset stage: upload the fuel invoices and receipts, prompt for the FTC columns, require date formatting such as YYYY-MM-DD, control column order, add source file and page references, and download the result as Excel, CSV, or JSON. For recurring clients, saved prompts help keep the same field list and review flags across monthly or quarterly jobs.

A practical pre-BAS review before lodging the FTC claim

Before the FTC amount reaches BAS label 7D, run the extraction file through a focused review:

1. Reconcile total litres back to the source documents.
2. Filter exception flags and resolve the rows that should not flow into the claim yet.
3. Check that each purchase sits in the correct rate period for its acquisition date.
4. Review use-category allocations against the supporting records.
5. Test for duplicate receipt numbers, duplicate images, and repeated card transactions.
6. Compare the worksheet or calculator total to the amount that will be reported at label 7D.
7. Keep the source documents, extracted data, calculation file, and supporting evidence together.

Use current ATO rates or the ATO calculator for the exact acquisition date, fuel type, and activity. Do not rely on an old workbook rate, a prior-quarter formula, or a supplier summary that has already blended transactions across dates.

Escalate uncertain items before lodgement. That includes light vehicle treatment, mixed-use apportionment, retrospective claims, large adjustments, and any row where the fuel document and operational evidence do not line up. A BAS agent or tax adviser can only make a sound call if the dataset shows what was bought, when it was acquired, how it was used, and where the supporting record sits.

A Fuel Tax Credit claim is easier to defend when the file shows the full path from document to calculation: fuel invoice or receipt, extracted row, use-category evidence, rate-period treatment, and BAS label 7D amount.