How to Evaluate Expense Software Fed by Workday

A Workday customer can enter a transfer today that takes effect next month, or correct a cost center back to last month. An expense tool receives some version of that history. Which version, and who maintains the pipe, is the real decision. Here is what each vendor documents, checked on October 7, 2026.

• Brex: connects to Workday through its partner Merge, using a Workday Integration System User. Its HRIS article lists synced fields such as manager, department, location, cost center, and legal entity, refreshed on Merge's schedule with a fallback of about every 12 hours. Automatic offboarding is off unless enabled. Deactivation blocks spending on the user's cards without cancelling them, which the article says leaves them available to transfer.
• Navan: its integrations directory lists a Workday integration for employee data and user provisioning. It also lists an HR-SFTP connection for Workday and other HR systems. It does not publish the field mapping.
• SAP Concur: publishes a User Provisioning Service API that accepts employee number, department, cost center, manager, approvers, and custom fields. Partner-built HR connectors may exist; we could not open SAP Concur's App Center listing on October 27, 2026, so ask SAP whether a managed or partner Workday connector fits before deciding to build your own feed.

Buyer constraint: a future-dated transfer during an open trip

Consider an engineer whose move to a new cost center and manager is entered in Workday on the 3rd, effective the 20th. She travels from the 15th to the 25th with a card and files one report afterward.

The sources reviewed here do not document how a future-dated Workday event is applied. Brex describes syncing attribute values on a schedule, so test whether the new manager appears on the 3rd or the 20th, and which one approves a report mixing both periods. With Navan's HR-SFTP option or a Concur provisioning feed, your Workday report decides which effective date ships, so your team owns that logic. With a packaged connector, the vendor's logic decides and you test it.

Rehires, leave, and who owns the fix

Rehires deserve their own test, because a returning worker who gets a new identity can leave old refunds without an owner. None of the three articles addresses rehire matching or leave of absence. Brex's offboarding design softens termination, since a deactivated user's cards stop spending but, per Brex, can still be transferred to someone else. Even so, a worker on leave must not be treated as terminated by an automatic rule. Under a Concur API feed, rehire matching on employee number is your integration's job. Under Brex or Navan's listed integration, it is a vendor support question.

Reproducible lifecycle check

In a Workday sandbox, create a hire, a future-dated transfer, a retroactive cost-center correction, a leave of absence, a termination, and a rehire under the same employee ID. After each sync, record the user's manager, cost center, card state, and the owner of an earlier refund. Spend Management Guide has not executed this configuration.

Verdict and counter-case

Pick Brex when HR has no integration engineers and a scheduled attribute sync with opt-in offboarding is enough. Pick Navan when travel is the main use and you want the option to send Workday data as a file your team controls. Pick SAP Concur when a Workday integration team already maintains feeds and wants effective-date and rehire logic in code it owns.

If finance needs historical cost-center attribution enforced automatically from Workday's effective dates, the sources reviewed here do not establish it for any of the three. Keep attribution on the expense record at submission time and treat the HR sync as routing only.