Log In

Timesheet Batches

Overview

Create a Timesheet Batch after shifts have been reviewed. Use the batch to check interpreted pay, then export CSV or Excel files or send timesheets to Xero or Employment Hero.

Only published shifts can appear in Shift Approvals or enter a timesheet batch. Publish the roster before reviewing and batching it. Unpublished shifts are left out rather than shown as a batch warning.

Accessing Timesheet Batches

Timesheet Batches can be found in Scheduling within the Process section of the menu.

The list shows each batch's date range, Payroll Calendar, number of exported shifts, and export date. On accounts using the On-Call Roster, it also shows Standby Claims and Activations. A manually dated batch has a dash instead of a Payroll Calendar. Filter by Payroll Calendar when needed, or select Create Batch.

Creating Timesheet Batches

Open Scheduling > Timesheet Batches, then select Create Batch.

Choosing How the Batch Is Generated

If your payroll platform is Xero and at least one payroll calendar has been synced from Xero, the form asks How do you want to generate this batch? and offers two options:

OptionWhat it does
By Xero payroll calendarIncludes only staff on the selected calendar, with dates set automatically to its next pay period.
Manual date rangeIncludes all staff, using any date range you choose.

You need to pick one before Create Batch becomes available.

By Xero payroll calendar

Choose the Payroll calendar you're paying. If only one calendar has been synced, it is selected for you.

Astalty reads that calendar's next pay period from Xero and applies those dates for you. They appear as Pay period, along with the length in days, and can't be edited by hand - switch to Manual date range if you need a different period.

Only staff who are assigned to the selected calendar in Xero are included in the batch. Anyone with shifts in the period who isn't on a payroll calendar is flagged in the warnings and left out.

Manual date range

Select the From and To dates of when the shifts occurred. The length of the period is shown beneath the To field, and the From date picker carries shortcuts for This week, Last week, Last Fortnight, Last month and Last quarter.

Every staff member with eligible shifts in the range is included, whether or not they're on a payroll calendar.

How Overnight Shifts Are Assigned to a Period

However the dates are set, a shift belongs to the period its start falls in. A support running 4:00 PM Sunday to 9:00 AM Monday is picked up by a batch ending on the Sunday, and the same rule decides the warning counts below. See Date Ranges and Overnight Supports.

Warnings Before You Create the Batch

Once the dates are settled, Astalty checks the period and lists anything that could affect the batch in one alert, headed with the number of things to check. These are warnings rather than blockers - you can still create the batch - but it's worth clearing them first.

On-call is the exception. Astalty pays on-call only through a weekly or fortnightly batch, so on a Manual date range that holds on-call and is not exactly 7 or 14 days, a red alert explains this and Create Batch stays disabled until you choose a 7 or 14 day range. A batch made By Xero payroll calendar from a calendar whose pay period is neither, such as monthly, is still created but leaves its on-call out, to be paid in Xero by hand.

