iUcto

iÚčto is Czech online accounting and invoicing software. Agents manage parties and documents, post invoices and payments, upload incoming documents, import bank transactions, and track stock cards and warehouses.

48 actions API key available

iUcto website Platform Documentation Capability data verified 2026-08-24

A supplier invoice arrives in a monitored mailbox, as a PDF or a Czech ISDOC file

Upload Incoming Document files it into the inbox, where an ISDOC is read into a received invoice

Get Document reads the resulting document back with its lines and totals

Get Accounting Types returns the classifications this document type will accept per line

The proposed account entry type, VAT type, and chart account are compared against how similar documents were posted before

The proposed mapping goes to the bookkeeper with the supplier, the amount, and each line's account

The bookkeeper approves the mapping before Post Document writes anything to the ledger

What This Integration Enables

iÚčto is Czech online accounting software, not an invoicing app with a ledger bolted on, and the connector reflects that. Create Document produces a document. Post Document is a separate operation that writes it into the ledger, and the vendor is explicit that every line must already carry its accounting settings, meaning its account entry type, its VAT type, and its chart account, or the whole posting fails. Get Accounting Types exists to tell you what a given document type will accept. That two step design is the most useful thing about this integration, because it gives an agent somewhere to stop that is neither too early to be useful nor too late to matter.

FlowRunner agents work all nine registers through one shape: issued and received invoices, proformas and credit notes, orders in both directions, and the internal cost record. They manage the address book, record and post payments, import and post bank movements, upload supplier documents into the inbox, maintain the price list, and move stock across warehouses through stock cards. They also read the journal directly. The Czech variable symbol runs through all of it, because that is what a bank movement is matched to an invoice on, and setting it deliberately on creation is what makes the later reconciliation work at all.

Without FlowRunner

Supplier documents queue up Invoices sit in a mailbox until someone has an afternoon to key them in

Coding decided line by line, late Account entry types and VAT types are chosen at the end of the month, away from the source document

Corrections blocked by the calendar A misposted document found after the period is filed is refused, and the reason is easy to misread

With FlowRunner

Documents land as records Files reach the inbox on arrival, and an ISDOC becomes a received invoice rather than an attachment

Coding proposed with the document The classification each line needs is gathered at intake and presented with the evidence behind it

Mistakes caught before posting The commitment step is the one a person sees, so the correction happens while it is still cheap

Use Case Scenarios

Supplier invoices from the mailbox to the ledger

A supplier sends an invoice to a shared mailbox monitored through Gmail, or drops it into a folder in Dropbox. The agent calls Upload Incoming Document, which puts the file into the iÚčto inbox. When the file is an ISDOC or ISDOCX, the Czech electronic invoice format, iÚčto reads it into a received invoice rather than merely filing it, which is the cheapest route supplier documents have into a Czech ledger. The agent then reads the document back, calls Get Accounting Types for that document type, and proposes a classification for each line based on how the same supplier's previous documents were coded. It stops there. Posting is the next scenario's problem, and it belongs to a person.
Bank movements matched on the variable symbol

Bank movements are imported with Import Bank Transaction. The variable symbol on each one is the Czech payment key, and it is what ties a movement to an invoice, so the agent sets it deliberately on Create Document for anything a flow issues. On import, it matches each movement's variable symbol against open issued invoices, creates the payment with Create Payment where exactly one document matches, and posts both with Post Payment and Post Bank Transaction. A movement that arrives without a variable symbol has to be matched by hand, so those are collected and posted into Slack as a short list with the amount, the counterparty, and the two or three invoices that come closest.
Stock that moves when the paperwork does

A goods receipt or a dispatch is recorded through Create Stock Movement against the relevant warehouse, with a negative quantity taking stock out. Because a product needs a stock card in a warehouse before stock can move there, the agent calls List Stock Cards first and creates the missing card with Create Stock Card rather than failing the movement. It reads List Stock Movements back to confirm the position, and where the movement corresponds to a document it attaches the delivery paperwork with Upload Attachment so the physical event and its evidence sit together in one system.

Human-in-Loop Highlight

Post Document is the moment this connector commits, and it needs a person for a reason that is specific to how iÚčto validates. Get Accounting Types reports what a document type will accept, not what is correct for this particular supplier and this particular line. A posting whose lines carry a valid but wrong account entry type is not refused. It succeeds. And once it has succeeded, Delete Document is refused for a posted document, and refused again once the accounting or VAT period closes over it, which iÚčto reports with the same 403 it uses for a missing permission. So the agent gathers everything, proposes the mapping, and stops: "Received invoice from Alza for 48,400 CZK, three lines. I propose office supplies for lines one and two and hardware under 80,000 for line three, matching how this supplier's last six invoices were posted. Line three could also be a fixed asset. Post as proposed, or reclassify?" The bookkeeper answers, the agent posts. Intake, matching, and coding at machine speed; the entry into the ledger stays a decision someone made on purpose.

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

