Telstra & Optus Business Bill PDF to Excel for Tax Apportionment

An Australian sole trader or contractor with a bundled Telstra, Optus, TPG, or Vodafone Business plan must apportion each service line — each mobile number, fixed line, and internet service — separately when claiming work-use deductions. The work-use percentage applies at the service level, not the bundle level. That single rule turns a stack of monthly PDFs into a per-service-line spreadsheet job. Getting a telstra business bill pdf to excel for tax claims means producing one row per phone number or service ID, with the issue date repeated on every row, so the ATO 4-week-diary work-use percentage can be applied at the line level rather than the bundle level.

ATO guidance on mobile phone, mobile internet and other devices accepts a continuous 4-week period as a representative record of work-related phone and internet use, which can then be applied across the income year using a reasonable basis (such as the proportion of work calls or work-related data) to calculate the deductible portion. That guidance is the load-bearing rule the rest of this article rests on. It is also where the rule explainers stop and where the actual extraction work starts.

The destination spreadsheet has eight columns, one row per service per bill:

• Service identifier — the mobile number, fixed-line ID, or service-account number
• Service description — a self-describing label that overrides the carrier's generic "Mobile Bundle Plan"
• Issue date — repeated on every row of that bill
• Line charge — the per-service charge before bundle-level adjustments
• Discount or credit allocation — the share of any header credit attributed to this line
• Net cost — line charge minus the allocated discount
• Work-use percentage — populated from the diary, potentially different per service
• Claimable amount — net cost multiplied by work-use percentage

A worked column-by-column treatment comes later. The shape above is what the rest of the article builds toward.

A note on scope before going further. This article produces the spreadsheet. It does not produce the diary, which remains the user's responsibility under ATO substantiation rules, and it does not give tax advice on what work-use percentage is right for any given role. The percentages belong to the taxpayer (and where applicable their tax agent) to defend; the spreadsheet is the structure the percentages get applied through.

What the ATO Actually Expects from a Bundled-Bill Claim

Where one bill carries several services — a primary mobile, a secondary mobile, home internet, a fixed line — the work-use percentage applies to each service on its own substantiated cost. There is no single bundle-wide percentage, even when the carrier prints a single bundle-wide total. Each service may carry a different percentage and must be calculated against its own line charge. Below the $50 incidental claims threshold the ATO does not require detailed records, but a sole trader running a Telstra Business or Optus Business bundle is well above that threshold by month one and sits in the substantiation tier from the start.

Two pieces of evidence pair to support the claim. The bill substantiates the cost incurred for each service: the line charge, the bundle credits and discounts attributable to that line, the resulting net cost. The diary substantiates the work-use percentage applied to that cost: the work calls and work data over a representative period, recorded against the service it relates to. Neither evidence replaces the other. The bill alone shows what was spent but not what proportion was for work; the diary alone shows the proportion but not the amount.

The per-service shape matters most for contractors. A contractor caught by the Personal Services Income (PSI) rules with a dedicated work mobile that never sees a private call sits at 100% on that service. The same contractor's home internet, shared with the household, might sit at 30%. A secondary mobile used for both work and family might sit somewhere in between. Each service identifier carries its own percentage, and a single bundle-wide figure would either overclaim the home internet or underclaim the work mobile. The schema's whole point is to keep those numbers separate.

The pattern of producing per-line tax-substantiating data directly from the source document is not unique to telco bills. The same shape applies to fuel: extracting fuel tax credit data from fuel invoices decomposes a single supplier invoice into the per-litre, per-fuel-type figures that the FTC calculation needs, under a different ATO regime but with the same evidence-from-source-document logic. A sole trader running both workflows ends up with a bills-to-spreadsheet step in front of every deduction that requires substantiated per-line cost data.

Anatomy of a Telstra Business and Optus Business Bill PDF

A Telstra Business bill PDF is built in three layers, and only the second and third produce data the ATO substantiation work needs.

The Account Summary is the front page: total amount due, payment date, account-level credits and adjustments. Useful for paying the bill, useless for apportionment, because everything on it sits at the bundle level.

The Service Summary is the section that matters for apportionment. It lists each service identifier on the account — every mobile number, every fixed-line ID, every data-service ID — alongside its plan name and a per-service subtotal. On a multi-page Telstra Business bill the Service Summary typically falls on page two or three, after the Account Summary but before the detailed charges. It is the first time on the bill the carrier expresses the cost at the level the ATO wants the apportionment done.

The detailed charges per service follow the Service Summary. Each service identifier gets its own block: plan fee, call charges, data charges, any per-line discounts. This is where the carrier's accounting actually lives, and it is where the per-service-line extraction reads from when the Service Summary subtotal needs to be reconciled or broken down further.

