When you need this
GreenTree CSV Activity must resolve for producing timesheet lines. You configure either an explicit Pay Types activity mapping (highest precedence) or Combinations / Automatch letter composition.
Before you start
Activity codes catalogue synced.
Work Centres synced if you use Work Centre fields on Pay Types (not used for CSV Wcentre).
Trades and shift types exist in Sprintsuite.
Steps
A. Pay Types (absolute precedence for CSV Activity)
Open Settings â Integrations â Greentree â Pay Types.
On Shift Types (and Allowances as needed), map Greentree Pay type and optional Activity code.
Save row or Save all mappings. You can also Download current list / Upload CSV for bulk shift/leave mappings where available.
Remember: if a shift type has an Activity code on Pay Types, it is excluded from Activity Codes â Shift types / Combinations editing (shown under Mapped on Pay Types).
B. Combinations / Automatch (when no Pay Types activity)
Open Activity Codes â set trade and shift-type letter codes (see Compose trade / shift-type codes).
On Combinations, run Create codes (auto composition / Automatch against the synced catalogue).
Manually map any remaining Unmapped rows to a Greentree activity code.
Ensure each job used on timesheets has Field service or Rostered maintenance set when composition needs it.
[Screenshot: Pay Types shift type activity mapping]
[Screenshot: Combinations Create codes / Automatch]
[Video: Pay Types vs Combinations decision]
What success looks like
Producing lines stamp/resolve Activity without mapping errors â or you knowingly Export anyway with blanks.
Allowances used in the period have Pay Types â Allowances PayCode + Activity where you need them filled.
If it fails
Mapping errors cite missing trade / shift type / service kind / no matching composed code â fix letters, Field/rostered, or catalogue match.
Pay Types activity set but wrong code â edit Pay Types (not Combinations) for that shift type.