NEWS WIRE
05 MAY 2026 CODAT ANNOUNCES ADVISORY INTELLIGENCE PLATFORM + BMO COLLABORATION18 AUG 2026 BANKING ON: FNBO’S MARIA LINE TALKS DATA + AI

Company / Fintech / The data business

Codat wants your bank to read between the ledger lines

After years connecting business software, Codat is teaching commercial banks what to do with the data. Its next test is whether better information makes for a better conversation.

Advertisement

A bank can watch money enter an account without knowing much about the business that earned it. Which supplier is tightening payment terms? Which invoices are still unpaid? How much activity happens at another bank? The answers may already be sitting in the customer's accounting software. Getting them onto a banker's desk is the business Codat has spent years building.

Now it wants a place in the conversation, too. In May 2026, Codat announced an advisory intelligence platform for commercial banks and an agreement with BMO to apply AI-powered spend insights to middle-market client discussions. The move gives a once largely invisible financial-data company a more visible ambition: help bankers arrive with a useful suggestion before the customer asks.

That is a sharper proposition than selling access to another stream of numbers. It also raises the bar. A working connection can be tested; good advice has to survive a meeting with someone who knows the business.

350,000+

connections to business customers’ financial systems, reported by Codat in May 2026.

Connections, not a count of paying customers.

01First, get the books out of the inbox

Codat's founders had seen the paperwork up close. Peter Lord, Alex Cardona and David Hoare worked together at the invoice-finance business now known as MarketFinance. They founded Codat in 2017, with Lord as CEO, Cardona as COO and Hoare as CTO. Their target was the human relay between financial systems: documents attached to emails, information collected again, software that could not readily talk to other software.

The original product was a universal API, a common interface through which banks and financial-software companies could connect to customers' accounting, banking and commerce systems. Instead of building a separate translation for every platform, a developer could work with standardized data. The unglamorous work of making records intelligible across systems became something a specialist supplier could handle.

Its customers were the companies serving businesses, while the businesses authorized access to their records. That distinction still matters. Codat supplies infrastructure and analysis to lenders, payment providers and software platforms. It does not become the customer's bank or replace the accounting system where the books live.

“The way small businesses interact with banks has been broken for a long time.”Peter Lord · June 2020
Codat team gathered in an office in an archival company photograph
Everybody in the frame. Codat’s team in the photograph published with its June 2020 funding announcement. The data business still needed plenty of people.

02The connection worked. The question remained.

Codat's account of its 2026 repositioning contains a useful admission: access was only part of the problem. Commercial banks came with a harder request. They had transaction histories and relationship records, but accounting data arrived in a form designed for bookkeeping. Someone still had to work out what it meant for a banking conversation.

The change in emphasis followed that demand, according to the company's brand announcement. This was a second job emerging from the first, rather than evidence that the original connections had stopped working. Codat told developers in April that existing APIs, authentication and data flows would continue unchanged. Its new identity even hides a small accounting joke: the letters c and d in the brandmark nod to company data, the idea behind its name.

The platform combines financial information from the client's ERP and accounting software with the bank's own context. Codat says that combination happens inside the bank's environment. Specialists configure recommendations around the institution's products, rules and priorities, then deliver outputs through its approved AI tools. A proposal should reflect what that bank can actually offer.

The distinction is practical. A larger capital purchase could prompt a financing discussion; balances held elsewhere might open a treasury conversation. Those are possible uses, not automatic conclusions. A banker still has to establish why the money moved and whether a product would help.

Anatomy of a useful conversation
01 / CONNECTThe client’s booksAuthorized accounting and ERP records
02 / INTERPRETThe bank’s contextProducts, relationship data and configured rules
03 / ACTThe banker’s judgmentA relevant question, analysis or proposal
Conceptual workflow. Access enables analysis; the banker remains part of the decision.

03Follow the supplier, follow the spend

Commercial cards give the strategy a specific job. A business may pay hundreds of suppliers, with payments spread across cards, checks, ACH and wires. The issuer wants to know where a card might fit. The business wants a payment arrangement that works for its suppliers and its cash flow. A list of transactions alone leaves plenty of homework.

Codat's Spend Insights collects authorized ERP data, or accepts uploaded files, and produces supplier breakdowns, payment analyses and directional card-acceptance scores. Teams can use those scores to prioritize outreach rather than treat every supplier as equally likely to say yes. Ongoing monitoring can show changes in spend or payment methods after the initial campaign.

In a published Tearsheet interview, Lord described the target as middle-market businesses spending tens of millions annually on accounts payable, often across hundreds or thousands of suppliers. That scale explains the appeal: the potential opportunity is large enough to matter, while the supplier list is too unwieldy for a casual inspection.

BMO's announced collaboration applies Spend Insights to card optimization and advisory conversations. J.P. Morgan also provides a public customer endorsement of Codat's supplier-data collection work. These are concrete institutional relationships. They should not be confused with proof that every recommendation produces a sale.

The wider product range follows the same financial records into different jobs. Working Capital Insights supports treasury analysis; FX Insights, included in the May launch, examines cross-border activity and currency exposure. The established integration tools cover bill payment, expense synchronization, bank feeds and lending. Reading data for underwriting and writing transactions back to the books are separate capabilities, so buyers need to match the integration to the task.

