Skip to main content

Push timesheets to Greentree payroll (live push)

Send approved timesheets from a pay run straight into Greentree payroll, what's sent, and how to fix failures.

When you need this

You want approved timesheets sent straight into Greentree payroll (Browser Timesheets) from a pay run, instead of exporting and importing a CSV file.

Live timesheet push is switched on per company by SprintSuite. It only sends payroll timesheets. If you need job costing timesheets in Greentree, use the CSV export.

Before you start

  • Greentree is connected and the Company code is set.

  • Your role has the Greentree timesheet push permission under Staff Times, at Read & Write.

  • Each staff member is linked to a Greentree employee who is enrolled for browser timesheets in Greentree.

  • On Pay Types → Shift Types, each shift type and non-producing type has a Greentree pay type, Work Centre, and ideally an activity code.

  • Work Centres and activity codes are synced.

  • Every job used on timesheets is synced or linked to Greentree, and every entry has a department.

Steps

  1. Open Settings → Integrations → Greentree → General and turn on Enable API timesheet push.

  2. Optionally, set a default activity code under Procurement → Defaults for Job-linked pushes. Live push uses it when a pay type has no activity code.

  3. Go to Staff Times → Pay Runs and open the pay run's timesheets.

  4. Tick the staff to send, then click Push to Greentree.

  5. Watch each row: Pending, Sending…, then Sent with a Greentree reference, or Failed with the reason.

What goes to Greentree

One payroll timesheet per employee per week ending date, with a line for each manager-approved entry: date, hours, start and finish times, pay type, activity code, Work Centre, job and branch.

Good to know

  • Rows that fail checks are marked Failed, but valid rows in the same push still go through.

  • Failed rows aren't retried automatically. Fix the cause, tick them again and push.

  • If a retry finds Greentree already has that employee's week, SprintSuite marks it Sent without posting it twice.

  • For fortnightly pay runs, the worst status of the two weeks is shown.

  • Changes made in Greentree don't sync back to SprintSuite.

  • Your company may require staff to sign their timesheets before they can be pushed.

Pay run status

The Greentree API Push Status column on Pay Runs shows Pass when every week is Sent, Partial for a mix, or Failed. It's separate from the CSV export status.

What success looks like

  • Every pushed row shows Sent, and the pay run shows Pass.

  • The timesheets appear in Greentree's browser timesheets for that week.

If it fails

Message

Fix

Staff is not linked to a Greentree employee

Link them on the Staff tab

No approved entries to push

Approve the entries, and get staff signatures if your company requires them

No Greentree pay type mapped

Map it on Pay Types

No Greentree activity code

Add one on Pay Types, or set the default

No Greentree work centre mapped

Sync Work Centres and map one on Pay Types

Entry has no department

Set a department on the entry or job

Timesheet has no job, or the job isn't linked

Assign a job, then sync or link it

Employee not enrolled for browser timesheets

Enrol them in Greentree

Closed payroll period

Reopen the period in Greentree, or move the times

If wrong data reached Greentree, correct it in Greentree first, then contact SprintSuite support to reset the push so you can send it again.

Did this answer your question?