Dutch accounting B2B API & access tokens Entries, contacts & products

Custom Snelstart integration development

Appfront builds custom Snelstart integrations that connect your accounting to web shops, CRM systems, custom back-office applications and industry-specific software. Via the official Snelstart B2B API, we synchronise sales entries, purchase entries, contacts, products and general ledger transactions, automatically, reliably and without double entry.

What is a Snelstart integration?

A Snelstart integration automatically connects your Snelstart accounting to other systems in your organisation. Via the Snelstart B2B API, systems exchange contacts, sales and purchase entries, products and general ledger data, at fixed intervals or triggered by events in the source system.

Snelstart is used mainly by SMEs and accountants in the Netherlands, with packages such as inStap, inKaart, inBalans, inZicht and inHuis. Each package has its own scope of functionality, and therefore its own API capabilities. At Appfront, we start every integration with a short analysis of your accounting package and your source system, so we know which endpoints are actually available.

Automatically posting sales and purchase entries

Orders from your web shop or ERP are created as sales entries in Snelstart, with the correct general ledger account, VAT code and cost centre. Purchase invoices can be booked from document flows or email inboxes.

Keeping contacts and products in sync

Customers and suppliers stay automatically aligned between your CRM and Snelstart. Products and prices can be updated from your product catalogue or PIM system, so your accounts are always correct.

Control over the general ledger and cost centres

Booked entries are assigned straight to the right general ledger account and cost centre, with automatic validation. This prevents rework for your accountant and speeds up your month-end and year-end close.

How we build your Snelstart integration

An integration with an accounting system rarely fails on technology — almost always on assumptions: which entry belongs in which journal, which relation needs to be looked up or created, how do we handle credit notes and returns. That's why, in the first two phases, we explicitly spend time working out these decision rules.

1

Intake & scope

We map out your Snelstart package, the source system, the data volume and the desired direction(s) of synchronisation. The result: a sharp scope document with entities and decision rules.

2

Design & mapping

For each entity (relation, entry, product, ledger) we define the field mapping, including how to handle edge cases: a missing VAT code, a new customer, a credit entry, multiple currencies.

3

Build & testing

We build the integration layer with encrypted credential storage, automatic token refresh, rate-limit handling and retries. In parallel, we run it in a test administration to validate the mapping.

4

Go-live and management

After acceptance, we take the integration live in phases, with monitoring for API errors, deviating entries and synchronisation backlog. Afterwards, we provide maintenance and further development.

What can a Snelstart integration do for you?

Snelstart's B2B API covers the most important administrative processes. Appfront translates those capabilities into concrete integrations that automate your specific process.

Sales entries from your web shop or ERP

Orders from Shopify, WooCommerce, Magento or your own web shop are automatically created as sales entries in Snelstart, including VAT codes, cost centres and the link to the correct journal.

Purchase entries from document flows

Purchase invoices from scan-and-recognise solutions or email inboxes are booked with ledger allocation, supplier linking and automatic VAT validation.

Relation synchronisation with your CRM

New customers in your CRM appear as a relation in Snelstart; address or contact detail changes flow through automatically. This prevents duplicate relation records and manual corrections.

Product and price flows

Products from your PIM or web shop are updated in Snelstart, with the correct VAT code and product group. Price changes stay in sync without manual work.

Subscriptions and recurring invoicing

For SaaS providers and membership organisations, we build subscription integrations that create sales entries monthly or periodically based on contract rules in your source system.

Stock & product movements

For editions that support stock, we synchronise stock levels and movements between your WMS or web shop and Snelstart, so your warehouse and accounts stay aligned.

Which companies do we work with on Snelstart?

Snelstart is popular with a wide range of Dutch businesses. In practice, we see four typical types of business where a custom integration pays for itself fastest.

Webshops and e-commerce

Online sellers who process dozens to hundreds of orders a day and don't want an employee creating sales entries for them by hand. Typical gain: saving hours every week and a clear administrative basis for the accountant.

Service providers with project administration

Agencies, consultancies and technical service providers who manage hours, expenses and projects in their own system, and want to generate invoices per project in Snelstart without double entry.

