Apply pay rates

Applying pay rates turns a pay period's timesheets into pay lines: hours, rate, amount and cost code for every part of every worker's day. You do it from Payroll, then Pay Rates, on the Pay Rates tab. Owners and Admins can apply pay rates by default.

Before you start

• At least one pay rate document is Active and in force on the period's dates, with its rule groups and cost codes set up.
• Your workers have profiles, with employment types if your documents use them.
• Your payroll cycle and public holidays are set.
• The period's timesheets are in Assignar Pay. They arrive from Assignar Operations, from a CSV import, or from My Shifts; see Review timesheets. To import one group's timesheets from Assignar Operations, see Import timesheets for one group of workers.

Import timesheets for one group of workers

When you pay two groups separately, and each group shares a worker tag, import only that group's timesheets.

1. On the Pay Rates tab, select Import Timesheets. The button is available once Assignar Operations is connected.
2. Choose the Date Range.
3. Open Filters & Options.
4. Under Filter by Worker Tag, pick one or more tags. A timesheet is included when the worker has any of those tags. The list shows tags that are already on a worker. All tags means you have not picked any.
5. To narrow further, pick types under Filter by Worker's Employment Type. The worker then has to match a tag and an employment type.
6. Select Fetch Timesheets.
7. Leave Import All selected and select Import. Only the timesheets in the list are imported.

This browser keeps the tags you picked and shows them the next time you open Import Timesheets. A saved tag that is not on a worker in this account is left out, and Filter by Worker Tag shows All tags. If you change the tags or Filter by Timesheet Status after a fetch, the list clears. Fetch again before you import.

Leaving Filter by Worker Tag on All tags includes every worker. Choosing every tag still leaves out a worker who has none.

Timesheets for a worker who is not in Assignar Pay yet, or who has no tags, are left out of the list. You see how many, for example 3 timesheets skipped: worker not synced to Pay or untagged. That number counts timesheets that match the employment types you picked, and every such timesheet when you have not picked an employment type.

A worker who has tags, but none of the ones you picked, is left out and is not part of that count. Bring the worker across from Assignar Operations, or add a tag on their profile, then fetch again.

If the client, project, or employment type list does not load, Fetch Timesheets stays unavailable and you see Could not load the Assignar filters. Select Retry.

If only the worker tag list fails and Filter by Worker Tag is still All tags, you can fetch and import. The tag list shows The Assignar filter lists could not be loaded. Select Retry beside it. When a tag is already selected, including one this browser restored, Fetch Timesheets stays unavailable and Could not load the Assignar filters appears above it, with The Assignar filter lists could not be loaded. Select Retry on that message. It stays on screen when Filters & Options is closed.

Import timesheets for one worker

1. Choose the date range and select Fetch Timesheets.
2. Choose Import Selected and search for the worker's name.
3. If selected timesheets are hidden, select Clear selection beside the hidden count to untick every timesheet. If none are hidden, select Deselect N shown instead.
4. Tick the worker's timesheets, or select Select all N shown to tick every timesheet in the results.
5. Check the selected count beside Import, then select Import.

Select all N shown and Deselect N shown change only the rows currently shown. Ticked rows hidden by a search or filter stay selected. When any are hidden, their count and Clear selection appear beside the selection controls. Clear selection unticks them all.

Results search and filters do not narrow Import All. To import just the rows you ticked, choose Import Selected.

Apply pay rates to a pay period

1. On the Pay Rates tab, select Summary View.
2. Next to Pay Period, use the arrows or the date to pick the period. Periods follow your payroll cycle.
3. Select Apply Pay Rates. The dialog shows the period and how many workers, timesheets and hours it covers.
4. To process only some workers, choose a tag under Filter by worker tag, or tick Select specific workers to process and pick them. Expand Worker Details to see each worker's timesheets and which have uncoded time.
5. Select Start Processing.

Processing runs in the background. The Summary View and Table View update by themselves when it finishes, so you can keep working.

