e-conomic sync
Stop keying the same customer into two systems
A two-way connection between CloudDialer and e-conomic that keeps customers, suppliers, invoices and credit notes in agreement — with you deciding which side leads and who wins a disagreement.
Two-way, not one-way
The customer your seller edits is the customer your bookkeeping sees
Most integrations push one direction and leave the other side to drift. CloudDialer syncs customers, suppliers, invoices and credit notes both ways, so a phone number a seller fixed during a call and a payment term your bookkeeper changed in e-conomic both land where the other needs them. No re-typing, no second source of truth.
- Customers and suppliers flow up and down, with contacts kept attached
- Invoices pull back booked, with their numbers, so the CRM knows what's been billed
- Credit notes sync alongside invoices, so refunds aren't a blind spot
- Edits made locally after a sync are protected — a stale pull won't clobber them
You hold the controls
Direction and conflict rules, set per entity
Not every record should behave the same. You decide, for each entity, whether CloudDialer reads from e-conomic, writes to it, or both — and what happens when both sides changed. Products, accounts, journal entries and purchases read from e-conomic first, so your chart of accounts and catalogue stay exactly as your accountant set them.
- Four conflict strategies: e-conomic wins, local wins, newer wins, or read-only
- Pull, push and auto-sync toggled independently for each entity
- Products, accounts, entries and purchases default to read-first
- A sync interval and lookback you set, not one we impose
What the connection actually covers
How it runs
From connect to converged
Connect
Add your e-conomic app and grant tokens. CloudDialer tests the connection and, if you want, runs a first sync on connect.
Choose the shape
Set direction and a conflict strategy per entity. Leave write-back off while you watch it read, then enable the pieces you trust.
Let it converge
On your interval, records sync both ways. Local edits made since the last sync are kept; the rest reconciles.
Tie it to your process
Use the Rules engine to create an e-conomic draft when an order is paid — a step you configure, never an automatic posting.
The honest version
Does it auto-post my invoices to e-conomic?
No. This is a sync, not an autopilot. Write-back is off by default, and even when you turn it on, creating a draft invoice from a paid order is a rule you configure — you decide when it runs, and the booking happens in e-conomic on your terms.
Will a sync overwrite something my team just edited?
No. If a record was changed locally after the last sync, CloudDialer protects that edit rather than pulling stale data over it, then re-converges on the next pass.
Can I keep my chart of accounts and product catalogue exactly as they are?
Yes. Accounts, journal entries, products and purchases are read-first by default, so e-conomic stays the source for those and CloudDialer mirrors them.
What happens when both sides changed the same record?
You pick the rule per entity: e-conomic wins, local wins, the newer edit wins, or keep it read-only. There's no hidden default deciding for you.
See your accounting and your sellers agree
Connect e-conomic, leave write-back off, and watch it read. Turn on the pieces you trust, one entity at a time.