After this article
You’ll be able to connect Expensify to Lumos to ingest user, policy, and policy role data, and optionally provision user access. There are two versions of this integration. Expensify reads expenses for spend visibility. Expensify Provisioning syncs users, policies, and policy roles, and can create, update, and delete users and assign policy roles. You choose the version when you connect in Lumos.Capabilities
- Everything in these tables comes from the
Expensify Provisioningversion. TheExpensifyversion reads expenses only.
Required plan and roles
- Expensify credentials: you’ll generate a partnerUserID and partnerUserSecret pair from the Expensify integrations tools page. Any Expensify account can generate the pair. The credentials act as that account, so use a dedicated account.
- Expensify Provisioning role: the account that generates the pair needs to be a policy admin on each policy Lumos manages.
- Unique ID: an identifier you choose for this connection, such as
lumos-expensify-1. It tells multiple Expensify connections apart. The Expensify version calls it the App Instance Identifier, and Expensify Provisioning calls it Unique ID.
Read-only access vs provisioning
Is read-only possible? For expense data, yes. The Expensify version only reads expenses. For users, policies, and policy roles, no. Expensify Provisioning authenticates with a single partnerUserID and partnerUserSecret pair, and that same credential is used for both syncing and provisioning. What full provisioning requires. The Expensify Provisioning version, the partnerUserID and partnerUserSecret pair generated from the Expensify integrations tools page, and a unique ID you choose. Follow the steps below to connect. Watch out for. Expensify identifies employees by anemployeeID. Lumos uses the value you map on Create Account, and when an Expensify employee has no employeeID, Lumos generates one before writing, so write actions no longer fail on a missing ID. There are two versions of the integration, Expensify and Expensify Provisioning; make sure the correct one is selected.
Instructions
Phase 1: Gather your Expensify credentials- Navigate to https://www.expensify.com/tools/integrations/.
- Log in with your Expensify account credentials and follow the instructions to set up Integration Server Access.
- Expensify provides a partnerUserID and partnerUserSecret pair.
- Save the partnerUserSecret immediately. Expensify won’t show it again after it’s generated.
- Choose a unique ID for this connection, for example
lumos-expensify-1.
- Go to Settings → Integrations, find Expensify, and select Expensify (expenses only) or Expensify Provisioning (users, policies, policy roles, and provisioning).
- Fill in the fields for the version you chose, then connect the integration.
Expensify
Expensify
- App Instance Identifier: the unique ID you chose in Phase 1. It differentiates multiple Expensify integrations from each other.
- Partner User ID and Partner User Secret: the partnerUserID and partnerUserSecret pair from Phase 1.
- Category Filter (optional): to filter the expenses retrieved by category, enter a comma-separated list of category names with quotes around each name. For example: “Software”,“Software Services”,“Software Infrastructure”,“Data Feeds”,“Dues & Subscriptions”. If you leave this empty, all expenses are retrieved.
Expensify Provisioning
Expensify Provisioning
- Partner User ID: the partnerUserID from Phase 1.
- Partner User Secret: the partnerUserSecret from Phase 1.
- Unique ID: the unique ID you chose in Phase 1.
API Endpoints Used
Troubleshooting
Invalid credentials error when connecting. Re-check the partnerUserID and partnerUserSecret values. Expensify returns “Invalid credentials” for a bad credential pair, and the connector classifies this as an authorization error. Older tasks failed with “Employee … is missing employee ID”. Before September 2026, assign, unassign, and delete actions required the Expensify employee record to carry anemployeeID and failed when it was missing. Lumos now generates an employeeID for employees that have none, so the error no longer occurs. Retry any task that failed with this message.