INTEGRATIONSSNELSTARTSnelStart integration
A SnelStart integration ends the retyping of orders, customers and entries. Your revenue is in the books the same day, stock is right and your bookkeeper has less to correct. Below you'll read how integrating with SnelStart, the Dutch accounting package, works and what to check beforehand.
ISO 9001 & 27001
- Sales orders or sales entries goes back and forth with Your other systems
- Customers and suppliers goes back and forth with Your other systems
- Items and stock goes back and forth with Your other systems
- Purchase entries goes back and forth with Your other systems
Built for clients including Tata Steel, M&G Investments, Digistore24, Toppers in Concert, Bar-le-Duc and Loogman
This is the data organisations most often let flow between systems. Which of it matters to you depends on where work is getting stuck today.
Sales orders or sales entries
You can read in an order as a sales order, with items and quantities, or as a sales entry with only amounts, VAT and general ledger. You need orders if you keep stock and item history in SnelStart. Entries are simpler if it's only about revenue.
Customers and suppliers
Customers and suppliers, with address, VAT number and payment terms. A fixed customer number stops the same customer appearing three times in your list of debtors.
Items and stock
For trading companies, SnelStart is often where stock is accurate. An integration passes stock levels on to the online store or sales channel and sets up new items there.
Purchase entries
Supplier invoices, and costs from platforms and payment providers that belong on their own general ledger account as purchases.
Payments and open items
Which invoices have been paid and which are still open. Useful to report back to an online store, CRM or customer portal, so nobody has to look it up in SnelStart.
For each combination: which data moves back and forth, what the standard integration does and what to watch out for.
- Connect SnelStart to ShopifyConnect SnelStart to Shopify: choose between sales orders and entries, keep your stock in line and reconcile Shopify Payments payouts via a clearing account.
- Connect SnelStart to WooCommerceConnect SnelStart to WooCommerce: how business orders on account, stock and customer-specific prices flow between your online store and your accounting.
- Connect SnelStart to bolConnect SnelStart to bol: how to post bol orders, process the bol invoice with its commission, and upload invoices for business buyers per shipment.
Not always. If an existing integration for SnelStart does exactly what you need, we'll tell you.
SnelStart doesn't build integrations itself. Its integrations overview has a long list of integrations from software partners, for online stores, payment providers, tills, CRM, planning and industry software. You activate them with a connection key or from the partner's site.
For online stores there are variants: some create orders in SnelStart as sales orders, with extensions for stock and items; others post the sale as an entry including VAT, shipping costs and discounts. If the way you work fits one of those variants, a standard integration is usually the quickest route.
- Your own software, such as a customer portal, planning or quoting tool, needs to create orders or invoices in SnelStart.
- You sell through several channels that each use different item codes or pricing agreements.
- You want to combine SnelStart data with other sources, for example for alerts or reporting.
- A standard integration doesn't match your agreements with your bookkeeper, for example on general ledger accounts per channel.
The B2B API and the developer portal
SnelStart offers a B2B API with its own developer portal on Microsoft Azure API Management. There you'll find automatically generated documentation with code samples and an API console. A temporary account for the documentation is free; once you register your integration, you get a development key.
The connection key per administration
The customer creates a key (koppelsleutel) in SnelStart Web under Koppelingen (integrations) and pastes it into the other application. That key belongs to one online administration. For a custom integration you use the Maatwerk (custom) tile.
Custom or production integration
You build a custom integration for one customer, a production integration for multiple users. For both, you apply for certification after building; SnelStart then monitors the integration for about twelve days and issues a permanent key afterwards. Production integrations have extra requirements, such as OAuth and a webhook URL, and SnelStart is cautious about new applications.
Online administrations only
An API integration works entirely online, so only with an online administration. During the free trial you can't set up an integration yet; the subscription has to be confirmed first.
An integration moves data. In between, AI can read, sort and prepare a suggestion. Where it matters, a person decides.
Checking purchases against your order
For trading companies, AI can read a purchase invoice and compare it with the purchase order: are quantities, prices and discounts right? Differences come to you as a suggestion. You decide what gets posted.
Keeping an eye on debtors
Every day, AI summarises which customers are past their payment terms and prepares a draft reminder. You send it or call yourself.
Holding back orders that don't add up
An order with a foreign VAT number, an unknown item or an unusual address doesn't go through automatically, but goes onto a review list with an explanation why.
The wrong package
According to the SnelStart Kennisplein, the Maatwerk tile is available in the inZicht and inControle packages. If you want a custom integration on a smaller package, check beforehand whether you need to upgrade.
A restored backup
If you restore a restore point or backup and keep working in it, it needs a new connection key. The integration then has to be reactivated, or it stops without anyone noticing.
Mixing orders and entries
Decide beforehand whether a channel creates sales orders or sales entries. Switching halfway through the year makes your stock and revenue reporting hard to compare.
Forgetting certification in the planning
You only get a permanent key after certification, and that period takes about twelve days. Plan that time in before you want to go live.
What goes where
Which data moves, in which direction, and which system wins when two values differ. That is written down before anything gets built. For this integration, that means: Sales orders or sales entries, Customers and suppliers, Items and stock, Purchase entries, Payments and open items.
Fields and rules
For every field, how it translates between the systems: statuses, VAT codes, general ledger accounts, item numbers. And what happens with a duplicate or a missing value. For this integration, that means: The B2B API and the developer portal, The connection key per administration, Custom or production integration, Online administrations only.
Testing with real cases
In a sandbox or test administration, with the exceptions you actually run into: credit notes, partial deliveries, changed customer details.
Live, with logging and monitoring
Every sync is logged, and when something fails, someone gets an alert. If a vendor changes its API, we update the integration.
No account manager. You talk to someone who builds integrations themselves, and who will tell you when a standard integration is enough.
- Office on the Duivendrechtsekade in Amsterdam
- ISO 9001 and ISO 27001, certified by Kiwa
- 500 projects delivered
- 4.8 from 127 reviews
Does SnelStart have an API?
Yes, SnelStart has a B2B API for online administrations. The documentation is in the developer portal, where you can also test calls in an API console with a temporary account. For a permanent integration you need a certified custom or production key.
What is a connection key in SnelStart?
A connection key (koppelsleutel) is a unique key that belongs to one online administration. You create it in SnelStart Web under Koppelingen and paste it into the application you're connecting. That gives the application access to the administration.
What is the difference between a custom integration and a production integration?
A custom integration is made for one specific customer, who keeps it under their own management. A production integration is meant for multiple end users and has to meet extra conditions, such as using OAuth. Both get a permanent key after certification.
Does the API also work with an administration that isn't online?
No. An API integration works entirely online and can only be used with an online administration. If you still work with a local administration, you first move to an online administration before you can integrate through the API.
Can I set up an integration during the trial period?
No. According to SnelStart, you can't create an integration during the free trial. Confirm your subscription first; then you set up the integration.
Which SnelStart package do I need for a custom integration?
For a custom integration you use the Maatwerk tile, which according to the SnelStart Kennisplein is available in inZicht and inControle. Partner integrations often work with smaller packages too; which ones exactly is listed per integration in the overview.
- Connect Exact Online to your other systemsCloud accounting and ERP software from the Dutch company Exact, widely used by SMEs and their accountants.
- Business Central integrationMicrosoft's ERP for growing and mid-sized organisations: finance, purchasing, sales, stock and projects in one system.
- Moneybird integrationDutch online accounting package for business owners, freelancers and online stores, with invoicing, purchases, banking and VAT returns in one place.
- Twinfield integrationOnline accounting software from Wolters Kluwer, widely used by accounting firms and organisations with several administrations.
Sources
The technical facts on this page come from the vendors' official documentation, checked on 19 September 2026. Vendors change their APIs and limits; when we build an integration, we always check the current state.