48 actions

Company Registers

Get Company Profile Reads the company the API key belongs to. A key is one company and one user, so this is what a flow confirms first.
Get Company List Reads one of the company registers: bank accounts, cash registers, cost centers, contracts, business premises, document states, customer or supplier groups, currencies, payment types, or rounding types.
Create Company Record Creates a bank account, cost center, contract, or document state in a company.

Address Book

List Parties Lists the customers or suppliers of a company, and doubles as a lookup by registration number, VAT number, email, or your own external code.
Get Party Reads one customer or supplier in full.
Create Party Creates a customer or supplier in a company.
Update Party Updates a customer or supplier.
Delete Party Deletes a customer or supplier from a company.

Documents

List Documents Lists the documents of one register: issued or received invoices, proformas, credit notes, orders, or internal cost records. The register is a parameter, so one operation covers all nine.
Get Document Reads one document with its line items and totals. The read back before a posting decision.
Create Document Creates a document in one of the registers together with its line items. Creating it does not post it to the ledger.
Update Document Updates a document. Sending line items replaces the existing ones, so read the document first when only one line is changing.
Delete Document Deletes a document from a register. A posted document or a closed accounting period is refused.
Post Document Posts a document to the ledger. Every line must already carry its accounting settings, and this is the step that makes a created document count. The operation this page's human gate exists for.
Download Document PDF Downloads an issued invoice or issued proforma as a PDF into FlowRunner file storage.
Send Document By Email Emails an issued invoice, proforma, or credit note. This reaches the recipient and cannot be recalled.
Share Document Produces a shareable link to an issued document, which lets a customer see it without an account.
Pay Proforma Records a full payment against an issued proforma, which iÚčto creates for the whole amount.

Incoming Documents

List Incoming Documents Lists the documents waiting in the inbox, which is where forwarded or uploaded supplier documents arrive.
Upload Incoming Document Uploads a supplier document into the inbox. An ISDOC or ISDOCX file is read into a received invoice rather than merely filed.

Payments

List Payments Lists the payments of a company, received or issued.
Get Payment Reads one payment in full.
Create Payment Records a payment against an invoice, proforma, or credit note.
Update Payment Updates a payment in a company.
Post Payment Posts a payment to the ledger, the same separate commitment step that documents have.
Delete Payment Deletes a payment, which reopens the document it settled.

Banking

List Bank Transactions Lists the bank movements imported into a company.
Import Bank Transaction Imports a bank movement. Its variable symbol is what matches it to an invoice, and a movement without one has to be matched by hand.
Post Bank Transaction Posts a bank movement to the ledger.
Delete Bank Transaction Deletes a bank movement from a company.

Price List

List Price List Items Lists the price list items of a company, which are the products and services document lines are built from.
Create Price List Item Creates a price list item in a company.
Update Price List Item Updates a price list item.
Delete Price List Item Deletes a price list item from a company.

Stock

List Warehouses Lists the warehouses of a company.
List Stock Cards Lists the stock cards, which record what each product holds in each warehouse.
Create Stock Card Creates a stock card, which a product needs in a warehouse before stock can move there.
Create Stock Movement Records a stock movement in a warehouse. A negative quantity takes stock out.
List Stock Movements Lists the stock movements of a company.

Accounting

List Journal Entries Reads the accounting journal, filtered by date, account, document, party, cost center, contract, or VAT type.
List Internal Documents Lists the internal accounting documents of a company.
Create Internal Document Creates an internal accounting document in a company.
Get VAT Rates Reads the VAT rates iÚčto applies on a date, for a country, which is what keeps a back dated document right.
Get Accounting Types Reads the account entry types or VAT types a document type accepts, which is what a line must carry before the document can be posted. It reports what is allowed, not what is correct.

Attachments

List Attachments Lists the files attached to a record.
Upload Attachment Attaches a file to a record.
Download Attachment Downloads an attachment into FlowRunner file storage.
Delete Attachment Deletes an attachment from a record.

Frequently Asked Questions

What can FlowRunner do with iUcto?

FlowRunner agents can run Get Company Profile, Get Company List, and Create Company Record in iUcto, plus 45 more actions.

Does connecting iUcto to FlowRunner require OAuth?

No. iUcto connects to FlowRunner with an API key, no OAuth flow required.

Can iUcto trigger a FlowRunner workflow automatically?

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

Start building with iUcto

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us