A policy check on every claim
Every claim is checked against your policy when it is submitted. The check is rule-based.
Travel and expense spend is checked against policy when it is claimed, approved through your own levels, and posted to SAP once approved.
Every claim is checked against your policy when it is submitted. The check is rule-based.
Approval workflows are multi-level and configured per module and per company, with delegation.
Xpense has finance, manager and travel dashboards.
Approved expense reports are posted to SAP, with GL mapping.
GST details are captured and validated at submission and included in report exports.
AI features are switched on per company, and AI usage is metered with plans and budgets.
Store utility bills are filed per store, follow their own approval chain and post to SAP as vendor invoices.
Utility billsCompany groups, companies, business units, plants, cost centres and projects are set up in Xpense, so a group runs travel and expense in one place while each company keeps its own approval workflow.
Approvals and actions are logged, and every trip, expense and advance has a timeline. Access to them is role-based.
When it is submitted, before it reaches an approver. Every claim is checked against the policy you have configured.
No. The policy check is rule-based. It applies the rules and limits you set up.
Yes. Approval workflows are multi-level, and you configure them per module and per company.
Approval workflows support delegation, so an approver can hand their approvals to someone else while they are away.
Xpense sends a reminder when an approval passes its SLA.