If your account limits access by location, the run checks your access again when it starts. A worker who is no longer inside your access, because their home location or Business Unit changed or your access did, is skipped, and the notification when it finishes says so, for example "2 worker(s) were skipped because they are no longer inside your payroll access." When none of the workers is inside your access any more, nothing is processed and you see Pay Rates Processing Failed with "None of the 2 selected worker(s) are inside your payroll access (home location and Business Unit) any more, so no pay rates were processed".

What is and isn't recalculated

Applying pay rates replaces the pay lines already calculated for the timesheets it covers, with two exceptions: timesheets marked as reviewed and timesheets whose pay lines were edited by hand are left exactly as they are. When the run fails for a timesheet that already has pay lines, that pay stays as it is.

To recalculate them, use Reset Pay Items: in the … menu next to Apply Pay Rates it resets every timesheet in the period, and in the … menu on a worker's row it resets that worker's. Resetting removes the calculated pay lines and the reviewed mark, and the next run calculates the timesheets again.

Applying pay rates to an earlier period again uses the documents that were in force on those dates, including ones that have ended since. Archived documents are never picked automatically.

When a public holiday or RDO date on a worker's calendar has no timesheet, processing can add one for it. See Timesheets for days not worked.

Check the results

The Summary View lists every worker with a timesheet in the period, or with a shift that has no timesheet, with their hours and pay by pay code, and a total.

The columns are your own pay codes, allowances included, for example ORD (Ordinary Hours), OT15 (Overtime 1.5x), RDO (RDO Taken), SITE (Site Allowance) and MEAL (Meal Allowance). They come from the cost codes your pay rates use, so every account sees its own. A heading with a code shows the code. Point at the code, or move to it with the keyboard, to see its name. There is one column for every pay code used in the pay period, so the columns stay the same as you move between weeks and blocks:

• Hour codes show hours over pay, for example 128.00h over $6,973.44. Leave codes such as RDO are hour codes too.
• Allowances show a quantity over pay, for example 154 qty over $438.90.
• A worker who didn't use a code shows 0.00h and $0.00 in grey.
• A loading is in its own cost code's column with its pay, and adds no hours, because its hours are already counted on the hours it loads.
• A pay line with no cost code has a column of its own, named after its pay item, for example Ordinary Hours. It has no code above the name.
• Hours that haven't been given a pay rate yet are in an Uncoded column after the hour codes. These are the same hours the banner counts as uncoded, and the column only appears when there are some.
• Each code's pay is rounded once over its pay lines, and the total is rounded once over all of them, so the codes can add up to a cent or two away from the total. The total is the figure that matches the exports.
• Anyone who can manage settings (owners and admins by default) can select Configure on the summary to set the left-to-right order of the pay code columns for the whole organisation, in Summary settings under Pay code column order. Hour codes still come before allowances. Codes you haven't ordered keep the default order after the ones you have. Reset to default restores the default order.

