Fakturoid

Fakturoid is Czech online invoicing. Agents manage subjects, issue invoices across six document kinds, log expenses, track inventory with stock moves, and run invoice templates on recurring schedules.

1 trigger 61 actions OAuth available

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

An order closes in the storefront and reaches the agent

Agent reads the buyer, the lines, and the currency from the order

Search Subjects resolves the customer on your own Custom ID rather than on a name

Get Account reports the price basis the invoice will total under

Create Invoice issues the document, assigns its number, and emails nobody

The billing owner receives the issued document with its totals and the price basis named

The billing owner approves, and Send Invoice puts it in front of the customer

What This Integration Enables

Fakturoid is built for Czech small businesses and freelancers who bill often and bill small, and it is unusually honest about what an issued document is. Once an invoice has gone out there is no edit path. The correction is a Correction document, linked to the original in both directions, and your customer receives it as a second piece of paper with an explanation attached. That is the right behavior for a tax document, and it changes what an agent should be allowed to do unattended.

FlowRunner agents work the whole cycle around that constraint. They keep subjects in step with a CRM matched on your own Custom ID, issue invoices across six document kinds, record payments and produce tax documents from advance payments, push supplier scans into the OCR inbox and pick up the draft expense afterwards, maintain an inventory catalog with stock moves, and run recurring schedules. The realtime trigger covers the account's documented event range, so a paid invoice or an overdue one starts a flow rather than waiting for a poll. Deliveries carry no signature, so agents re-read the record with Get Invoice before acting on anything that matters. The judgment that stays with a person is the one Fakturoid itself refuses to take back, and FlowRunner's human-in-the-loop design is what puts it there with the evidence already assembled.

Without FlowRunner

Invoices built by retyping Order details are copied into the invoice by hand, one document at a time

Payment news arrives late Nobody knows an invoice was paid until someone opens the account and looks

Supplier paper piles up Scanned supplier invoices wait for a person to read them into expenses

With FlowRunner

Invoices assembled from the order The document is drafted from the source record with the customer matched on your own identifier

Payment moves a flow The event feed starts the next step the moment an invoice is paid or falls overdue

Supplier paper triaged on arrival Scans go to the OCR inbox and come back as draft expenses ready for review

Use Case Scenarios

From order to issued invoice, with the loop closed

An order closes in Shopify or a payment lands in Stripe. The agent resolves the buyer with Search Subjects on your own Custom ID, creating the subject if it is genuinely new, and builds the invoice lines. Where a line refers to stock it pulls the inventory item in by SKU, so your system never has to store Fakturoid's identifiers. Due In Days is set from the subject's own terms rather than a computed due date, because the due date is derived and read only. Create Invoice issues the document. Later, when the invoice is paid, the trigger fires and the agent posts the confirmation into the deal record in Pipedrive and appends the movement to a sheet in Google Sheets. Nothing about payment status has to be polled.
Supplier scans become draft expenses

Supplier PDFs arriving in a shared mailbox go straight to Create Inbox File, and Send Inbox File To OCR asks Fakturoid to read them. The agent waits for the OCR event rather than polling, then reviews what came back: the supplier, the amounts, the dates. Where the parsed supplier matches an existing record and the totals reconcile against a purchase order, Create Expense files it. Where the OCR is uncertain, or the supplier is new, or the amount sits outside the range that supplier has ever billed, the agent files nothing and posts the scan with its parsed fields to the bookkeeper in Slack. List Inbox Files is the standing view of what is still waiting.
Chasing, and the point where chasing stops

An invoice becomes overdue simply because the date passed. No write happens, which is worth knowing because a flow watching for record updates will never see it. The agent works from the event feed instead. On the first overdue event it drafts a chase whose tone matches how long the customer has been late, sends it through Gmail, and logs the attempt. It escalates on a schedule. What it never does on its own is Fire Invoice Action with Cancel or Mark As Uncollectible, because both change the document's legal standing and both are the finance owner's call. The agent brings the history, the contact record, and the outstanding balance, and someone decides whether this debt is still a debt.

Human-in-Loop Highlight

Send Invoice is the moment a number becomes somebody else's problem. Before it, an invoice can be updated or deleted and the world does not know. After it, the only correction is a Correction document that the customer receives, reads, and has to reconcile against the first one. The specific failure worth stopping for is quiet: vat_price_mode decides whether the line prices you sent are read as excluding or including VAT, there is no error either way, and the document simply totals differently. An order feed that changes its price basis produces an invoice that is well formed and wrong by exactly the VAT rate. So the billing agent issues the document and stops. It posts: "Invoice 2026-0912 for Novak s.r.o., 3 lines, total 48,400 CZK. The account default reads line prices as excluding VAT, and the source order supplied gross prices. Under the account default this invoice bills 9,400 CZK more than the order. Send as issued, or correct the basis first?" A person answers before anything leaves Fakturoid, which is cheaper than a Correction document and a phone call.

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

61 actions

Account

Get Current User Returns the connected user and every account they can reach, with the slug and permission held on each. The one route that needs no account slug, and the way a flow finds its own configuration.
Get Account Reads the account's settings, including the default price basis that decides how invoice line prices are totaled.
List Account Users Lists the people with access to the account. Used to resolve the right approver before a decision is routed.
List Bank Accounts Lists the bank accounts configured on the account, which is what an invoice's payment details reference.
List Number Formats Lists the numbering formats available. A format can only be set when a document is created, never on update.

Subjects

