--- title: "SuperFaktura Integration" description: "SuperFaktura is the Slovak and Czech invoicing platform. Agents issue invoices of every kind with their items, record payments, send documents by email or post, generate PDFs, and manage clients and contact people." url: https://flowrunner.ai/integrations/superfaktura date_modified: 2026-09-04T14:53:04-07:00 --- # SuperFaktura [Accounting](https://flowrunner.ai/integrations/category/finance-accounting) SuperFaktura is the Slovak and Czech invoicing platform. Agents issue invoices of every kind with their items, record payments, send documents by email or post, generate PDFs, and manage clients and contact people. 72 actions · Custom auth · available [SuperFaktura website](https://www.superfaktura.sk/) · [Platform Documentation](https://github.com/superfaktura/docs) · Capability data verified 2026-08-24 1. A confirmed order arrives and needs a document raised against it 2. Agent reads the buyer, the lines, the currency, and the order reference 3. Get Response By Checksum asks whether this order reference already produced an invoice 4. List Clients resolves the buyer against the address book by tax identifier 5. Create Invoice issues the document carrying the order reference as its checksum 6. Send Invoice By Email delivers it using the account's own template 7. A person rules on any order whose recovered response was an error rather than an invoice ## What This Integration Enables SuperFaktura runs a separate installation for each country it serves, and an account exists on exactly one of them. That single fact tells you what the product is: not a global invoicing veneer, but the working book of a Slovak, Czech, or Austrian business, with the numbering, the VAT treatment, and the document types its own tax office expects. FlowRunner agents work inside that book on both sides of it. They raise invoices of every kind with their items and clients, record supplier invoices as expenses, move stock, post cash register entries, and read the bank movements the platform has already imported. One capability changes how a careful flow is written. Create Invoice accepts a checksum of your own, and Get Response By Checksum returns the original answer to that write for months afterward. An agent that loses its connection mid write does not have to choose between raising a duplicate and leaving a customer unbilled. It asks. That is an unusually honest piece of API design, and it is the difference between an automation you can restart and one you have to reconcile by hand. The other half of the story is that two operations in this connector spend real money and cannot be recalled, which is where [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) stops being a checkbox and starts being the reason the flow is safe to run at all. ### Without FlowRunner **Duplicate documents after a timeout**: A dropped connection leaves nobody sure whether the invoice exists, so it gets raised again **Receivables chased by memory**: Whoever remembers sends a reminder, and nobody can say which reminders already went **Payables entered by hand**: Supplier invoices are keyed in separately from the sales side, in a different rhythm ### With FlowRunner **Writes that can be recovered**: Every document carries a checksum, so an interrupted flow asks what happened instead of guessing **Dunning as a running ladder**: Free reminders escalate on evidence, and the steps that spend money wait for a person **One book, both directions**: Invoices, expenses, stock movements, and cash register entries land in the same system ## Use Case Scenarios ### Order to invoice, restartable An order confirms in [Shopify](https://flowrunner.ai/integrations/shopify) or a charge settles in [Stripe](https://flowrunner.ai/integrations/stripe). Before writing anything, the agent calls Get Response By Checksum with the order reference. If SuperFaktura already holds a response for it, the invoice exists and the flow moves on. If not, List Clients resolves the buyer by tax identifier and Create Invoice issues the document with that same order reference as its checksum. Send Invoice By Email delivers it, Get Invoice PDF files a copy, and the invoice number goes back onto the order record. Rerun the flow after a crash and it costs one read, not a duplicate document. ### Supplier invoices that arrive as email Supplier PDFs land in a shared mailbox and get parsed by [Parseur](https://flowrunner.ai/integrations/parseur) or [Mindee](https://flowrunner.ai/integrations/mindee). The agent creates the expense with Create Expense, files it against a category from List Expense Categories, and links it to the sales invoice it relates to with Add Expense Related Item. Download Expense Attachment pulls the original document back out for the accountant's archive. When the bank feed clears, List Bank Account Movements reads the imported line and Pay Expense settles it. The payable and the receivable end up in the same book with the link between them intact. ### The dunning ladder, with a rung nobody automates past A daily sweep runs List Invoices for unpaid documents past their due date and reads Get Activity Log for each one, which records when the invoice was viewed, sent, downloaded, and paid. Documents the customer has never opened get a plain Send Invoice By Email reminder, which costs nothing. Documents opened repeatedly and still unpaid are a different problem, so the agent assembles the case and hands it to a person rather than escalating on its own. Meanwhile Mark Invoice As Sent By Email keeps the record straight for invoices your own systems delivered, so the ladder never double counts a reminder it did not send. ## Human-in-Loop Highlight Two operations here leave the platform and cannot be taken back. Send Invoice By Post has SuperFaktura print the invoice and physically mail it, spending postage credit on the account, and there is no draft state and no recall. Send SMS Reminder is charged per message and reaches a real phone immediately. Everything below them on the ladder is free and reversible, which is exactly why the agent is allowed to run it unattended and is not allowed to run these. So the collections agent builds the case and stops: "Invoice 2026-1130 for 4,180 EUR to Hronsky s.r.o. is 62 days overdue. The activity log shows it opened four times and downloaded twice, so it was received. Two email reminders are already recorded. Escalate to SMS reminder, escalate to printed post, or mark it will not be paid?" The controller picks the rung. The agent then runs it, and only that one. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via email Human decides Agent resumes with decision ## Agent Capabilities 72 actions ### Invoices 13 - **Create Invoice** Issues an invoice with its items and its client. Accepts a checksum of your own, which is what makes the write recoverable later. - **Update Invoice** Amends an invoice. The identifier travels in the body rather than the path, which the connector handles. - **Get Invoice** Reads one invoice with its items, client, payments, and totals. Also the read that returns the per invoice token the PDF route needs. - **Get Invoices Details** Reads several invoices in one call. The efficient way to refresh a known set rather than looping. - **List Invoices** Lists invoices filtered on type, status, client, tag, amount, and several date ranges. The read behind reporting and receivables sweeps. - **Delete Invoice** Removes an invoice. Reserved for documents that should never have existed. - **Delete Invoice Items** Removes one or more lines from an invoice, for corrections that do not warrant a new document. - **Add Invoice Related Item** Links an invoice to another invoice or to an expense, which is how a credit note, an advance, or a pass through cost stays tied to its counterpart. - **Delete Invoice Related Item** Removes a link between an invoice and another document. - **Set Invoice Language** Sets the language the invoice renders in, so an export customer receives the document in their own. - **Get Invoice PDF** Downloads the invoice as a PDF into FlowRunner file storage. It needs the invoice's own token as well as its identifier, so it follows a read. - **Get Invoice Receipt** Reads the cash register receipt issued against an invoice. - **Get Response By Checksum** Returns the original response to an earlier write that carried this checksum. The operation that lets an interrupted flow ask what happened instead of writing twice. ### Payments and Collections 8 - **Pay Invoice** Records a payment, settling the invoice in full when no amount is given. The step a bank feed match ends in. - **Delete Invoice Payment** Removes a recorded payment and puts the invoice back to unpaid. Used when a match turns out to be wrong. - **Send Invoice By Email** Emails the invoice using the account's own subject and body templates unless the flow overrides them. The free rung of the dunning ladder. - **Mark Invoice As Sent By Email** Records that the invoice was emailed from somewhere else and sends nothing. Keeps the history honest when delivery happens outside the platform. - **Send Invoice By Post** Has SuperFaktura print and physically mail the invoice, consuming postage credit. There is no draft and no recall, which is why it sits behind the review gate above. - **Mark Invoice As Sent** Marks the invoice sent without sending anything, for deliveries made by hand or by another channel. - **Mark Invoice Will Not Be Paid** Takes an invoice out of dunning and receivables without deleting it. A write off decision rather than a housekeeping one. - **Send SMS Reminder** Sends a payment reminder by SMS. Charged per message, delivered immediately to a real phone, with no draft state. ### Clients and Contact People 8 - **Create Client** Adds a client to the address book with their identifiers and billing details. - **Update Client** Amends a client record. Used for enrichment passes and for correcting tax identifiers before the next document. - **Get Client** Reads one client. - **List Clients** Lists clients with search, paging, and the platform's own filters. The matching step that stops a repeat buyer becoming a second record. - **Delete Client** Removes a client from the address book. A client carrying documents cannot be removed, which is the platform protecting your history. - **Add Contact Person** Adds a named contact to a client, so invoices and reminders reach the person who handles them. - **List Contact People** Lists a client's contacts. - **Delete Contact Person** Removes a contact from a client. ### Expenses 12 - **Create Expense** Records a supplier invoice against the books, with its items and its supplier. - **Update Expense** Amends an expense. As with invoices, the identifier travels in the body. - **Get Expense** Reads one expense with its items and payments. - **List Expenses** Lists expenses with search, paging, and date filters. The read behind payables reporting. - **Delete Expense** Removes an expense. - **Delete Expense Items** Removes one or more lines from an expense. - **Pay Expense** Records a payment against an expense, settling it in full when no amount is given. - **Delete Expense Payment** Removes a recorded payment and puts the expense back to unpaid. - **Download Expense Attachment** Pulls a file attached to an expense into FlowRunner file storage, which is how the original supplier document reaches an archive or an accountant. - **Add Expense Related Item** Links an expense to another expense or to an invoice. - **Delete Expense Related Item** Removes a link between an expense and another document. - **List Expense Categories** Lists the categories an expense can be filed under, which drive the expense reports. ### Stock 7 - **Create Stock Item** Adds a stock item that invoice lines can then draw their name, price, and movement from. - **Update Stock Item** Amends a stock item, typically for price and description changes fed from a product catalog. - **Get Stock Item** Reads one stock item with its current quantity. - **List Stock Items** Lists stock items with their quantities. The read a reorder check starts from. - **Delete Stock Item** Removes a stock item. - **Add Stock Movement** Records a movement in or out of stock without raising a document. How a count correction or a goods receipt is posted. - **List Stock Movements** Reads an item's movement history, which is how a disputed quantity is reconciled rather than argued about. ### Bank Accounts and Cash Registers 11 - **Create Bank Account** Adds a bank account to the profile, which invoices can then print as the account to pay into. - **Update Bank Account** Amends a bank account on the profile. - **List Bank Accounts** Lists the accounts on the profile. - **Delete Bank Account** Removes a bank account from the profile. - **List Bank Account Movements** Lists the movements the platform has imported on your accounts. This is what its own payment matching reads, and what an agent reconciles against. - **List Cash Registers** Lists the cash registers with their current balances. - **Get Cash Register** Reads one cash register. - **Create Cash Register Item** Records a movement in or out of a cash register, optionally against an invoice or an expense. - **List Cash Register Items** Lists a cash register's movements. - **Delete Cash Register Item** Removes a movement from a cash register. - **Get Cash Register Receipt** Reads the receipt for a cash register movement. ### Tags 4 - **Create Tag** Adds a tag that invoices, expenses, and clients can carry. - **Update Tag** Renames a tag everywhere it is used. - **List Tags** Lists the tags on the account, so a flow segments on real labels rather than inventing its own. - **Delete Tag** Removes a tag and strips it from every document it was on. ### Exports, Account, and Reference Data 9 - **Create Export** Starts an export job for a set of documents. It answers a job identifier rather than a file. - **Get Export Status** Reads how far an export job has got. The poll that precedes the download. - **Download Export** Fetches a finished export into FlowRunner file storage, ready for the accountant or the archive. - **List Accounts** Lists the companies this login can act for, whose identifiers the connection's Company ID setting takes. - **Get Companies Data** Reads the company details behind the login, optionally across every company it reaches. - **Get Activity Log** Reads an invoice or expense's activity log, recording when it was viewed, sent, downloaded, and paid. The evidence a collections decision is built on. - **List Countries** Lists the countries the platform knows, whose identifiers every address takes. - **List Sequences** Lists the numbering sequences grouped by document type, which decide what number a document gets. - **List Logos** Lists the logos on the profile, whose identifiers an invoice takes. ## Frequently Asked Questions ### What can FlowRunner do with SuperFaktura? FlowRunner agents can run Create Invoice, Update Invoice, and Get Invoice in SuperFaktura, plus 69 more actions. ### Does connecting SuperFaktura to FlowRunner require OAuth? SuperFaktura uses a custom authentication method to connect to FlowRunner. ### Can SuperFaktura trigger a FlowRunner workflow automatically? SuperFaktura doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at SuperFaktura?** This integration exposes SuperFaktura to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/superfaktura. Site index: https://flowrunner.ai/llms.txt