• Use Filters to narrow the list by worker tag, or by employment type when your workers have one.
• On fortnightly, four weekly, monthly and twice-monthly cycles, the Summary View opens on the full pay period, and a View control beside Pay Period chooses how much of it to show: Week, Fortnight, 3 weeks, 4 weeks or the full period (Full fortnight, Full four weeks, Full month or Full pay period). Only the views that fit inside your cycle are offered. The Pay cycle chip next to it names your cycle; View only changes what is on screen and never changes your pay cycle. It isn't remembered: each time you open the Summary View it starts on the full period again. On a weekly cycle there is no View control.
• The card above the workers says what the figures cover, for example 5 workers · totals for fortnight · Sep 1 – 13, or totals for the full month.
• Every view lists everyone with a timesheet anywhere in the pay period, even when they have none in the dates shown. Workers with allocated shifts but no timesheets are listed only for the dates of those shifts, and only for days that have passed, so a worker whose only shifts are today or later isn't listed yet. The full period lists them for all those days, while Week and the other shorter views list only those whose shifts fall in the dates shown, so the worker count can drop when you switch to a shorter view. A note under the card's title says which rule the current view uses.
• In Fortnight, 3 weeks and 4 weeks, the pager on the card shows which block you are on, for example Fortnight 1 of 2 or 3 weeks · block 1 of 2, with its dates. Use its arrows to move through the period, and Back to full month (or fortnight, four weeks, pay period) to return to the full period.
• Each worker's row shows their totals for what is on screen. In a block view, the total cell also shows the full period's figures underneath, for example Full month: 162.00h · $8,400.00. In the full period it shows how many of their timesheets in the whole period are locked, for example 20 timesheets · 5 locked. It counts the same timesheets as the banner, and a lock beside the worker means at least one of them is locked.
• Under the workers, the All workers row adds up every pay code for the workers listed, in every view including Week, and its total cell says how many timesheets that covers.
• Select the arrow beside a worker to see their time:
  • In Fortnight, and in Full fortnight on a fortnightly cycle, an hour-by-hour timeline runs across the whole fortnight, with a Week 1 total and Week 2 total column after each week. Each shift shows its hours and its hourly rate in your account currency. Shifts are coloured by pay class. In Fortnight the legend (ORD, OT15, OT20, RDO, Other) sits above Jump to. On Full fortnight it stays in the card header. The Jump to cards show each week's dates, hours, pay and how many of that week's timesheets are locked, for example 1 of 3 timesheets locked this week, or No timesheets for a week without any; select one to scroll the timeline to that week. A shift that runs past midnight is drawn on both days, and each day's block shows only its share of the shift's hours and pay. A pro-rated timesheet's shift shows its whole hours and pay on both days, and a shift whose next day isn't shown stays whole on its first day. The day totals still count the whole shift on its timesheet's day. Select a shift, leave, RDO or uncoded block to open its timesheet's Rate Calculation Details, the same as in Week. Closing it leaves you on the same worker and place in the timeline.
  • In 3 weeks, 4 weeks and any full period longer than a fortnight, a month grid shows one row per week, Monday to Sunday (or from your week start day). Each day card shows its hours and pay and, for a single timesheet, its shift time, project and timesheet number, with a colour bar for its pay classes. In 3 weeks and 4 weeks the same legend sits under the week rows. On the full period it stays in the card header. A lock marks a locked timesheet, and a day with two or more timesheets says so; select it to see each one.
  • On monthly and twice-monthly cycles, the days of the first and last week that belong to the previous or next pay run are hatched and labelled with that run, for example August run. Their hours aren't in any total on the screen. A partial week says how many of its days are in the period, for example 6 of 7 days in this month.
  • Each row ends in a Week total card with the week's hours and pay, how many of that week's timesheets are locked (No timesheets for a week without any), and a badge: Open, Upcoming for a week that hasn't started, or Locked when all its timesheets are locked. Select View week in timeline to open that week in the Week view's hour-by-hour calendar.
  • In Week, move between the weeks of the period with the week arrows. Each pay line shows its hours and hourly rate in your account currency, and the rate is hidden if you can't see pay figures. On a cycle longer than a week, a muted row under each worker shows the full pay period's figures for every pay code. A shift that runs past midnight is drawn on both days, and each day's card shows only its share of the shift's hours and pay. A pro-rated timesheet's shift shows its whole hours and pay on both days, and a shift whose next day isn't in the week stays whole on its first day. The day totals still count the whole shift on its timesheet's day. Select a timesheet to open its Rate Calculation Details: the document and classification it matched, each pay line, and the steps behind them. A worker with no timesheets in one of the weeks shows No timesheets this week for it.
• Changing the view or moving between blocks keeps your filters and the workers you have open.
• Locked timesheets are the ones whose pay was changed by hand or marked reviewed; Apply Pay Rates leaves them as they are.
• Delete Timesheets and Reset Pay Items act on the timesheets on screen: the whole period in the full-period view, the block shown, or the week shown. Apply Pay Rates always processes the whole pay period.
• To delete just one timesheet, select it in Week or on the hour-by-hour timeline to open its Rate Calculation Details, select Delete Timesheet, then select Delete to confirm. If several timesheets open together, it deletes the one whose tab is showing. If someone else deleted it first, you're told it was already deleted.

