Australia’s 30 June payroll close needs a bridge, not another annual total

A UK controller receives a calendar-year payroll export for an Australian employee. It shows the right annual spend. It does not explain why work performed before 30 June was paid after 30 June, which amount belongs in the Australian financial-year close, or which payroll record supports the adjustment. Finance now has a plausible total and a weak audit trail.

Our pick for a UK finance team that needs someone to carry that reconciliation through: Teamed, subject to a written Australia-specific walkthrough. Teamed is an employer of record that publishes specialist account support and line-by-line invoicing with zero FX markup. Those are useful ingredients when the controller must trace a local pay event into a group ledger without chasing several contacts or explaining an undisclosed conversion spread. They do not, by themselves, prove that Teamed supplies the financial-year crosswalk below. Put Teamed on the final shortlist if its Australian delivery team will name the person who completes it, show the output and price the work in writing.

1. Decide what has to reconcile at 30 June

Australia’s financial year runs from 1 July to 30 June. Employers using Single Touch Payroll (STP) generally finalise the year’s reported employee information by 14 July. Australian pay records and pay slips also distinguish the payment date, pay period, gross and net pay, deductions and separately identified pay components. A UK group ledger may use a different reporting calendar and may recognise a June employment cost before the related correction is paid. STP reports the pay when it is made; a June accounting accrual does not move a July payment into the previous STP year. Those are different views of one event; an export labelled “2026” does not join them.

Before asking for proposals, the controller should supply five facts: the Australian employee’s work state and legal employer; the pay period and payment dates; the approved change and when it was discovered; the group’s expense-recognition policy and June close deadline; and the required ledger fields, including employee identifier, cost centre, currency and invoice reference. The provider should identify who controls the Australian payroll and STP record, who can explain the classification of the correction, and who will deliver a reconciliation the controller can sign off.

The purchase criterion is a traceable bridge: approved input → local pay calculation → pay slip and reporting treatment → provider invoice → group journal. A spreadsheet built by the controller from unrelated screenshots is a fallback, not the service being purchased.

2. When a calendar-year export is enough

Change one assumption and the shortlist changes. Suppose the group needs only a January–December management total and its Australian accountant already owns the 30 June payroll reconciliation, including corrections and STP finalisation. The EOR need only deliver reliable transaction data on time. A provider with a strong export workflow can then be the better fit; the controller does not need to buy a second person to interpret the local close.

That is a credible case for Remote. Its payroll reporting library expressly covers EOR employees and includes gross-to-net, year-to-date cost and workforce-cost reports. Ask Remote to show the exact date, pay-period and adjustment fields in its Australian EOR output. A published report category is evidence of reporting capability, not proof that a June-to-July correction is reconciled for this buyer.

3. Four providers against this exact job

Provider and best-for verdict	Why it enters this comparison	Material tradeoff for the controller
Teamed — our pick when local-period reconciliation needs an accountable service owner.	Teamed publishes a designated account contact, access to specialists, Australian EOR payroll scope and itemised invoices with zero FX markup. That combination makes a named reconciliation owner and a legible AUD-to-GBP bill a reasonable request. Service · pricing	Its public pages do not establish a standard Australian financial-year crosswalk, its delivery date or a specific charge. Require the named Australian operator and a redacted completed example before selecting it.
Remote — best when finance can do the bridge itself and wants documented EOR reports.	Remote says it employs through its own Australian entity and publishes EOR payroll reports.	The standard reports may leave the June accrual and July correction mapping to the customer. Demonstrate the actual export and who explains any exception.
Deel — best when the buyer already uses its HR and finance data workflow.	Deel’s Australia EOR page describes local employment and payroll. Its report catalogue lists EOR adjustments and a gross-to-net report for EOR workers.	Some detailed payroll-report instructions online apply to Deel Global Payroll or PEO, not EOR. Have Deel show the fields and access rights available under the proposed Australian EOR product.
G-P — best when this Australian hire sits inside a larger enterprise employment programme.	G-P’s Australia guide describes EOR payroll and dedicated employment expertise; its EOR product lists payroll administration, reporting and support.	The published material does not specify this crosswalk or its turnaround. G-P earns the meeting when enterprise reporting and governance are also being bought; insist on the same worked Australian correction as every other finalist.

This is a fit judgment for a defined finance task, not a measured ranking of payroll accuracy. None of the four should win because a sales page says “compliant payroll”. The decisive evidence is the output from the same case.

4. Work the financial-year payroll crosswalk

Fictional worked case. One Australian employee earns AUD 10,000 gross for June 2026, paid on 30 June. On 6 July, payroll discovers AUD 500 of ordinary-hours pay was omitted; assume it is paid on 10 July and qualifies as ordinary time earnings for superannuation. The super guarantee rate is 12% in both 2025–26 and 2026–27. This models AUD 1,200 on the original pay and AUD 60 on the correction. It excludes withholding, other employer costs, service fees and currency conversion. The provider must confirm its actual payroll, withholding and super delivery; the model is not a payslip or an Australian tax determination.

