SUTIEXPENSE / ADMINISTRATION
AWS hosting included, role-based permissions, policy in one panel, and a timestamped approval record held for a minimum of seven years.
Get a Demo →01 / HOSTING
SutiExpense is AWS hosted and hosting is included in the price. Your company manages no server, no server permissions and no server access. There is no operating system to patch, no capacity to size and no internal access list to review every quarter.
HOSTED ENVIRONMENT
01
SutiExpense is hosted on AWS.
02
Your team has no operating system to maintain.
03
Server permissions are not managed by the customer.
ROUTING MODEL
LEVEL
→
SCOPE
→
CONTINUITY
02 / APPROVALS
Approval workflows route by level, by department and by project, in serial or in parallel.
Delegation, backup approvers and out-of-office escalation keep reports moving when an approver is traveling. Build the routing once against your org chart and it holds as people change roles.
03 / POLICY
A centralized policy panel holds your spending rules, and role-based spending limits are enforced at submission rather than discovered at approval.
Per diem overage, disallowed categories such as alcohol, and missing required receipts are flagged to submitter and approver at the same moment, and a submission cannot go through without a required receipt.
Location-driven tax rules work the same way, so a new provincial or country rate is a configuration change rather than a project.
CENTRALIZED
Limits and categories live in one panel.
AT SUBMISSION
Required receipts and policy exceptions are caught before approval.
BY LOCATION
Regional tax changes remain configurable.
04 / PERMISSIONS & RECORDS
Permissions are role-based. What a submitter, an approver, a finance administrator or an auditor can see and do follows the role they hold, so adding somebody is an assignment rather than a support ticket.
Approvers can act from the mobile app with push notifications, and other signature options are available where a team wants a signed approval on file.
Underneath sits a timestamped audit trail carrying the full approver chain. Expense data is retained a minimum of seven years and typically longer.
ROLE-BASED ACCESS
ROLE 01
ROLE 02
ROLE 03
ROLE 04
The approval chain is timestamped and retained with the expense record for a minimum of seven years.
YOUR QUESTIONS, ANSWERED
Choose a question to see the answer.
NEXT IN THE FLOW
That closes the feature set. The product page pulls the pieces back together.
GET A DEMO
See hosting, policy, role access and the approval record working together in one expense workflow.