Each pay line also has a rate type, which the Table View, the worker's week table and the exports show. Saturday and Sunday hours paid by a day rule are Overtime, or Second Overtime when the day rule pays 2x or more. The day rule decides, not a time-of-day loading on the same hours: a Sunday at 2x is Second Overtime and a Saturday at 1.5x is Overtime, with or without a night loading. A worked hours loading on those hours has the same rate type as the hours.

When the cost code on those hours is in the Regular Time, Overtime or Second Overtime category, that category decides the rate type instead. On hours where a time-of-day loading applies, that is the loading's cost code.

On a timesheet without activities, the hours are Regular Time, or Overtime or Second Overtime past a daily or weekly threshold. The weekend penalty pay and any time-of-day loaded hours take the day rule's rate type.

Pay that was already calculated shows 2x weekend pay as Overtime until you apply pay rates again. Applying again moves it to Second Overtime in the Table View and in exports. The move itself doesn't change any amount.

The Table View lists every pay line in the period, one row each, with columns you can choose under Column Views. Add the AI Confidence column to find pay lines matched with low confidence, which are worth checking by hand. Display Mode switches between a row per pay line and a row per timesheet.

Workers linked to a supplier, such as consultants and agency workers, are paid through their supplier's invoice, so their timesheets are left out of both views and the exports. To see them on purpose, turn on Include supplier workers in either view; the exports then include them too. Either way, Apply Pay Rates still works out their pay, so turning the switch on later shows it ready; deleting or resetting timesheets only touches the ones on screen. If you filter Table View to a worker who is linked to a supplier, a note names them and offers the same switch. See Pay a worker through a supplier.

Workers whose employment type is excluded from payroll aren't paid through Assignar Pay. Their timesheets that don't have pay yet are left out of both views and the exports, even with Include supplier workers on, and Apply Pay Rates doesn't work out their pay. Timesheets that already had pay before the type was excluded keep it and still show. See Leave an employment type out of payroll.

If your account limits access by location, both views and the exports show pay only for workers whose home location and Business Unit are in your access, whichever project the time was worked on. A worker from another location who worked on one of your projects doesn't appear here, and Apply Pay Rates skips them. You can still change pay on a timesheet for one of your projects if you can edit that timesheet, for example when you approve it. Pay rate documents are shared by the whole account and stay visible to everyone who can see pay rates.

Once your account has started coding, Column Views also offers Working Location, Home Location, Business Unit, Entity Code and GL Code, and they export with the other columns you choose. They are hidden until you add them, including in saved views. Each pay line shows the coding its timesheet was given when it was created, with the Business Unit as its code; timesheets created before coding started show —. Leave and public holidays are coded too, with your Leave GL account as their GL account.

In a CSV export or Copy for Excel, the Business Unit code is under the header Business Unit Code. A value the timesheet doesn't have is left blank, so your payroll or ERP import never reads — as a code. In a JSON export the same value is null.

Column Views also offers PO: the purchase order line the timesheet is booked to, for example PO010241 · 2. Labourer, or - when it isn't booked. It is hidden until you add it, including in saved views. It exports as two columns, PO Number and PO Line, so your import can match on the purchase order number alone. A timesheet that isn't booked leaves both blank in a CSV export or Copy for Excel, and null in a JSON export. Most booked time belongs to supplier workers, so turn on Include supplier workers to see it. See Book time to a purchase order line.

Select a GL Code to see Why this value?: where each part of the code came from, which source gave the Business Unit, and, if your setup has changed since, what it would give today. A timesheet that was coded but has no GL code shows —, which you can select too.

Under Filters, the Coding section narrows the table by working location, home location or Business Unit. A location includes every location under it, and timesheets created before coding started never match these filters.

Recode a row

If a timesheet was coded wrongly, select its GL Code and click Recode in Why this value?. Owners and admins can recode. If you don't see Recode, ask one of them.

Choose a new Business Unit, Location or GL account, or any of them; anything you leave as Keep current stays as saved. As on cost codes, a GL account can't contain spaces, is at most 40 characters, and must match the Width set on the {Account} row of your GL code template. The Preview shows the GL code and Business Unit before and after. Type a Reason (it's required), then click Recode.

