Skip to content
← Share and support customer ideas for Xero

Settings and activity

2 results found

  1. Expenses - Multi-layer departmental approval process

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    submitted  ·  2 comments  ·  For small businesses » Business features  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Heinrich Badenhorst shared this idea  · 

  2. User Roles - Expenses: Two step approval process in the New Expenses feature

    37 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    submitted  ·  9 comments  ·  For small businesses » Settings & user roles  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Heinrich Badenhorst commented  · 

    Our company has locations in in London, France, Germany, and the US and has a Xero entity set up for each.

    I onboarded all employees to Xero Expenses 2 months ago and it staff are happy with the mechanics of the process.

    The challenge I have is the approval hierarchy. All expense approvals sit with me. This needs to change as each line manager/ department/ team head should be responsible for approving their teams’ expenses.

    We have a tracking option for “Department” which can be used to pool employees in their respective teams.
    I would then like to add approvers for each “Department” that controls their teams’ expenses and be the first line of approval.
    The finance team and MD's are responsible for final (second tiered approval).

    Hope this can be implemented and this scenario is prevalent elsewhere. Xero expenses works really well, we just need it to be scalable from a hierarchial perspective.

    Heinrich Badenhorst supported this idea  ·