Codat promotional Spend Insights illustration showing supplier counts and a trend chart
The supplier list gets a second career. Codat’s Spend Insights illustration. The numbers here are marketing artwork, not measured customer results.

04The $100 million round - and the invoice problem

Building the connections attracted substantial backing. Index Ventures invested $10 million in June 2020. A $40 million Series B followed in July 2021, led by Tiger Global and joined by Index and PayPal Ventures. Then came the $100 million Series C in June 2022, led by J.P. Morgan Growth Equity Partners, with Canapi, Shopify, Index and PayPal Ventures participating; Plaid was publicly named as an investor for the first time.

The investor list had commercial logic. Banks and payment businesses could use the infrastructure Codat was building. The 2022 announcement also described a Plaid partnership that brought banking data into Codat's API alongside accounting and commerce records. Capital and distribution were intertwined, although an investment is not the same thing as a deployment.

Those funding amounts describe money raised, not the cost of a customer installation. Codat sells enterprise software. A case study published by billing provider m3ter documents a platform fee alongside usage-based charges and bespoke contracts. Buyers enter a sales process for commercial terms; the economics depend on the agreement rather than a universal sticker price.

Here the story becomes pleasantly human. The company connecting everyone else's systems had disjointed billing systems of its own. Joe Lambert, identified as senior business operations at Codat, told m3ter that manual usage billing consumed a day or two at month-end. The platform-fee calculation was manageable; matching usage to invoices was the troublesome part.

Codat connected its sales and billing process so contract details and usage could be matched to plans. The case study reports roughly 90 percent automation and one to two days saved monthly. The lesson is available to any software business: when contracts become complicated, the spreadsheet behind the invoice can become a bottleneck before the product does.

Three disclosed equity rounds / USD
2020 · A
$10m
2021 · B
$40m
2022 · C
$100m
Capital for the connections. Announced round sizes, on a common scale. This chart excludes grants and other investments; it is not a spending or revenue chart.

05A specialist in a crowded integration aisle

Codat occupies the space between business records and financial products. Its expertise is both technical and domain-specific: translate accounting data, infer useful meaning, and fit the result into a bank's workflow. Its 2022 nCino partnership illustrates the approach, bringing financial-data connectivity into a platform banks already used for lending.

It has company. Rutter markets accounting and ERP integrations, bank feeds, accounting automation and supplier enablement. Merge offers accounting integrations alongside categories such as human resources and customer relationship management. Building directly against accounting providers is another option for teams prepared to own the connections and their maintenance.

The competitive boundary is therefore fuzzy. Supplier scoring and AI do not give Codat an empty market. Its current pitch emphasizes banking context, implementation expertise and recommendations shaped around an institution's own products. That makes the evaluation more specific than counting integration logos: can this system answer the bank's actual question using the customer's actual records?

A broader integration platform may suit a product that needs several unrelated software categories. A narrow internal build may suit a team with one essential system and unusual requirements. For Codat, the stronger case is a recurring financial workflow where maintaining connections and interpreting the records would otherwise consume substantial effort.

06Less machinery, more ownership

The engineering organization has been doing some subtraction. On its public engineering site, Codat says it consolidated an organically grown architecture from about 400 microservices to about 100. It also describes work on payment-method inference, where the same real-world payment can be recorded differently across accounting systems. That is the kind of detail concealed by a tidy product diagram.

Its stated working model gives engineers responsibility for running what they build, with automated tests, observability and canary deployments supporting frequent releases. The careers page adds a more personal promise: equity for all employees and a four-week paid sabbatical after four years. These are published practices and benefits, rather than an independent verdict on employee experience.

Taken together, they suggest a company trying to reduce internal friction while taking on a more demanding external job. The software has to handle messy financial records; the organization has to avoid becoming equally difficult to navigate.

Stylized company portrait of Codat co-founder and CEO Peter Lord
A face behind the interface. Co-founder and CEO Peter Lord, in Codat’s company portrait. The business began with a problem his founding colleagues had seen at an invoice-finance platform.

07A better meeting still needs a banker

For a bank testing the idea, the sensible unit of progress is one useful conversation. Start with a defined portfolio and a specific decision, such as which suppliers to approach about card payments. Establish how long the analysis takes today, then examine whether the connected workflow produces information people actually use. Expand after the working process earns its place.

There are firm conditions attached. A client must agree to share data. An accounting connection cannot reveal a transaction that has not been recorded, and a one-off upload cannot refresh itself. Supplier acceptance scores express likelihood, not consent to a payment method. A bank also needs people able to question a recommendation instead of simply forwarding it.

Codat's own August 2026 interview with FNBO's Maria Line makes that last point well. Her team starts with the business's objective; some vendor relationships are better served by ACH or wire. Predictive information increases the importance of human judgment because somebody still has to choose the appropriate response.

The opportunity for Codat is to make that judgment better informed and less laborious. Its test is equally plain: after the data has moved, the charts have appeared and the AI has spoken, does the banker have something worthwhile to say?