Only the coding changes. Hours, rates and amounts stay exactly as they were. The row then shows Set manually for the parts you changed, and Why this value? shows who changed it, when and why.

To undo a manual change, click Reset to setup. It removes the values set manually and codes the row again from your current setup. It also needs a reason, and only shows on a row with values set manually.

Check the banner above the summary

The banner tells you whether the period is ready to pay. A green All hours are coded means every timesheet has pay rates applied, every timesheet could be read, and none has uncoded time. It doesn't show while any of these is true:

• hours uncoded: see Fix uncoded time.
• timesheets have not had pay rates applied: pay was never calculated for them, so their pay isn't in the totals. Apply pay rates to include them.
• timesheets couldn't be read and aren't in these totals: the pay saved on them can't be read, so their hours and pay are missing from every figure on the page. The banner names the first three by worker and date (the timesheet ID where the worker is unknown), and counts the rest. Don't export the period until they are fixed.

In every view except Week, the banner also counts the timesheets on screen and how many of them are locked, for example 97 timesheets in this fortnight · 12 locked (reviewed or edited). Weekly cycles don't show this count. Locked timesheets keep their pay when you apply pay rates.

A worker filter narrows the uncoded, not-applied and locked counts. The unreadable count ignores filters and covers the whole pay period, so on a fortnightly or four-weekly period it includes the other weeks.

Fix uncoded time

The banner shows how many hours in the period are uncoded: timesheets that could not be matched to a pay rate document or classification, so they have no rate. Expand the worker to find the timesheet; its Uncoded Time Error Details give the reason.

Common fixes:

• Give the worker an employment type, or the role the document expects.
• Add a matching pattern to the classification on the document's Rate Tree tab (see Set up a pay rate document).
• Widen a document's scope, or assign a document to the worker.
• If the Error in those details begins No active pay rate document is in force, no document that fits the timesheet covers its date. On the Pay Rate Documents tab, check the Effective Dates of the document that should pay it, then change them with Edit or add a document for those dates.
• If the Error begins This worker is assigned to, every pay rate document the worker is assigned to has ended by the timesheet's date. Give them an assignment to the document now in force (see Assign a pay rate document to a worker).
• For one timesheet only, pick a document under Document Override in its Rate Calculation Details.

Then apply pay rates again.

Chase shifts with no timesheet

If you allocate workers in Scheduling, the Summary View checks the shifts on screen (the full pay period, the block shown, or the week shown) for missing timesheets. A shift counts as covered when a timesheet has been submitted for it, or when the worker has submitted a labour or leave timesheet for that day that isn't for another of their shifts. A public holiday or RDO timesheet counts too. Equipment timesheets don't, declined shifts are skipped, and shifts from today onwards aren't checked yet. Workers linked to a supplier aren't checked, because their time isn't paid through payroll, unless Include supplier workers is on. Workers whose employment type is excluded from payroll are never checked.

If your account is connected to Assignar Operations, the panel also checks the shifts rostered there, on every day a worker has no shift allocated in Pay. A day with a shift in Pay is checked against Pay only, so no day is checked twice, and a week you are moving from Assignar Operations to Pay scheduling is still checked in full. When all the shifts checked came from Assignar Operations, the panel says "Shifts checked against the Ops roster." When some came from each, it says "Checked shifts allocated in Pay, and the Ops roster on days with no Pay shift." Neither line shows in a week with no shifts to check. Each rostered person is matched to the Pay worker brought across from Assignar Operations, and the same rules decide whether their shift is covered. A timesheet imported from the shift's Assignar Operations timesheet covers it too. Declined shifts are skipped, and so are bookings with only a machine on them.

The result shows in a panel above the list of workers:

