How the accounting sync behaves

Sync runs on a schedule, not instantly. A change made in either system appears in the other on the next run, so a few minutes of disagreement is normal and not a fault. Most connections also allow a manual sync when you need something across immediately.

Some records are read-only in the CRM on purpose. Skrivebeskyttet (betalt/annulleret) A posted or paid invoice belongs to the accounting system, and letting it be edited here would mean the two disagree about something that has legal and tax consequences. Where an action has to finish on the accounting side, DealJourney says so — Fakturakladde oprettet i Fiken, afventer bekræftelse — rather than pretending it completed.

Failures are recorded rather than announced. A sync that cannot map a customer or is rejected by the accounting system logs the problem and moves on. This is deliberate — one bad record should not stop the rest — but it means nobody finds out unless somebody looks. Check the sync activity log after any change to the setup, and periodically otherwise.

Duplicates come from matching on names. If the same customer exists on both sides having been created independently, the sync only recognises them as one another if it can match on something stable. Fixing the match rule stops new duplicates; the existing ones need merging.

A missing customer usually failed validation. Accounting systems demand fields a CRM does not — a registration number, a country, a payment term — and a customer without them is rejected rather than created. The log names which field.