Accounting Available
SnelStart
SnelStart is the bookkeeping and schakl. is the CRM, and it stays that way. Clients, invoices and articles go there; who has paid comes back.
What goes out
Your clients become relations, your issued invoices become sales bookings with the rendered PDF attached, and your products become articles. A line books to the ledger account its VAT rate points at, with a default account for the rest; which VAT kind that is we look up in your own administration's rate table, because the low rate was 6% until 2019 and 9% after, and a 2018 invoice still has to book as low.
- A draft never travels: it has no number yet and is nobody's agreement
- What you filled in inside SnelStart (memo, credit limit, direct-debit mandate) stays
- An empty field in schakl. erases nothing in SnelStart: not filled in is not an instruction to clear
- An article code your administration refuses is reported up front, not halfway through
Never the same invoice twice
A duplicate invoice at a client is not a slip, it is an incident, so there are four locks on it. We remember what we sent. If we do not, we ask by invoice number. If SnelStart refuses the number because it already exists, that is not a failure but an answer: we look the booking up and adopt it. And if we get no answer at all (a timeout), we check whether the booking is there before sending anything again.
- A booking that was already there is adopted, not overwritten
- If its amount disagrees with your invoice, that is on the screen instead of being quietly corrected
- Syncing a second time writes nothing: unchanged is the normal answer
Who has paid
The bank statement is matched inside SnelStart, so SnelStart is the only place that knows an invoice was paid. We read that back, and in schakl. it becomes an ordinary payment on the invoice: the status flips to paid, reminders stop, and the client portal is right again. A partial payment counts too, because somebody who paid half is not somebody who paid.
- Only money *in* is booked: reversing a payment is a person's decision
- Every night on its own, or whenever you press the button yourself
- If something fails overnight, whoever administers the connection hears about it straight away
Permissions
Grant these to the role that manages this integration (Settings → Roles). Admin-only by default, and never to the client role.
-
snelstart.settings.manageConnect the administration, replace the key, choose the default ledger account and remove the connection. -
snelstart.sync.runRead the administration: fetch reference data, review relations and pull payments back. Nothing changes inside SnelStart. -
snelstart.ledger.writeWrite into the books. Pushing invoices additionally requires the right to edit invoices.
What it deliberately does not do
- Quotes do not travel; sales invoices and credit notes do.
- The one-click connect is waiting on certification by SnelStart: today you paste a connection key from SnelStart Web.
- One connection is one administration. If you run several, you connect them separately.
- Hours, projects and subscriptions do not travel as such: what goes across is the invoice that comes out of them.
- Peppol and e-invoicing networks are separate from this.
Where to find it Instellingen → SnelStart (Settings → SnelStart). Each client's state also shows on their own page.
Read the guide
