Export timesheets to Smartly
Turn a week of recorded hours into a file Smartly payroll will import.
If you run payroll in Smartly, a week’s timesheets can leave Tradie as a file Smartly accepts, instead of being retyped. You download the file here and upload it in Smartly - there is no direct connection between the two systems.
Setting it up
Four things have to be in place before the first export. Once done, they stay done.
Step by step: set up the export
- Switch on Smartly payroll integration under Payroll Integration in module settings. Nothing Smartly-related appears until you do.
- Open Smartly Row Types from the hamburger menu and check the list matches how your Smartly account is set up. It arrives pre-filled with the usual row numbers.
- On the Users screen, give each person their Smartly Employee Code - the short code Smartly knows them by, not their email address.
- On the Labour Codes screen, give each labour code a Row Type and, where Smartly needs one, a Smartly Code.
Mapping labour codes can wait. Anything unmapped is listed during the export and can be mapped from there.
Running an export
Step by step: export a week
- Open Timesheets and move to the week you want.
- Click Export to Smartly.
- Under Options, choose All timesheets (processed and unprocessed) or Processed timesheets only.
- Tick Count leave days in Days Paid if leave days should count towards each employee’s days paid.
- Tick Include lunch breaks if lunch break entries should be in the file. Left unticked, they are left out.
- Deal with anything listed as excluded - see below.
- Click Export.
The file downloads as Smartly-Timesheets- and the week’s start date. Upload it in
Smartly, under their timesheet import.
What gets left out, and how to fix it
The dialog lists anything that will not make it into the file, and only appears when there is something to report.
Users without a Smartly employee code - their hours are left out entirely. Add the code on the Users screen and export again.
Labour codes not mapped to a Smartly row type - those hours are left out. Pick a Row Type and Smartly Code for each one right there in the dialog. The mapping is saved when you export and applies from then on, so you only do this once per labour code.
Tips
- The two options remember your defaults from module settings, so the routine weekly export is two clicks.
- A row type that is in use cannot be deleted. Untick Active instead, which stops it being picked for new mappings while leaving existing ones alone.
- Check the first file you generate against a known-good pay run before trusting it with a full week.
See also
- Timesheets - where the hours come from.
- Labour codes - the codes being mapped to Smartly row types.
- Download a timesheet report - a printable report rather than a payroll file.