Errors timesheeting to Xero

Common timesheet errors

• Explicit job-task-staff allocation in XPM is preventing anyone who isn't explicitly allocated to the task in XPM from timesheeting to it. Solution: Remove explicit job-task-staff allocations (don't create new ones) and re-send the timesheet in Link>Export Queue>Action>Resend to Xero.
• Job task is completed: slow timesheeters sometimes don't keep up with everyone else completing their tasks and when they do catch up they find the tasks are long completed. Solution: Do timesheets as you go. Un-complete task in XPM and resend timesheet to Xero.
• Job itself is completed: As above, slow timesheeters sometimes get caught out because by the time they go to timesheet the job is completed and sometimes invoiced! Solution: Timesheet as you go. Re-activate the XPM job in XPM and resend the timesheet to Xero.
• Timesheet already invoiced or washed-up This occurs on a timesheet update. XPM does not allow you to update a timesheet that has already been included in an invoice or washed-up. This is because an update would affect the WIP ledger. Updates include note changes for things like spelling mistakes which also provide errors. Solution: Undo the wash-up and/or invoice. Re-push the updated timesheet from Link to XPM then re-do the wash-up and/or invoice.
• Timesheet period locked XPM has a ‘Submit timesheet’ function which is designed for hourly based invoicing firms to ensure timesheets are moving while they are doing invoicing. It’s also a good way to create accountability around timesheet completion but can encourage the wrong behaviours around weekly timesheeting (too slow for job budget monitoring, capacity and balancing work among team members). Solution: Un-submit timesheet, re-push timesheet for the period, lock timesheet again.