Sources checked 11/05/2026. Xero changes its plans and products, so confirm what your own organization shows.
If your team still files expense claims in Xero's classic screens, or uses a tool that reads them through Xero's ExpenseClaims API, that path is closing. You don't lose the ability to reimburse people. You lose one particular way of recording it, and the replacement is simpler: a bill.
What Xero is retiring
Xero is retiring the Classic Expenses product and the API behind it. Its developer changelog entry of 07/31/2025, titled "Classic Expenses API Deprecation," says Xero will be "disabling access to the already deprecated ExpenseClaims endpoint" and "will also be deprecating the Receipts endpoint." The entry carries a Feb 2027 label and doesn't give separate dates for each step.
Two groups feel it. Anyone still entering claims in the classic screens has to move to Xero Expenses or another tool. And any integration that writes expense claims or receipts through those endpoints has to post a different way. If a tool you rely on still uses them, ask the vendor what it does instead.
How expense claims post to Xero now
Expense claims post to Xero as bills now, payable to the employee. Xero's own product works that way: its Expenses page says "the approved claim becomes a bill you pay like any other." The bigger outside tools do the same.
| Tool | Out-of-pocket expense | Company card expense |
|---|---|---|
| Xero Expenses | Approved claim becomes a bill, or is reimbursed through Xero Payroll, per Xero | Not covered on that page |
| Expensify | Purchase bill, status Draft, Awaiting Approval or Awaiting Payment, per Expensify's Xero guide | Bank transaction on the account you choose |
| Ramp | Bill, vendor = the employee, with a bill payment if paid through Ramp, per Ramp's Xero overview | Card transaction on a bank-type account in Xero |
The split matters. An out-of-pocket expense is money the company owes a person, so it belongs in accounts payable until it's paid. A card purchase is money that already left a company account, so it's a bank transaction. Post a card purchase as a bill to the employee and you'll pay them for something they never paid for.
How to reimburse an employee in Xero by hand
- Set up the employee as a contact. One contact per person, named so nobody confuses them with a supplier.
- Enter one bill per claim. A line per expense, each coded to the right account, with the merchant and purpose in the description.
- Attach the receipts. The bill should carry its own evidence for your bookkeeper and your auditor.
- Approve it. Someone other than the employee checks the business reason and the coding.
- Pay it and record the payment. Record the payment against the bill from the bank account the money left, so the bank feed line matches.
That works for a handful of claims a month. It breaks down when dozens of people send photos by text, half the receipts arrive after the month closes, and two people submit the same lunch.
Xero Expenses vs Expensify and Ramp
The choice comes down to where people capture receipts, who approves, and how the money reaches the employee.
- Xero Expenses keeps everything in Xero. The Expenses page says employees snap receipts in the Xero Accounting app and submit through Xero Me, and that it's included on the Established plan.
- Expensify posts to Xero as purchase bills and lets you choose the bill status on export, per its Xero guide. With auto-sync on, it says reports export after approval.
- Ramp creates the bill and, when it pays the employee by ACH, syncs the bill payment too, per its Xero overview. A reimbursement set to Manual Pay stays unpaid in Xero, with no payment recorded.
Cannabis companies have one more filter: whether the tool will move money for them at all. Check the provider's eligibility rules before you plan your reimbursements around its payments.
When to post: at approval or at payment
Ask your bookkeeper which they want. Posting at approval puts what you owe in accounts payable for the period it was approved, even if the reimbursement goes out after month end. Posting at payment keeps unpaid claims out of the books until the money moves. Either way, the bill and the payment should land once, with a reference that ties them back to the claim, so nobody enters the same report twice.