• 3 shifts with no timesheet: select it to show only the workers with a shift to chase, and select it again to show everyone. The Has missing timesheets button beside Filters does the same.
• "Every allocated shift so far this week has a timesheet." There is nothing to chase.
• "No shifts are allocated in Pay so far this week, so missing timesheets can't be checked." This is not an all-clear: without allocated shifts, the panel can't find workers who submitted nothing.
• "No shifts are allocated in Pay or rostered in Ops so far this week, so missing timesheets can't be checked." The same, on an account that rosters in Assignar Operations.
• In the full pay period or a block of weeks, these three messages name the days that were checked instead of "this week", for example "Checked Jun 21 – Jul 3: no shifts are allocated in Pay, so missing timesheets can't be checked." The check covers every day on screen up to yesterday.
• "2 shifts have timesheets submitted in Ops, not yet imported": the workers submitted their timesheets in Assignar Operations, but Pay doesn't have them yet. Import the timesheets, and the shifts are covered.
• "1 worker rostered in Ops is not in Pay: Sam Lee": the person has no Pay worker, so their shifts can't be checked. Bring the worker across from Assignar Operations. This line only shows when you can see every worker. If their names couldn't be read from Assignar Operations, each is shown as Ops worker and a number, followed by "(Their names couldn't be loaded from Ops.)"
• "No shift is missing a timesheet, but some need following up:" The only findings are the two lines above.
• "Nothing to check yet: shifts are checked for missing timesheets once their day has passed." The week hasn't started, or today is its first day, so no shift has been checked.
• "Couldn't fully check allocated shifts for missing timesheets, so some may not be shown." The shifts listed are real, but there may be more. Select Retry. When Assignar Operations is the part that couldn't be read, a second sentence says why:
  • "The Ops roster couldn't be read in full this time." Select Retry.
  • "The Ops roster couldn't be read because this account's Assignar connection needs attention. Check it in Integrations." Retrying won't help, so there is no Retry button. Fix the connection on the Integrations page, then reload the page.
• "We couldn't check allocated shifts for missing timesheets." Select Retry.

The last two messages appear when the check of which shifts have no timesheet fails or only partly finishes, including when Assignar Operations can't be read. You still see each shift that was found when its order, project, role, or the people to message could not be loaded.

A red calendar icon on a worker's row means they have shifts to chase; point at it to see how many. A worker with allocated shifts but no timesheets that week still gets a row, with zero hours and the label Allocated only — no timesheets. Applying pay rates skips that row, because there is nothing to pay yet.

If that worker's name could not be loaded, the row says Unknown Worker. A worker who already has a timesheet keeps the name from that timesheet.

When Filters is set to a worker tag or an employment type, shifts whose worker could not be loaded stay in the list. Pay cannot tell whether that worker matches the filter.

Expand a worker's row to see a card on each day for every shift to follow up, with its order, project, times and role. The cards show in every view: on the day in the timeline or month grid, and in the Week view's calendar and table. A shift rostered in Assignar Operations with no times says "No times set in Ops". (+1 day) marks a shift that ends the next day. The card's heading tells you what is missing:

• No Timesheet Submitted in red: nothing has been filed for the shift.
• No Timesheet Submitted in amber, marked Pending allocation: the shift was never confirmed, so it may not have been worked.
• Timesheet started, not submitted in blue: the worker started a timesheet for the shift, in Pay or in Assignar Operations, but hasn't submitted it.
• Submitted in Ops, not yet imported in grey: the worker submitted the shift's timesheet in Assignar Operations, and Assignar Operations still has it. Import it rather than chasing the worker. A shift whose timesheet was deleted in Assignar Operations shows as No Timesheet Submitted.

If the order and project could not be loaded, the card says "Couldn't load the order or project for this shift." The times stay, and the order, project and role are blank. Convert to leave still works.

Each card has three buttons: Convert to leave, Message worker and Message supervisor. Point at a button to see its name, or why it's unavailable.

On a shift rostered in Assignar Operations, all three are unavailable: "This shift is rostered in Ops. Convert to leave and messaging work on shifts allocated in Pay." Add the leave timesheet or contact the worker another way.

Convert a shift to leave

When the worker was on leave instead of working the shift:

1. On the shift's card, select Convert to leave.
2. Choose the Leave type: Annual leave, Sick leave, Personal leave, RDO, Unpaid leave or Other leave.
3. Hours starts at the length of the shift. Lower it for part of a day; the most is 24.
4. Select Convert to leave.

