Timesheet spreadsheet import appears on Require Approval and Approved tabs when the user has import permission and the company has timesheet import enabled. Import Hours appears under amendment actions for company admins when import-hours permission exists and either timesheet import is enabled with Timesheets auto-approved on import, or the company uses manual timesheets from the Pending tab. For manual timesheets, enabling Timesheets auto-approved on import makes Import Hours available from the Pending, Require Approval, and Approved tabs. Agency admins can also use Import Hours for their agency timesheets by selecting one eligible company in the dialog before downloading the template or uploading a file. The agency company selector lists only companies where supplier-side timesheet adjustment is enabled and, for import-method companies, Timesheets auto-approved on import is enabled.

​

Use the template action before importing. The template is company-specific so it can reflect the company's weekend day, WRA configuration, enhanced uplifts, and other import rules.

​

The standard import includes reference, worker ID, week ending, hours, pay type, expense hours, expense value, shift type, and assignment. Enter Mileage as a claimed amount in the mileageValue column; it is not calculated from miles or an hourly rate. Daily hour values must use 0.25-hour increments. Shift type accepts only day, night, or backshift; a blank value defaults to day. When WRA or enhanced uplifts are enabled, absence day-type columns can also appear. When WRA accommodation is enabled, the template includes a WRA Accommodation YES/NO column. When WRA travel is enabled, it includes a WRA Travel/Fare Allowance YES/NO column.

​

The importer can look up assignments and flag rows that need a manual assignment selection, including cases where more than one assignment matches the supplied reference. Assignment links can be opened from the importer for review. For hirers, the downloadable exceptions report carries through supplied worker reference and name, site and agency names, and assignment details when those columns are present in the uploaded file. When a row has no site or agency name, the importer uses the matching ID and name from the uploaded template's project or agency reference sheet if available. It also shows worker details found during matching, even when no assignment matches. Details that were neither supplied nor matched remain blank. For rows with no matching assignment, otherAssignment lists alternative assignment references for the same worker and agency on other projects within the hiring company, subject to the existing assignment-date and active-assignment import settings. These are suggestions to review before cloning; they are not selected or imported automatically. Completed assignments can appear when eligible under those settings. The exceptions report includes each row’s week ending in the we column, and its filename includes the imported week ending or the first and last week endings for a multi-week file. Agencies cannot create timesheets through this import.

​

Hirers can enable Single-row import under Company > Configuration > Timesheets > Import Method. The option is off by default, so each company can adopt it separately. Download a fresh company template after changing the setting. The import preview hides the Shift Type column when Single-row import is enabled. The default format keeps the row-level shiftType column; the single-row format replaces it with monShiftType through sunShiftType next to the daily hours. Each daily shift accepts day, night, or backshift. A blank daily shift defaults to day. Older files with a row-level shiftType remain supported: it supplies the default for blank daily shift fields.

Use one row per assignment and week ending, with a unique Ref. For example, GSA-A126 can have mon=8 with monShiftType=day, tue=8 with tueShiftType=night, and wed=8 with wedShiftType=backshift on one row. This creates one weekly timesheet, preserving each day's shift type and applying the assignment's applicable rates and uplift rules. Multiple rows for the same assignment and week ending are rejected, including after manual assignment selection. Daily shift fields cannot be used while the company option is off.

Existing cost-code, piece-work, expense, WRA, approval, and assignment-matching rules still apply. The completion email counts import rows and identifies failed rows by Ref and week ending. When automatic approval is enabled and a purchase order is required, an imported timesheet is approved only with an active purchase order, or an expired purchase order covering the timesheet period. Agencies cannot create timesheets through this import; they see one weekly timesheet with mixed daily shifts and can use Import Hours where the hirer permits it.

​

