Finance, Agencies, Config, Competency Matrix, Rates, and Log are shown to admin users where their role and access-control settings allow them. Rate data can be hidden when rates access control is restricted.

​

The Finance tab controls whether the project bills as the parent business and whether it uses the parent billing address. If inheritance is turned off, project-level tax, VAT, registration, deduction status, billing name, and billing address fields become editable.

​

The Agencies tab manages project-level agency setup. Administrators can add or amend agency configuration, remove agencies from the project, export agency data, or revert a project-specific override back to the company-level setup.

​

Hirers can open an overridden agency on the project Agencies tab and select Company comparison to see only the differences between its saved project configuration and the current company agency configuration, with values side by side. Unsaved dialog edits are excluded. If the company configuration cannot be loaded, use Retry. Agencies continue to see the resulting rates and permissions rather than this configuration comparison.

Company agency setup is the default. A project override is used when the project needs different agency settings. Removing an agency excludes it from the project, while reverting an override returns the agency to company-level setup.

When hirers create or edit an Agencies rule on the company Access Control page, the Agencies selector includes all connected suppliers, including those restricted at company level. This allows rules to cover suppliers that are unrestricted for a specific project. Selecting a supplier in an access control rule does not change its company or project restriction settings. Agencies can receive requisitions only where the project’s supplier settings and the hirer user’s access control rules allow selection.

​

The Rates tab shows project and supplier rates. For hirers and agencies with restricted rate access, financial amounts are hidden on both master and agency override cards; the availability of hourly, daily, and piece rates is preserved. Hiring-company users can switch between By location and By trade. By location keeps the sector and region tabs for reviewing a complete location rate card. Hover over a shortened sector or region tab name to see its full name in a tooltip. By trade provides a searchable trade selector and optional sector and region filters, then lists the selected trade across matching locations with Region and Sector columns. Searching for a known trade from By location opens that trade in By trade. The selected display and trade are reflected in the page URL. For agency users, the Rates page uses the filter panel to select the connected client company and trade; the first available company and trade are selected by default, and those filters cannot be cleared. If the company has no regions or no sectors, the Rates page prompts users to complete company setup before rates can be added or imported. When adding one time rate, adding one piece rate, or importing rates, hirers first choose whether the rate is a company, project, project-and-agency, agency, or tier rate. The form then shows only the project, agency, or tier fields required for that choice. Company and agency choices apply across the selected region and sector, while an import can apply project choices to one or more selected projects. A project rate can be added without a company rate for the same trade, region, and sector. A project-agency rate can use that project rate as its parent. Company-agency and tier rates still require a company base rate. Hirers can create or import project-only rates, and agencies see them when connected to that project. The applicable rate is selected in this order: project-agency rate, project rate, company-agency rate, company tier rate, then company base rate. An agency's existing tier determines which company tier rate card applies when no more specific rate exists, with the company base rate used when that tier card does not exist. Company agency and tier cards appear as labelled rows inside the matching company rate's expandable Rate Scope section rather than appearing as duplicate company rates. A company admin with reset-rate permission can open and delete a company-agency or tier rate from the dialog only before that rate has been used; subsequent rate resolution falls back to the next applicable project, tier, or company rate. Project time rates and project piece rates inherit independently, so a project can override piece rates while hourly or daily time rates continue to come from the company rate card. Agency markup uses the selected trade adjustment when configured and otherwise uses the agency default adjustment. An active assignment markup override replaces that resolved percentage. Piece rates can be created from the Rates page actions menu for active trades, including trades that do not yet have hourly or daily rates, or imported as active rates from the rates import template; the singular and plural unit labels are required in both workflows, and piece-rate codes are generated by the system. Duplicate piece-rate rows in an import file are skipped and listed in the downloaded exceptions report before saving. Piece rates with values for the selected rate type appear when the rates table is switched to Piece rates and can be marked active or inactive after creation. Inactive piece rates remain on the rate card but are not offered for new timesheet piece-work entry. Piece-rate charge values use the assignment agency's applicable trade markup adjustment unless an assignment markup override is active. Piece rates can be deleted only before they have been used on a timesheet. Users with reset-rate permission can reset project and supplier rates back to the company-level rate card when project or supplier overrides exist.

