Custom Bizcuit integration
Bizcuit connects banking with bookkeeping. The platform has integrations with Dutch banks and accounting packages, and offers software vendors APIs to use them in their own product. Appfront builds your side of that connection: bank data, transactions and invoices flowing through Bizcuit into your software or platform, so you don't have to integrate with every bank and every accounting package yourself.
What is a Bizcuit integration?
Bizcuit is a Dutch platform that connects banking and bookkeeping. It has a banking hub for integrations with banks, an accounting hub for integrations with accounting packages and a document hub. Banks such as Rabobank and the Volksbank use Bizcuit for the accounting integration offered to their business customers, and entrepreneurs know the Bizcuit app for managing their finances.
For software vendors, the API is what matters most. If you have your own package or platform, you want customers to be able to link their bank account, payments to be reconciled automatically and invoices to end up in the customer's accounting package. Integrating with every bank and every package yourself is a lot of work that is never finished. Bizcuit handles that part, and your software talks to a single API.
We build custom integrations because every product is different. Which data you need, how the customer gives consent, which accounting packages your customers use and what has to flow back into your software all determine how the integration works. Bizcuit has a sandbox and public API documentation, so we can build and test before any real accounts are involved.
One API
For banks and accounting packages.
Customer consent
The account holder decides.
Sandbox first
Testing without real accounts.
How we build your Bizcuit integration
We start with your product: what does your software need to do with bank data and bookkeeping, who are your customers, and which banks and packages do they use. Then we look at which parts of the Bizcuit API fit and which agreements you need to make with Bizcuit. We often start with linking a bank account and retrieving transactions, because that is where most of the manual work lies. Invoices and postings to the accounting package follow once that runs smoothly. After that, we maintain the integration whenever Bizcuit or your own software changes.
Customers, banks and packages.
What Bizcuit offers you.
Sandbox first.
Go-live, monitoring, and maintenance when things change.
What a Bizcuit integration actually does
The components below appear in almost every Bizcuit integration. Which ones you need depends on your product and your customers.
Linking an account
With the customer's consent.
Transactions
Retrieving balances and transactions.
Reconciliation
Payment matched to the right invoice.
Accounting package
The customer's choice.
Invoices
To the accounting system.
Log
Every message recorded.
Who we build a Bizcuit integration for
The integration is intended for companies that want financial features in their own software without integrating with every bank and every accounting package themselves. The more customers and the more different packages, the more it pays off.
Software vendors
Industry, ERP or payroll.
Platforms and PSPs
Payments in the accounting system.
In-house administration
Banking directly in your software.
Accountancy firms
In-house tooling for customers.
Technology and integrations
This page is about integrations via Bizcuit. If you want to integrate directly with a single accounting package, see our page on the Exact Online integration, our page on the Twinfield integration and our page on the Moneybird integration. For incoming invoices, see our page on invoice recognition. You can read about our approach at custom software development.
Why Appfront for your Bizcuit integration?
Building and maintaining your own integration with every bank and every accounting package costs a software vendor more than the product itself. That is what we build on: one API for banks and packages, consent from the customer, and testing in the sandbox first.
Fewer integrations
One API instead of dozens.
Customer stays in control
Consent per account.
Securely tested
Sandbox first.
Security and privacy in a Bizcuit integration
The integration processes your customers' financial data: accounts, balances, transactions and invoices. Access to a bank account depends on the account holder's consent, and the customer can withdraw it. Keys and tokens are stored encrypted, we only use the data that is needed, and every message is logged.
The part we build runs in a European data centre, with encrypted storage and daily backups. We record the processing in a data processing agreement, and we agree with you which arrangements you make with Bizcuit and with your customers.
Frequently asked questions about a Bizcuit integration
Questions software vendors ask before they start.
Bizcuit is a Dutch platform that connects banking with bookkeeping. It has a banking hub for integrations with banks, an accounting hub for accounting packages and a document hub. Banks use it for the accounting integration of their business customers, entrepreneurs use it for their finances, and software vendors use it via the API.
Because every bank and every accounting package needs its own integration, with its own rules, contracts and maintenance. Through Bizcuit, your software talks to a single API. If your customers only use one bank or one package, a direct integration can be simpler, and we will tell you so.
Via Bizcuit's APIs, which are publicly documented. There is a sandbox, so we can build and test the integration without real accounts. Which components you use and which terms apply is something you arrange with Bizcuit. We will look at that together in the first step.
Yes. A bank account is only linked if the account holder gives consent, and they can withdraw that consent again. The integration lets the customer take that step from within your software, and keeps track of which accounts are linked.
Often, yes. The integration retrieves transactions and finds the matching invoice, by amount, reference or description. Whatever is certain is reconciled automatically. Doubtful cases go into a list for manual review, so nothing gets booked incorrectly.
The integration reports it and records what went wrong. The message is retried or queued for review, so no transaction is lost or ends up in the books twice.
For vendors of industry-specific, ERP and payroll software, for platforms and payment service providers, for companies with their own accounting software and for accountancy firms with their own tooling. If you use the Bizcuit app yourself and miss nothing, you do not need a custom integration.
Banking and bookkeeping in your own software?
Tell us what your software needs to do with bank data and bookkeeping. We will show you how the integration with Bizcuit works.