Wholesalers and importers

Companies with their own stock or ERP system who want to see purchase and sales transactions, creditor and debtor movements in Snelstart automatically — including the right cost centres and cost price entries.

Accountancy and bookkeeping firms

Firms that want to streamline recurring processes for their clients (booking bank transactions, flagging debtors, month-end close) and need integrations from their own portals or scan-and-recognise tools to do so.

Our technical approach

Snelstart's B2B API has characteristics that an integration needs to handle robustly: short-lived access tokens, rate limits and no public webhooks. We build integrations that are resilient to all of these by default.

We develop the integration layer in modern back-end stacks (Node.js, Python, Laravel or .NET) with encrypted credential storage, automatic token refresh and idempotent write operations. For the polling architecture we use modification-date filters and job queues, so any backlog is cleared in a controlled way without overloading the API.

Monitoring is standard: every integration comes with dashboards showing how many bookings are processed per day, how many retries were needed and where any mapping errors occur.

Tech stack

Snelstart B2B API OAuth-style tokens Node.js / Python Laravel / .NET PostgreSQL / MySQL Job queues (BullMQ, Sidekiq) Polling + event triggers Sentry / Datadog monitoring

Why choose Appfront for your Snelstart integration?

Building an accounting integration is not the same as calling an API. It requires an understanding of administrative processes, of Dutch VAT rules and of how your accountant works. Appfront brings that combination of administrative and technical experience.

  • Experience with multiple Snelstart editions and administration set-ups
  • Tightly defined scope, no loose ends afterwards
  • Fully fixed price or transparent hourly rate: you choose
  • Monitoring and alerting included as standard
  • Maintenance and further development with a dedicated contact person
  • Documentation for your accountant and processing register

Security and compliance

Snelstart contains financial data: accounts receivable, accounts payable, general ledger, revenue. An integration between systems must meet Dutch privacy and security standards.

We store the B2B API credentials encrypted, using scoped key management. Data is transferred over TLS, logs are redacted for personal data and the scope of each integration is documented for your processing register. With every delivery you receive a technical description, including data flows and retention periods.

  • Encrypted storage of API credentials
  • TLS for all data connections
  • Audit logging for write actions in Snelstart
  • Scope minimisation in line with GDPR
  • Custom data processing agreement
  • Phased rollout with a rollback scenario

Frequently asked questions about Snelstart integrations

A Snelstart integration is a technical integration that lets the Dutch accounting software Snelstart automatically exchange data with another system via the B2B API. Commonly used entities are relations, sales and purchase entries, items, general ledger accounts and cost centres.

The B2B API is available for the cloud editions (inStap, inKaart, inBalans, inZicht, inHuis). Which functionality is accessible depends on the package; stock management and cost centres, for example, are only available from certain editions. During the intake we determine whether your package supports the required endpoints.

The B2B API uses a subscription key combined with a short-lived access token (valid for roughly an hour). Our integrations refresh tokens automatically in the background, so your integration keeps running 24/7 without manual intervention.

No, the public B2B API does not offer webhooks. We therefore use a polling architecture at set intervals (for example every 5 or 15 minutes) via modification-date filters. For near-real-time scenarios we combine this with event triggers in the source system.

A simple one-way integration is usually production-ready within a few weeks. Bidirectional scenarios in which relations and products are kept in sync across multiple systems take a few months, including acceptance testing and a controlled rollout.

The investment depends on the number of systems, entities, synchronisation direction and volume. We provide a clear quote after a no-obligation analysis in which we map out your administration set-up and the source system.

Yes. API credentials are stored encrypted, data is encrypted in transit, and we minimise the scope of the data exchanged. All data flows are documented for your record of processing activities.

Ready to integrate your Snelstart?

Book a no-obligation consultation. We'll review your Snelstart package, the source system and the data flows you need — and deliver a concrete approach and indicative price within a week.

If you also need bank data and other accounting packages in your software through a single API, read more about our Bizcuit integration.

If you use Compenda for your contacts and projects and want it to work with your website or planning too, take a look at our Compenda integration.

Edit content