List Subjects Lists customers and suppliers, with Since and Updated Since filters for keeping another system in step.
Search Subjects Finds subjects by query. The matching step that keeps a CRM sync from creating a second copy of an existing customer.
Get Subject Retrieves one subject with its defaults, including the payment terms a new invoice inherits.
Create Subject Creates a customer or supplier. Carrying your own Custom ID here is what lets later flows match without storing Fakturoid's identifiers.
Update Subject Updates a subject. Turning off the delivery address flag clears the stored delivery address rather than merely hiding it.
Delete Subject Removes a subject record.

Invoices

List Invoices Lists invoices with status and date filters, paged at a fixed size. The Updated Since filter is the cheap way to read only what moved.
Search Invoices Finds invoices by query. Used to locate the document behind a customer's question or a bank reference.
Get Invoice Retrieves one invoice with its lines and payment state. The read that follows every unsigned webhook delivery.
Create Invoice Issues an invoice and assigns its number. It emails nobody, which is usually right and occasionally a surprise.
Update Invoice Updates an invoice that has not gone out. There is no edit path for a document already delivered.
Delete Invoice Deletes an invoice. Available while the document is still yours alone.
Fire Invoice Action Applies one of the document's defined actions, including Mark As Sent, Cancel, and Mark As Uncollectible. Two of those change the invoice's legal standing, so the connector refuses any value outside the defined set rather than passing it through.
Send Invoice Emails the invoice from Fakturoid using the account's templates. Turning off the default replacement makes the address, subject, and message all required, and the connector checks that before calling rather than letting the request be rejected.
Download Invoice PDF Fetches the invoice PDF into FlowRunner file storage. A PDF still being generated returns no content, and the connector raises a clear error rather than storing an empty file.

Invoice Payments

Create Invoice Payment Records a payment against an invoice. The step a bank feed or a payment provider drives.
Create Tax Document From Payment Produces a tax document from a payment on a proforma. The Czech document kind that a plain payment record does not cover.
Delete Invoice Payment Removes a recorded payment, reopening the invoice it settled.

Expenses

List Expenses Lists supplier invoices and other costs, filterable by date and status.
Search Expenses Finds an expense by query. Used to check whether a supplier document has already been filed.
Get Expense Retrieves one expense with its lines and payment state.
Create Expense Files a supplier document as an expense. The write at the end of an OCR triage flow.
Update Expense Corrects an expense that has already been filed.
Delete Expense Removes an expense record.
Fire Expense Action Applies one of the expense's defined actions, in the same constrained way as the invoice equivalent.
Create Expense Payment Records a payment made against a supplier document.
Delete Expense Payment Removes a recorded supplier payment.

Inventory

List Inventory Items Lists the stock catalog with quantities. The read behind a low stock watch.
Search Inventory Items Finds an item by query or SKU.
Create Inventory Item Adds an item to the catalog. Setting a SKU is what lets invoice lines reference stock without knowing Fakturoid's identifiers.
Update Inventory Item Updates an item. Changing quantity here sets the level directly, with no movement recorded.
Archive Inventory Item Archives an item so it stops appearing in normal listings.
Unarchive Inventory Item Returns an archived item to active use.
Delete Inventory Item Permanently removes an item from the catalog.
List Inventory Moves Lists stock movements. The history that sizes a reorder properly.
Create Inventory Move Records a stock movement, which is the audited way to change a quantity.

Generators and Recurring Schedules

List Generators Lists invoice templates.
Create Generator Creates an invoice template to issue from repeatedly.
Delete Generator Removes a template.
List Recurring Generators Lists the templates bound to a recurring schedule.
Create Recurring Generator Puts a template on a schedule so Fakturoid issues and sends on its own.
Pause Recurring Generator Suspends a schedule without deleting it.
Activate Recurring Generator Resumes a schedule from its own next occurrence date, so a long pause can produce an invoice immediately.
Delete Recurring Generator Removes a recurring schedule.

OCR Inbox

List Inbox Files Lists files waiting in the inbox. The standing view of supplier paper not yet turned into expenses.
Create Inbox File Uploads a supplier document to the inbox.
Send Inbox File To OCR Asks Fakturoid to read the file, which is what produces the draft an agent then reviews.
Download Inbox File Fetches an inbox file into FlowRunner file storage.
Delete Inbox File Removes a file from the inbox.

Activity and To-Dos

List Events Lists account activity since a point in time. The polling alternative to the trigger, and the basis of a month-end sweep.
List Todos Lists the account's to-do items.
Toggle Todo Completion Flips a to-do's completion state. It is a toggle rather than a setter, so a flow that needs a specific outcome reads the current state first.

Webhooks

List Webhooks Lists the webhooks registered on the account.
Create Webhook Registers a webhook against an endpoint of your choosing. Separate from the trigger below, which manages its own subscription.
Delete Webhook Removes a registered webhook.
List Failed Webhook Deliveries Lists deliveries that did not succeed. Where to look when a flow stops firing but the subscription still exists.

Triggers

1 triggers

Event Triggers

On Fakturoid Event Fires on the account's documented events across invoices, expenses, generators, recurring schedules, the OCR inbox, inventory, and subjects. FlowRunner registers the subscription when the trigger is switched on and removes it when it is switched off. Webhooks require a paid Fakturoid plan with webhook management enabled, and deliveries carry no signature, so a flow acting on anything consequential re-reads the record with Get Invoice or Get Expense first.

Frequently Asked Questions

What can FlowRunner do with Fakturoid?

FlowRunner agents can run Get Current User, Get Account, and List Account Users in Fakturoid, plus 58 more actions.

Does connecting Fakturoid to FlowRunner require OAuth?

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

Can Fakturoid trigger a FlowRunner workflow automatically?

Yes. Fakturoid supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Fakturoid

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us