Questions, answered.
How BookSyncer keeps your data safe, what it books where, and how it handles the tricky parts.
Security & data
How much access does BookSyncer have to my Stripe account? +
Read-only. You connect through Stripe Connect, which grants BookSyncer permission to read your invoices, charges, refunds and payouts — and nothing that can move money or change your Stripe settings. A single platform webhook receives your events, so there is no webhook to configure and no secret to paste.
How are my e-conomic credentials stored? +
You authorize BookSyncer through e-conomic's official app grant flow, which returns an agreement grant token. We encrypt that token at rest and use it together with our own app secret for every API call. We never see or store your e-conomic username or password.
Where is my data hosted? +
In the EU. Application data lives in EU-hosted infrastructure (Cloudflare and a Supabase Postgres database in the eu-west-1 region), encrypted at rest. See our Privacy Policy and DPA for the full picture.
What gets booked where
What exactly does BookSyncer post to e-conomic? +
When a Stripe invoice is finalized, BookSyncer ensures the customer exists and creates the matching invoice. When it is paid, BookSyncer books the invoice, books a customer payment voucher against your debtor (accounts receivable) account, and books finance vouchers for the Stripe fee and any FX difference. Refunds create and book a credit note. Payouts are booked as a journal entry from your Stripe clearing account to your bank account.
Which accounts does it use? +
You choose them during setup, from dropdowns pulled live from your e-conomic agreement: the journal for Stripe entries, the debtor account, the Stripe clearing/balance account, the fee account, FX gain/loss accounts, and the bank account for payouts. You can also set customer group, payment terms, invoice layout and product mappings.
Can I see what it did for each Stripe event? +
Yes. Every event has a drill-down view showing the original Stripe payload and the ordered list of actions BookSyncer took in e-conomic — each with its request, response and a deep link to the resulting invoice or voucher. Failed events show the error and a retry button.
VAT & reverse charge
How does BookSyncer handle VAT? +
It resolves a VAT zone for each customer from their country and VAT number: zone 1 is your home country (standard VAT), zone 2 is the EU with a valid VAT number (reverse charge, 0%), and zone 3 is outside the EU (no EU VAT). The matching e-conomic VAT codes are applied automatically. Zones and codes are configurable per pipeline, with overrides where you need them.
Do you validate EU VAT numbers? +
Yes. EU VAT numbers are validated so that cross-border B2B invoices carry the correct reverse-charge treatment. If a number is missing or invalid, BookSyncer treats the sale as standard-rated rather than silently applying reverse charge.
Control & behavior
Can I keep invoices as drafts instead of auto-booking? +
Yes. Auto-book is the default — that is the "it just works" promise — but you can switch any pipeline to draft-only, so BookSyncer creates the invoices and vouchers and leaves the final booking to you. It is a single toggle you can change any time.
What about refunds and payouts? +
Full refunds are handled end to end: BookSyncer creates and books a credit note against the original invoice. Payouts from Stripe to your bank are booked as a journal entry from your Stripe clearing account to your bank account, so your Stripe balance always reconciles.
Does it handle historical invoices? +
Yes. You can choose a start date and BookSyncer will sync invoices from that point forward, so you can bring your books up to date without going all the way back to the beginning of your Stripe history.
What happens if a sync fails? +
Failed events are retried automatically with backoff. If they still fail, they are marked clearly in the app with the error message, and you can retry them manually once the cause is fixed. Nothing is silently dropped.