Newgate Systems Start a conversation

Case study · Integration

Making an AP platform
fluent in Dynamics.

Tipalti is a US payables automation platform. For its customers running Microsoft ERP, the integration between the two systems is the product — and it had to be built properly.

Client
Tipalti
Industry
Financial software & payables automation
Region
United States
Platform
Dynamics 365 F&O, REST APIs

01

The client

Tipalti automates accounts payable — supplier onboarding, invoice processing, tax compliance and mass payouts. It sells to finance teams, and those finance teams run ERPs.

That makes ERP integration a commercial capability rather than an internal convenience. If the Dynamics connection is unreliable, Tipalti cannot sell to Dynamics customers.

02

The problem

Payables integration is deceptively hard because it touches the parts of an ERP with the least tolerance for error. A misposted journal, a duplicated purchase order or a vendor credit applied twice is not a bug report — it is a reconciliation problem someone has to unpick by hand.

It also has to survive the messiness of real accounting: partial payments, credits against invoices that have already been paid, currency differences, and GL structures that differ from one customer to the next.

03

Requirements

  • R1Invoice processing automated between the payables platform and the ERP
  • R2General ledger account integration, extraction and export
  • R3Purchase order integration, including creation and processing
  • R4Vendor credits created and correctly applied against invoices
  • R5Imported bills and payments written back with matching payment records
  • R6Built to work across more than one customer's chart of accounts

04

The solution

We led the engagement as the technical lead with a small delivery team, building custom services and APIs on the Dynamics side rather than forcing the ERP to accommodate an off-the-shelf connector.

The outcome that matters commercially: the integration was not a one-off. Tipalti now runs it for two of its own customers, which means it had to be built as a product — configurable, documented and supportable by someone other than the person who wrote it.

05

The work

  • 01Invoice automation. Invoice processing automated end to end between the payables platform and Dynamics 365 F&O.
  • 02GL integration. General ledger account integration with extraction and export.
  • 03Purchase orders. Purchase order integration, creation and processing.
  • 04Vendor credits. Vendor credits created and applied correctly against the right invoices.
  • 05Bill payments. Imported bills and payments written into the ERP with matching payment records.
  • 06Custom services. REST services and APIs built on the Dynamics side to support the whole flow.
D365 Finance & OperationsX++REST APIsGL integrationAccounts payable

06

Outcome

Resold

Now running in production for two of Tipalti's own customers

Automated

Accounts payable and receivable processing without manual entry

Productised

Built to be configured and supported, not a bespoke one-off

More work

Other records.

Next

Facing something like this?