Skip to content
Dino Correia
Let's talk

Fintech integrations

Xero, QuickBooks and Codat integrations for lenders and fintechs

I spent five years building lending and finance platforms at a London fintech, including the integrations that pulled applicants' accounting data from Xero, QuickBooks and Codat, credit data from Creditsafe, and company data from Companies House. If you're building something that depends on that data, I can design the integration, build it, or both.

Let's talk See where I built them →

What I've built

Integrations behind real lending decisions

Five years at a London fintech, across the client app, the internal tools and the partner portals.

  • Integrations with Xero, QuickBooks and Codat for accounting data, and Creditsafe and Companies House for credit and company data
  • A buy now, pay later service offered through the Xero marketplace, which I helped build and integrate
  • Payment reconciliation and scorecard services in an internal lending portal
  • Finance applications for invoice and supply finance in a white-label partner portal

Where it goes wrong

The first API call is the easy part

Connecting to an accounting platform takes an afternoon. These are the parts that decide whether the integration survives production.

Consent that quietly expires

OAuth connections get revoked, tokens expire, and a customer reconnects to a different organisation. Each case needs a defined state and a way back, or the data just stops arriving.

Platforms that disagree about the same data

Invoices, contacts, due dates and tax are modelled differently in each accounting package. The mapping between them is where most of the real work sits.

Stale data in live decisions

Rate limits and sync schedules decide how fresh the numbers are. A lending decision needs to know how old its data is, not just what it says.

Failures nobody notices

A webhook that stops arriving looks exactly like a quiet day. Without reconciliation and alerting, gaps surface weeks later as wrong numbers.

Direct API or unified API

Integrating each platform yourself gives control; a unified accounting API gives speed and one data model, at a per-connection cost and a new dependency. The right answer depends on volume, timeline and which platforms your customers use.

Ways to work together

Assess it, decide it, or build it

Three of my engagements fit this work. Durations are typical, not fixed.

1-5 days, depending on scope

Migration & Integration Assessment

Before you build: map the platforms, data, consent flows and failure cases, and leave with a phased plan.

How it works →

Half a day-2 days

Technical Decision Workshop

When the question is direct integrations or a unified accounting API, and the answer needs to hold up later.

How it works →

Ongoing, part-time or full contract

Contract Software Engineer

When you need it built: I join your team and build the integration, sync and reconciliation alongside your engineers.

How it works →

Track record

Career figures

Aggregate figures across my career, not from a single project.

primarily in fintech
5 years
external integrations
20+
transactions processed annually
500K+
records involved in data migrations
6.5M+

Go deeper

Writing on integrations and decisions

Building on accounting or credit data?

Tell me which platforms, what the data is for, and where it's getting difficult.

Let's talk Email me