Feature overview
This page summarizes what your business customers can do with Expense Management. Everything here comes ready to use in the native mobile apps and the web dashboard that Open Fabric provides in your brand. It helps your product, sales and support teams explain the product. You don't need to build anything for these features beyond the integration.
Roles inside a business
A person can hold several roles.
| Role | What they do |
|---|---|
| Admin | Sets up the workspace, departments, members, cards, spend and approval policies, budgets and vendors |
| Finance | Reviews and codes every expense, runs reimbursements and supplier payments, exports to accounting |
| Member | Everyone, admins and finance included. Holds cards, records expenses and receipts, submits claims and requests |
Approval rights come from relationships: line manager, department head or budget owner. Nobody approves their own expense or request.
Cards
- Virtual cards issued instantly from the business dashboard, on the business's funding account.
- Freeze, unfreeze and cancel by the cardholder or an admin.
- Card details shown in the issuer processor's secure, PCI DSS-compliant widget, in your colours. Details hide again after 60 seconds.
- Card requests and limit increase requests from employees, routed for approval.
- Vendor cards dedicated to one supplier, with their own policy and budget.
Spend policies, checked at the moment of payment
- Policy templates such as Travel, Meals and SaaS, with a rule per category: allowed, capped or blocked.
- Limits per payment, per day and per month. The same per-person limits apply across card, QR payments and out-of-pocket claims.
- Countries: home country only, or anywhere.
- Your platform-wide rules on top: categories you always block, and your card limits.
- Plain-words declines. The employee sees why a payment was declined, on screen and by push notification. For example: "Casinos aren't allowed on your Travel policy."
- Ask for approval. For a decline that can be appealed, the employee asks for a one-off exception, by default valid for 24 hours. Employees can also request a temporary limit raise for up to 90 days.
Approvals
- One approval inbox on mobile and web, with the receipt, the policy result and the budget impact.
- Approve from the notification.
- Default routing: claims and flagged card payments go to the line manager, and spend requests to the budget owner. If there is no line manager or budget owner, they go to the department head, then finance, then an admin.
- Multi-step approvals for higher amounts or specific categories.
- Team spend view for managers.
Budgets and departments
- Departments with a head and members.
- Department budgets, monthly, quarterly, yearly or one-off, with live usage.
- Budgets are hard limits. A payment that would exceed the budget is declined at the moment of payment.
Vendors and bill pay
- Vendor records with their own spend policy and budget.
- Invoice upload with automatic data extraction, approved by the budget owner.
- Payment by scheduled bank transfer from the funding account, or by vendor card.
Receipts
- Snap a receipt in the app. Its details are read automatically and it is matched to the card payment.
- Missing receipt reminders, and finance can ask for a new receipt.
- Notes: an on-device scratchpad where employees jot down costs and turn them into claims later.
Out-of-pocket claims
- Claims for spend paid with a personal card or cash, with receipt, category and purpose. The employee sees the policy result and the approver before submitting.
- Reimbursement runs: finance pays approved claims in one run, from the funding account through your payout API.
- Statuses the employee can follow: submitted, approved or rejected, scheduled, paid.
QR payments
- Scan a local QR code in the app, with schemes such as SGQR, PromptPay, QRIS and QR Ph. Any market works where you already have a QR integration. The payment is checked against the policy before your ledger pays the merchant.
- QR payments in your own app can also be checked and recorded, by sending the authorization check.
Payments outside the product
Not every payment on a funding account starts in Expense Management. Activity that you report as account events still becomes part of the business's records:
- Fees, interest and transfers show as account activity.
- Card or QR payments without an authorization check are evaluated after the fact and flagged for review if they are out of policy.
- Spend already paid another way can be recorded as an "already paid" expense.
Finance and accounting
- Expense review across card, QR and claims, with filters.
- Coding: category, ledger account, cost center and tax code, with defaults per category and bulk Accept coding.
- Accounting export to CSV and Excel. Exported expenses never change; later corrections become adjustment lines.
Notifications
- In-app inbox, push notifications and email, all in your brand.
- Comments and other free text never appear in a push notification or email.
Security and privacy
- Sign-in with email, password and two-factor authentication. Optional fingerprint or face unlock on mobile.
- Sensitive actions, such as revealing card details or changing bank details, ask for a recent sign-in.
- Card numbers never touch Expense Management. They are shown only in the issuer processor's PCI DSS-compliant widget.
- Businesses own their expense data. Your staff see aggregates and support details, not individual expenses.
Coming next
- Physical cards, and tap to pay with mobile wallets
- Direct integrations with accounting systems such as Xero, NetSuite and QuickBooks
- Single sign-on and HR system sync
- Claims in foreign currencies
- More markets and national QR standards
- Languages other than English