Expenses Setup Overview
What this does
This overview explains what needs to be in place before Expenses works properly for your team.
Expenses is easier to use when the company structure, app access, and pay grouping rules are already configured elsewhere in the suite.
What must already be set up
- the company must have an active
Expensessubscription - the user must be assigned access to
Expenses - pay periods should already be set up in the
Admin App - the surrounding staff and company structure should already be in place in the
Admin App
Why the Admin App matters here
If you are in Expenses and trying to find where pay periods are configured, that setup lives in the Admin App.
That matters because Expenses uses pay periods to help group payment-related views, filters, and reporting correctly.
The Admin App also controls who has access to Expenses in the first place.
What you can set up inside Expenses
Once the Admin App setup is in place, Expenses gives you the app-specific workflow surfaces such as:
- manual expense entry
- bulk upload
- bulk queue handling
- viewer
- reports
- export settings
- permissions and preferences
Recommended setup order
- Finish pay periods and company access in the
Admin App. - Assign the user access to
Expenses. - Configure any
Expenses-specific settings such as export and permissions. - Start using entry, upload, queue, viewer, and reports.
What stays incomplete if skipped
If pay periods are missing, reporting and filtering in Expenses will be less reliable.
If app assignment is missing, the user may not be able to access Expenses at all.