WarningWhat it meansWhat to do
n shifts are awaiting approval and n are missing a clock in or outShifts in the period are unapproved - missing an hours, travel or active overnight approval - or have open shift alertsUse View approvals or View alerts to open Shift Approvals or Shift Alerts in a new tab, already filtered to these dates
n shifts are still in progressThose shifts hadn't ended when the check ran, so they're excluded from the batch until they haveWait until they've ended and create the batch then, or pick them up in a later period
n approved shifts from dates are in no timesheet batchThose shifts were approved after the batch for the previous period was created, so that batch left them outSelect View earlier shifts to open Shift Approvals for those dates, then create another batch for those dates to pay them. It pays only what the first batch missed. On Xero, MYOB and the award-interpreted file exports, it counts the first batch's work towards caps and overtime bands, and refuses to export if adding these shifts would change what the first batch paid: rebuild the batches together. Employment Hero, PayCat and QuickBooks Payroll rate shift hours themselves, so they refuse such a batch only when the worker has on-call in an earlier batch from the same pay period. On Xero, do not delete the first batch's draft timesheet: add the new batch's hours to it in Xero by hand, or delete both batches and create one batch for those dates. The new batch also fails Validate once payroll has moved past those dates, usually because their pay run already exists. See A Pay Run Has Moved Xero Past the Batch for when to delete and re-create that pay run, and when to export the batch as a file and enter it in Xero instead
n on-call activations have not been approved, or n have no end timeUnapproved activations are never paid, and an activation with no end time cannot be approvedSelect View on-call roster to approve them or set an end time - see Recording and Approving Activations on the Web
n on-call records cannot be paid in fullThe workers' employment contracts do not cover all of the on-call, so batches leave the uncovered parts outSelect View records and add a contract, or extend the one that ends. A weekly or fortnightly batch over these dates then pays on-call that had no contract, and the next period's batch pays a night that runs past them
On-call in these dates is left out of this batchShown on an existing batch that is not 7 or 14 days long, which pays none of the on-call in its dates. The create form blocks such a batch insteadCreate a 7 or 14 day batch over these dates to pay it
On-call in this pay period is left out of the batchThe payroll calendar's pay period is neither weekly nor fortnightlyPay that on-call in Xero by hand
n on-call activations are held back from timesheet batches, or n approved on-call activations are in no timesheet batchAn approved shift that overlaps the activation is not batched yet, or a batch already covered the date without itSelect View activations and resolve any holding shift. Then create another 7- or 14-day batch for the earlier batch's exact dates, which pays only what the first batch missed. Earlier work contributes to caps and overtime bands, but the catch-up exports only newly claimed on-call. If adding the catch-up changes the recalculated earlier pay, rebuild the batches together. Reconcile any pay already processed in payroll, especially if contracts, pay settings or award calculations have changed. On Xero, do not delete the earlier batch's draft: add the catch-up's hours to it in Xero, or delete both batches and create one batch for those dates. Follow Timesheet Batch Warnings before changing either system
n approved on-call activations from dates are in no timesheet batch, and this batch will not pay themThey were approved after the batch for the previous pay period was created, or a shift held them backSelect View earlier activations to list them. Once any shift holding one back is in a batch, create another batch for those dates to pay them. It pays only what the first batch missed
n shifts start less than 10 hours after an approved on-call callUnder the Nurses Award, and for full-time or part-time workers under Aged Care, the calls left the worker without 10 consecutive hours off duty between the end of their last shift and the start of the next; a worker who had 10 hours off before the call is owed nothing and is not counted. Under the Health Professionals Award the rest is measured from the end of the call, so the shift is counted whatever time the last shift finished. Astalty does not add the resulting paymentSelect View short-rest shifts to see the worker, when the call ended and when the shift starts. If they keep working without the required rest, adjust their existing shift payment to a total of 200% of the base rate until release, or 250% for a casual Nurses or Health Professionals worker, including pay already exported. A worker other than a casual who takes the required rest instead is paid the ordinary hours they miss
n staff members with shifts or on-call have no payroll calendar in XeroThose staff aren't linked to a Xero employee, or aren't assigned a payroll calendar in Xero, so their shifts and on-call are excludedSelect View staff to open the Staff without a payroll calendar drawer and resolve them - see Staff Without a Payroll Calendar
n shifts have custom allowances that are still exportedCustom allowances were switched off for your account after they were added to these shiftsRemove the allowances from any shift where they should not be paid

Select Create Batch to confirm. The button reads Validating... while these checks run.

Your newly created batch will now appear in the Timesheets Batches. You can view the batch by selecting it.

Once inside the Timesheet Batch, you can access the Actions menu. Which options appear depends on the payroll platform set for your account:

ActionWhen it appears
Export Timesheet as ExcelAlways - opens the four file-based export options
Export Employment Hero Timesheet (CSV)Your payroll platform is Employment Hero (or PayCat / QuickBooks Payroll)
Send to Employment Hero and Replace in Employment HeroThe Employment Hero integration is connected and a business has been selected
Export Xero Timesheet (API)Your payroll platform is Xero
DeleteAlways

