Plex and Expensify integration

What moves between them

The primary flow runs from Expensify into Plex. After each expense approval cycle, ml-connector reads Expensify expense reports marked approved and unpaid, extracts individual transactions with merchant names and category codes, and posts them as GL entries in Plex's general ledger, mapped to the matching cost centers and GL accounts. Corporate card transactions that appear in Expensify are similarly extracted and posted as non-purchase expenses. The mapping from Expensify merchant names and category tags to Plex GL accounts and cost center codes is set up per customer. Expense data flows one direction only; Plex GL postings are not written back to Expensify.

How ml-connector handles it

ml-connector stores both credential sets encrypted: the Plex OAuth2 client credentials and the Expensify API key pair. On the Plex side, it authenticates with OAuth2 for cloud REST endpoints and can also support legacy SOAP Basic auth for customers on older instances. Because neither Plex nor Expensify offers webhooks, it polls both on a schedule tied to your expense approval and close calendars rather than waiting for a push. Plex rate limits are undocumented, so ml-connector implements exponential backoff on HTTP 429. The Expensify API has no sandbox, so all testing runs against production. Merchant names from Expensify are matched to Plex GL accounts via a configurable lookup table, and transaction categories are mapped to cost center codes in Plex so each posting lands on a valid GL dimension. ml-connector deduplicates on Expensify expense report ID and transaction date to avoid reposting approved reports, and every record carries a full audit trail.

A real-world example

A mid-sized discrete manufacturer runs Plex for production, inventory, and finance across three plants, and uses Expensify for employee expense reimbursement and corporate card reconciliation. Before the integration, the accounting team downloaded approved Expensify reports each week and manually re-keyed the totals by merchant and cost center into Plex's GL, a process that took 3 to 4 hours and carried risk of transposition errors. With Plex and Expensify connected, approved expense reports flow directly into the GL automatically, allocated to the correct cost centers by transaction category, and corporate card charges appear as documented expenses. The manual re-keying step is eliminated, and the GL reconciliation is complete within hours rather than days.

What you can do

• •Post approved Expensify expense reports into Plex's general ledger, mapped to the correct GL accounts and cost centers.
• •Sync corporate card transactions from Expensify into Plex as documented business expenses.
• •Map Expensify merchant names and category codes to Plex GL accounts and cost center dimensions.
• •Authenticate Plex with OAuth2 or legacy Basic auth and Expensify with API key pair, polling both on your expense approval cycle.
• •Deduplicate on Expensify expense report ID and maintain a full audit trail of every posting.

Questions

Which direction does data move between Plex and Expensify?

The flow is one direction: from Expensify into Plex. Approved Expensify expense reports and corporate card transactions post into Plex's GL as documented business expenses. Data does not flow back from Plex to Expensify.

How does ml-connector handle Expensify's lack of a sandbox and Plex's undocumented rate limits?

Expensify has no test environment, so all testing runs against production using test expense reports that can be deleted after verification. Plex's rate limits are undocumented, so ml-connector implements exponential backoff on HTTP 429 and tracks retry state to avoid outages when limits are hit.

How are Expensify merchants and categories mapped to Plex GL accounts and cost centers?

Expensify merchant names are matched to Plex GL accounts via a configurable lookup table, and Expensify transaction categories are mapped to Plex cost center codes so each posting lands on a valid dimension. The mapping is set up per customer and can be updated without code changes.