When importing rates for several projects, the result identifies any projects that could not be updated if the import only partly succeeds.

Company agency markup and employer costs are optional and may be left unconfigured. When agency markup is unconfigured, any agency markup adjustment still applies to the pay rate for PAYE, CIS and PSC. Hiring companies can clear the company markup value or remove employer cost components and save. Before removing a component referenced by agency markup, remove that code from the markup’s Based On selection or clear the affected markup. Company cost changes check project markups only where the effective employer costs or markup being edited will change, including on inactive projects. Projects whose effective configuration is unchanged keep their existing hirer and agency rates. Project cost changes and reverts check the resulting effective markup and costs. Invalid changes are rejected before costs or rates are saved, and company errors identify the affected project. After clearing PAYE markup or changing it to pay alone, hirers can remove the old PAYE cost components when no other effective markup uses them. Untouched CIS and PSC settings with no configured costs do not block removal; agencies continue to receive their existing pay-based markup. The Complete finance information onboarding step can be checked or unchecked manually after reviewing the relevant finance details, even when neither cost is configured. Hiring companies can configure employer cost components as a percentage or as a fixed value per rate unit. Use the PAYE, CIS and PSC tabs to configure components independently for each rate type. The same component can have different values, calculation types and Based On settings in each tab. Add applies to the selected tab, switching tabs preserves unsaved edits, and Save changes saves all tabs. Existing components without a rate type remain under PAYE; previously shared components retain their values in each relevant tab. Only components for the rate type and applicable sector contribute to costs. A percentage cost component can depend only on Pay Rate or another component configured for the same rate type. Components excluded by sector contribute zero. Agency Markup Configuration always shows PAYE, CIS and PSC, including rate types without cost components. Each rate type has its own percentage and Based On selection. Editing PAYE does not change CIS or PSC; review and edit each applicable tab. Choose Pay Rate and the individual cost components configured for that rate type. Switching tabs preserves unsaved edits and Save changes saves the edited tabs together. Clear a tab’s percentage for no base markup; agency adjustments then apply to pay alone. When adding a project markup override, only the edited tabs become project settings. Untouched tabs continue to follow later company markup changes for both hirer and agency rate cards. On projects, clearing a percentage sets no base markup for that tab; it does not inherit company markup. Existing whole-project markup overrides keep their saved settings for all rate types. Revert all tabs to company defaults restores company inheritance for every tab; you can then edit just the tabs that need project settings. Company and project Finance show the shared markup percentage when PAYE, CIS and PSC match, and By rate type only when their percentages differ. For hirers and agencies, time and piece-rate tables retain the PAYE employer-cost column. CIS and PSC columns are shown when the effective configuration includes that rate type or displayed rates contain saved costs, including expanded project and agency rows. When hirers add time or piece rates or preview an import, cost fields follow the selected project’s effective configuration, including an explicitly empty project cost configuration. Clearing the project selection restores company costs. Piece-rate edits also show employer costs already saved on the rate. Hiring companies can set a cost label for each rate type in the company’s Preferred Phrasing settings. Blank labels use Employer Costs. Projects inherit these labels, and hirers and agencies see them in rate screens, assignment cost breakdowns, assignment emails and rate exports. On first markup setup, entering a PAYE percentage also sets that percentage on Pay Rate for untouched CIS and PSC tabs. Separately edited tabs and existing markup configurations are preserved. Agencies see the resulting rates. Each unconfigured rate-type tab displays the percentage and full Based On selection from the previous shared markup settings. These defaults are separate from any later PAYE-specific override; editing PAYE does not change the defaults for untouched CIS or PSC tabs. Viewing tabs or reopening the Based On selector does not create an override. Existing shared markup settings retain their calculations until that rate type is edited. For these untouched settings, CIS and PSC without applicable employer costs use pay alone. When saving an explicit override, hirers must select costs configured for that rate type or remove unavailable costs from Based On. Agencies continue to see the resulting rates. An edited tab always uses its selected Based On values, with sector-excluded components contributing zero. Percentage components use their selected Based On values, while fixed components stay unchanged, including when enhanced uplift bands increase pay, and are labelled with the currency symbol for the company's jurisdiction; either type can be included in or excluded from the calculation base for later percentage components and agency markup. Agencies see the resulting employer cost and charge rates rather than configuring these assumptions. New projects inherit company employer costs and agency markup until a different project-specific value is saved. Saving a project cost configuration recalculates costs, markup and charges while preserving applicable pay. Hourly, daily and piece-rate slots without positive pay remain unchanged, so fixed costs do not create charges on unused slots. When this creates project cards, existing company-agency or tier pay is retained in project-agency cards; explicit project pay continues to take precedence. These project cards are separate from the company cards. Project-level employer cost configuration applies to the project rate-card sector, so sector restriction fields are only shown in the company-level cost configuration dialog. On the first project cost edit, inherited company components excluded from that sector appear as fixed zero-cost entries. Their codes remain available to dependencies, but they contribute nothing unless explicitly changed. The project Finance tab marks employer cost overrides and stored agency markup overrides with an Override label, and the configuration dialog can revert all employer-cost or agency-markup tabs to the company defaults. Removing all project cost components and saving leaves an explicit zero-cost configuration; it does not restore company components. Explicit project cost and agency markup overrides remain marked and can be reverted even when their values match the company defaults. Matching values do not restore inheritance; use Revert to company defaults to remove the stored override. Company Finance shows an override indicator next to employer cost or agency markup fields when projects use a different value; hover the indicator to see the project names.