Export Timesheet as Excel

Selecting Export Timesheet as Excel opens a page with four export options. Choose the one that matches what you need to do with the file.

OptionWhat you get
Raw shift dataShift start/end times and durations as recorded, without any award interpretation applied.
SCHADS interpreted timesheetInterpreted hours and allowances for each Support Worker, broken down by date, earning rate and Cost Code.
Xero-formatted timesheetInterpreted data in a pivot-table layout with days as columns, grouped by Support Worker and earning rate. Compatible with Xero payroll import.
Business Central timesheetA Resource Journal CSV with interpreted earning-rate lines, including the Support Worker's Resource No. and Cost Centre.

All four run in the background. Once the file is ready it appears on the Exports page, where you can select Download to save it to your device.

Raw shift data

A generic CSV of the batch that you can tailor for importing into your preferred staff payment software. Nothing is interpreted - the times are exactly as approved on the shift.

The file contains one row per line of shift activity, with these columns:

  • Date, Day Of Week, Start Time, End Time
  • Paid Break Start Time, Paid Break End Time
  • Units, Hours
  • Pay Item - hours, kilometres, travel, unpaid_break or custom_allowance
  • Cost Code - only when your account uses cost codes
  • User Name, User External ID, Comments

Hours has any unpaid breaks added to the shift taken off, floored at 0 - it's not the full approved start-to-end span. Comments names the deduction, for example Unpaid break 30 mins; a paid cancellation reads Paid cancellation. Unpaid break 30 mins. Paid breaks are never subtracted. A sleepover row's own hours are unchanged - an unpaid break inside the sleepover window is called out on that row instead, as Unpaid break 30 mins not deducted from sleepover.

Each custom allowance on a shift adds a custom_allowance row with its Units, a blank Hours, and the allowance name in Comments.

There is no validation step on this export. Select Create Export and the file is queued straight away.

SCHADS interpreted timesheet

An Excel (.xlsx) file of interpreted shifts and quantities, named Award Timesheet Export followed by the batch's start and end dates. A worker can have several lines on the same day when the earning rate or Cost Code differs. The columns are:

  • Support Worker, Date, Pay Group
  • Cost Code - only when your account uses cost codes
  • Earning Rate, Units

Award allowances appear as their own rows alongside the pay lines, and any line that works out to zero units is left out. Custom allowances are not included. Rows are ordered by Support Worker, then date, then earning rate.

Select Validate & Export to run the interpreted timesheet validation checks and then queue the file.

Xero-formatted timesheet

The same interpreted data as above, but laid out as a pivot table ready for Xero's payroll import. It is an Excel (.xlsx) file named Xero Timesheet Export followed by the batch's start and end dates, with these columns:

  • Support Worker
  • Earning Rate
  • One column per day in the batch, headed with the day and date (for example, Mon 04 May)

Each Support Worker's rows are grouped together with a blank row between workers, and earning rates with no units anywhere in the period are left out entirely. Units from a shift that runs past midnight on the final day of the batch are counted in the last date column. Each custom allowance adds a row under its own name, with its units on each day.

Select Validate & Export to run the interpreted timesheet validation checks and then queue the file.

Business Central timesheet

This CSV is ready for the Business Central Resource Journal. It lists interpreted earning-rate lines for each Support Worker. Lines with different Cost Centres stay separate, even when the date and earning rate match. The columns are:

  • Posting Date
  • Resource No. - the Support Worker's External ID in Astalty
  • Work Type - the interpreted earning rate or allowance
  • Quantity
  • Cost Centre - the shift's Cost Code, when one is set
  • Support Worker
  • Pay Group

Select Validate & Export. The export uses the same award interpretation checks as the other interpreted files. A worker with no External ID is shown as a warning rather than a blocker, but Business Central needs a Resource No. on every imported line. Use Fix issue to add the worker's External ID, then validate again. Export anyway leaves the Resource No. blank for that worker.

Export Employment Hero Timesheet (CSV)

