xMatix Expense Management

xMatix Expense Management covers the whole life of employee spend: an employee raises a claim with receipts, policy rules check it, approvers sign off, and on the final approval the claim posts itself to the general ledger — finance then pays it, singly or in a batch, or hands it to payroll. Advances, company cards and client-rechargeable expenses ride the same machinery, and every balance ties back to the finance ledger because every step is a posted journal.

The mental model

Four ideas explain most of what you will see in the Expenses app:

• You are your employee record. Every claim and advance is anchored on the claimant's employee record — the same record that holds their manager, department, grade and bank details. That is why approval routing, grade-based policy caps and payroll handoff need no extra setup per claim.
• Approve once — the books post themselves. When the final approver approves a claim, the platform posts it: the expense heads are debited, recoverable tax is split out, and an employee-payable balance is raised. Nobody re-keys an approved claim into finance.
• Three status tracks, not one. A claim carries a business status (Draft → Submitted → Posted → Paid/Settled), an approval status (Pending / Approved / Rejected) and a payment status (Unpaid / Partial / Paid). "Approved but unpaid" is a normal state, not a fault — payment is a separate finance step.
• Policy has teeth, in degrees. Policy rules can warn, demand a higher approver, automatically trim the excess over a cap, or block submission outright. Violations stay visible on the claim so approvers see exactly what was flagged.

Who does what

What is in this section

• Submit and approve expense claims — the full claim flow, from draft through policy check, approval and posting to payment, for both the claimant and the approver.
• Employee advances — request money up front, pay it out, settle it against claims and recover the unspent balance.
• Expense policies and violations — what gets checked and what each outcome does, from a recorded warning to a hard block.
• Expense categories, grades and limits — the spend taxonomy, category defaults, and how grade-scoped caps are built.
• Company cards and reconciliation — card masters, statement transactions, posting card spend and paying the statement.
• Reimburse expense claims — single payments, batch payments that settle many claims in one posting, and the payroll handoff.
• Expense accounting and recharge — the journals behind every expense event, employee balances as open items, and rebilling clients.
• Configuring Expense Management — control accounts, masters, policies, the approval process and security, in the order that works.
• Troubleshooting Expense Management — blocked submissions, approved-but-unposted claims, posting errors decoded, and balances that do not tie.

Common questions

My claim was approved — why haven't I been paid?

Approval books the expense and records what the company owes you; paying is a separate finance step. Watch the claim's payment status: it flips to Paid when finance runs your reimbursement — on its own or inside a reimbursement batch — or when a payroll-mode claim is handed to payroll.

Do I need the Finance app to use expenses?

No. Employees and managers work entirely in the Expenses app — claims, advances, approvals. The finance team touches the ledger side (posting is automatic; reimbursement, advances and cards are finance actions), and the results surface in the financial statements like every other posting.

Where do the amounts actually go?

Into the same double-entry ledger as every other document. A posted claim debits the expense accounts and credits an employee-payable account; reimbursement clears that payable against the bank. Expense accounting maps every event to its journal.

Related topics

• xMatix Expenses product overview
• xMatix Finance & Accounting — the ledger everything posts into.
• Approval processes — the engine expense claims route through.
• Book a demo
• Expense Voucher — entity reference