Assignar Pay adds a submitted leave timesheet for that worker and day, and the card goes. The timesheet is reviewed and approved like any other; see Review timesheets.

You need the Create timesheets permission to convert a shift. A Timesheet started, not submitted card can't be converted: the worker has to submit or delete their timesheet first.

Message the worker or their supervisor

Message worker sends the worker a direct message in Messages with the shift's date, times and order. It asks them to submit their timesheet, or to let payroll know if they didn't work the shift. Message supervisor asks each supervisor allocated to the same order that day to make sure the timesheet is submitted.

The card then shows Chased and when you sent it. Selecting the same button again doesn't send a second message.

A message button is unavailable when:

• "This worker has no Pay login, so they can't be messaged."
• "No supervisor with a Pay login is set for this shift."
• "Couldn't load this worker, so they can't be messaged right now."
• "Couldn't load the supervisor for this shift, so they can't be messaged right now." Message supervisor shows this when the worker could not be loaded too.
• "Messaging is off for this account, or you do not have permission to send messages." You need the Send messages permission.

When converting or messaging fails

• "This shift already has a timesheet. Refresh to see the latest." A timesheet arrived after the page loaded. Refresh the page; the card is gone.
• "This shift has been declined, so no timesheet is owed for it." Refresh the page.
• "You do not have permission to add a timesheet for this worker." Ask an Owner or Admin for the Create timesheets permission.
• "You are sending messages too quickly. Wait a moment and try again."

Ask Milo about the pay period

With the Summary View open, select Ask Milo to ask about the pay period on screen. Milo reads every worker you can see in the period, so you can ask questions such as:

• "Who didn't reach their minimum engagement this week?" Milo lists the workers whose pay includes a minimum engagement top-up.
• "Which workers are missing timesheets this week?" Milo uses the same check as Chase shifts with no timesheet: the days a worker was allocated a shift and has no submitted timesheet, including workers with no timesheets at all.
• "How many workers submitted timesheets this week?"

Milo can only find missing timesheets if you allocate shifts in Scheduling. Without allocated shifts for the period, Milo tells you it can't tell who submitted nothing, instead of saying everyone did. Shifts from today onwards aren't checked yet, and Milo says the last day it checked.

When the check of allocated shifts doesn't finish, Milo tells you its list of missing timesheets may be incomplete. Ask again, or use the panel above the list of workers. When a listed shift's order, project or the people to message could not be loaded, Milo still includes that shift.

Mark timesheets reviewed and export

In the Table View, tick the rows you want. The bar above the table then offers:

• Mark Timesheets as Reviewed: locks their pay lines, so later runs leave them unchanged.
• Set Public Holiday: treats the timesheets as a public holiday or not, whatever the calendar says (see Set up public holidays).
• Delete Timesheets: removes them from Assignar Pay everywhere, including job costing and invoicing. They are not imported again from Assignar Operations.

To export, open the ⋮ menu on the right of the table, select Export all (or Export with the number selected), then Export as CSV, Export as JSON or Copy for Excel.

Apply pay rates automatically

Instead of selecting Apply Pay Rates each period, you can have Assignar Pay recalculate as timesheets arrive. Turn on Auto-apply pay rates under Settings, General, then Payroll (see Set your payroll cycle). Organizations created since it became the default start with it on; for older organizations it's off until you turn it on.

With it on, Assignar Pay recalculates one worker's timesheets for one pay period, the period the timesheet falls in, whenever one of their timesheets is:

• imported from Assignar Operations or from a CSV file
• created or updated from a form response, such as one sent from My Shifts
• edited: its activity times, role, leave hours or document override

A large import for the same worker and period runs once, not once per timesheet. A message tells you when a background run starts, and the views update when it finishes.

While it is on, the Auto-run Pay Rates for Imported Timesheets option in the timesheet import dialog is hidden, and a timesheet's Rate Calculation Details no longer asks you to apply pay rates again after you edit it.

Apply Pay Rates stays available, for example to recalculate a reviewed timesheet after resetting it, or if a background run fails.