This produces a CSV of the Timesheet batch that is ready for importing into Employment Hero. If the integration is connected, the Actions menu also offers Send to Employment Hero and Replace in Employment Hero, which push the timesheets across without a file. See Employment Hero.

Export Xero Timesheet (API)

This opens the Export for Xero panel, where you can validate the batch and push it directly to Xero via the API. The panel also has an Export as Excel button in its top-right corner, which queues the same Xero-formatted timesheet file described above.

Astalty sends each worker separately. A result can therefore be Partially failed when Xero accepts some workers and refuses others. The result shows how many workers were sent, how many had earlier draft hours removed, and how many failed. Fix the failed workers before running the export again; Xero drafts already created for the others remain in place.

For more on the Xero integration for scheduling, see Xero Integration in Scheduling.

Delete

Within the Actions Menu, you can use the Delete option to remove the Timesheet Batch. You'll be asked to type the number of shifts in the batch to confirm. On accounts using the On-Call Roster, or when the batch holds on-call, type the number of shifts and on-call records the batch releases instead. Use of this function cannot be undone.

Deleting a batch releases its shifts and on-call to the next batch for those dates. A batch cannot be deleted while a later batch depends on it: one for overlapping dates that uses its work, including its shifts, or one whose on-call pay depends on it. Delete the later batch first.

Resolving Timesheet Batch Validation Errors

Before a batch can be exported, Astalty validates it. If anything would stop the export, the panel lists each problem against the worker it affects, and most rows include a Fix issue button (wrench icon) that opens the exact screen where you can resolve it - so you don't have to work out which setting is at fault.

For Xero exports, validation separates Errors from Warnings. Errors block Create Export. Warnings do not block the whole export, but some warnings mean a named worker will be left out. When there are warnings and no errors, select Continue anyway to review the employee selection and send the workers Xero can accept.

Which errors you see depends on how you're exporting:

Where you validateErrors you'll see
Export Xero Timesheet (API) > Validate - syncs the batch to Xero through the integrationXero validation errors
Export Employment Hero Timesheet (CSV) > Validate, or Send to your platformEmployment Hero validation errors
SCHADS interpreted timesheet, Xero-formatted timesheet or Business Central timesheet > Validate & Export - produces a fileInterpreted timesheet validation errors

The Raw shift data export has no validation step, because nothing is interpreted - it exports the approved shift times as they stand.

When the Fix issue button doesn't appear

Not every row has a Fix issue button. It's absent when:

  • The error has to be fixed by editing the shift. Problems such as a zero-length shift, a break that falls outside the approved shift times, or overlapping timesheet lines can only be corrected on the shift itself. Go back to the schedule, open the affected shift, and correct its approved start/end times or breaks - see Shift Approvals.
  • The error has to be fixed in your payroll platform. For example, if a worker isn't on the batch's payroll calendar in Xero, or their employee record isn't active in Employment Hero, the change has to be made in Xero or Employment Hero - Astalty can't do it for you.
  • You can't make the fix yourself. The Fix issue button for the Shift has no cost code error only appears if you can create cost codes, and every button leads to a settings or HR page you need access to. Ask an Admin to give you access or resolve the error for you.
  • The error isn't tied to a specific worker. Some Employment Hero errors need a linked worker on the row before Astalty can build a destination link.

Xero validation errors