Agency users choose the connected client company when exporting rates and when exporting the AWR report. Rate export filenames use the shared export naming format: rates, the company or agency scope, and the export date, for example rates-acme-ltd-23-05-2026.xlsx. Rate exports identify company tier cards in the tier column, include hourly and daily rows only for configured rate types, keep different project or agency override values, and omit project rows that duplicate the matching company-scoped rate values. Piece-only rates appear on the Piece Rates sheets.

A saved project time rate of £0 is an explicit override and is shown as a project override in company and project rate cards for hirers and agencies. Company rates are inherited only when the project rate for that pay type and hourly or daily basis is absent. No rate is saved as zero and displayed as -, and blocks new requisitions. POA is a separate explicit choice that allows requisitions and pending assignments while pricing is agreed; hirers and agencies must set positive assignment pay and charge before confirming time-based work. Selecting No rate saves an explicit zero override and keeps that time rate unavailable. If no applicable time rate or active piece-work rate remains, the trade is unavailable when raising a requisition.

​

Project Config can use company uplifts or project-specific uplifts. Standard uplifts apply a single percentage for the whole day. Enhanced uplifts allow day and time-based uplift configuration and update the project shift pattern from the enhanced uplift setup.

Hiring-company users with project edit permission open an agency's Rate Uplifts tab, then use Agency Uplifts for agency-wide standard or enhanced settings and the trade overrides sub-tab to search and review which trades inherit or override those settings. Opening a trade row or its accessible action menu launches a separate configuration dialog for standard or enhanced uplifts. Entered standard, regional, and enhanced block percentages are required and must be finite numbers of -100% or above with no upper limit. Negative percentages reduce the applicable rate: for example, -20% applies 80% of the basic rate. Configure an agency override to apply this to a specific supplier. Agencies see the resulting rates on their assignments and timesheets. A project-agency trade override takes priority, followed by the wider project-agency and project settings, then company-agency trade, company-agency, and company settings. Under a standard trade override, an uplift type without a configured row is treated as 0% rather than inherited. Removing a trade override restores the fallback order. The applicable settings are snapshotted when an assignment is created, including when an existing requisition is fulfilled. A requisition raised before an agency trade uplift override was saved can still use that override for a new assignment. Hirers and agencies should review the saved assignment rates before submitting timesheets; existing assignments are not changed automatically.

