Integration · Payroll and invoicing

Approved hours into Sage, one pay element at a time

Close the pay week in TempClock: check exceptions, approve, lock and export. You get a Sage 50 Payroll import file in Sage's own layout, built from figures that never change once locked. Client invoices go to Sage Accounting with Push to Sage (tried with your Sage business during set-up), or to Sage 50 Accounts by file.

Talk to us See how it works
app.tempclock.com/admin/close_week
Time & Pay · Close week Week locked
1. Check exceptions Done
2. Approve the remaining shifts Done
3. Lock the week Frozen
4. Export to Sage Ready
24
workers
41
pay lines
£11,406
gross pay
Batch #12 · recorded and kept Export to Sage
Illustration. Check exceptions, approve, lock, then export from the frozen figures.
01/What connects

Approved hours, in Sage's own layout

TempClock prices every shift with one rules engine, freezes the week when you lock it, and writes the Sage file from those frozen figures. During set-up we import a test week into a copy of your Sage company, with your payment codes, before the first live run.

One line per worker per Sage payment

Basic, overtime, weekend, Sunday, bank holiday and night hours go to the Sage payment you map them to. Sage pays Hours x Rate, and the rate is set so the pay matches TempClock to the penny.

Your payment codes

You set the Sage payment reference for each element in Settings, and choose where department and cost centre come from (site, cost code or client).

Locked figures that never change

Only approved shifts are exported, with every left-out shift listed and why. Close week exports a locked week from its frozen figures, and a clock that arrives after the lock goes into the next week as an adjustment. Each export is a recorded batch, and exporting again needs a reason.

Invoices to Sage Accounting

Push to Sage on the charge schedule sends a closed week to Sage Accounting (cloud) through Sage's API: one sales invoice per site, never sent twice, with paid status read back every 6 hours. Sage 50 Accounts gets an invoice import file instead.

The payroll path
In TempClock Close the pay week
Export Sage 50 hours and rates file
In Sage 50 Payroll Data Import: payment hours and rates

Payroll goes by file, imported with Sage's own import. Sage has no API for UK payroll.

02/The file

Hours and rates for each worker and payment

Sage 50 Payroll's own payment hours and rates layout, with your payment references. Sage pays Hours x Rate, so TempClock sets the rate to give the exact pay. We prove it with a test import into a copy of your Sage company before the first live run. 

# Sage 50 Payroll: Employee Payments (Hours and Rates) import (sample data)
Employee Reference,Payment Reference,Hours,Rate
1042,1,37.50,12.50
1042,2,4.00,18.75
1043,5,24.00,14.00

Header row first · CSV (Comma delimited) · one line per worker per payment · sample figures

In Sage 50 Payroll: File, Data Import, Import Sage Payroll Data, then Employee Payments (Hours and Rates). TempClock refuses payment references Sage would reject (letters, numbers and spaces only) and tells you why. Each payment must already be assigned to the worker in Sage.

02/The benefit

No re-keying, and a week that stays closed

The hours that reach payroll are the approved hours, priced once and frozen when the week was locked. Nothing that happens later moves them.

Close the week in one place

Check exceptions, approve what is left, lock the week, export to Sage and produce the charge schedule, on one page. Red items stop the lock until they are dealt with.

The figures reconcile

The payroll screen, the Sage file, the payroll API and the charge schedule use the same pricing engine, so the pay in Sage matches what you saw in TempClock.

An audit you can defend

Every exported line traces back to shifts, their clocks, any corrections with reasons, and the batch it was exported in.

03/Honest scope

What the Sage connection does, and does not, do

Payroll goes by file because Sage offers no API for UK payroll. Invoices can go by API to Sage Accounting, or by file to Sage 50 Accounts. We would rather be plain about the difference.

Included today

A Sage 50 Payroll import file in Sage's payment hours and rates layout: employee reference, payment reference, hours, rate, one line per worker per payment, checked against Sage's published import rules and proven with a test import in a copy of your company
A checking copy of the same week with names, amounts, departments and cost centres
A Sage Payroll (cloud) list to enter by hand (Sage documents no import of pay values for its UK cloud payroll)
A generic payroll CSV and a Detailed one-row-per-shift file for checking
Only approved shifts (from Close week, a locked pay week's frozen figures), with each export kept as a batch with a checksum, and a reason needed to export again
A Sage 50 Accounts sales invoice file from the charge schedule, with each site's own Sage customer reference
Push to Sage for Sage Accounting: one sales invoice per site from a closed week, never created twice, with paid status read back every 6 hours. We try it with your Sage business during set-up before you rely on it

Not part of this connection

Pushing pay values into Sage Payroll by API (Sage has no UK payroll API)
Running the pay run or payslips: that stays in Sage
Pulling employee records out of Sage into TempClock
A direct API link to Sage 50 desktop (it has none): Sage 50 Accounts gets an invoice import file

Need the step-by-step? See the Close the pay week guide, the Sage payroll file guide and the Sage Accounting guide.

Other integrations

Xero Invoice and timesheet files API and webhooks Connect your own systems Card readers: coming soon NFC and RFID cards, once tested Microsoft 365 Send mail from your own tenant Twilio Optional SMS add-on

Building something custom? The REST API (version 1.3) and signed webhooks let you connect any system.

Approve hours here, pay them in Sage

We import a test week into a copy of your Sage company during set-up, with your payment codes, before the first live run. Tell us how your payroll week works.

Talk to us See pricing

Hosted in the EU · Your largest site live first, with us alongside · No app needed to clock in