Komercni banka

Komerční banka is a Czech bank with an Account Direct Access API for business accounts. Agents list accounts, read balances and transaction history, download PDF statements, and manage event subscriptions that fire when new transactions arrive.

Verified 11 actions OAuth available

Komercni banka website Platform Documentation Capability data verified 2026-08-25

A scheduled reconciliation pass runs across the enrolled accounts

Check Service Availability confirms the bank's service is answering at all

Get Event Subscription reports whether each account's transaction feed is still active

Get Transactions walks the pages from zero across the window since the last pass

Receipts matched to open receivables close them in the accounting system

Unmatched debtors are posted alongside any feed reporting a stopped or suspended state

Credit control decides which overdue accounts get chased, knowing what the feed can prove

What This Integration Enables

Komerční banka's Account Direct Access API is a reporting surface, and the shape of it is the point. There is no payment operation anywhere on this connector, because the bank does not put one there. What it gives you is the accounts you enrolled, their balance types, two years of transaction history, and the signed statement documents an accountant asks for. Everything a business then does with that information happens in a different system, which is exactly the split that makes the API easy to reason about and easy to trust.

FlowRunner agents list the enrolled accounts, resolve an IBAN and its currency into the opaque account id every other route takes, and read balances as the list of types the bank actually publishes rather than as a single number. They page through transaction history oldest first, list and download statements as PDFs, and manage the event subscriptions that tell a system when new transactions have arrived. Because the connector reads and never pays, the human-in-the-loop moment here is not about releasing money. It is about what a business does when the money has not shown up.

Without FlowRunner

Balances read from a portal Somebody logs into internet banking each morning to copy a figure into a cash sheet

Statements filed by hand The official PDF is downloaded, renamed, and dropped into a folder when someone remembers

Silence read as payment An account with no incoming payment is assumed to be overdue, whether or not the feed was working

With FlowRunner

Balances collected on a schedule Every enrolled account reports its balance types with their own validity timestamps

Statements archived as they appear New statements are detected by sequence number and archived as the signed document

Silence checked before it is acted on Feed health is proved before an unpaid balance turns into a chase, a hold, or a notice

Use Case Scenarios

Receivables closed against what actually landed

On a schedule the agent reads each enrolled account's transactions for the window since the last pass, remembering that the page number is required and counts from zero and that results come back oldest first. It matches incoming credits against open receivables in NetSuite or Xero using the payer reference and amount, and closes what resolves cleanly. Everything that does not match is posted into Slack as a short list with the payer, the amount, and the reference it carried, so the person who knows the customer can identify it in seconds rather than opening the bank portal.
A cash position that reports the right kind of balance

Get Balances returns several balance types, including booked, available, and a credit line where one exists, each with its own validity timestamp. Taking the first row blindly gives a figure that may not be the one anybody meant. The agent reads all of them, labels each one, and writes the daily position for every enrolled account into Google Sheets with the timestamps attached. Treasury reads one table instead of several portals, and a movement in the available balance that the booked balance has not caught up with is visible rather than averaged away.
The statement archive that keeps itself current

Statements carry sequence numbers, and the flow that watches them does not have to guess. The agent calls List Statements from the last archived date, compares the sequence numbers with what has already been filed, and calls Download Statement for anything new. The PDF is the official document, as opposed to the transaction rows that a reconciliation flow works from, so it goes to document storage under the account and sequence number. An account whose statement sequence skips a number is flagged rather than filed, because a missing statement is a finding at audit time.

Human-in-Loop Highlight

The thing this connector cannot tell you is whether nothing happened or nothing was delivered. The bank's event mechanism does not deliver to a callback URL, it calls an Event API you have to host, and the payload it sends is only a count of events rather than the events themselves. A subscription whose endpoint answers 401, 403, or 404 is stopped permanently, and one that times out is suspended by a circuit breaker. Nothing raises an error on the reading side when that happens: transaction reads simply keep returning an empty list. Add the two year limit on history, beyond which a request is refused rather than trimmed, and a long outage becomes a hole nobody can fully backfill. So before an unpaid invoice becomes a chase, a credit hold, or a suspended service, the agent proves what it can. It runs Check Service Availability and Get Event Subscription, and where the subscription reports a stopped or suspended state it stops too, posting: "Account CZ65 0100 shows no incoming payment for 9 days. Its subscription has been SUSPENDED since the 12th, so the absence is not evidence. Chase these four customers anyway, or reconcile from statements first?" Credit control answers. Nothing goes out on the strength of a feed that was not running.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

11 actions

Accounts

List Accounts Lists the accounts this API service was registered for, with their id, IBAN, and currency. It returns only the enrolled accounts, so one you own but did not enroll simply is not here.
Get Account ID Turns an IBAN and its currency into the opaque id every other route takes. The currency is genuinely required, since one IBAN can carry several and each has a different id.
Get Balances Returns an account's balances as a list of types, including booked, available, and a credit line where one exists, each with its own validity timestamp.
Get Transactions Returns transaction history oldest first, one page at a time. History reaches back two years, and a request beyond that is refused rather than trimmed, so a backfill has to clamp its own window.

Statements

List Statements Lists an account's statements from a date onward, with sequence number, page count, and whether each is archived.
Download Statement Downloads one statement as a PDF. This is the official document an accountant wants, as opposed to the transaction rows a reconciliation flow reads.

Event Subscriptions

Create Event Subscription Subscribes an Event API you host to an account's transaction events. The bank calls your version route at subscription time and rejects the subscription unless it answers correctly.
Get Event Subscription Reads a subscription's status. Worth polling on a schedule, because a feed that quietly stopped delivering shows up here as stopped or suspended with a narrative, and nothing else reports it.
Delete Event Subscription Unsubscribes from an account's transaction events.

Service

Check Service Availability Reports whether the service is up. Any status other than a clean answer means it is not, since the bank is explicit that there is no partial state.

Registration

Register Software Statement Registers a third party application with the bank and returns the software statement its client credentials are issued from. A different API with different authentication, and a one time onboarding step done with the bank rather than something a flow runs.

Frequently Asked Questions

What can FlowRunner do with Komercni banka?

FlowRunner agents can run List Accounts, Get Account ID, and Get Balances in Komercni banka, plus 8 more actions.

Does connecting Komercni banka to FlowRunner require OAuth?

Yes. Komercni banka connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.

Can Komercni banka trigger a FlowRunner workflow automatically?

Komercni banka doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Komercni banka

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us