When the company has at least one active piece rate with values, the downloaded template includes a separate 'piece work' sheet for capturing piece-rate units alongside hours during the same import and the guidance sheet references this as 'PIECE WORK'. Each row on the template sheet represents one timesheet. Use the Ref column to attach any number of piece work rows to that timesheet; for example, a template row with Ref 1 can have five daily rows on the piece work sheet that also use Ref 1. The piece work sheet starts with five example rows. PieceRateCode is the code from the company rate card. Date is required in DD/MM/YYYY format for daily piece rates and ignored for weekly ones. Units accepts decimals at full precision (displayed to two decimals). CostCode is optional; when supplied, it must be a valid cost code for the project.

When the company has at least one active cost code, the template includes a 'cost codes' reference sheet with deduplicated CostCode and Description values to help complete daily cost-code allocation columns and piece work CostCode values. Because cost codes are validated against the timesheet's project, a code shown on the reference sheet must still be valid for the relevant project.

When the company has at least one active piece rate with values, the template also includes a final 'piece rates' reference sheet. Use this sheet to find the available PieceRateCode values, names, trade, region, sector, and frequency before completing the piece work sheet. Companies without active piece rates with values do not receive the piece work or piece rates sheets.

Validation runs server-side per row before processing: piece-rate codes must be active and available for the assignment's trade and project region or sector, missing dates on daily lines are rejected, invalid cost-code allocation formats are rejected, and cost codes that are inactive or not valid for the timesheet's project cause the row to be treated as an exception. These issues appear in the downloadable exceptions sheet during assignment matching and are also enforced during import. Existing assignment piece-rate snapshots take precedence. Without active assignment cost or markup overrides, ordinary piece-work processing preserves their saved pay, costs, markup and charge even if current company settings or agency adjustments change. Explicit assignment amendments remain a separate repricing action. For pieces without an assignment snapshot, the import resolves the applicable project, agency, tier or company rate and applies project costs and markup together. These values determine the charges shown to hirers and agencies. Captured piece-rate values are snapshot at the time of import with any assignment-level employer-cost and markup overrides applied, so subsequent rate-card edits do not retroactively change the imported timesheet.

For both hirers and agencies, dated piece work must fall within the actual start and end dates of the target timesheet, including when its period is shorter than seven days. Out-of-period dates are rejected on creation imports and adjustment imports.

​

When WRA accommodation is enabled, the importer calculates whether WRA is applicable using the effective company or project accommodation configuration. Project WRA override configuration takes precedence when enabled. Authorised absence, unauthorised absence, and non-working day values are supported when the configuration requires them.

For hiring-company timesheet imports, YES in the WRA Accommodation or WRA Travel/Fare Allowance column applies that allowance to the matched assignment during automatic confirmation. The importer then creates and reconciles the applicable accommodation or travel/fare expenses for the imported payable days. Existing assignment allowance flags are not removed by importing NO. When hirers import several weeks for the same assignment, later rows retain allowances enabled by earlier successfully imported rows, including when the later value is NO or blank. Travel values still depend on the assignment distance, fixed-depot and free-transport details, the date-effective rate table, and the effective project or company WRA configuration. Travel and accommodation cannot both be applied unless the effective configuration allows overlap.

Agencies do not create timesheets through this spreadsheet import. Where an imported assignment belongs to an agency, the hiring company's import controls the allowance flag and the automatically reconciled expenses that the agency subsequently sees on the timesheet.

When the assignment uses enhanced uplifts, imported hours use the enhanced uplift rules for threshold-based uplift calculation rather than adding separate weekday overtime simply because the imported day is longer than the assignment's standard shift.

​

Import Hours uses a separate template for daily hour adjustments by timesheet reference. The downloaded file name includes the selected company name, and agency admins can import for only that selected company at a time. The Hours sheet orders its day columns to match the company's working week. It supports up to 100 rows per import. Each day column must contain a numeric value with no more than two decimals. For hourly timesheets, use 0.25-hour increments, between 0 and 24 in absolute mode or -24 and 24 in delta mode; the resulting hours must remain between 0 and 24. For daily-paid timesheets, use 0.25-day increments with a resulting total between 0 and 2 day units per day. Delta mode may subtract units, but the resulting total must still meet these limits. Invalid rows are reported as exceptions rather than capped. These checks apply to both hiring-company and agency imports.

