--- title: "SnelStart Integration" description: "SnelStart is the Dutch bookkeeping platform. Agents manage relations and articles, read price agreements, create sales orders and quotations, read sales invoices, and post to the sales, purchase, bank, cash, and journal ledgers." url: https://flowrunner.ai/integrations/snelstart date_modified: 2026-09-04T14:53:04-07:00 --- # SnelStart [Accounting](https://flowrunner.ai/integrations/category/finance-accounting) SnelStart is the Dutch bookkeeping platform. Agents manage relations and articles, read price agreements, create sales orders and quotations, read sales invoices, and post to the sales, purchase, bank, cash, and journal ledgers. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 96 actions · Custom auth · available [SnelStart website](https://b2bapi.snelstart.nl/) · [Platform Documentation](https://developer.snelstart.nl/) · Capability data verified 2026-08-24 1. A supplier invoice arrives as a UBL e-invoice or as a scanned PDF 2. Upload Purchase Invoice UBL turns the e-invoice into a purchase entry, or Create Purchase Entry From Attachment starts the job that reads the scan 3. Get Attachment Entry Status follows the background job until it answers with an entry rather than a job id 4. Get Purchase Entry reads the result and the agent confirms the VAT lines sit on purchase accounts rather than sales ones 5. Create Bank Entry settles the entry through its purchase settlement lines once the payment clears 6. The agent posts the coded entry and its settlement to the finance channel with the original document attached 7. The bookkeeper rules on the VAT return position before any return is recorded as filed ## What This Integration Enables SnelStart draws an unusual line for a bookkeeping platform: the API writes the ledger but does not issue the invoice. Sales invoices are read-only here, produced by invoicing an order inside SnelStart itself, while the sales, purchase, bank, cash, and journal entries underneath them are fully writable. That tells you what to automate. The document that a customer sees stays where the business already produces it, and the bookkeeping around it, which is where the repetitive work actually lives, becomes an agent's job. Two behaviors govern every write. There are no partial update routes, so a PUT replaces: sending an order without its lines empties the order, and sending a relation without its address clears the address. The pattern that works is to read the record, change what is needed, and send the whole thing back. And bank and cash entries carry four separate line collections, where ledger lines post to an account and settlement lines pay off an existing sales or purchase entry. A statement line put in the wrong collection books the money and leaves the invoice open, which looks like a reconciliation problem weeks later rather than an error today. FlowRunner agents are built around both facts: read first, write completely, and settle where the settlement belongs. ### Without FlowRunner **Supplier invoices typed in**: Every bill is read by a person and re-entered line by line, including the VAT split **Settlements posted to the wrong collection**: A statement line books the money but leaves the invoice showing unpaid, and the difference is found later **Updates that quietly erase**: An update sent without its lines empties the document, and nobody notices until the order is picked ### With FlowRunner **Invoices read by the platform**: UBL files and scans become purchase entries through SnelStart's own routes, with the job followed to completion **Settlements matched to entries**: Payments land in the settlement collections that actually close the invoice they belong to **Updates built from the current record**: The agent reads the entry, applies the change, and sends the whole record back, because every update is a replacement ## Use Case Scenarios ### Supplier invoices captured without retyping E-invoices arrive as UBL and everything else arrives as a PDF. The agent routes each accordingly: Upload Purchase Invoice UBL for the structured ones, and Create Purchase Entry From Attachment for the scans, which starts a background job and answers a job id rather than an entry. Get Attachment Entry Status polls until the entry exists, and Get Purchase Entry reads what SnelStart actually produced. The agent then checks the coding rather than trusting it, because the sales and purchase VAT bands are different accounts and a reversed one posts to the wrong side of the return. The original file is attached with Upload Document so the evidence sits on the entry. ### Orders that move stage without being rewritten Orders arrive from a storefront on [Shopify](https://flowrunner.ai/integrations/shopify) or [WooCommerce](https://flowrunner.ai/integrations/woocommerce). The agent creates them with Create Sales Order, then advances them with Update Sales Order Process Status rather than Update Sales Order, because the status route is the narrow exception that moves an order to the next stage without touching anything else. Article prices come from List Article Price Agreements and List Action Prices, so a customer's negotiated price and a running promotion are both read rather than assumed. When a quotation is involved, Create Quotation carries the same lines and the same care about replacement semantics. ### Bank statements settled against the right entries Statement files land as CAMT.053, CAMT.052, or MT940. Upload Bank Statement Files delivers them, and for lines the agent can match confidently it calls Create Bank Entry with the settlement collections filled: sales settlement lines against sales entries, purchase settlement lines against purchase entries, ledger lines only for what genuinely belongs on an account. Payments captured through [Mollie](https://flowrunner.ai/integrations/mollie) are matched the same way. Anything the agent cannot match with confidence is listed in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and raised in [Slack](https://flowrunner.ai/integrations/slack) rather than posted to a suspense account, because a wrong settlement is harder to find than an unmatched line. ## Human-in-Loop Highlight Mark VAT Declaration Filed Externally does not file anything. It records inside SnelStart that a return was submitted somewhere else, and nothing reaches the tax authority as a result of the call. What makes it the sharpest gate in this connector is the side effect the vendor names: setting it makes SnelStart stop reminding you about that return. The system's own safety net is exactly what the operation switches off, and the connector offers no inverse. There is no unmark action anywhere in this action list, so an agent that stamps a return as filed on a bad assumption has removed the last automated signal that would have surfaced the omission, and the next thing that raises it is likely to be a penalty notice. So this operation never fires on inference. The agent does everything up to it: it reads List VAT Declarations, pulls the return with Get VAT Declaration and its sections and amounts, reconciles those against Get Column Balance and Get Period Balance for the same period, and presents the comparison. The bookkeeper says whether the return was genuinely filed and where. Only then does the agent record it. Everything else in the VAT area is read only anyway, which is the vendor telling you the same thing in a different way: the numbers are the platform's, and the declaration is a person's. 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 96 actions ### Connection and Company 4 - **Echo** Sends a string through the gateway and back, which confirms that both the client key and the subscription key are accepted. - **Get Company Info** Reads the details of the administration the client key belongs to, including its identifier, name, and address. - **Update Company Info** Updates the administration's settings. Only the foreign VAT invoicing setting is currently applied, and every other field is accepted and ignored. - **Check User Access** Checks whether a user has access to the administration the client key belongs to. ### Relations 10 - **List Relations** Lists the customers and suppliers, with full filtering, sorting, and paging. - **Get Relation** Reads a single relation. The read a flow runs before any update, because updates replace. - **Create Relation** Creates a customer or supplier in the administration. - **Update Relation** Updates a relation. It replaces rather than patches, so the record is read first and sent back with the change applied. - **Delete Relation** Deletes a relation. One with documents against it cannot be removed, and marking it inactive is the alternative. - **Get Relation Custom Fields** Reads the custom field values of a relation, which are read only on the relation record itself. - **Update Relation Custom Fields** Updates the custom field values of a relation, in the customer collection, the supplier collection, or both. - **List Relation Direct Debit Mandates** Lists the standing SEPA direct debit mandates of a relation, whose ids sales orders and sales entries take. - **List Relation Purchase Entries** Lists the purchase entries booked against a relation, which is what that supplier has invoiced you. - **List Relation Sales Entries** Lists the sales entries booked against a relation, which is what you have invoiced that customer. ### Articles and Pricing 12 - **List Articles** Lists the articles, optionally priced for one customer at one quantity, with full filtering. - **Get Article** Reads a single article, optionally priced for one customer at one quantity. - **Create Article** Creates an article, optionally under stock control. - **Update Article** Updates an article. It replaces rather than patches, so the record is read first. - **Delete Article** Deletes an article. One used on existing documents cannot be removed, and marking it inactive is the alternative. - **Get Article Custom Fields** Reads the custom field values of an article. - **Update Article Custom Fields** Updates the custom field values of an article. - **List Article Price Agreements** Lists the price agreements per article and customer, which is what decides a customer's price for an article. - **List Price Agreements** Lists the price agreements for one article. The filter must name the article, which the vendor requires. - **List Action Prices** Lists the promotional prices, which override an article's normal price for a period. - **List Revenue Groups** Lists the article revenue groups, which tie an article to the ledger account its sales post to. - **Get Revenue Group** Reads a single article revenue group. ### Sales Orders and Quotations 13 - **List Sales Orders** Lists the sales orders, with full filtering, sorting, and paging. - **Get Sales Order** Reads a single sales order with its lines. - **Create Sales Order** Creates a sales order with its lines, at any process stage the API allows. - **Update Sales Order** Updates a sales order. It replaces rather than patches, and omitting the lines empties the order. - **Delete Sales Order** Deletes a sales order. - **Update Sales Order Process Status** Moves a sales order to another document stage without touching the rest of the order. The narrow exception to replacement semantics, and the safe way to advance a quote to a confirmation. - **List Sales Order Templates** Lists the sales order templates, which decide an order's layout, numbering, and available extra fields. - **Get Sales Order Template** Reads a single sales order template, including the extra fields it defines. - **List Quotations** Lists the quotations, with full filtering, sorting, and paging. - **Get Quotation** Reads a single quotation with its lines. - **Create Quotation** Creates a quotation with its lines. - **Update Quotation** Updates a quotation. It replaces rather than patches, and omitting the lines empties it. - **Delete Quotation** Deletes a quotation. ### Sales Invoices 3 - **List Sales Invoices** Lists the sales invoices. Invoices are read only here, because they are produced by invoicing an order inside SnelStart. - **Get Sales Invoice** Reads a single sales invoice. - **Get Sales Invoice UBL** Reads a sales invoice as UBL, which is the machine-readable e-invoice form rather than a PDF. ### Sales and Purchase Entries 12 - **Create Sales Entry** Creates a sales entry, which books an outgoing invoice into the ledger. Line amounts are net and the VAT goes in its own collection. - **Get Sales Entry** Reads a single sales entry with its lines and VAT. - **Update Sales Entry** Updates a sales entry. It replaces rather than patches, so the entry is read first and sent back with the change applied. - **Delete Sales Entry** Deletes a sales entry from the ledger. - **Create Purchase Entry** Creates a purchase entry, which books a supplier invoice into the ledger. Line amounts are net and the VAT goes in its own collection. - **Get Purchase Entry** Reads a single purchase entry with its lines and VAT. - **Update Purchase Entry** Updates a purchase entry. It replaces rather than patches. - **Delete Purchase Entry** Deletes a purchase entry from the ledger. - **Create Purchase Entry From Attachment** Starts a background job that reads a scanned supplier receipt and builds a purchase entry from it. It answers a job id rather than an entry, so a flow follows it rather than assuming. - **Get Attachment Entry Status** Reads the status of the background job building a purchase entry from a scanned receipt. - **Upload Purchase Invoice UBL** Turns a supplier's UBL e-invoice into a purchase entry, optionally with the PDF alongside it. The structured path, where no reading is needed at all. - **List Purchase Invoices** Lists the purchase invoices, with full filtering. ### Bank and Cash 11 - **Create Bank Entry** Creates a bank entry, posting to ledger accounts, settling existing sales or purchase entries, or both. Which collection a line goes in decides whether an invoice actually closes. - **List Bank Entries** Lists the bank entries, with full filtering. - **Get Bank Entry** Reads a single bank entry with all four of its line collections. - **Update Bank Entry** Updates a bank entry. It replaces rather than patches. - **Delete Bank Entry** Deletes a bank entry from the ledger. - **Upload Bank Statement Files** Uploads one or more bank statement files in CAMT.053, CAMT.052, or structured MT940 format. - **Create Cash Entry** Creates a cash entry, posting to ledger accounts, settling existing sales or purchase entries, or both. - **List Cash Entries** Lists the cash entries, with full filtering. - **Get Cash Entry** Reads a single cash entry with all four of its line collections. - **Update Cash Entry** Updates a cash entry. It replaces rather than patches. - **Delete Cash Entry** Deletes a cash entry from the ledger. ### Journal Entries 4 - **Create Journal Entry** Creates a journal entry, which is the free-form memorial booking used for corrections, accruals, and anything the other journals do not cover. - **Get Journal Entry** Reads a single journal entry with its lines. - **Update Journal Entry** Updates a journal entry. It replaces rather than patches. - **Delete Journal Entry** Deletes a journal entry from the ledger. ### Ledger 6 - **List Ledger Accounts** Lists the general ledger accounts, with full filtering. - **Get Ledger Account** Reads a single general ledger account, including which VAT kinds it accepts. The check that stops a line landing on an account that will not take it. - **Create Ledger Account** Creates a general ledger account, with the ledger function that decides what the account is used for. - **List Ledger Mutations** Lists the individual ledger movements. The vendor caps this at the first 500 rows, so a flow filters the range down rather than paging blindly. - **Get Ledger Mutation** Reads a single ledger movement. - **List Journals** Lists the journals, which are the daybooks that bank, cash, and memorial entries are filed in. ### Cost Centers 5 - **List Cost Centers** Lists the cost centers of the administration. - **Get Cost Center** Reads a single cost center. - **Create Cost Center** Creates a cost center. - **Update Cost Center** Updates a cost center. It replaces rather than patches. - **Delete Cost Center** Deletes a cost center. One with bookings against it cannot be removed, and marking it inactive is the alternative. ### VAT 7 - **List VAT Rates** Lists the VAT rates configured in the administration. - **List Vat Rates** Lists the VAT rates from the newer rates resource, with full filtering. Two rate resources exist, and this is the current one. - **Get Vat Rate** Reads a single VAT rate from the newer rates resource. - **List Vat Rate Definitions** Lists the VAT rate definitions, which describe the rates a rate code can resolve to over time. - **List VAT Declarations** Lists the VAT returns of the administration, with full filtering. - **Get VAT Declaration** Reads a single VAT return with its sections and amounts. The evidence a person reviews before anything is recorded as filed. - **Mark VAT Declaration Filed Externally** Records that a return was filed outside SnelStart. Nothing is submitted to the tax authority by this call, and it stops SnelStart reminding you about that return, which is why this page holds it behind a person. ### Reference 2 - **List Countries** Lists the countries SnelStart knows, whose ids every address takes. - **Get Country** Reads a single country. ### Documents 5 - **Upload Document** Uploads a document and attaches it to a purchase entry, a sales entry, or a relation, so the evidence sits with the booking. - **List Documents** Lists the documents attached to one purchase entry, sales entry, or relation. - **Get Document** Reads a single document, including its content. - **Update Document** Replaces the content or name of a document. - **Delete Document** Deletes a document from the record it was attached to. ### Reports 2 - **Get Column Balance** Reads the column balance over a period, which is every ledger account with its opening balance, movements, and closing balance. - **Get Period Balance** Reads the period balance over a range, which breaks the ledger down by period. ## Frequently Asked Questions ### What can FlowRunner do with SnelStart? FlowRunner agents can run Echo, Get Company Info, and Update Company Info in SnelStart, plus 93 more actions. ### Does connecting SnelStart to FlowRunner require OAuth? SnelStart uses a custom authentication method to connect to FlowRunner. ### Can SnelStart trigger a FlowRunner workflow automatically? SnelStart doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at SnelStart?** This integration exposes SnelStart 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/snelstart. Site index: https://flowrunner.ai/llms.txt