Writing is where integrations usually go wrong, so this level is built around that risk. Field ownership decides which system wins when both change the same value. Deliveries are idempotent, so a retry can never create a second order. Outbound messages queue when the target is down and resume by themselves. Business rules and approvals run before anything is written, and every write is stored with the receipt the target system gave back.
As on every level, the interface is monitored, each sync is protocolled, and you can inspect, retry or hold traffic yourself. The agreed sync is a contractual obligation, and a critical interface puts our whole team on it immediately.
Key features
Read and Write in One Interface
Master data comes in, transactions go out — one interface, one mapping, one protocol, instead of two half-integrations that drift apart within a year.
Write-Back with Confirmation
Nothing counts as delivered until the target system confirms it. The receipt — document number, booking id, timestamp — is stored against your record.
Field Ownership & Conflict Rules
Decide per field which system is the master, so a change on both sides resolves by a rule you agreed rather than by whichever job happened to run last.
Retry-Safe by Design
Every message carries an identity the target system recognises, so a retry after a timeout updates the existing record instead of creating a duplicate order.
Queue, Backpressure & Resume
If the other system is down or in maintenance, outbound traffic queues in order and resumes by itself — your people keep working while the queue drains.
Business Rules Before Sending
Validations, approvals and completeness checks run before a write leaves the building, so the ERP receives only what it is allowed to accept.
Sandbox & Dry Run
Test against the test system, replay a real day without writing, and see exactly what would have been sent before anything touches production.
End-to-End Traceability
One correlation id follows a record from the source, through the transformation, into the target and back — so 'where did this number come from' has an answer.
Monitored, Protocolled, Self-Serviceable
Continuous monitoring, a full record of every run in both directions, and the controls to retry, hold or release traffic yourself without opening a ticket.
Contractual Sync Obligation
The agreed frequency and availability are owed, not promised. Interfaces marked critical escalate to a high-priority, all-hands response from us.
What holds for every module.
You never pay for these separately.
Your private cloud in Zurich
Customer data is stored and processed in Zurich. Keys and secrets are kept in a key vault in Zurich.
Encrypted
Your data is encrypted at rest (AES-256) and in transit (TLS).
Certified infrastructure
On ISO/IEC 27001 and SOC 2/3 certified infrastructure · revFADP · GDPR.
AI that does not train on your data
AI in your processes is Google Gemini via Vertex AI, processed in Zurich, contractually without training on your data.
Your source code
The source code is yours by contract. Cancel any time. Free offboarding within 10 working days, up to four handover meetings and 12 months of e-mail support.