--- title: "Apideck and Dolfin AI: the connectivity layer for embedded finance agents" description: "Apideck is partnering with Dolfin AI to power embedded finance agents for banks and SaaS platforms. The AP and AR use cases, and who they fit." author: "Bernard Willems" published: "2026-06-16" updated: "2026-06-16T11:25:53.565Z" url: "https://www.apideck.com/blog/apideck-dolfin-ai-embedded-finance-agents" tags: ["Accounting"] --- # Apideck and Dolfin AI: the connectivity layer for embedded finance agents Most small businesses still run accounts payable the slow way. Someone keys the bills into a separate tool by hand, then exports a CSV at month end to reconcile against the accounting system. The work sits outside the products the business uses every day, and the lost time adds up. Embedded finance agents change that, and Dolfin AI is building them. That is why we are partnering with them. [Dolfin](https://www.dolfinai.co/) builds embedded, white-label accounts payable and receivable agents that banks and software platforms can offer their SMB customers. The agents run invoicing, bill payment, and reconciliation inside the product a business already logs into, and a user can instruct them in plain language instead of clicking through forms. Apideck provides the connectivity underneath: one unified API across more than 40 accounting and ERP systems. You can see the scale of the opportunity in our [State of B2B Embedded Finance report](https://www.apideck.com/embedded-finance-report), where BCG and Adyen put the SaaS-addressable market at 185 billion dollars with less than 20 percent captured so far. ## What Dolfin actually builds Inside the bank or the software platform, fully white-labeled, a business sees a financial operations screen with its invoices and bills. Alongside it sits an agent. A user can type "invoice Acme for 10 units at 25 euros and send it," and the agent creates the customer if needed, then builds and sends the invoice with a payment link. On the payables side, the agent reads incoming bills and schedules them for payment once approved. The product reflects where financial software is going. The job that used to live in a standalone destination like Bill.com is moving into the systems a business already uses, the bank and the platform, and increasingly an agent does the work. As James Regan, Dolfin's CEO, describes it, businesses would rather the system they already log into did more, instead of adopting yet another point solution to manage. ## Why embedded finance agents need a connectivity layer An agent that drafts an invoice is only useful if that invoice lands in the customer's real accounting system, and the payment that follows is matched and posted back. That write-back is the part teams underestimate. Reading data from QuickBooks is one problem. Writing a bill into NetSuite and confirming it posted, with its tax logic applied correctly, is a harder one. The difficulty grows with coverage. Accounting is regionally fragmented, with more than 20 major platforms and the top five vendors holding only about half of global share (BCG and Adyen). A bank serving SMBs in the Benelux needs Exact and Yuki. A US bank needs QuickBooks and NetSuite. Building and maintaining each of those connections in-house runs 50,000 to 150,000 dollars per integration per year, and the point where a unified API becomes cheaper arrives at four to five integrations, according to the same research. Apideck handles that layer: the connection management and the write-back across accounting systems, behind one data model. For an agent builder, that means a single interface to read bills and push invoices across more than 40 systems, rather than a separate integration project for each platform. Dolfin builds the agent and the experience; we make sure it can reach what sits behind it. ## The use cases this unlocks Three patterns matter most for the businesses Dolfin serves. ### Accounts payable that closes the loop An agent ingests vendor bills and writes the payment back to the customer's ledger once approved, so the books stay current without anyone exporting a file. This is the [accounts payable automation](https://www.apideck.com/use-cases/accounts-payable-automation) pattern, run by an agent instead of a screen full of forms. ### Invoicing and accounts receivable A user asks the agent to bill a customer. The agent creates the invoice in the connected accounting system and matches the incoming payment once it arrives. [Accounts receivable automation](https://www.apideck.com/use-cases/accounts-receivable-automation) becomes a conversation the user can have rather than a workflow they have to drive. ### Reconciliation across systems When payments and invoices flow through the bank or platform, they can be matched and posted to the general ledger automatically. The alternative is the CSV-export-and-rekey routine that embedded financial products are meant to retire, a problem we have written about for [vertical SaaS](https://www.apideck.com/blog/embedded-finance-vertical-saas). ![Dolfin Financial OS](//images.ctfassets.net/d6o5ai4eeewt/4UAIUlXx6Xezbn41PDikNl/da2409669058cd4f5aadb3adbaadbc72/Dolfin_platform.png) ## Which customers this is relevant for Three profiles fit best. ### Banks and neobanks serving SMBs This is the clearest case. Business banking that wants to put real financial management in front of customers can offer AP and AR agents under its own brand, with the accounting write-back handled underneath. The white-label model is built for it. ### Vertical SaaS platforms for small businesses A platform sitting in a daily workflow already owns the customer relationship and the data. Adding embedded financial operations deepens that without standing up an accounting integration team. About 60 percent of small US businesses already run on vertical SaaS (BCG and Stripe), which is the distribution that makes the model work. ### Agent-first B2B fintech Teams building agent-native financial products from scratch get the operations agent from Dolfin and the connectivity from Apideck, instead of constructing both and maintaining the second one forever. This is not the right fit for everyone. A product built around a single ERP with deep customization, or one that needs only one or two integrations, will see less return from a unified layer. The economics show up once you support several systems across regions, the four-to-five integration threshold again. ## What comes next We are collaborating on product now, with Dolfin testing what we ship and telling us what agent builders need from a connectivity layer. As shared customers come on, the integration will deepen. The bet behind it is simple: financial operations are moving into the tools businesses already use, run by agents, and those agents need a dependable way to reach every accounting system behind them. If you are building financial operations into a bank or a platform, the connectivity is the piece you do not want to maintain yourself. See how the [accounting API](https://www.apideck.com/accounting-api) handles read and write across systems, or read more on [what embedded finance means for B2B platforms](https://www.apideck.com/blog/what-is-embedded-finance).