Expense Management
Open Fabric Expense Management is a white-label expense management suite that you offer to your business customers under your own brand. It comes complete: ready-made native iOS and Android apps, a web dashboard and an admin console. There is no SDK to integrate and no app to build. Open Fabric builds, hosts and operates all of it. Your core ledger keeps the money: it holds the funding accounts and authorizes, holds and posts every payment.
The difference from a traditional expense tool is when policy is checked. A traditional tool finds an out-of-policy payment at month-end. Expense Management checks each card and QR payment at the moment of payment. When a payment is declined, the employee sees the reason in plain words and can ask for approval on the spot.
What your business customers get
| Surface | Used by | What it does |
|---|---|---|
| Mobile app (native iOS and Android, provided by Open Fabric) | Employees, approvers | Virtual cards, payment decline reasons, receipt capture, out-of-pocket claims, QR payments, approvals |
| Business dashboard (web) | Business admins, finance team, approvers | Team and card management, spend policies, approval policies, budgets, vendors, expense review, coding and export |
| Admin console (web) | Your staff | Onboarding business customers, branding, card limits, portfolio reporting and first-line support |
Every surface carries your brand: your product name, logo, colours, support details and email sender name. Your customers never see Open Fabric. See Branding.
How it fits together
Expense Management sits next to your payment flow, not in it. It never holds funds and never moves money itself. Three systems work together:
| System | Role |
|---|---|
| Open Fabric Expense Management | The expense suite: apps, dashboards, policy decisions and expense records. It talks only to your core ledger. |
| Your core ledger | Holds the funding accounts and decides, holds and posts every payment. |
| Your card issuer processor | Processes the virtual cards on the card networks and sends you authorizations, clearing and settlement. We recommend Open Fabric Issuing, which Expense Management is fully integrated with. |
- Cards are issued on your card program, on the business's funding account in your ledger. Your issuer processor sends you each card authorization as it does for any card program.
- Before you approve a payment, you ask Expense Management whether the payment is within the business's policy. Expense Management answers within a second. You make the final decision.
- You report what happened on the funding accounts as account events: holds, debits, refunds, payouts and fees. Expense Management turns these into expenses for the business.
- For QR payments and reimbursements, Expense Management asks your core ledger to pay, through a small API that you host.
Who owns what
| Component | Owned by | Role |
|---|---|---|
| Funding accounts and ledger | You | Hold the business's money. Authorize, hold, debit and credit every payment. |
| Authorization check call and account events | You | Ask Expense Management before approving a payment, and report what happened afterwards. See Integration overview. |
| Core ledger APIs | You | Account lookup, QR payments and payouts that Expense Management requests. See Core ledger APIs. |
| Business onboarding and KYB | You | You approve a business through your own process, then onboard it in the admin console. See Onboarding businesses. |
| First-line support | You | Your staff help business customers with the admin console. See Admin console and roles. |
| Card issuing and processing | Your issuer processor (Open Fabric Issuing) | Virtual cards, card networks, authorization, clearing and settlement. |
| Card details display | Your issuer processor (Open Fabric Issuing) | Card numbers are shown in the processor's PCI DSS-compliant hosted widget, inside the app. Expense Management never stores a card number or CVV. |
| Expense Management applications | Open Fabric Expense Management | Building, hosting, operating, updating and monitoring the native mobile apps, the business dashboard, the admin console and the APIs. You don't build or embed anything. |
| Second-line support | Open Fabric | Issues your staff can't resolve. |
Where to go next
- Your technical team: start with the Integration overview.
- Your operations team: read Admin console and roles, Branding and Onboarding businesses.
- Product, sales and support teams: read the Feature overview and How businesses get started.