ErrorWhere Fix issue takes you
User is missing a Pay GroupThe worker's HR tab, with the Update payroll drawer open
User is missing a Xero Employee IDThe worker's HR tab, with the Update payroll platform drawer open
User does not have an employment contract within the timesheet batch periodThe worker's Employment Details, with the Add Employment Details drawer open
No state is set on the organisation's address or on this user's address, so the public holidays in their on-call cannot be pricedThe worker's profile, with their address open for editing
The worker's pay group is set up for a different award from their employment contractThe worker's HR tab, with the Update payroll drawer open
Shifts carry a pay group set up for a different award from the worker's contractSettings > Scheduling > Pay Groups. Change the pay group on those shifts, or the pay group's award
The award on the worker's contract doesn't support sleepoversThe worker's HR tab
Pay Group is missing Xero configuration, or is missing a pay itemXero Pay Groups settings, usually opened ready to edit that pay group's pay item mapping
A pay item mapped on the worker's Pay Group, or an on-call pay item, has been deleted or archived in Xero, or - for a rate per unit item - isn't measured in hours thereXero Pay Groups settings, opened to that pay item's mapping row
A custom allowance on a shift in the batch has no Xero earnings rate mapped, or its earnings rate has been deleted or archived in Xero, or isn't measured in hoursXero Custom Allowances settings, listing archived allowances too
Cost code is missing a Xero payroll tracking optionXero Cost Codes settings
Shift has no cost code, but your Xero organisation requires a tracking category on timesheetsSettings > Scheduling > Cost Codes, with the Re-evaluate Existing Records drawer open and scoped to this batch's date range
Two or more workers share the same Xero employeeThe worker's HR tab, with the Update payroll platform drawer open. The message names everyone sharing that employee - each needs their own Xero employee before the batch can be exported
Xero has a draft for this worker and pay period that this batch can replaceNo fix is required. The warning shows the draft's period and hours. Continuing replaces every line in that draft with the current batch.
A draft from another Astalty batch for this pay period prevents this worker from being sentKeep that draft: this batch pays only what the other batch did not. Add this batch's hours to the draft in Xero by hand, using the Xero-formatted timesheet export to list them, or delete both batches in Astalty and create one batch for those dates, which sends everything together and replaces the draft. You can continue and send the other workers. See Timesheet Already Exists.
A non-draft for this period, or any later timesheet, prevents this worker from being sentManage Xero Timesheets, filtered to the worker, for a later draft that Astalty created. Otherwise resolve it in Xero. You can continue and send the other workers. See Timesheet Already Exists.
A previous export of this batch sent a worker who no longer has hours in itNo fix is required while that timesheet is still a draft. Continuing removes every line from the earlier draft. If it is no longer a draft, Astalty cannot remove the hours and the worker fails.

Which pay items get checked

Validation interprets the batch under the award on each worker's employment contract, then checks that every rate and allowance it pays has a pay item mapped on the worker's pay group. A pay item the batch does not use is not checked. A pay group can pass one week and fail the next, when a worker first works a night, a public holiday or a sleepover. The error names the missing pay item, and its row lists any shifts that needed it.

The same applies to on-call: standby and activations in the batch need the on-call pay items for the worker's award, such as On Call Weekday and Remote Work for SCHADS.

Validation also checks the Xero pay item behind every mapping the batch actually uses, not just that one is mapped. The export is blocked if that pay item has been deleted or archived in Xero, or - for a rate per unit item - if its Type of Units isn't Hours, because Xero only accepts hours on a timesheet. Kilometre and sleepover allowances are no exception: their pay item still needs to be measured in Hours in Xero, and Astalty sends the kilometre or sleepover count as the quantity, the same as any other pay item. Each error names the pay group and the pay item, and Fix issue opens Xero Pay Groups settings at that mapping row.

Map every pay item for the worker's award before the first pay run, rather than waiting for validation to name each one. Each award page lists the pay items and suggested multipliers for its own pay group - see SCHADS, Nurses, Aged Care and Health Professionals.

A pay group's mapping encodes one award's rates, so a pay group holding workers on two awards stops the export and names both - see Setup Pay Items and Employee Templates in Xero. On-call has no pay group of its own. When neither the worker's pay group nor their shifts on the same days carry a pay group for the award on the contract covering the on-call, it cannot be exported, and the error asks you to pay that period outside Astalty.

User is not on this timesheet batch's payroll calendar in Xero has no Fix issue button. This can only be fixed in Xero - assign the employee to the batch's payroll calendar there, then re-run the export.

For the two cost code errors, the row also lists the affected shifts as clickable dates and times - selecting one opens the shift viewer on the same page, so you don't lose your place. Six are shown at a time; if there are more, select +2 more (the count varies) to reveal the rest, then Show fewer to collapse them again.

