Integrations with banking, payments and accounting

Banks, Mollie and Stripe, Exact Online and webshops. Built so that a repeated or interrupted run never books or mails anything twice.

What it is

An integration is only good if it also works on the day the other side is slow, returns an error or sends the same data twice. That is what I build for: a step that runs twice does the work once.

I integrate through REST APIs and OAuth, and stay within the other side's limits, so an integration does not get blocked at the busiest moment.

What I build

  1. 01

    Bank matching

    Transactions from bunq, Mollie, Stripe and myPOS are normalised and matched to invoices by an idempotent pipeline.

  2. 02

    Posting to the accounts

    Entries go to Exact Online without duplicate postings and within the limits of the API.

  3. 03

    Payments and subscriptions

    Per-user subscriptions through Mollie with pro-rata invoicing in Fyldd, and checkout through Mollie in the Riha webshop.

  4. 04

    Webshop and stock

    In the warehouse system I built the order sync from the webshop and the parts API.

  5. 05

    Mail that never goes twice

    The warehouse system's customer mail engine sets a claim first and only sends after that, so a customer never gets the same mail twice.

  6. 06

    Export to the accountant

    Fyldd delivers a closed period as CSV, PDF and UBL 2.1.

Two systems that need to talk to each other?

info@bitvire.com