Expense on Demand & Apideck

The Company

ExpenseOnDemand (EOD) is a UK-based expense management platform founded in 2003, serving small-to-mid-sized businesses in 96 countries. The platform automates expense tracking, compliance, and reporting (mobile receipt capture, multi-currency support, and a Cash Advance feature) bringing enterprise-grade tools to SMB pricing. We spoke with Siddharth Nigam, Senior Director of Product & Strategy about their experience with Apideck.

The Challenge

Before Apideck, EOD spent about a year evaluating integration partners to solve a build-vs-buy problem: supporting Xero, NetSuite, and Microsoft Dynamics 365 Business Central without standing up a separate native integration for each. Accounting was the priority, with NetSuite and Dynamics becoming increasingly important to their pipeline.

Compliance mattered a lot too! EOD wasn't initially aware of Apideck's no-data approach, but once it was explained, it became a deciding factor. They wanted to store the bare minimum themselves (expenses only). A representative use case: customers with ~200 employees generating 4,000–5,000 expense items a month, where reliable employee and tax mapping mattered more than sheer connector breadth.

EOD initially went to market with Merge to build out the same NetSuite and Dynamics integrations, drawn in partly by Merge's marketing muscle in the expense management space. Over time, Merge's focus shifted away from expense management and toward AI, and pricing rose to a point that was untenable for a company EOD's size still investing in its own growth.

Just as significant was the support experience: Merge's team was technically capable but routed everything through a single, highly technical contact, and EOD felt like "just a number" as Merge chased larger accounts. EOD wanted a partner that would grow with them, not one they were subsidizing.

The Solution

EOD started their proof of concept on Xero. The use case covered employee/contact mapping, tax code assignment, expense-category sync.

The relationship then expanded across:

• NetSuite: including a custom Employees endpoint built specifically so EOD could post journal entries against individual employees
• Microsoft Dynamics 365 Business Central: Employees-endpoint support plus ongoing hardening of attachment handling on bills and journal entries
• Tracking categories: expanded to full category detail based directly on EOD's feedback

The pattern: EOD raises a feature request, Apideck ships it, EOD confirms it in production. As Sidd put it after testing a recent batch of delivered endpoints, "everything is working exactly as expected."

The Results

EOD now runs live, production expense workflows across Xero, NetSuite, and Microsoft Dynamics 365 Business Central. They're also scoping SAP Concur as a future connector based on demand from their own customers.

Speed was a standout result of the switch. EOD kicked off the NetSuite and Dynamics build in February and was live by June. This, despite NetSuite being "a monster" of an integration that Merge itself had struggled to support. Sidd estimated Apideck's documentation and support roughly halved the developer hours the build would otherwise have taken, helped by having a dedicated contact who could flex between non-technical conversations with him and deep technical ones with his developers.

The engagement has also settled EOD on a deliberate hybrid model going forward: build simple integrations natively, and lean on Apideck specifically for the ones that would be painful to own in-house. And we still have a plan to go further! EOD’s main ask of Apideck: keep up and expand the clear guidance through documentation or account conversations!