When the company has at least one active piece rate with values, the Import Hours template also includes an optional Piece Work sheet and a Piece Rates reference sheet listing PieceRateCode, name, trade, region, sector, and frequency values. The reference sheet includes applicable company-agency piece rates, and agency admins receive only rates for their selected agency. Piece work rows are matched by Timesheet Ref and can be imported with or without hour changes for the same timesheet, including files where the Hours sheet has no data rows. PieceRateCode is the code from the rate card, Units is required for payable work, and Date is required in DD/MM/YYYY format for daily piece rates. In absolute mode, imported piece-rate values replace the timesheet's existing piece-rate entries. In delta mode, imported units are added to or subtracted from existing piece work. Saved values are snapshot with the assignment's applicable rates and markup after server-side validation.

For companies that use timesheet spreadsheet import, Import Hours can adjust rows only when Timesheets auto-approved on import is enabled; eligible Approved rows remain Approved after adjustment. For companies that use manual timesheets, Import Hours can adjust only Pending timesheets by default. When Timesheets auto-approved on import is enabled, eligible Pending, Require Approval, and Approved rows are accepted and saved as Approved without sending a new manager approval request. The new manual-timesheet setting is off by default. Cancelled, absent, and invoiced timesheets remain ineligible.

When an agency admin imports hour adjustments, each row is checked against the timesheet's company and project timesheet-adjustment configuration. Rows where supplier-side adjustment is not allowed are reported as exceptions and are not saved.

​

Import Hours validates the file, checks for missing or duplicate timesheet references, previews daily before and after values, and reports row exceptions before saving. Fix validation errors in the spreadsheet and re-upload before continuing.

​

For hirer spreadsheet timesheet imports, assignment matching and final submission each accept up to 50,000 timesheet rows and a 10 MiB request payload. The payload is the imported row data sent to Requidex, so its size can differ from the spreadsheet file size. Larger payloads return HTTP 413. Split large spreadsheets into smaller batches and avoid resubmitting rows that have already imported successfully.

These limits apply to spreadsheet creation of timesheets. Agency Import Hours adjusts existing timesheets through a separate workflow and is not subject to these two endpoint-specific limits. Existing permissions and adjustment rules still apply.

​

If you work for an agency, you cannot create timesheets from scratch, but you can adjust hours through Import Hours when the hiring company has enabled it for your agency.

​

When the hirer selects Lodge-to-project journeys, dated imported hours determine stays and journey expenses. No new import column is needed. In the hirer’s create-timesheet import, YES in WRA Travel/Fare Allowance applies travel eligibility to the assignment; NO does not remove an existing travel flag. Both lodge and project postcodes are required, and fixed-depot workers do not qualify. Travel and accommodation can both apply only when the effective overlap setting allows it.

Imported timesheets are treated as complete for their covered dates: blank and zero-hour days count as non-working evidence and can end a stay. Consecutive worked days on the same assignment continue across week boundaries. Completely blank pending placeholders do not end a stay. A worked assignment end date establishes the return immediately.

The return is dated on the last worked day but uses the payment week of the timesheet supplying the non-working evidence. All eligible assignments share at most two paid journeys per worker, company and agency each week; extra journeys are unpaid without carry-forward. Review adjacent weeks when correcting hours.

With Pay regardless of days worked enabled, hours do not determine journey quantities. A daily 04:00 UK-time reconciler allocates the latest completed company week, creating a pending timesheet if needed for a no-hours week. Partial active weeks qualify without proration, subject to the same shared cap. Normal timesheet approval is required before billing.

Agencies use Import Hours to adjust existing timesheets where permitted and can review the resulting expenses for their own workers. Hours corrections recalculate unbilled stay-based travel; billed travel remains unchanged and requires separate review. Corrections do not automatically create billed adjustments or credits. See WRA Travel and Fare Allowance on Timesheets for full configuration and reconciliation rules.