Checking your Simpro connection
If your organisation exports timesheets to Simpro, an administrator can check the connection any time under Settings → Integrations. The Simpro card shows a status strip at the bottom that tells you, at a glance, whether everything is working.
| What the card shows | What it means | What to do |
|---|---|---|
| Org: <your Simpro organisation>, with “Last export: <time> ✓” and a green ● Active dot | Connected and working. The most recent timesheet export went through. | Nothing — this is the normal, healthy state. |
| “No exports yet” under the organisation name | The connection is set up, but no timesheet has been exported since it was created. | Nothing to do yet — this updates itself once the first timesheet is exported. |
| ● Paused (grey dot) | An administrator paused the connection manually. | Resume it from the card when you’re ready to export again. |
| “Last export failed <time>: <reason>” (amber) | The most recent timesheet export didn’t reach Simpro. | See “A timesheet hasn’t appeared in Simpro” below. Teammate keeps retrying automatically. |
| “Simpro not responding…” (amber) | Teammate’s hourly check couldn’t reach Simpro at all, at least 3 times in a row. | Check Simpro is online. If it keeps failing, contact Teammate support. |
| “Paused automatically: Simpro rejected the API key…” (red) | Simpro is refusing the saved API key, so Teammate paused the connection to stop repeated failures. | Re-enter the API key under Configure, then Resume the connection. |
The warning when a timesheet can’t be sent to Simpro
When someone clocks in, clocks out, or a timesheet is added, edited or deleted, Teammate always saves that action first. If the export to Simpro fails at that moment, you’ll see a short amber message such as:
“Your timesheet couldn’t be sent to Simpro. It will be retried automatically tonight; your administrator can see the details under Integrations.”
This is a warning, not an error — your timesheet is safely saved in Teammate. It just hasn’t reached Simpro yet. Nothing else needs to be done at that moment; Teammate will keep trying to send it.
Automatic retry, for up to 30 days
A timesheet that failed to reach Simpro is retried automatically every night, for up to 30 days from the day it first failed. If the cause is fixed in that time — for example, an administrator links the workplace to the right Simpro job — the timesheet goes across automatically at the next nightly retry. You don’t need to do anything to trigger it.
After 30 days of failed attempts, Teammate stops retrying that timesheet automatically and records a note in the connection’s integration log. To send it after that, open the timesheet in Teammate and press Save — this sends it to Simpro straight away, no matter how old it is.
Troubleshooting: a timesheet hasn’t appeared in Simpro
- Open Settings → Integrations and check the Simpro card’s status strip against the table above.
- If the workplace on that timesheet is set to Ignore on the Simpro mapping screen, this is expected — timesheets for an ignored workplace are never sent to Simpro, and no action is needed.
- If the workplace was created directly in Teammate (rather than imported from Simpro), check it has been linked to a Simpro job on the mapping screen. A workplace with no linked job can’t have its timesheets exported until it’s linked.
- Once the workplace is correctly linked (or any other cause is fixed), no further action is needed — Teammate retries automatically every night for up to 30 days.
- Need it sent immediately, or is the timesheet older than 30 days? Open the timesheet and press Save — this sends it to Simpro right away regardless of its age.
Common questions
Was this helpful?