--- title: "FreeFinance Integration" description: "FreeFinance, also sold as FinanzFenster, is Austrian online accounting and invoicing software. Agents manage customers, suppliers, and items, create and finalize invoices, record payments, and pull invoice PDFs and XML for each bookkeeping client." url: https://flowrunner.ai/integrations/free-finance date_modified: 2026-09-04T14:53:04-07:00 --- # FreeFinance [Accounting](https://flowrunner.ai/integrations/category/finance-accounting) FreeFinance, also sold as FinanzFenster, is Austrian online accounting and invoicing software. Agents manage customers, suppliers, and items, create and finalize invoices, record payments, and pull invoice PDFs and XML for each bookkeeping client. 53 actions · OAuth · available [FreeFinance website](https://www.freefinance.at/) · [Platform Documentation](https://freefinance-dev.github.io/) · Capability data verified 2026-08-24 1. The point of sale reaches its cut-off time and a scheduled close begins 2. List Receipts gathers the day's receipts for the register 3. Get Last Daily Closing reports where the previous close left the chain 4. The agent reconciles the receipt total against the takings recorded at the register 5. The register owner receives the reconciliation with any gap named 6. The agent confirms no sale is still open at the terminal 7. The register owner approves, and Close Cash Register Day seals the day ## What This Integration Enables FreeFinance is Austrian accounting and invoicing software, also sold as FinanzFenster, and its API is unusually opinionated because Austrian bookkeeping rules are built into it rather than layered on top. Two behaviors follow from that and they shape every flow. An invoice is a draft until it is finalized, and finalizing is what gives it a number in an unbroken sequence; after that the only correction is a cancellation that writes a reversal. A cash register receipt is stricter still, because it enters the register's tamper-evident chain the moment it is created, with no edit and no delete available at all. Software that lets an agent quietly fix things is comfortable right up until an auditor asks a question, and this platform simply does not offer that comfort. FlowRunner agents work with the grain of that design. They keep customers, suppliers, and the item catalog in step with the systems upstream, assemble invoice drafts from orders and finish them in one reviewed step, record payments with an explicit treatment for whatever the payment did not cover, produce invoice PDFs and electronic XML, and run the cash register cycle from receipt to daily close. Discovery is worth building in from the start: Get Client Features reports whether the cash register, dunning, and e-invoicing capabilities are switched on for this set of books, and Get Permissions reports what the technical user is actually allowed to do, both of which are cheaper to check than to discover through a failure. The decisions the platform will not let anyone take back are exactly where FlowRunner's [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) design puts a person. ### Without FlowRunner **Closing happens when someone gets to it**: The daily close waits on whoever is still in the building, and the reconciliation happens afterwards **Invoices finalized by hand, one at a time**: Each draft is opened, read, and finalized individually before it becomes a numbered document **Part payments left as judgment calls**: A short payment is either ignored or written off from memory, with no consistent treatment ### With FlowRunner **Closing arrives reconciled**: The day's receipts are totaled and matched against takings before anyone is asked to approve **Drafts arrive ready to finalize**: Documents are assembled and checked, and finalizing is a single reviewed decision **Part payments arrive classified**: The remainder is proposed with a reason attached, and the write-offs are escalated rather than assumed ## Use Case Scenarios ### Orders become finalized invoices, in one reviewed step An order closes in [Shopify](https://flowrunner.ai/integrations/shopify) and the agent builds the invoice. It resolves the customer with List Customers, creating the record and its address if the buyer is new, and prices the lines from the item catalog. One detail decides whether the totals are right: an item carries its own net or gross basis, and a document line carries its own too, so the same figure under the wrong one is wrong by the tax rate on every document that uses it. The agent reads the item before pricing rather than assuming. Create Invoice can finalize in the same call, and for routine orders inside a tolerance the finance team has set, it does. Anything outside that tolerance is created as a draft and posted for review, because a draft can be edited or deleted and a finalized invoice can only be reversed. ### Payments, and the part the payment did not cover Payments captured in [Stripe](https://flowrunner.ai/integrations/stripe) or arriving from the bank are matched against open invoices. Record Invoice Payment requires a decision about the remainder, which is the useful part: leave it outstanding, treat it as a discount the customer took, write off a rounding or currency difference, book a correction, or mark it uncollectible. The agent applies the first three automatically inside limits the controller sets, because those are arithmetic rather than judgment. It never applies the last one on its own. An uncollectible balance is money the business has decided not to chase, so the agent assembles the invoice, the payment history, and the customer's other open documents and posts them to the controller in [Slack](https://flowrunner.ai/integrations/slack). Cancel Invoice Payment exists for the cases where the match turns out to be wrong, and it requires a reason, which the agent supplies from the record rather than from a template. ### The daily close, prepared rather than performed A retail location closes at a fixed time. The agent runs the reconciliation before anyone is asked to do anything: List Receipts pulls the day's receipts for the register, Get Last Daily Closing reports where the previous close left the chain, and the totals are matched against the takings recorded at the terminal. A gap is named with the receipts that could explain it rather than reported as a number. The result appends to a running sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) so the pattern across locations is visible over a month. What the agent does not do is close the day, because that is the one act in this connector that cannot be walked back. ## Human-in-Loop Highlight Close Cash Register Day is final in a way that is easy to underestimate. There is no reopen, and once a day is closed no further receipt can be dated into it. That combination is what makes an early close expensive: a sale rung up after the agent decided the day was over has nowhere to go, and the receipt itself cannot be edited or deleted either, because an Austrian register receipt enters the tamper-evident chain the moment it is created and the only correction is a reversing receipt that stays in the chain beside it. A cash register is also the one part of the books where the record and the physical drawer are supposed to agree, and only a person standing at the terminal knows whether they do. So the agent prepares and stops. It posts: "Register Wien Zentrum, 148 receipts, 6,412.30 EUR. Terminal takings recorded as 6,437.30 EUR, a gap of 25.00 EUR. Two card sales at 17:52 are not yet settled. Closing now excludes anything rung after this point, and the day cannot be reopened. Close, or hold?" The register owner answers from the shop floor. The counting, the matching, and the explanation were the agent's work. Sealing the day was not. 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 53 actions ### Bookkeeping Clients 4 - **List Bookkeeping Clients** Lists the sets of books this connection can reach. The identifier this returns is in nearly every other path, which is why it is set once as configuration. - **Get Bookkeeping Client** Retrieves one set of books with its configuration. - **Get Client Features** Reports which capabilities are switched on for this client, including the cash register, dunning, and electronic invoicing. Worth calling before a flow discovers the answer by failing. - **Get Permissions** Reports what the technical user's role actually allows, which is a different question from what the API offers. ### Customers 8 - **List Customers** Lists customers for the current set of books. - **Get Customer** Retrieves one customer with their addresses and defaults. - **Create Customer** Creates a customer record. - **Update Customer** Updates a customer. - **Delete Customer** Removes a customer record. - **List Customer Addresses** Lists the addresses held against a customer. - **Create Customer Address** Adds an address to a customer. - **Set Default Customer Address** Marks which address new documents should use. ### Suppliers 5 - **List Suppliers** Lists suppliers for the current set of books. - **Get Supplier** Retrieves one supplier record. - **Create Supplier** Creates a supplier. - **Update Supplier** Updates a supplier. - **Delete Supplier** Removes a supplier record. ### Items 7 - **List Items** Lists the product and service catalog. - **Get Item** Retrieves one item, including whether its selling price is held net or gross. - **Create Item** Adds an item to the catalog with its price basis and tax class. - **Update Item** Updates an item. Changing the price basis changes every document that prices from it afterwards. - **Delete Item** Removes an item. - **List Item Categories** Lists the catalog's categories. - **Create Item Category** Creates a category. ### Invoices 12 - **List Invoices** Lists invoices with date and status filters. The polling read that stands in for a trigger, since this platform publishes no webhook registration. - **Get Invoice** Retrieves one invoice with its lines and payment state. - **Create Invoice** Creates an invoice, optionally finalizing it in the same call. Without that, the result is a draft with no legal number. - **Finalize Invoice** Assigns the number and makes the document final. After this the only correction is a cancellation that writes a reversal. - **Cancel Invoice** Writes a reversing document for a finalized invoice. The correction path, and irreversible in its own right. - **Delete Invoice** Deletes a draft. Not available once an invoice has been finalized. - **Record Invoice Payment** Records a payment and states what happens to the part it does not cover: left outstanding, taken as a discount, written off as a rounding or currency difference, booked as a correction, or marked uncollectible. - **List Invoice Payments** Lists the payments recorded against an invoice. - **Cancel Invoice Payment** Reverses a recorded payment and reopens the invoice. A reason is required. - **Download Invoice PDF** Fetches the rendered invoice into FlowRunner file storage. - **Download Invoice XML** Fetches the electronic invoice in the format chosen when the invoice was created. There is no XML unless a version was set at creation. - **Get Invoice Statistics** Returns a period summary. The lightweight alternative to walking the invoice list for a monthly figure. ### Cash Register 6 - **List Cash Registers** Lists the registers configured for this set of books. - **List Receipts** Lists receipts for a register and period. The read behind a daily reconciliation. - **Create Receipt** Records a cash register receipt. It enters the register's tamper-evident chain immediately, with no edit and no delete available afterwards. - **Cancel Receipt** Writes a reversing receipt. Both the original and the reversal stay in the chain. - **Get Last Daily Closing** Reports where the previous close left the register. The starting point of any reconciliation. - **Close Cash Register Day** Seals the day. It cannot be undone, and no further receipt can be dated into a closed day, which is why this page's human gate sits here. ### Documents 1 - **Upload Document** Files a document against the books, such as a supplier scan supporting an entry. ### Reference 10 - **List Accounts** Lists the ledger accounts for this set of books. - **List Payment Accounts** Lists the accounts a payment can post to. - **List Tax Rates** Lists the tax rates in use. - **List Tax Classes** Lists the tax classes a document line references. Read rather than assumed, because a line's tax reference has to exist. - **List Payment Terms** Lists the payment terms available to a document. - **List Document Sequence Groups** Lists the numbering sequences documents are assigned from. - **List Layout Setups** Lists the print layouts documents render through. - **List Dunning Levels** Lists the dunning stages configured for overdue documents. - **List Tags** Lists the tags records can be labeled with. - **Get Global Reference List** Returns the portal-wide lists of countries, currencies, languages, salutations, and units of measure in one call. These are not per set of books. ## Frequently Asked Questions ### What can FlowRunner do with FreeFinance? FlowRunner agents can run List Bookkeeping Clients, Get Bookkeeping Client, and Get Client Features in FreeFinance, plus 50 more actions. ### Does connecting FreeFinance to FlowRunner require OAuth? Yes. FreeFinance connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can FreeFinance trigger a FlowRunner workflow automatically? FreeFinance doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at FreeFinance?** This integration exposes FreeFinance 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/free-finance. Site index: https://flowrunner.ai/llms.txt