We watch what's missing — so you don't have to.
Most EDI failures aren't error messages. They're silences: the 997 that never came back, the ASN that never shipped, the order that never reached your ERP. Comparatio detects the absence of expected data and opens the ticket before you notice.
- No configuration required
- Included in every deployment
- 24/7, both directions
- 73%
- of our support tickets are opened by our own monitoring
- 9,859
- VAN-outage tickets detected and resolved automatically
- ~20,000
- support tickets handled per year
- 30 days
- advance warning on certificate expiry
The problem
Broken EDI is loud. Missing EDI is silent.
Every EDI platform reacts to errors. Almost none notice absence — and absence is what costs you: unacknowledged POs, unshipped orders, invoices that never match, stock that never syncs.
What silence looks like
- You sent an 850. No 997 ever came back — and nobody noticed until the customer called about a late order.
- A vendor confirmed the order, then never sent the ASN. The receiving dock found out when the truck didn’t.
- A PO arrived via EDI but never imported into your ERP. It aged quietly for a week.
- An AS2 certificate expired on a Saturday. Monday’s transactions bounced.
What Monitoratio does about it
- Tracks every outbound 850, 856, and 810 until its 997 arrives — with escalating alert frequency the longer it’s missing.
- Expects the 856 within one day of a confirmation and the 855 within three days of an order, and alerts when they don’t show.
- Cross-checks EDI against your ERP, so an order that never imported is a ticket — not a surprise.
- Flags certificates 30 days out and manages the renewal.
Missing-data detection
Nine kinds of silence we listen for
Each detector runs continuously against your live transaction flows and your ERP — not just the EDI mailbox.
Missing 997 acknowledgements
Every outbound 850, 856, and 810 is tracked until acknowledged. Alerts escalate with quadratic backoff the longer the 997 stays missing.
Missing 855 confirmations
A vendor that hasn’t confirmed your order within three days triggers an alert — before the delay becomes a stockout.
Missing 856 ASNs
Confirmed but not shipped? If the ASN hasn’t arrived within a day of the confirmation, you hear about it.
ASN / invoice cross-check
Bidirectional matching between 856s and 810s, down to line counts — catching mismatches that surface as chargebacks months later.
Missing orders in your ERP
POs received via EDI are verified against your ERP. An order that never imported becomes a ticket, not a mystery.
Delayed inventory imports
Inventory feeds that stall past 36 hours are flagged before stale stock levels reach your trading partners.
Trading-partner changes
Deactivation or deletion of a trading partner triggers an immediate alert — no silent drop-offs.
Connection & VAN outages
SFTP, AS2, and VAN connections are checked around the clock — 9,859 VAN-outage tickets were opened and resolved by this detector alone.
Certificate expiry
AS2 certificates are watched continuously, alerted 30 days before expiry, and renewed managed — weekend expirations included.
How it works
Detection to resolution, without you in the loop
- 1
Detect
24/7 monitoring of connections and content: VAN outages, SFTP and AS2 failures, certificate problems, and every missing-data pattern above.
- 2
Escalate
Two tiers, by severity. Routine issues route to operations; critical errors — access violations, syntax errors, connection failures — go straight to senior engineers.
- 3
Resolve
Engineers you know by name fix the issue and the ticket closes — often before your team knew there was one. That’s how 73% of our tickets run.
FAQ
Proactive monitoring, in practice
What does Comparatio actually monitor?
Every transaction flow, in both directions: missing 997 acknowledgements on outbound 850s, 856s, and 810s; missing 855 vendor confirmations (3-day threshold); missing 856 ASNs (1 day after confirmation); ASN-to-invoice mismatches down to the line level; POs received via EDI that never arrived in your ERP; inventory imports delayed past 36 hours; trading-partner deactivations; and AS2 certificates within 30 days of expiry.
What happens when Monitoratio detects a problem?
A ticket is opened automatically and routed by severity: routine errors go to our operations team, while critical errors — access violations, syntax errors, connection failures — escalate directly to senior engineers. 73% of our support tickets start this way, before the customer has noticed anything.
Do I need to configure any of this?
No. Missing-data detection, connection monitoring, and certificate tracking are part of every Comparatio deployment. Thresholds like the 3-day confirmation window are tuned to your trading partners during onboarding.
How is this different from the monitoring my VAN provides?
A VAN can tell you a connection dropped. Monitoratio tells you a document that should have arrived never did — which no connection check can see. When Loren Data’s VAN had outages, our monitoring auto-detected and resolved 9,859 resulting tickets.
Find out what your EDI isn't telling you.
See Monitoratio against your own transaction flows — including the silences your current setup can't hear.