When a weekly night threshold is enforced, the first-block night allowance remains on eligible hours worked. If normal working hours are short, higher night overtime premiums are reduced by the shortfall, starting with the highest premium. Bank holiday night premiums remain protected. Active authorised Monday–Friday absences protect normal hours only when authorised-absence threshold reduction is enabled. The reduction uses the duration of the earliest configured block for the recorded shift type; weekend, inactive and unauthorised absences do not reduce the threshold. A missing night threshold inherits the normal weekly threshold, while an explicit zero remains zero. Where night blocks have distinct thresholds, those block thresholds continue to apply separately. The timesheet threshold calculation shows normal weekly hours, night premium hours, the shortfall, and the premium hours still payable. Hiring companies configure these rules, and agencies see the resulting rates on affected timesheets.

​

When project-specific standard uplifts are enabled, at least one project rate uplift must be configured before saving. Enhanced uplift changes are saved back to the project configuration and can also drive the project shift pattern. Each configured day, night, and backshift requires a break assumption before the enhanced uplift setup can be saved.

New enhanced uplift configurations enable uplift rules for every day, including Saturdays, Sundays, and bank holidays. Hirers should review each shift's percentage blocks; a 0% block gives no uplift. To reuse a day's settings, select the Day, Night, or Backshift tab and the source day, then choose Copy to in the editor footer. In the copy dialog, select the destination days and apply the copy before saving the uplift configuration. This replaces only the selected shift type's blocks, start time, and break assumption on the destination days. Other shift types and the default shift pattern setting are unchanged. The Default shift pattern setting controls scheduling separately, with weekends and bank holidays excluded by default. Agencies receive the configured uplifts when hours worked on those days are calculated under the assignment's enhanced uplift settings.

​

The project requisition setting Auto assign qualifying workers by default controls whether matching workers should be auto-assigned by default when requisitions use the project.

​

The project Competency Matrix tab can define project-specific competency requirements for individual trades. Choose Combine with inherited requirements to keep the current company or sector matrix in effect, or choose Use project requirements only to apply only the project requirements. A requisition-level competency amendment still takes precedence for that requisition.

Combine with inherited requirements stays linked to the company or sector matrix, so later changes to inherited requirements also apply to the project. Exact duplicate requirements are included only once.

When bulk amending project competency requirements, hiring companies choose whether to add, remove, or replace project-specific requirements separately from the inheritance setting. The selected inheritance setting applies to every selected trade, and the dialog warns when it will change an existing project entry. Removing a project-specific competency does not remove a company or sector requirement. Reset project requirements in the bulk amend dialog removes every project competency override and returns all trades on the project to inherited company or sector requirements.

Project competency exports include each stored project entry's requirement mode as extend or replace, including project entries with no project-specific requirements. This allows hiring companies to identify whether the exported project requirements were combined with inherited requirements or used on their own. Agencies continue to see the resulting effective requirements rather than configuring the inheritance mode.

If a project override is created before the trade has a company-level competency matrix, the system also creates a base matrix with no requirements. Other projects continue to use the company-level matrix unless their own override or requisition amendment applies.

Project competency overrides are hiring-company configuration. Agencies see the effective competency requirements when submitting or reviewing workers, and worker eligibility checks use the effective project or requisition requirements.

​

Timesheet adjustment can be configured so adjustments are handled by the supplier only, project only, or supplier or project. An override indicator is shown on a project when it has its own supplier setting. On the company Agency Actions configuration, the matching indicator beside Timesheet Adjustment lists the projects with their own supplier setting. Project values that match the company configuration are cleared when the project is saved so those values inherit future company changes.

​

