Supplier timesheets

For professionals and agency workers, Saral turns the Site Register into a priced timesheet each period, sends it to the supplier to approve, raises the invoice from it and follows that invoice to payment. Exceptions first: a clean week goes straight to the supplier and never appears here. The office only sees what waits for it — a timesheet that needs a look, a dispute, an invoice to decide, a delivery that failed, a rate waiting for a second person. CIS subcontractors have their own screens and are untouched by this one.

You enter

On a timesheet that needs a look: fix the register or the rate and Rebuild from register, or Send to supplier when the days are right as they stand; Build last period now when you do not want to wait for the nightly build.
On a dispute: the answer to the supplier's issue — a corrected version or a reply.
On an invoice: accept a held one, reject it with a supplier-safe reason, ask a query, or — for a bill processed in another app — mark it approved or paid by hand.
On a rate card: Approve or Reject a proposed rate (a second person, while two-person rates are on).

Saral fills in

The timesheet: every register day in the period for each professional and agency worker, priced at their confirmed rate card, with the reasons it waits — a self-marked day, a missing check-out, no confirmed rate, no paying company.
The supplier's answer: approved, an issue raised, or deemed approved after the number of days set in HR settings with no reply; the version number each time a correction goes out.
The invoice raised from an approved timesheet and its payment-queue step — the same status the supplier sees in their portal.
Where each invoice went: into BillScan, to the accounts inbox, or downloaded — and which deliveries failed.

It produces

A timesheet per worker per period, approved by the supplier, and the invoice raised from it.
Each invoice delivered into BillScan or the accounts-software inbox, or the period's invoices as a bill-import CSV for Xero, QuickBooks or Sage, with each invoice's PDF.
A decided rate card, which every later timesheet is priced from.

What this page is for

A professional and an agency worker are paid at a rate, from the days the Site Register recorded, like a CIS subcontractor — but they invoice you themselves, and the money goes through their own invoice. This screen is the office end of that route: the register becomes a priced timesheet, the supplier approves it in their portal, the invoice is raised from the approved timesheet and delivered into the accounts system, and its payment is followed on the Invoices tab. The route is built so a clean period needs nobody: only exceptions surface here, worst first.

From the register to an approved timesheet

Each period Saral builds one timesheet per worker from their register days, priced at the confirmed rate card for that worker or that agency role. A sheet with a problem — a self-marked day, a missing check-out, no confirmed rate, a day with no paying company — stops under Needs a look; everything else goes straight to the supplier. The supplier approves or raises an issue; silence past the deemed-approval days counts as approval. A correction after sending makes a new version, and the supplier is told. The period length and the deemed-approval days are set on HR → Settings → Supplier invoices.

From an approved timesheet to a paid invoice

An approved timesheet raises the invoice and delivers it — into BillScan when the subscription has it, so it is read and matched like any supplier bill; to the accounts-software inbox one invoice per email; or as a download. The Invoices tab is the single place the office decides: accept a held invoice, reject it with a reason the supplier can read, ask a query, or close one. A bill handled in another app can be marked approved or paid by hand, and the row says it was updated by the office. Delivery shows every failed send with a Resend.

Rates need two people

A rate card prices every timesheet after it, so a new or changed card waits on Rates to approve before it is used. With two people for a rate switched on — the default — whoever proposed the card cannot approve it, and nobody approves a rate on their own worker record; the server refuses both. Approving needs permission to edit commercial terms. The confirmed rate is what Needs a look is waiting for on every new starter.

Where the settings live

The timesheet period, the deemed-approval days, the match tolerance, where invoices are delivered and the two-people-for-a-rate switch are all on HR → Settings → Supplier invoices. The rate cards themselves are proposed on the worker's record and on the agency's record (HR → Agencies). The register these timesheets are built from is HR → Site Register. The supplier's own view — approve, raise an issue, see the payment step — is their portal. Payroll for employees runs in your payroll app, not here.

Next screen: /hr/payment-batch

Not what you needed? Inside Saral, ask Kuku (Alt+K) — if it cannot answer, “Ask a human” sends the question to Saral support with the chat attached.