Employment Hero validation errors

Connection and Shift Errors

Employment Hero validation splits results into Errors, which must be fixed before you can export, and Warnings, which don't block the export. If there are warnings and no blocking errors at all, an Export anyway button appears so you can proceed - but Employment Hero may still reject overlapping lines when the pay run is processed.

Each row also shows a plain-English explanation beneath the error, telling you what triggered it.

Fix issue takes you to the worker's HR tab for:

ErrorDrawer opened
Not yet linked to an Employment Hero employeeUpdate payroll platform
Linked, but the employee couldn't be found in Employment HeroUpdate payroll platform
Not assigned to a pay groupUpdate payroll
Their pay group is set up for a different award from their employment contractUpdate payroll
The award on their contract doesn't support sleepovers(no drawer - the HR tab itself)

Fix issue takes you elsewhere on the worker's profile for:

  • No employment contract for the batch period, on a worker with a sleepover or on-call in the batch - their Employment Details, with the Add Employment Details drawer open
  • No state on the organisation's address or the worker's, so the public holidays in their on-call can't be priced - their profile, with their address open for editing

Fix issue takes you to Employment Hero Pay Groups settings for:

  • The pay group has no Employment Hero work type mappings yet
  • A required work type isn't mapped - Ordinary Hours, KMs Travel, Paid Meal Break, Unpaid Meal Break, Sleepover, Active Overnight, or Paid Cancellation
  • 24-hour Care isn't mapped and a home care worker has a 24-hour care shift in the batch, including one cancelled with pay
  • Only one of Pre-Sleepover and Post-Sleepover is mapped (a warning) - map both, or clear both to keep the previous behaviour
  • The worker was on call, but their pay group doesn't map the work type for that on-call pay
  • A mapped work type can't price what is sent as units: KMs Travel, Sleepover and the on-call allowances need a fixed-rate pay category. The other on-call rows need a custom work type on a pay category of its own, or one of the platform's own work types on a fixed-rate pay category. Weekday remote work and weekday on-call ordinary hours may also use a custom work type on the employee's primary pay category
  • A work type mapped in Astalty no longer exists in Employment Hero

Fix issue takes you to Settings > Scheduling > Pay Groups for:

  • Shifts carry a pay group set up for a different award from the worker's contract, so their on-call can't be paid. Change the pay group on those shifts, or the pay group's award

Fix issue takes you to Employment Hero Custom Allowances settings for:

  • A custom allowance on a shift in the batch has no work type mapped
  • A custom allowance is mapped to a work type that no longer exists in Employment Hero
  • A custom allowance's work type doesn't pay a pay category of its own, or is one of Employment Hero's own work types without a fixed rate

Fix issue takes you to Employment Hero Cost Codes settings for:

  • A shift's cost code hasn't been mapped to an Employment Hero location
  • A mapped location no longer exists in Employment Hero

These errors have no Fix issue button:

ErrorWhat to do
The approved start and end times are identical, giving zero hoursReview the shift's approved times
A calculated value came out negative (such as travel kilometres or sleepover units)Review the shift's approved details
A paid break starts or ends outside the approved shift timesReview the shift's break times and approved start/end times
A shift falls outside the batch's date range (common when a shift crosses midnight near the batch boundary)Adjust the shift, or the batch date range
Timesheet lines overlap (a warning)Review the approved times on the overlapping shifts
The employee exists in Employment Hero but isn't activeUpdate their status in Employment Hero, or exclude them from the export
Astalty couldn't work out the employee's on-call pay for this batchThe message says why. Fix the cause, then validate again
On-call is paid at a rate Astalty does not send to your platform, so the export leaves it out (a warning)Pay it outside Astalty, or select Export anyway to send the rest of the batch

Interpreted timesheet validation errors

The three interpreted file exports - SCHADS interpreted timesheet, Xero-formatted timesheet and Business Central timesheet - validate against the award interpretation. Here the fix control is a wrench icon rather than a labelled button; hover it to see the Fix issue tooltip.

