Once it is clear which workflow eats time, the technical work begins. This category is about connecting systems and replacing repetitive manual work: interfaces via APIs, webhooks and file exchange, middleware as a broker between systems that cannot talk to each other directly, and approval and notification flows. A particular focus lies on what quotations usually leave out: error handling, retries without duplicate postings, logging and monitoring. An interface is not a one-off project but a component that needs maintenance in day-to-day operation — articles in this category cover both.
Since October 2025, banks check name and IBAN before every credit transfer. How supplier master data, payment blocks and call-backs handle the bank's responses.
How a stage of completion becomes an interim invoice, why a variation is a case with a deadline of its own, and how that produces a final account that can be checked without rework.
How rest periods, working time limits, qualification and availability are calculated as rules while the roster is built - and how plan and actual finally come together.
Matching order, goods receipt and invoice by machine: which fields are compared, where the tolerance band sits, who owns the exception and what stays manual.
A shared mailbox starts deadlines nobody ordered. How incoming messages become cases with an owner, a deadline and a filing location, and what the law expects.
Where the days between an enquiry and a sent quote really go, how templates and system prices shorten drafting, and how following up becomes a planned routine.
From the circulation folder to a digital approval: responsibility, deputies, deadlines, reminders, dual control, value limits and a sound audit trail.
Monitoring interfaces beyond availability: business-level checks, thresholds without false alarms, escalation to a named owner and logs with defined retention.
Why an unprotected retry creates a second invoice and how idempotency prevents it: operation key, check before writing, log of keys, finding old cases.
Detecting, reporting and bridging silent interface failures: heartbeat, time windows, volume reconciliation, queueing and a defined restart procedure at work.
Daily file transfers between two systems: six typical failure modes from delimiters to duplicate deliveries, and how to check, log and report every one of them.
Middleware brokers between systems that cannot talk to each other directly. When a direct connection is enough and when the extra layer starts to pay off.
Poll on a schedule or get notified? What each approach costs in daily operation, what a receiver must provide and when polling remains the safer choice.
Request and response, data formats, credentials, permissions, limits and versions: how interfaces work and how to check whether a system can be connected.
When does an interface pay off and when is manual work cheaper? A decision framework based on volume, frequency and error rate, plus the interim steps.
Frequency times time saved against implementation plus ongoing maintenance: the full calculation behind an automation, and an honest threshold, not a promise.