Oracle NetSuite and Expensify integration

What moves between them

Expense reports and individual expense transactions flow from Expensify into Oracle NetSuite. ml-connector polls Expensify on a daily or weekly schedule you define, reads approved expense reports and their line items, maps Expensify expense categories to NetSuite GL accounts and cost centers, and creates vendor bills in NetSuite's general ledger. The integration respects Expensify approval workflow, so only approved reports are synced. Expensify is read-only from ml-connector's perspective; no updates flow back to Expensify.

How ml-connector handles it

ml-connector stores both credential sets encrypted: Expensify API keys and Oracle NetSuite OAuth client credentials and certificate. On the Expensify side, it polls the integration endpoint with partnerUserID and partnerUserSecret to retrieve approved reports and their transactions within a date range, using onReceive to capture report state. On the Oracle NetSuite side, it creates vendor bills mapped to the expense report ID, allocates each expense line to the correct NetSuite GL account and cost center based on the Expensify category and tag mappings you define, and handles OAuth token refresh when a call returns 401. Expensify does not offer webhooks, so ml-connector polls on a schedule tied to your expense review and approval cycle. Because Expensify runs on production only, ml-connector validates all data before posting to avoid posting duplicate or unapproved expenses. Every vendor bill carries the full audit trail and can be replayed if downstream steps fail.

A real-world example

A mid-sized professional services firm uses Oracle NetSuite for financial consolidation and general ledger close. Employees submit expense reports to Expensify for travel, meals, and client entertainment; the expense approval workflow runs in Expensify before submission to accounting. Before the integration, the accounting team downloaded approved reports from Expensify each week and manually entered the amounts into NetSuite as vendor bills, splitting line items across cost centers based on project codes. With Expensify and Oracle NetSuite connected, approved reports flow into NetSuite as vendor bills automatically, allocated to the correct cost center per the expense tags, and the manual entry work is eliminated. Month-end close starts with all approved expenses already recorded.

What you can do

• •Post approved Expensify expense reports into Oracle NetSuite as vendor bills with the correct GL account and cost center allocation.
• •Map Expensify expense categories and tags to NetSuite GL accounts, cost centers, and departments per your accounting policy.
• •Authenticate Expensify with API key pairs and Oracle NetSuite with OAuth 2.0 client credentials and certificate.
• •Poll Expensify on a daily or weekly schedule to capture approved reports without manual intervention.
• •Maintain a full audit trail on every vendor bill posted, with error handling and replay capability for failed downstream steps.

Questions

How does the integration know which Expensify expenses are approved and ready to post to NetSuite?

Expensify has an approval workflow that marks reports as approved when they complete the review process. ml-connector polls the Expensify integration endpoint and filters for reports in approved status before creating vendor bills in Oracle NetSuite. Only approved reports are synced.

How are Expensify expense categories and tags mapped to NetSuite GL accounts and cost centers?

You define the mappings in the integration configuration. Each Expensify expense category is mapped to a NetSuite GL account, and Expensify tags (which function as accounting dimensions like project, class, or cost center) are mapped to corresponding NetSuite cost centers or departments. The mapping is applied to each expense line when the vendor bill is created.

Does the integration support Expensify corporate card transactions, or only employee-submitted reports?

Expensify corporate card transactions are included in the Expensify report export. ml-connector reads approved reports and all transaction types within them, so both employee-submitted expenses and corporate card transactions are synced to Oracle NetSuite as vendor bill line items, subject to your approval workflow.