ErrorWhere the wrench takes you
User is missing a Pay GroupThe worker's HR tab, with the Update payroll drawer open
No employment contract for the batch periodThe worker's Employment Details, with the Add Employment Details drawer open
No state on the organisation's address or the worker's, so the public holidays in their on-call can't be pricedThe worker's profile, with their address open for editing
Their pay group is set up for a different award from their employment contractThe worker's HR tab, with the Update payroll drawer open
Shifts carry a pay group set up for a different award from the worker's contractSettings > Scheduling > Pay Groups
The award on their contract doesn't support sleepoversThe worker's HR tab

If the batch contains no shifts to export at all, No shifts found to export is shown on its own instead of against a worker, with no wrench icon.

The Business Central export adds a warning when a worker has no External ID to use as their Resource No. The warning's wrench opens that worker at the External ID field. It does not block Export anyway, but the worker's Resource No. is blank in the file.

Managing Xero Draft Timesheets

If your account uses Xero for payroll, you can review and bulk delete the draft timesheets Astalty has sent to Xero and recorded. This is useful when a later-period draft must be removed before sending an earlier period. Do not delete a draft that another batch for the same dates sent: add this batch's hours to it in Xero by hand, or delete both batches and create one batch for those dates. Re-exporting the same batch normally replaces its existing drafts, so you do not need to delete those first.

From the Timesheet Batches page

From Timesheet Batches, select the Actions menu next to Create Batch, then choose Manage Xero Timesheets.

The Bulk delete draft timesheets panel opens, listing the recorded Astalty drafts that still exist in Xero, with the Worker, Pay Period and Hours. Select individual timesheets, or use Select all, and then select Delete to remove them.

From Settings

You can also reach the same tool through Settings:

  1. Go to Settings > Integrations.
  2. On the Xero card, select View Details.
  3. In the Xero settings menu, open Manage Timesheets.
  4. Select Actions > Bulk delete, then choose the draft timesheets to remove and select Delete.

This page also shows a full table of the recorded Astalty drafts that still exist in Xero, so you can review them before deleting.

Deletion runs in the background, so you can keep working while it completes. Once finished, you'll see how many were deleted and any that failed, so you can retry or remove them directly in Xero.

Award Interpretation

Each worker in the batch is interpreted under the award on their employment contract. For supported rules and manual checks, see SCHADS, Nurses, Aged Care and Health Professionals. For the full standalone report documentation, including pay period requirements, stat cards, filtering, and excluded employees, see the Award Pay Report.

Open a Timesheet Batch and select Award Interpretation to review how Astalty interpreted its shifts. On Employment Hero, PayCat and QuickBooks Payroll, the payroll platform calculates award pay from the timesheets Astalty sends, so its result can differ from these figures.

Use a complete pay period. For adjoining work that crosses into it, Astalty carries the previous period's interpretation into the later period's shift, daily, overtime-band, meal, and minimum-engagement calculations without exporting the earlier hours twice. Check Pay Period Settings, resolve missing or unapproved records, and compare the final payroll amounts after export.

Viewing the Interpretations per Support Worker

The table shows Astalty's interpretation of each worker's shifts in the batch. Group the rows by day or view the itemised results.

By Daily Breakdown

If you are viewing by Daily Breakdown you can view the different pay line totals applied per days, and you then group each of the pay lines across the pay cycle to display the total accumulated amounts of that pay line in the pay cycle.

By Itemised Lines

If you are viewing by Itemised Lines you can view it grouped by the Paylines and Allowances, which will then provide you with the date of support, Pay rate or Allowance, and the amount of units.

Exporting to CSV

Select Export CSV to queue a CSV of every employee interpreted for this batch - including anyone hidden by the table's search. If your organisation requires a reason for exports, an Export reason box appears; enter at least 10 characters before selecting Create export.

The file is queued in the background and appears on the Exports page as Award Interpretation Export followed by the batch's start and end dates. Its columns match the Award Pay Report's CSV export.