Matthew Schinckel

My feedback

  1. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Xero Accounting API » Authentication  ·  Flag idea as inappropriate…  ·  Admin →
    Matthew Schinckel supported this idea  · 
  2. 97 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  Xero Accounting API » Authentication  ·  Flag idea as inappropriate…  ·  Admin →
    Matthew Schinckel supported this idea  · 
  3. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Xero Accounting API » Developer Tools  ·  Flag idea as inappropriate…  ·  Admin →
    Matthew Schinckel supported this idea  · 
  4. 45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Xero Payroll API » Timesheets  ·  Flag idea as inappropriate…  ·  Admin →
    Matthew Schinckel supported this idea  · 
    Matthew Schinckel commented  · 

    This is actually turning into a pretty big deal.

    It's compounded by the fact that an employee may only have one timesheet for a given period, even if the existing timesheet is already processed. This breaks the ability for using timesheets to do corrections (or advances, but I suggest that's not really the best way to do that anyway).

    We are not prepared to send through timesheets as DRAFT, as they have already been approved in our system, and approving 300 timesheets again is a fairly big ask.

    A workaround might be to send through the data as an EarningsRateLine in a Payslip, but in that case the cost cannot by associated with a Tracking Category.

Feedback and Knowledge Base