Custom Snelstart integration development
Appfront builds custom Snelstart integrations that connect your administration with webshops, CRM systems, your own back-office applications and industry-specific software. Through the official Snelstart B2B API, we synchronise sales bookings, purchase bookings, relations, items and general ledger entries — automatically, reliably and without duplicate entry.
What is a Snelstart integration?
A Snelstart integration automatically connects your Snelstart accounting software with other systems in your organisation. Via Snelstart's B2B API, systems exchange customer and supplier records, sales and purchase entries, items and general ledger data, either at fixed intervals or triggered by events in the source system.
Snelstart is mainly used 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 begin every integration with a short analysis of your accounting package and source system, so we know which endpoints are actually available.
Automatically forwarding sales and purchase bookings
Orders from your webshop or ERP are created as sales bookings 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 relations and items in sync
Customers and suppliers stay automatically aligned between your CRM and Snelstart. Items and prices can be updated from your product catalogue or PIM system, so the administration is always accurate.
Control over the general ledger and cost centres
Booked transactions are automatically assigned to the correct general ledger account and cost centre, with automatic validation. This prevents rework with your accountant and speeds up your monthly and year-end close.
How we build your Snelstart integration
An accounting integration rarely fails on technology, almost always on assumptions: which entry belongs in which journal, which customer record should be looked up or created, how we handle credit notes and returns. That is why, in the first two phases, we explicitly invest time in working out these business rules.
Intake & scope
We take stock of your Snelstart package, the source system, the data volume and the desired direction(s) of synchronisation. Outcome: a clear scope document with entities and decision rules.
Design & mapping
For each entity (relation, entry, product, general ledger) we define the field mapping, including handling of edge cases: missing VAT code, new customer, credit entry, multiple currencies.
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.
Go-live & management
After acceptance, we take the integration live in stages, with monitoring for API errors, unusual entries and synchronisation backlog. Afterwards, we provide maintenance and ongoing 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 processes.
Sales entries from webshop or ERP
Orders from Shopify, WooCommerce, Magento or your own webshop are automatically created as sales entries in Snelstart, including VAT codes, cost centres and posting to the correct journal.
Purchase entries from document flows
Purchase invoices from scanning and recognition tools or email inboxes are booked with general ledger allocation, supplier linking and automatic VAT validation.
Relation synchronisation with CRM
New customers in your CRM appear as relations in Snelstart; address or name-and-address changes flow through automatically. This prevents duplicate relation records and manual corrections.
Product and price flows
Products from your PIM or webshop 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 & inventory movements
For editions that support stock, we synchronise stock levels and movements between WMS or webshop and Snelstart, so that the warehouse and the accounts stay aligned.
For which businesses do we work with Snelstart?
Snelstart is popular with a broad group of Dutch businesses. In practice, we see four typical business types where a custom integration pays for itself the fastest.
Webshops and e-commerce
Online sellers processing dozens to hundreds of orders a day who don't want an employee manually creating sales entries for them. Typical benefit: hours saved each week and a clear administrative basis for the accountant.
Stock-driven SMEs
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 bookkeeping.
Wholesalers and importers
Businesses with their own stock or ERP system who want purchase and sales transactions, and creditor and debtor movements, to appear automatically in Snelstart — including correct cost centres and cost-price entries.
Accountancy and administration firms
Accountancy firms that want to streamline recurring processes for their clients (booking bank transactions, flagging outstanding debtors, month-end closing) and need integrations from their own portals or scanning tools.
Our technical approach
Snelstart's B2B API has characteristics that a robust integration must handle: short-lived access tokens, rate limits and no public webhooks. We build integrations that are designed to cope with these as standard.
We develop the integration layer on 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 worked through in a controlled way without overloading the API.
Monitoring is standard: every integration provides dashboards showing how many entries are processed per day, how many retries were needed and where any mapping errors occur.
Tech stack
Why choose Appfront for your Snelstart integration?
Building an accounting integration is not the same as calling an API. It requires understanding of administrative processes, of Dutch VAT rules and of how your accountant works. Appfront brings together that combination of administrative and technical experience.
- Experience with multiple Snelstart editions and administration setups
- Clear scope definition, with no loose ends afterwards
- A fixed price or a transparent hourly rate, your choice
- Monitoring and alerting included as standard
- Maintenance and further development with a dedicated point of contact
- Documentation for your accountant and your record of processing activities
Security and compliance
Snelstart holds financial data: debtors, creditors, general ledger and revenue. An integration between them must comply with Dutch privacy and security standards, including GDPR.
We store the B2B API credentials encrypted, using scoped key management. Data travels over TLS, logs are redacted of personal data, and the scope of each integration is documented for your record of processing activities. 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
- Data minimisation in line with GDPR
- A bespoke data processing agreement
- Phased rollout with a rollback scenario
Frequently asked questions about Snelstart integrations
A Snelstart integration is a technical connection that allows the Dutch accounting software Snelstart to automatically exchange data with another system via the B2B API. Commonly used entities include customers, 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: inventory management and cost centres, for example, are only available from certain editions. During intake, we establish whether your package supports the endpoints required.
The B2B API uses a subscription key in combination with a short-lived access token (valid for roughly one 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 work with a polling architecture at set intervals (for example every 5 or 15 minutes) using 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. Two-way scenarios, where relationships and items stay in sync across several systems, take a few months, including acceptance testing and a controlled rollout.
The investment depends on the number of systems, entities, direction of synchronisation and volume. We provide a clear quote after a no-obligation analysis in which we map out your bookkeeping setup and 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 will assess your Snelstart package, the source system and the data flows you need, and within a week we will provide a concrete approach and an indicative price.