An Optus Business bill is laid out the same way under different labels. The Account Summary at the front. The block Optus calls Charges by Service (the equivalent of Telstra's Service Summary), broken down per service identifier with a subtotal each. The per-service charge details that follow. The structural point is the same — there is a per-service block, and that is the one that matters — but the labels and the page positions differ, and the place where header-level credits and bundle adjustments land on the page is not always the same as Telstra's. Read the Account Summary for the bundle-level adjustments, then read the Charges by Service block for the service-level breakdown.

TPG Business bills consolidate mobile and broadband under a single account, with the per-service breakdown sometimes appearing as a Services and Charges table rather than a labelled Service Summary. Vodafone Business bills typically follow a per-mobile breakdown with bundle plans grouped on the first page; layout varies more between Vodafone plan generations than between any two Telstra bills.

Across all four carriers the practical implication is the same: every bill has a per-service block somewhere, and that block is where the service identifier lives. The Account Summary on its own is insufficient because it sits at the bundle level — exactly the level the ATO does not want the apportionment done at. Locate the per-service block first; everything downstream depends on it. The carriers' own billing-help pages are the right reference if a particular bill format is hard to read.

The Bundle Decomposition Problem — and How to Solve It in One Prompt

The technical core of the problem is that bundled business plans apply discounts, credits, and bundle promotions at the bundle header. A primary mobile, a secondary mobile, home internet, and a fixed line each carry their own line charge in the per-service block, but a single dollar-figure credit at the header level reduces the bundle as a whole rather than any individual service. To produce an honest per-service cost, those header-level adjustments need to be allocated back to the service lines using a defensible basis — most commonly proportional to the line charge, so a service that contributes 60% of the line charges absorbs 60% of the bundle credit.

The reasonable basis for that proportional allocation is the same kind of judgement the ATO expects on the work-use percentage itself: a defensible method, applied consistently, documented somewhere the taxpayer can point to at audit. Proportional by line charge is the workable default; alternatives (fixed proportions stated in the plan terms, allocation to a single service when the credit relates specifically to it) sit on top of that default when the plan documentation supports them.

The whole job — bundle decomposition, line-level extraction, repeated issue date, generic-label override, allocated credits — fits in a single natural-language prompt. A worked example: "Extract one row per service identifier from each Telstra Business bill. Repeat the issue date on every row. For the service description, override 'Mobile Bundle Plan' with the service-specific name in the format 'Mobile — [number]' or 'Home Internet — [account]'. Allocate any header-level credits or discounts proportionally across the service lines based on each line's share of the total line charges, and show the allocation in its own column. Output as Excel with one sheet covering all bills." That single instruction set is what turns the workflow from re-typing twelve bills into running them through an AI-powered bill and invoice data extraction once and downloading the result.

The operational shape for a sole trader running a year of bills: drop the twelve PDFs into a single batch upload, apply the saved prompt, download a single spreadsheet with every service line from every month already in shape and ready for the work-use percentage column. The same prompt produces consistent rows across every bill in the batch, which is what makes the spreadsheet usable for tax-time reconciliation rather than a per-month re-cleaning exercise. A bookkeeper running the same workflow across multiple sole-trader clients saves the prompt once and re-applies it per client; the output is consistent enough for a tax agent to re-perform the calculation if needed.

The prompt-based interaction model is the same whether the batch is two bills or twenty-four. Single PDFs of up to 5,000 pages and batches of up to 6,000 files are supported, which covers any realistic year of telco bills with substantial headroom. Saved prompts in the prompt library make the second tax year's job a one-click apply rather than a re-write, and the saved prompt enforces the same column shape across years so the spreadsheet remains comparable from year to year.

The Per-Service-Line Schema, Column by Column

Each column has a definition, a source on the bill, and a role in the apportionment chain.

Service identifier. The mobile number, fixed-line ID, or service-account number printed next to each service in the Service Summary (Telstra) or Charges by Service (Optus). This is the join key. Every other piece of evidence — the diary, the prior month's bill, the next month's bill, the year-end deduction worksheet, the GST input-tax-credit calculation — joins back to this column. Frame the spreadsheet around the service identifier rather than the bill date and the year-long view falls out naturally; frame it the other way and apportionment splinters across worksheets.

Service description. The self-describing label that overrides the carrier's generic "Mobile Bundle Plan" or equivalent. A practical format is "Mobile — 04XX XXX XXX" for a mobile, "Home Internet — Account 12345" for a fixed-line broadband service, "Fixed Line — 02 XXXX XXXX" for a landline. The point is that a row is intelligible on its own without the reader going back to the source PDF.

Issue date. The bill's issue date, repeated on every row of that bill. The repetition is the trick that makes the year-long view work. Sort by issue date, filter to a quarter, group by service identifier — none of that works if the date sits on one row at the top of each bill's block and the others are blank. Repeat it.

Line charge. The per-service charge as it appears in the bill detail, before any header-level credit or discount allocation. This is the gross figure for that service, that month.

Discount or credit allocation. The share of any bundle-header credit attributed to this service line, calculated using the apportionment basis chosen in the prompt — proportional to line charge by default. If the bill has no header-level adjustments the column reads zero; if there are several, they sum into this column for each line.

Net cost. Line charge minus discount or credit allocation. This is the substantiated cost the work-use percentage applies against — what was actually spent on that service that month, after bundle adjustments.

Work-use percentage. A column the reader fills from their 4-week diary or representative-period record. It can carry a different value per service identifier, and the per-row design is what makes that work. The next section covers how the diary populates this column.

Claimable amount. Net cost multiplied by work-use percentage. The deductible portion for that line, that month. Sum the column over the income year, grouped by service identifier or by service category, to get the figures that go on the return.

The design principle worth stating explicitly is that the service identifier is the join key, not the bill date. The bill date is one column among eight; the service identifier is what the rest of the apportionment infrastructure pivots on. That reframing alone is what separates this schema from the generic per-line phone bill to Excel workflow — the document-type parent that handles non-Australian phone bills and consumer-plan extraction without the per-service-identifier-as-join-key emphasis. The ATO's per-service apportionment expectation is what makes the join-key emphasis necessary.

One common adaptation. A sole trader registered for GST who is claiming input tax credits on the work-use portion needs a GST split. The simplest variation is to split line charge into a GST column and a net-of-GST column before the work-use percentage applies, then calculate the GST input tax credit on the GST column at the work-use percentage. The schema's shape does not need to change; only the line-charge column splits in two.

Applying Your Work-Use Percentage at the Line Level

The diary populates the work-use percentage column one service identifier at a time. For each service, the diary records the proportion of work-related use over a continuous representative period — work calls divided by total calls for a mobile, work-related data divided by total data for an internet service, work-related minutes for a fixed line. The proportion the diary produces for that service identifier is the work-use percentage that gets applied across the income year against every row carrying that identifier.

The per-service variation introduced earlier — work mobile at 100%, shared home internet around 30%, secondary mobile somewhere between — is the whole reason the schema is shaped per row. Three services on the same bundle, three different work-use percentages, three different claimable amounts per month. The per-service-identifier schema is what keeps each percentage on the row it belongs to.

The application mechanic is a single multiplication done at the row level. Claimable amount equals net cost multiplied by work-use percentage, calculated per row. Summed across rows for the income year — grouped by service identifier, or by category, or for the bundle as a whole — the totals are the figures that get reported on the return. Spreadsheet formulas handle this directly; pivot tables do it with one drag of the service identifier into rows and the claimable amount into values.

The shape of work-use evidence is not unique to phones and internet. The same audit-evidence pattern applies under FBT for parallel FBT meal entertainment work-use record-keeping — different rule regime, different documents, but the same idea of substantiating a percentage applied to a cost. A sole trader who runs both workflows ends up with two parallel evidence chains: extract the source documents into a per-line schema, apply a substantiated percentage, total the deductible portion.

Audit Readiness — Pairing the Spreadsheet with the Diary

A phone-and-internet apportionment claim under audit is built on three pieces of evidence. The bills themselves, retained as PDFs, one per month, for the statutory record-keeping period. The per-service-line spreadsheet, which decomposes those bills into substantiated per-service costs and shows the apportionment basis used for any header-level adjustments. The diary or representative-period record, which justifies the work-use percentage applied per service.

The three pieces join through the service identifier. The bills produce the costs at the service level; the spreadsheet's service-identifier column is the join key against the diary's per-service records; the diary justifies the percentage in the work-use column; the claimable amount column ties the substantiated cost and the substantiated percentage back to the deduction figure on the return. An auditor following any one column from any one row should be able to walk from the deduction back to a specific service identifier on a specific bill, paired with the diary entry that carries the percentage.

A short audit-readiness checklist for a sole trader running this workflow:

• Bills retained as PDFs for the ATO's statutory record-keeping period — typically five years from the date the return is lodged.
• The per-service-line spreadsheet preserved in a format that can be re-opened and explained, with the formula for the claimable amount column visible (not pasted as values).
• The diary kept with the spreadsheet, or referenced clearly enough that a tax agent or auditor can locate it.
• The apportionment basis used for header-level credits noted somewhere defensible — a note on the spreadsheet, a saved copy of the prompt, or a written description in the records folder.
• The same prompt re-applied year over year so the spreadsheet shape is consistent across income years and the comparable view holds up across audits.

For readers wanting the broader audit-readiness frame, preparing apportionment records for an ATO tax audit covers the document-organisation and evidence-chain practices that apply across deduction categories, not just phone and internet. The deduction's downstream landing is the BAS reconciliation if GST is in play and the income tax return either way: feeding the deduction into Xero BAS preparation walks the GST and reporting handover from the per-service spreadsheet to the BAS.