Xero Payroll

Send approved timesheets straight to Xero Payroll.

BondiByte connects to a Xero Australia Payroll organisation, maps your staff and pay items to Xero, and sends approved timesheets across as draft Xero timesheets, ready for your payroll team to review.

Xero Payroll stays the payment authority. BondiByte classifies approved time, and nothing reaches Xero until an administrator clicks Send.

Start free trial Book a demo

Prefer written steps? Read the Set up Xero Payroll guide.

The Xero Payroll connection card in BondiByte Configuration, showing the connected organisation, connected by, and last connection check

One connection, checked before anything sends.

Connect in minutes

OAuth connection to a Xero Australia Payroll organisation
Map BondiByte staff to Xero employees
Test the connection any time
Disconnect without losing timesheet history

Two ways to handle rates

Pay Levels off: every approved hour to one default Xero earnings rate
Pay Levels on: map each pay item to a Xero earnings rate
Choose Xero or BondiByte as the payroll rate source
Either way, the send itself is hours only

Payroll calendars checked first

Every mapped employee's Xero payroll calendar compared to your roster period
Aligned or not aligned, calendar by calendar
A plain-language fix when they do not line up
Checked again automatically at Preflight

Send with a transfer register

Approved timesheets sent as draft Xero timesheets
One logical timesheet per employee, per period
Duplicate-safe, with automatic retry
Nothing sent until an administrator clicks Send

The Payroll calendars panel in BondiByte, comparing the roster period against three Xero payroll calendars, with Aligned and Not aligned states

Checked before you send

Payroll calendars, lined up before anything moves.

Xero pays each employee on a payroll calendar with fixed period dates, and only accepts a timesheet whose dates match one of those periods. BondiByte compares your roster period against every Xero payroll calendar your mapped employees sit on, and explains the fix in plain language when a calendar's periods start on a different weekday.

The prerequisite is a Xero Australia Payroll organisation with a payroll calendar that starts on the same weekday as your BondiByte roster period.

Roster to Xero

From an approved timesheet to a draft in Xero.

Once staff and pay items are mapped, an approved timesheet for the roster fortnight becomes a draft Xero timesheet: one logical timesheet per employee and period, checked at Preflight, duplicate-safe to send, and tracked in a transfer register until Xero confirms it.

Nothing sent until you click Send. Xero stays the payment authority. Hours only, whichever rate source you choose.

Timesheet approved

Staff and pay items mapped

Preflight checked

Sent as a draft

Reviewed in Xero

Preflight first, then send.

Preflight checks the selected fortnight against your mappings and payroll calendars, and shows what is ready before anything reaches Xero.

The Send to Xero panel in BondiByte Timesheets, showing the selected fortnight, a Preflight summary of approved timesheets and hours, and the transfer register with a Sent to Xero status

Xero Payroll, plainly.

What exactly does BondiByte send to Xero?

Approved timesheet hours, sent as draft Xero timesheets, one logical timesheet per employee for the roster period. BondiByte does not send invoices, pay runs, leave, or new employees, and it does not sync with MYOB or Employment Hero through this connection.

Does BondiByte become our payroll system?

No. Xero Payroll stays the payment authority. BondiByte classifies approved time against your pay items and sends it across; your payroll team still reviews and processes it in Xero.

What happens with Pay Levels off?

Every approved hour is sent against one default Xero earnings rate that you choose. There is no per-item mapping to set up.

What happens with Pay Levels on?

Each pay item, such as weekday, Saturday, Sunday or public holiday, is mapped to its own Xero earnings rate from inside the Pay Level line item editor. Items without a mapping are held at send time instead of going to Xero under the wrong rate.

What is the payroll rate source, and does it matter which one we pick?

It decides where the dollar rate comes from. Choose Xero and Xero's earnings rate supplies the rate, so a pay item does not need a BondiByte rate. Choose BondiByte and your BondiByte rates stay authoritative. Either way, BondiByte only ever sends hours.

What do I need in Xero before connecting?

A Xero Australia Payroll organisation with a payroll calendar that starts on the same weekday as your BondiByte roster period. The Payroll calendars panel checks this for every mapped employee and explains the fix when a calendar does not line up.

Can a timesheet reach Xero twice by mistake?

No. Sending is duplicate-safe: each employee and period combination is one logical Xero timesheet, and the transfer register tracks its status through Ready, Sending, Sent to Xero, Needs mapping, Needs attention or Failed, with automatic retry.

Go deeper into pay and payroll.

Each of these has its own page: why it exists, how it works, and the controls that stay with managers.

Feature

Send timesheets to Xero without re-keying them.

Start your free trial, or book a demo to see the Xero Payroll connection, mapping, and Send to Xero workflow.