Why PAYG Summary Manual Entry Costs More
Than Most Payroll Teams Realize
The Australian Taxation Office's data-matching system processes roughly 14 million individual income tax returns each year, comparing the salary and wage figures taxpayers declare against the PAYG withholding data employers report. When the two figures do not match — and the ATO's own Inspector-General of Taxation review found that 85-89% of flagged discrepancies result in an adjustment — the letter that lands on an employee's myGov inbox has a chain reaction. The employee calls their payroll department. The payroll officer opens the original payment summary. And someone — usually the person who typed that TFN into the reconciliation spreadsheet four months ago — spends the next two hours tracing a single transposed digit across three systems and two tax years.
Key Takeaways
- The July PAYG crunch is three deadlines wearing one date on the calendar: STP finalisation, non-STP summary distribution, and an August annual report that cross-references the data you typed four weeks earlier against four quarterly BAS returns.
- 85–89% of ATO data-matching flags result in actual adjustments — and each resolved query traces back to a single transposed digit you typed during a compressed July window when error rates double under interruption.
- STP eliminated summaries for 88 of your 100 employees and made the remaining 12 consume 80% of your reconciliation time — automate those 12 edge cases and the entire July bottleneck collapses around them.
The July Crunch Is Three Deadlines Masquerading as One
Most descriptions of the PAYG summary process focus on a single date: 14 July, the deadline for issuing payment summaries to employees and completing STP finalisation. But for the payroll team doing the work, July is actually three overlapping deadlines, each with its own reconciliation requirement, and each pulling from a different data source. The manual entry workload is the sum of all three — not the time it takes to type one summary.
The first deadline — STP finalisation by 14 July — requires the payroll officer to confirm that every employee's year-to-date figures in the payroll system are correct before submitting the finalisation declaration. This means reconciling the system's totals against the summary output. For a company on a single payroll platform with clean data, this is a review step. For a company that changed payroll providers mid-year, has employees across multiple entities with different ABNs, or has closely held payees with a 30 September finalisation extension, the review becomes a multi-source reconciliation — and every source that cannot be queried electronically must be typed in manually.
The second deadline — issuing PAYG payment summaries to employees not reported through STP, also by 14 July — creates the document pile. STP-exempt employers, closely held payees receiving interim summaries, and employees whose pre-STP periods require a traditional certificate all produce physical or PDF summaries that the payroll team must verify before distribution. Each summary sits in a folder; each folder contains data that needs to make its way into the reconciliation spreadsheet.
The third deadline — the PAYG payment summary annual report (NAT 3447) due 14 August — demands the aggregate of every summary issued, cross-referenced against the four quarterly BAS withholding totals (labels W1 and W2). A single digit transposed on a single summary creates a $10 discrepancy on the annual report — and a $10 discrepancy triggers the same ATO query letter as a $10,000 one.
What most payroll teams miss: the workload is not the number of summaries times the time to type one summary. It is the number of summaries times the time to type, plus the time to cross-reference each summary against a different source system, plus the time to investigate the discrepancies the cross-reference finds. Manual entry is the visible cost; reconciliation rework is the invisible one that doubles it.
Three Data Sources, Three Formats, One Reconciliation Spreadsheet
The July reconciliation spreadsheet draws from three distinct data sources, and each introduces its own manual entry friction:
Source 1: STP payroll system data. For the majority of employees, the payroll system holds the correct year-to-date figures — gross payments, tax withheld, super contributions — but those figures exist inside the payroll software, not in a format the reconciliation spreadsheet can directly consume. Exporting a payroll register report to CSV is step one. Matching each row in that CSV to the corresponding PAYG summary — by employee name or TFN — is step two. Step two is manual unless every summary has already been extracted to a matching row-and-column format. The data exists; the connection between the payroll CSV row and the summary PDF does not — and building that connection is typing.
Source 2: Pre-STP payment summaries. Employees who worked part of the financial year before the company transitioned to STP — or whose employer changed payroll providers mid-year, leaving the pre-transition period outside STP reporting — have a traditional PAYG payment summary for the pre-STP months. These summaries exist only as PDFs generated by the previous payroll software or as scanned copies of printed certificates. They have no corresponding row in the current STP data, so the reconciliation spreadsheet must include them as independent entries. Every field on every pre-STP summary — ABN, TFN, gross, tax withheld, RFBA, RESC, lump sum amounts — must be retyped because no electronic extract exists.
Source 3: Third-party provider payment summaries. Contractors paid under a voluntary withholding agreement, employees of related entities that share payroll administration but operate under separate ABNs, and workers who received payments from a labour-hire firm that issued its own PAYG summary — these certificates arrive in the payroll inbox as PDF attachments or physical mail. Each one is a single document with 15-20 fields that must be extracted and added to the reconciliation spreadsheet. Unlike the payroll system data, there is no CSV export, no STP record, no electronic counterpart. The only path from that PDF to the spreadsheet is through a keyboard. This is also the scenario encountered by UK payroll teams processing P60 manual data entry and P45 paper processing — the document type changes, the geography changes, but the core problem of extracting data from a paper or PDF certificate into a reconciliation spreadsheet remains identical.
The Costs Nobody Tallies: ATO Queries, Audit Friction, and the Employee Inquiry Flood
The direct cost of manual entry — hours spent typing — is the smallest component of the total burden. Three downstream costs are larger, harder to quantify, and almost never budgeted for in payroll planning:
ATO data-matching query resolution
The ATO's data-matching system compares every employee's tax return against the PAYG data reported by the employer. The Inspector-General of Taxation found that 85-89% of flagged cases result in an adjustment — meaning the overwhelming majority of mismatches are real errors, not false positives. A transposed TFN digit (employee 123 456 789 typed as 123 456 798) creates a mismatch that survives three systems: the employee's myGov pre-fill shows the wrong employer, the employee disputes it, the ATO queries the employer, and the payroll officer must locate the original TFN declaration form to prove the correct number. Resolution time per query: 30 minutes to two hours. Number of queries from a batch of 100 manually typed summaries where the payroll officer's error rate is a conservative 1%: at least one per year — and often more, because fatigue compounds in an eight-hour data entry session.
External audit friction
When the external auditor selects 20 employees for substantive testing of payroll expenses, they need to trace each employee's PAYG summary figures back to the payroll system, the bank statement showing the payment, and the quarterly BAS. If the summaries exist only as unextracted PDFs and the reconciliation spreadsheet was built through manual typing, the auditor cannot independently verify the extraction accuracy without re-keying a sample themselves. This extends the audit timeline and increases billable hours — not because the data is wrong, but because it cannot be demonstrated as right without repeating the manual process. A single spreadsheet generated from automated extraction, in contrast, provides the auditor with a traceable source that can be sampled against the original PDFs without re-entry.
Employee inquiry flood during tax time
Australians can lodge their tax returns from 1 July. The moment an employee logs into myGov and sees their income statement, any discrepancy between what appears on the pre-filled ATO data and what they expect — based on their final payslip, their understanding of their salary, or a previous year's summary — generates a call or email to the payroll department. During the two weeks between 1 July and 14 July, a payroll officer for 120 employees typically fields 15-25 employee inquiries about summary figures. Each inquiry requires pulling up the original summary, the payroll register, and the employee's final payslip to explain the discrepancy — which is often not a discrepancy at all, but a timing difference (a June bonus paid in July, a salary sacrifice arrangement the employee forgot about, a reportable fringe benefit the employee did not realise was reportable). If the reconciliation spreadsheet was built manually, the payroll officer is looking at their own data entry to answer the question — with no way to confirm whether the figure the employee sees is correct or a transcription error without rechecking the original PDF.
What the STP Transition Was Supposed to Fix — and What It Left Behind
Single Touch Payroll was introduced with the promise of eliminating PAYG payment summaries. For most standard employees at most employers, it succeeded: once the employer finalises STP data by 14 July, the employee accesses their income statement through myGov and no paper or PDF summary is needed. The ATO receives the data directly with each pay run; the end-of-year finalisation declaration confirms it.
But the STP promise breaks in three specific scenarios that collectively affect thousands of Australian payroll teams every July:
First, the pre-STP tail. Any employer that transitioned to STP partway through a financial year — or that changed payroll software and cannot report the pre-migration period through the new system's STP channel — still owes traditional PAYG payment summaries for the pre-STP period. These summaries exist as PDFs generated by the old software, and the ATO requires employers to retain them for five years. When the new payroll officer in July 2026 needs to reconcile the 2023-24 financial year (because a former employee raised a query on their 2024 tax assessment), those pre-STP summaries are PDFs in an archive folder — not rows in the STP data.
Second, closely held payees. Directors, family members of a family business, and certain trust beneficiaries classified as closely held payees have a separate STP finalisation deadline of 30 September — two and a half months after the standard employee deadline. Many employers choose to issue these payees a traditional PAYG payment summary as an interim document while STP data is still being finalised. Each closely held payee summary arrives as a PDF in July — and needs to be extracted and reconciled separately from the STP data that will not be finalised until September.
Third, third-party certificates. Labour-hire firms, umbrella companies, and related entities operating under different ABNs issue their own PAYG summaries to workers who may also appear on the primary employer's payroll for a different engagement. These certificates arrive from outside the organisation's payroll system. They have no STP counterpart in the employer's own reporting. And every field on every one of them — ABN, TFN, gross, tax withheld — must be manually entered into the reconciliation spreadsheet because no automated pipeline connects a third party's PDF to the employer's reconciliation process.
The STP narrative — "PAYG summaries are obsolete" — is correct for the majority of straightforward employee scenarios. It is incorrect at precisely the edges where manual data entry workload concentrates. A payroll team that processes 100 employees through STP and 12 employees through traditional summaries does not spend 12% of its reconciliation time on traditional summaries. It spends 80% — because STP data is already electronic, and the traditional summaries are the ones that require typing.
The same pattern appears in every jurisdiction that has modernised employer tax reporting: PAYG summary extraction in Australia mirrors P60 extraction in the UK — both reconcile modern digital reporting against legacy paper certificates that refuse to disappear.
Frequently Asked Questions
Why can't I just use the CSV export from my payroll software for the reconciliation?
A payroll CSV export gives you the data as recorded in your payroll system. The PAYG payment summary gives you the data as reported to the employee and the ATO. The two can differ — and the differences are exactly what reconciliation is designed to catch. A manual pay adjustment entered directly in the payroll system after the final pay run, a bonus paid in June but processed in the July pay cycle (which belongs to the next financial year), or a salary sacrifice arrangement that was incorrectly coded as standard SG rather than RESC — all create discrepancies between the CSV and the summary. The CSV tells you what the payroll system thinks it paid; the summary tells you what the employee and ATO were told was paid. Reconciliation requires both sources, and the gap between them is what manual entry creates — because someone has to key the summary data into the same format as the CSV to run the comparison.
Does STP finalisation mean I can skip the manual reconciliation step entirely?
No. STP finalisation confirms that the data you reported throughout the year is correct — but it does not independently verify that the data matches the payment summaries you issue, your general ledger, or your quarterly BAS. The ATO will match your STP data against employee tax returns regardless. If an employee's tax return declares different income than what you reported through STP, the ATO's system flags the discrepancy — and the investigation traces back to your payroll records. STP automates the reporting pipeline; it does not replace the verification step that confirms the pipeline carried the right numbers.
What's the actual time difference between manual entry and automated extraction for 100 summaries?
Manual entry for a single PAYG payment summary — typing 15-20 fields including ABN, TFN, gross payments, tax withheld, RFBA, RESC, allowances, and lump sum amounts, with a cross-check against the payroll register — takes approximately 2-3 minutes per summary when done carefully. For 100 summaries: 3.5-5 hours of typing, not including the time to handle discrepancies found during entry. Automated extraction — uploading all 100 summaries in a batch and receiving one consolidated spreadsheet — takes a few minutes of processing time, followed by 15-30 minutes of reviewing computed validation flags. The difference is roughly 3-4.5 hours per 100 summaries — and the time is saved at the point in the July calendar when payroll teams have the least time to spare.
How do pre-STP paper summaries from years ago affect the current reconciliation?
During an ATO audit or review of a prior tax year — which the ATO can initiate up to four years after the assessment for most taxpayers, and indefinitely for fraud or evasion — the employer must produce the original payment summaries for the year under review. If those summaries were generated by payroll software that no longer runs on current systems (a MYOB desktop version retired in 2020, for example), the only accessible record is the scanned PDF or printed copy. When the auditor asks for a spreadsheet of all summaries issued for that year, the payroll team faces a choice: retype every field from every scanned summary, or extract them from the scans into a spreadsheet. The further back the tax year, the higher the probability that the original payroll data is inaccessible — and the more valuable automated extraction becomes as the only path from a filing cabinet of paper to a spreadsheet the auditor can review.
What about contractors paid under a voluntary withholding agreement — do they need a PAYG summary too?
Yes. If you have entered into a voluntary PAYG withholding agreement with a contractor, you must issue them a PAYG payment summary — business and personal services income (NAT 72545) by 14 July. This is a separate summary type from the individual non-business form, with different field labels, but the same core data: gross payments and tax withheld. These summaries do not flow through the regular STP channel. They exist as separate PDFs — typically one per contractor — and each one needs to be extracted and included in the annual report lodgment. For a construction company with 15 subcontractors on voluntary withholding agreements, that is 15 additional summaries to process in July, each with its own extraction requirement.