[SnelStart](https://www.snelstart.nl) is a Dutch accounting software. X-Sitter transfers your orders to your SnelStart administration as sales orders (*verkooporders*). The customers (*relaties*) and items (*artikelen*) of these orders are created in SnelStart as well, if they do not exist there yet.

The page **Accounting › SnelStart** (*Buchhaltung › SnelStart*) shows whether the connection works, how many records have been transferred and which transfers failed.

![Screenshot: SnelStart page, card "Status" with SnelStart active, country filter, webhook URL and the connection list with the buttons "Test Connection" and "Enable pairing"](/accounting/images/snelstart-status.png)

## Before you start

- Your user needs the permission **SnelStart** in the area **Accounting** (*Buchhaltung*) of the permissions tree. Ask your administrator.
- You need a SnelStart administration and access to the SnelStart B2B API: a **Subscription Key** from the SnelStart developer portal and – depending on the kind of coupling – a pairing key or the **AppShortName** from the registration email of SnelStart.
- X-Sitter support switches SnelStart on for your company and sets the **country filter**. Only orders whose delivery country is in the filter are transferred. As long as **SnelStart is active** (*SnelStart aktiv*) shows **no** (*nein*), nothing is transferred.
- The transfer runs as two jobs, **Bestellungen zu SnelStart senden** (send orders to SnelStart) and **Artikel zu SnelStart senden** (send items to SnelStart). You create them yourself under **Administration › Jobs & connections** (*Administration › Jobs & Verbindungen*) › **New job** (*Neuer Job*), group **SnelStart** – see [Jobs & connections](/administration/jobs-and-connections.md). Without the permission for jobs & connections, ask your administrator; sub-clients additionally need the release of their main client.

## Step by step

### 1. Create the SnelStart connection

1. Open **Administration › Jobs & connections** (*Administration › Jobs & Verbindungen*), click **Connections** (*Verbindungen*) and then **New connection** (*Neue Verbindung*) – see [Jobs & connections](/administration/jobs-and-connections.md).
2. Choose the type **SnelStart** and enter a **Comment** (*Bemerkung*), e.g. the name of your administration.
3. Enter the **Subscription Key** – the primary or secondary key from your profile in the SnelStart developer portal.
4. Depending on the kind of coupling:
   - **Maatwerk:** create a key in SnelStart Web under *Koppelingen › Maatwerk* and enter it as **Pairing Key (Client Key)** (*Kopplungsschlüssel (Client Key)*).
   - **Productie:** enter the **AppShortName** from the registration email of SnelStart and leave the pairing key empty – SnelStart fills it in step 2.
5. Click **Save** (*Speichern*).

![Screenshot: Connection form of the type SnelStart with Subscription Key, pairing key, AppShortName, user, password and API base URL](/accounting/images/snelstart-connection-form.png)

### 2. Pair the connection with SnelStart (Productie only)

1. Open **Accounting › SnelStart** (*Buchhaltung › SnelStart*).
2. Click **Enable pairing** (*Kopplung aktivieren*) in the row of the connection. The button only appears when an AppShortName is stored.
3. X-Sitter takes you to SnelStart Web. Confirm the coupling there.
4. SnelStart sends you back to X-Sitter. You see "The pairing has been confirmed in SnelStart. As soon as SnelStart has transmitted the key, the connection is active." (*Die Kopplung wurde in SnelStart bestätigt. …*)
5. SnelStart sends the pairing key to the **Webhook URL** shown on the page. Afterwards the column **Pairing Key** (*Kopplungsschlüssel*) shows a check mark and **Activated** (*Aktiviert*) shows the date.

### 3. Test the connection

Click **Test Connection** (*Verbindung testen*). X-Sitter sends a test request to SnelStart and reads the details of your administration. If it works, you see "Connection to "…" successful" (*Verbindung zu "…" erfolgreich*) and the column **Administration** shows the name of your SnelStart administration.

### 4. Watch the transfers

The card **Transfers** (*Übertragungen*) counts per kind of record – **Orders** (*Bestellungen*), **Customers** (*Kunden*), **Items** (*Artikel*) – how many have been **transferred** (*übertragen*), how many failed (**Error**, *Fehler*) and how many are still **pending** (*offen*). Below, you see the SnelStart jobs of your company with their state (**active** / **inactive**) and the time of the last run.

![Screenshot: Card "Transfers" with the counters for orders, customers and items and the list of SnelStart jobs](/accounting/images/snelstart-transfers.png)

### 5. Retry failed transfers

Failed transfers are listed under **Recent Errors** (*Letzte Fehler*) with type, key (order, customer or SKU), number of attempts, the error message of SnelStart and the time.

1. Fix the cause in SnelStart or in X-Sitter (see the error message).
2. Click **again** (*erneut*) in the row. You see "The entry will be resubmitted the next time the system runs." (*Der Eintrag wird beim nächsten Lauf erneut übertragen*) and the row disappears.
3. The next run of the job transfers the record again.

![Screenshot: Card "Recent Errors" with one failed item, its error message and the button "again"](/accounting/images/snelstart-errors.png)

## Fields and options

### Status

| Field | Meaning |
|---|---|
| **SnelStart is active** (*SnelStart aktiv*) | **yes** = the jobs transfer data. **no** = SnelStart is switched off for your company; contact X-Sitter support. |
| **Country Filter** (*Länderfilter*) | Delivery countries whose orders are transferred, e.g. Netherlands (NL). **All countries** (*alle Länder*) = no restriction. |
| **Webhook URL** (*Webhook-URL*) | Address to which SnelStart sends the pairing key. Give it to SnelStart in your API application. |

### Connection

| Field | Meaning | Required |
|---|---|---|
| **Subscription Key** | Primary or secondary key from the SnelStart developer portal (profile). | yes |
| **Pairing Key (Client Key)** (*Kopplungsschlüssel (Client Key)*) | Maatwerk: created by you in SnelStart Web under *Koppelingen › Maatwerk*. Productie: filled automatically via the webhook. | yes, unless user and password are used |
| **AppShortName** | From the registration email of SnelStart, part of the activation link. Only for the Productie coupling; without it the button **Enable pairing** is missing. | no |
| **SnelStart user (optional)** / **SnelStart password (optional)** (*SnelStart Benutzer* / *SnelStart Passwort*) | Login with user name and password, only if there is no pairing key. | no |
| **API Base URL** (*API Basis-URL*) | Address of the SnelStart API, `https://b2bapi.snelstart.nl/v2`. Leave it as it is. | no |

The column **Connection** (*Verbindung*) of the page marks the connection your company uses by default with **Default** (*Standard*). A job uses this connection unless another one is chosen in the job.

### What the jobs transfer

| Job | What it does |
|---|---|
| **Bestellungen zu SnelStart senden** (send orders to SnelStart) | Transfers orders of the last days (default 30) with the chosen order status (default `sent`) as sales orders. The customer is looked up in SnelStart by email address, customer number, name – or always created new. Unknown items are created or the order is marked with an error. Optionally the shipping costs are added as a line with their own item code. The SnelStart process status can be e.g. *Order* or *Factuur* (creates an invoice directly). Prices are transferred gross or net; after a number of failed attempts (default 5) the order is no longer retried. |
| **Artikel zu SnelStart senden** (send items to SnelStart) | Creates your items in SnelStart if they do not exist there yet (default 500 per run). Name and EAN come from the item attributes, the price from the last order line that sold the SKU. Items that already exist in SnelStart are only linked. |

You set these values in the job.

## Good to know / Troubleshooting

- Every transfer error can also be reported to you via Telegram (notification **SnelStart - error**, *SnelStart - Fehler*), see [Telegram notifications](/account/telegram-notifications.md).
- An order that has been transferred once is not transferred again. A failed record is retried with every run until the maximum number of attempts is reached; **again** resets the attempts.

| Message | Cause | Solution |
|---|---|---|
| *Es ist keine SnelStart-Verbindung hinterlegt. …* (no SnelStart connection has been configured) | Your company has no connection of the type SnelStart. | Create it as described in step 1. |
| "The subscription key and pairing key (or user data) must be stored" (*Subscription Key und Kopplungsschlüssel (oder Benutzerdaten) müssen hinterlegt sein*) | The connection is incomplete, e.g. the pairing has not been confirmed yet. | Complete the connection or finish the pairing (step 2). |
| "The Echo request to SnelStart failed" (*Die Echo-Anfrage an SnelStart ist fehlgeschlagen*) | SnelStart cannot be reached or rejects the keys. | Check the Subscription Key and the pairing key, then test again. |
| "This connection is not associated with your company" (*Diese Verbindung gehört nicht zu deiner Firma*) | **Enable pairing** was clicked for a connection another company has shared with yours. | Pair the connection in the company it belongs to. |
| A counter under **Error** grows | SnelStart rejected records, e.g. because a required field is missing. | Read the message under **Recent Errors**, fix the cause and click **again**. |
| **SnelStart is active: no** | SnelStart has not been switched on for your company. | Contact X-Sitter support. |
| No job is listed under **Jobs** | The SnelStart jobs have not been created yet. | Create them under **Administration › Jobs & connections** › **New job**, group **SnelStart** (the SnelStart page links there). |