Accountant STP Finalisation Checklists: Use case and AI Confidentiality
Single Touch Payroll finalisation is the year-end step where a business tells the ATO its payroll reporting is complete, and an accountant’s checklist records what was done for each person. It is a document staff paste into ChatGPT or Claude to tidy the wording or to ask what is still open. The checklist names the client’s employees, who are not the practice’s clients, along with a tax file number, a director’s fees, a dismissed employee and a casual who was missed. This page marks every item in a realistic checklist, separates the public rules from the client facts, and shows how the same checklist is kept on Ermos inside the practice.
The STP finalisation checklist
Kept for each payroll client at year end and when an employee leaves, to record who has been finalised, by when and what is still open. The ATO says a finalisation declaration is lodged by 14 July, by providing a finalisation indicator for each employee as part of STP reporting, with a later date for closely held payees.
STP finalisation checklist
Northgate Partners · Monday 16 November 2026
Client. Harbourline Joinery Pty Ltd (ABN 51 824 753 556), payroll run in Xero by Rachel Dunne1. Prepared by Jessie Whitlam10. Reviewer: Sarah Lindqvist (review pending).
| A. Year ended 30 June 2026 | ||
| Check | Result | Note |
| STP is reported under the same ABN as the activity statement | Done | Matches. |
| Every person paid in the year was finalised, including casuals and former staff | Late | Bernard Bandara, casual labourer, last paid Friday 13 March 2026, was left off the 14 July finalisation. Rachel finalised him on Monday 9 November. We do not know whether the ATO has been in touch.5 |
| Due dates applied | Done | Arm’s length employees by 14 July. Where there are both kinds of payee, closely held payees by 30 September.7 Rachel Dunne and Sione Tupou2 are arm’s length and were finalised in July. |
| Closely held payee reported and finalised | Done | Priya Okafor, director: $24,000 director’s fees for the year, nothing withheld.4 Finalised Tuesday 29 September, together with Daniel Okafor, the other closely held payee. |
| Tax file number matches her records | Open | Correct TFN 123 456 782, keyed wrongly in Xero until Wednesday 28 October.3 The finalised record went in under the old number. How a finalised record with a wrong number is corrected is not confirmed, and Jessie will ask on the agent line. |
| Reportable fringe benefits (FBT year 1 April 2025 to 31 March 2026) | Open | Daniel Okafor’s car, 40% private use from the logbook.8 The FBT workings are not final, so we do not know whether any amount is reportable. Marcus Hale’s ute use began after he started on 4 August 2026. |
| Year-to-date amounts agree to W1 and W2 on the activity statements | Done | Checked by Jessie on Thursday 5 November. |
| B. Year ending 30 June 2027, to date | ||
| Leaver finalised when employment ended | Not finalised | Sione Tupou, terminated Saturday 19 September 2026. Final pay included 23.4 hours of unused annual leave. He has lodged an unfair dismissal application with the Fair Work Commission.6 The indicator stays off because a settlement payment may follow. How any settlement payment is reported is for Sarah and has not been checked. |
| Back pay in the pay event | Done | Marcus Hale: back pay of $1,846 for the first two pays at the apprentice rate, in the pay event of Friday 6 November.9 Super on the back pay not yet checked. |
| Corrections lodged by update event, employee told, W1 and W2 revised | Ongoing | Each correction is lodged as soon as it is found. |
An invented checklist about invented people. The ABN and TFN are the ATO’s published example values. Hover or tap any highlighted item for the analysis; the full list is below.
Payroll finalisation checklist tracker
An Agent+ that prepares the finalisation checklist from a client's payroll records. It sets each employee against your checklist items, including leavers and payments with nothing withheld, and records what is still open for the payroll officer.
What it does
- Reads payroll records and the employee list
- Builds the checklist against your own items
- Marks open items, leavers and unusual payments
What stays with your people. A payroll officer completes each item and decides when a client is finalised. The agent builds the list; it does not finalise anything.
An Agent+ is built once and anyone in the practice can run it. It works from your own documents and runs on Ermos Dominion, the AI unit in your office, or on Ermos Edge, your own instance in an Australian data centre.
What leaves the firm
- 1The client, its ABN and its payroll set-up
Names the client, the system it uses and who runs its payroll. Confidential client information under APES 110 (R114.2), and the key that ties every employee entry below to a real business. APES 110 confidentiality guide.
Frontier Models (ChatGPT, Claude) Transmitted to the provider, generally offshore on personal plans Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Payroll finalisation checklist tracker. Builds the year-end finalisation checklist for each payroll client from the payroll records, marking what is complete and what remains open for the payroll officer. See the use case - 2Employees named in the checklist
The client’s staff are not the practice’s clients and have never dealt with it. Each is an individual whose personal information the practice holds only because it supports the payroll, and who has not been asked about any of this. Privacy Act guide.
Frontier Models (ChatGPT, Claude) Employees who are not clients transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Payroll finalisation checklist tracker. Builds the year-end finalisation checklist for each payroll client from the payroll records, marking what is complete and what remains open for the payroll officer. See the use case - 3A tax file number
The Privacy (Tax File Number) Rule bears on how tax file number information is used, disclosed and secured by a file number recipient. A payroll correction is a tax purpose; a frontier model provider is not someone who needs access for that purpose. A person in possession or control of a record containing TFN information is a file number recipient under section 11(1) of the Privacy Act. Tax file numbers guide.
Frontier Models (ChatGPT, Claude) Transmitted to the provider, which is hard to reconcile with the TFN Rule Ermos Edge Stays on your instance in Australia. If it sits in a permitted excerpt, it goes only to a named Australian provider that answers and keeps nothing Ermos Dominion Stays on the unit in your office Use case Payroll finalisation checklist tracker. Builds the year-end finalisation checklist for each payroll client from the payroll records, marking what is complete and what remains open for the payroll officer. See the use case - 4A director’s fees and nothing withheld
The earnings of a named individual, a director and the owner’s spouse, and the fact that no tax was withheld. The ATO treats a director or family member as a closely held payee. Personal financial information, and a compliance question the client has not yet been advised on. Privacy Act guide.
Frontier Models (ChatGPT, Claude) A director’s earnings and nil withholding transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Payroll finalisation checklist tracker. Builds the year-end finalisation checklist for each payroll client from the payroll records, marking what is complete and what remains open for the payroll officer. See the use case - 5A casual missed from the finalisation
The client missed a deadline for one person and fixed it almost four months later. A compliance lapse recorded against a named worker. The ATO says its quick checks include casual and former employees who have not been paid for a while, and that finalising on time helps avoid follow-up reminders. TPB Code guide.
Frontier Models (ChatGPT, Claude) A compliance lapse transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Payroll finalisation checklist tracker. Builds the year-end finalisation checklist for each payroll client from the payroll records, marking what is complete and what remains open for the payroll officer. See the use case - 6A dismissed employee and his claim
That a named person was terminated, his final pay, his leave balance and that he has lodged an unfair dismissal application. Highly sensitive to him and to the client, and the practice’s decision to leave his record open depends on a dispute it does not control. The ATO says to remove the indicator if another payment is expected and to make another declaration for a one-off payment. APES 110 confidentiality guide.
Frontier Models (ChatGPT, Claude) A live employment dispute transmitted Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Payroll finalisation checklist tracker. Builds the year-end finalisation checklist for each payroll client from the payroll records, marking what is complete and what remains open for the payroll officer. See the use case - 7The due dates
The ATO says that where a business has both closely held payees and arm’s length employees, the arm’s length employees are finalised by 14 July and the closely held payees by 30 September (Concessional reporting, updated 23 October 2026). The sentence carries no client data. Which payees are closely held is the client’s own information.
Frontier Models (ChatGPT, Claude) Public ATO rule with no client data in the wording Ermos Edge Nothing to protect in a public rule Ermos Dominion Nothing to protect in a public rule Use case Payroll finalisation checklist tracker. Builds the year-end finalisation checklist for each payroll client from the payroll records, marking what is complete and what remains open for the payroll officer. See the use case - 8The director’s car and its private use
A named person’s vehicle, a logbook percentage and an unfinished fringe benefits calculation. Personal information about how a director uses a company asset, and a figure no tool can complete without the logbook. The ATO says reportable fringe benefits for the FBT year to 31 March 2026 may need reporting through STP at finalisation. Privacy Act guide.
Frontier Models (ChatGPT, Claude) A private-use percentage and an open FBT question transmitted Ermos Edge Stays in Australia, but the reportable amount is still a calculation a person must make Ermos Dominion Stays on the unit, but the reportable amount is still a calculation a person must make Use case Payroll finalisation checklist tracker. Builds the year-end finalisation checklist for each payroll client from the payroll records, marking what is complete and what remains open for the payroll officer. See the use case - 9An underpayment and back pay
An amount owed to a named employee for pay at the wrong rate, with the date it was fixed. Information the employee may not have seen in this form, and a figure a person must check along with the superannuation on it. Privacy Act guide.
Frontier Models (ChatGPT, Claude) An underpayment transmitted before the employee has seen it Ermos Edge Stays in Australia, but a person must still check the back pay and the super on it Ermos Dominion Stays on the unit, but a person must still check the back pay and the super on it Use case Payroll finalisation checklist tracker. Builds the year-end finalisation checklist for each payroll client from the payroll records, marking what is complete and what remains open for the payroll officer. See the use case - 10The preparer and the reviewer
Ties the checklist to a junior employee working under supervision (APES 110 R113.2) and shows that the partner has not yet reviewed it, which makes any leak traceable to the practice. Checking AI output guide.
Frontier Models (ChatGPT, Claude) Transmitted, and the leak is traceable to you Ermos Edge Stays on your instance in Australia; leaves only inside a permitted excerpt, per question, to the named provider Ermos Dominion Stays on the unit in your office Use case Payroll finalisation checklist tracker. Builds the year-end finalisation checklist for each payroll client from the payroll records, marking what is complete and what remains open for the payroll officer. See the use case
What happens in Frontier Models (ChatGPT, Claude)
- The whole document is transmitted to the provider’s servers. On personal plans the user cannot choose where it is stored or processed, and for the major providers that has generally meant outside Australia, under that country’s legal process. Some business plans offer storage in Australia, but the provider still receives the content.
- On consumer tiers, prompts can be retained and used to train future models.
- The provider’s staff and systems can reach the content under the provider’s own policies.
- Once sent, the firm no longer controls it. Retention and deletion happen on the provider’s terms.
The same document on Ermos
Ermos Dominion
The document is drafted on a unit in your office, from your own templates and the client file. Every marked item stays on the unit, which keeps working with the internet switched off. Nothing in it is transmitted to an AI provider, so there is no disclosure to analyse: the confidentiality work is the same as for your file server.
Ermos Edge
Your documents, the index and your access boundaries stay on your own instance in an Australian data centre. When a staff member asks for this draft, only their question and the excerpts they are permitted to see go to a named Australian provider, who is contractually barred from keeping the content or training any model on it. Nothing is processed outside Australia. Where a checklist carries a tax file number, the access boundaries you set decide who can raise an excerpt containing it, and the provider keeps nothing once the answer is returned.
| Frontier Models (ChatGPT, Claude) | Ermos Edge | Ermos Dominion | |
|---|---|---|---|
| Where the document is processed | Provider servers, generally offshore on personal plans | Your instance in an Australian data centre; answers generated in Australia | The unit in your office |
| Who can read it | Provider staff and systems, under policy | Your staff, within the boundaries you set. The named Australian provider processes only permitted excerpts, under contract, and keeps nothing | Your staff only |
| Is it kept | On the provider’s terms | Kept on your instance; the provider is barred from retaining it | Stays on the unit |
| Can it train a model | On consumer tiers, yes | No, by contract | Only your own unit learns from it, on your hardware |
Part of Use cases in accounting firms. See how this works in practice: Client correspondence on Ermos.
Common questions
Do ChatGPT and Claude use the information in an STP finalisation checklist?
Can we use ChatGPT or Claude for an STP finalisation checklist if we remove the employees' names?
What travels with an STP finalisation checklist when it is uploaded to ChatGPT or Claude?
How can an accounting practice use AI for an STP finalisation checklist without sending it to ChatGPT or Claude?
When does Single Touch Payroll have to be finalised?
What can be done if a mistake is found after finalising?
What happens if an employee is finalised and then paid again?
See Dominion answering from your own documents.
A demonstration takes 30 minutes, uses no client data, and comes with no obligation.
Book a demo