SAP Business One and Expensify integration

What moves between them

Approved expense reports flow from Expensify into SAP Business One. ml-connector polls Expensify for reports matching a date range or approval status, extracts the line items with amounts and GL account codes from the expense categories, aggregates expenses by profit center or cost center tag, and posts them as journal entries into SAP Business One's general ledger. The flow is one-directional: Expensify is the source of truth for expenses, and SAP Business One is the destination for accounting records. Polling runs on a schedule you control, typically daily or weekly.

How ml-connector handles it

ml-connector manages the session-token lifecycle on the SAP Business One side, logging in once and reusing the B1SESSION cookie for multiple OData calls within the 30-minute window, then re-authenticating when the token expires or a -5002 error signals timeout. On the Expensify side, it treats the REST API as POST-only, building the request payload with the API key and status filters, then parsing the response to extract report data. GL account mappings are configured per customer by mapping Expensify expense categories to SAP Business One chart of accounts. If a category or profit center mapping is missing, the record is flagged for manual review before posting. Journal entry deduplication is handled by checking the report ID and date to avoid double-posting on retry.

A real-world example

A mid-market professional services firm runs SAP Business One for accounting and uses Expensify for employee expense tracking across multiple offices. Before the integration, finance staff approved expenses in Expensify, then exported CSV files and manually entered the totals as journal entries in SAP Business One, splitting amounts across profit centers for each office. This process took two to three hours per week and introduced data-entry errors during month-end close. With SAP Business One and Expensify connected, each approved report is automatically converted into a journal entry, coded to the correct profit center, and posted overnight. The process now takes minutes, month-end reconciliation is faster, and expense records audit clearly.

What you can do

• •Poll Expensify for approved expense reports and automatically post them as journal entries in SAP Business One's general ledger.
• •Map Expensify expense categories and tags to SAP Business One GL accounts and profit centers so expenses post to the right dimensions.
• •Manage SAP Business One session tokens automatically, re-authenticating every 30 minutes without interrupting the data flow.
• •Deduplicate expense reports on retry using report IDs and dates to prevent double-posting.
• •Maintain a full audit trail of every expense posted, with the ability to review and replay failed records.

Questions

How does the integration handle SAP Business One's session token that expires every 30 minutes?

ml-connector monitors the token expiry and automatically re-authenticates before the 30-minute window closes, using a new B1SESSION cookie for the next batch of requests. If a call returns a -5002 timeout error, it immediately refreshes the session and retries the operation.

Why does Expensify integration use POST-only calls instead of a standard REST read pattern?

Expensify's API design requires all requests, including queries and exports, to be sent as POST operations to a single endpoint with a JSON payload containing filters and request parameters. ml-connector builds and sends these payloads directly without using an SDK, handling the response parsing internally.

Can expenses be mapped to profit centers automatically, or must they be configured manually?

Mapping is configured once per customer by matching Expensify expense categories and tags to SAP Business One GL accounts and profit centers. ml-connector uses these mappings for every future expense report. If a category lacks a mapping, the record is flagged for review before posting, preventing miscoded entries.