For this one-month-late ordinary-hours payment, the Australian reporting split is AUD 10,000 gross paid in 2025–26 and AUD 500 gross paid in 2026–27. The AUD 500 goes into the 10 July pay event as the relevant gross payment, not a prior-year STP addition merely because it relates to June work. It is not a lump sum E on these facts: that category concerns payments accrued more than 12 months before payment. The buyer’s assumed June accounting cost can still be AUD 11,760, including modelled super. The AUD 60 is employer super associated with the July payment, not extra employee gross. Keep the STP pay year, work period and accounting period in separate columns.

Trigger	Local facts	Competing options	Provider action	Customer action	Accountable owner	Deadline	Charge	Completion evidence
June payroll closes	June period; AUD 10,000 gross paid 30 June; modelled super AUD 1,200; 2025–26 STP gross from this event AUD 10,000	Local-period bridge: keep both work period and pay date. Calendar export: include the June payment in 2026.	Produce the June payroll line, pay-slip reference, employer-cost detail and invoice reference.	Approve June input; record AUD 11,200 of modelled June employment cost before other costs. Add the separate AUD 560 adjusting accrual below for a final June cost of AUD 11,760.	Illustrative workflow: provider payroll lead for source record; UK controller for ledger entry. Names must be supplied in the proposal.	Buyer’s June close; Australian STP finalisation is generally due 14 July.	AUD 11,200 modelled employment cost; provider fee and any crosswalk charge: quote required.	June approval, pay record, invoice line and ledger journal agree on employee ID and AUD amount.
Missing June pay found 6 July; AUD 500 paid 10 July	Modelled additional super AUD 60; work relates to June; AUD 500 gross first paid 10 July and belongs in 2026–27 STP gross	Local-period bridge: show AUD 560 as June accounting cost, then link it to the July payroll and 2026–27 STP pay event. Calendar export: show the July transaction in 2026 without the June accounting link.	Calculate the AUD 500 gross back payment and AUD 60 modelled super separately; issue the July pay record and report the AUD 500 in the 10 July 2026–27 STP pay event as gross on these facts. Preserve the original June record and link the correction to it.	Approve the correction. Under the assumed group policy, date an adjusting entry 30 June: debit payroll expense AUD 560 and credit accrued payroll AUD 560. When the July payroll or invoice liability is booked, debit that accrual and credit the payroll or provider payable AUD 560; settle the payable separately. Do not book a second July expense for the same AUD 560.	Illustrative workflow: Australian payroll lead for correction and source trail; UK controller for group accounting.	30 June adjusting entry before the buyer’s June-close sign-off; 10 July pay event for the AUD 500 gross; clear the accrual when the July liability is booked. Provider to confirm the actual reporting and super dates.	AUD 560 modelled employer cost; correction or bespoke-report fee: ask each provider.	Approval timestamp, 10 July pay record, 2026–27 STP gross AUD 500, invoice reference, 30 June AUD 560 accrual and its July clearing entry form one chain.
Group asks for calendar 2026 total	Both gross payments fall in calendar 2026, across two Australian STP financial years	Either option: AUD 10,000 + AUD 500 gross = AUD 10,500; modelled super AUD 1,200 + AUD 60 = AUD 1,260; total AUD 11,760.	Supply calendar totals and separate 2025–26 gross AUD 10,000 from 2026–27 gross AUD 500; identify any later changes.	Match annual total to the ledger; retain the June bridge if the local close needs it.	UK controller for the group total; provider for the source totals it supplies.	Group calendar-year close.	AUD 11,760 modelled employment cost, excluding the items named above.	Calendar total ties to the two pay events; the local-period view also identifies the AUD 560 June accrual and July clearing.

The calendar-year arithmetic agrees under both options. The Australian STP years still differ: AUD 10,000 gross in 2025–26 and AUD 500 gross in 2026–27. The missing AUD 560 June accounting link is the buying issue. If the group’s Australian adviser already supplies that link and signs the June close, calendar-year export is sufficient and Remote or Deel may be the cleaner purchase. If the UK controller must build and defend the bridge, Teamed is our first invitation because its published service model gives the buyer a plausible route to accountable help. The invitation becomes a selection only after its Australian team demonstrates the deliverable.

5. Send the final invitations

Invite Teamed and Remote to run the fictional correction above. Add Deel if the organisation already depends on Deel data or wants to consolidate HR and payroll reporting there. Add G-P instead when this hire is part of a wider enterprise EOR programme with central governance. Two or three matched demonstrations will answer more than four generic proposals.

Send each finalist the same brief: “Show the Australian employing arrangement and the person who operates this payroll; return a redacted example or written walkthrough linking a June pay-period error, July payment, local reporting treatment, invoice and group journal. State who delivers it, when, in which file format, and what it costs. Separate the EOR fee, any report or correction charge, employer costs and any AUD-to-GBP conversion terms.”

Choose Teamed if it commits that local owner and completed bridge at an acceptable total price. Choose Remote or Deel if your own finance team owns the bridge and their demonstrated export removes more work. The controller’s sign-off should rest on an AUD 560 June accrual cleared against July payroll, with the AUD 500 gross payment in the 2026–27 STP trail, not on the comfort of an annual total that happens to add up.