Hirers can configure Timesheet Request Approval separately from Timesheet Adjustment, choosing supplier only, project only, or supplier or project. Project values override company Agency Actions settings; matching values are cleared on save so future company changes are inherited. Override indicators identify projects with their own supplier setting. When the company first saves the separate request approval setting, existing project request access is preserved from its previous timesheet adjustment settings.

For agencies, request approval access applies to single and bulk requests for pending timesheets. It does not grant amendment or recall access; those continue to use Timesheet Adjustment. Existing user permissions still apply.

​

Worker permissions and worker notification settings can be configured at company level and overridden on individual projects. Project overrides apply to worker timesheet access, worker expense submission, cost code allocation, timesheet and expense approval notifications, and assignment created notifications for that project. When a project worker setting is saved with the same value as the company setting, the project override is cleared and the project inherits the company value.

​

​

Allowances settings have separate Default Allowances and Custom Allowances sections. The WRA switch controls default accommodation and travel, each of which also has its own enabled setting. Custom allowances work independently of that switch. Projects can inherit the company settings or enable an override for project values. Project overrides can change lodge thresholds, lodge day subtraction, and payable day floor values. These settings affect allowance behaviour on assignments and timesheets for that project.

The travel allowance rate table is company-owned. A project override changes travel eligibility rules and behaviour but always uses the company rate table. The travel configuration can default the allowance on for new assignments whose calculated worker-home-to-site distance is payable under the rate table in force on the assignment start date. A project override can change this default for assignments on that project. When project travel is enabled, the project Travel (WRA) section also shows the company rate table versions so they can be reviewed or maintained from the project context.

Hirers can add named custom daily allowances with an optional description in company or project Allowances settings. A project-only allowance applies to that project without enabling the WRA project override. Each allowance expands to show its amount, absence payment settings, and payable-day rules. Hirers can choose to show each custom allowance as a named line in invoice totals. Otherwise it remains included in general expenses. Hirers and agencies with invoice access can review these lines on the resulting invoices and AfPs. Save company changes before leaving; navigation and reload warn when changes remain unsaved. Custom allowances do not require an assignment lodge address. A project override can change company-defined allowance settings for that project. Hirers can choose to apply each custom allowance by default to new assignments that meet its trade and home-to-site rules. Otherwise, they can enable agency requests for the allowance when agencies respond to a requisition. Hiring-company administrators can change custom allowance applicability on an assignment. Agencies can see the resulting allowance expenses on their workers' timesheets. Eligible worker-weeks are calculated separately for each allowance, so Food and Health can both be payable in the same week.

​

Authorised hiring-company users can edit the project shift pattern unless enhanced uplifts are controlling the shift. Start and end times are available in 15-minute intervals through 24:00, allowing a full-day shift to end at the day boundary. Sites that have not overridden their own shift pattern are updated when the project shift changes. Agencies use the resulting shift pattern on requisitions and assignments but do not edit the project default.

​

The Finance, Agencies, Config, and Competency Matrix tabs are hiring-company controls, but several of these settings directly determine what your agency earns and can do, so it is worth knowing where they come from.

​

The maximum is two journeys or allocations per worker, company and agency each week, shared across eligible assignments. Extra journeys remain unpaid without carry-forward. Agencies review the expenses for their workers and can maintain accessible assignment lodge addresses; they cannot configure the hiring company’s travel settings.

Pay-regardless reconciliation runs daily at 04:00 UK time for the latest completed company week and creates pending timesheets where needed. Normal timesheet approval is required before billing. Cancelled weeks are not recreated and missed historical weeks are not automatically caught up.

Settings changes apply when unbilled weeks are next recalculated; saving settings does not recalculate all historical weeks. Changing the project postcode recalculates eligible existing unbilled journey expenses after save, and clearing it removes those expenses. A recalculation failure does not undo the project save; review the expenses if a failure occurs. Billed travel remains unchanged. See WRA Travel and Fare Allowance on Timesheets for journey evidence, review and correction rules.