Bizibox: The Link Between the Business, the Accountant and the Bank - and What Actually Moves

Bizibox is a platform that pulls a business's bank, credit card and card-clearing data into one place, according to what the company presents on its own site. It does not move money: the access is read-only. The design consequence is that it shortens the path data travels between three parties, and replaces none of them.

The three parties and what each actually needs

The owner, the accounting firm and the bank do not want the same thing, and most of the pain in this workflow comes from someone trying to give all three the same screen.

• The business owner wants to know how much money there is and what leaves in the next fortnight. That is a forward cash-flow picture, including commitments that have not touched the bank yet.
• The accounting firm wants classified transactions that can become journal entries, with a reference behind every line. A forward projection is of almost no use to them.
• The bank wants nothing. It is a data source, it publishes only what already happened, and it does so in a format it chooses.

An aggregation platform sits between the first two. It pulls from the third and serves different cuts of the same data to the first two. Once that is clear, "is the system accurate" splits into two separate questions: is the pull from the bank complete, and is the classification right. The first is technical. The second is professional.

What "read-only access" actually means

Read-only access means the system reads transactions and balances and cannot move money. It is worth confirming with any vendor, because it changes the risk profile of the connection entirely.

What it does not mean:

• It does not mean the data is not retained. It is retained, usually for a long period.
• It does not mean nobody operating the account can see sensitive commercial information. They can.
• It does not mean revoking the permission deletes history already collected.
• It does not mean the connection will not fail. Authorisations expire, passwords rotate, and the pull stops quietly.

The most common failure in a connection like this is not a wrong number. It is a day on which nothing was pulled and nobody noticed. Any process leaning on a daily pull needs an alert on the absence of a pull, not only on an unusual value. That is the same principle described in monitoring silent failures in Zapier and Make.

Does Bizibox have a public API?

I found no public developer API documentation for Bizibox. The company's site presents the product in terms of capability - aggregating bank and card data, moving it into accounting software, a mobile app, alerts - and not in terms of a programmable interface. There is no published developer portal, no Swagger reference and no description of an authentication scheme.

That is a claim about what is published, not about what exists. There may well be an interface offered to customers or partners. But for project planning purposes, you cannot commit to a schedule against a specification you have not seen.

Four approaches that do work when a system publishes no interface:

• Start from the destination, not the source. If the destination is accounting software with documented APIs, build against that and treat the platform as the thing feeding it.
• Agree a file layout. A scheduled export in a fixed, agreed structure is a real integration, and it is more stable than an undocumented API.
• Buy the vendor's professional services. A mid-sized Israeli vendor will build a point connection for a fee, and that is a perfectly legitimate answer.
• Read the reporting output. If everything else fails, the report is the interface. It is the least elegant route and still better than inventing an endpoint.

That decision is expanded in what to do when an Israeli system has no API.

The handoff table: what moves, where to, and how

The third row is what breaks reconciliations. A settlement credited as one aggregated amount for a day does not map one-to-one to the invoices issued that day, and the gap between them is fees and timing. Anyone expecting those two lines to match exactly will lose a week.

What should you check before connecting a bank account to an outside vendor?

• Which route the access uses: a regulated open-banking interface, or handing credentials to a third party. Those are two very different things.
• Whether the vendor appears in the Capital Market Authority's register of financial service providers. The register is public and searchable.
• Who inside the business and inside the accounting firm can see the data, and how access is revoked when someone leaves.
• What happens to already-collected data when the service is terminated.
• Whether a full history export exists in a format readable without the system itself.
• Whether the connection alerts on a failed pull, and who receives that alert.

Related: business bank account data and open banking in Israel, automation for accounting firms.

Sources

• bizibox - company site
• Register of financial service providers - Capital Market, Insurance and Savings Authority
• Application procedure for a financial information service provider approval - gov.il