Getting full, defensible proof that every EDI document reaches its destination is one of the toughest operational challenges in modern B2B environments. When you run multiple VAN providers, or migrate between them, finance, IT, and EDI teams need an auditable way to confirm no document was lost, delayed, or acknowledged incorrectly. Dual-VAN reconciliation gives you that visibility across the full document lifecycle.
Quick Answer
Dual-VAN reconciliation is the process of matching outbound and inbound EDI records across two networks to confirm a document legitimately left your system, passed through your provider, and was accepted by your trading partner. It relies on control numbers (ISA, GS, ST), timestamps, and acknowledgment codes like the 997. It's most critical during VAN migrations, when running two networks in parallel lets you catch gaps before cutover.
In This Article
- What Dual-VAN Reconciliation Really Is
- Why It Matters in EDI Operations
- How It Works: The Core Steps
- Critical Data Points You Need
- What Single-VAN Monitoring Misses
- Setting Up an Effective Control Process
- Role During Migration and Consolidation
- What a Good Dashboard Should Show
- The Pricing Connection
- Implementation Checklist
- How Nexus VAN Supports Reconciliation
- Best Practices
- Frequently Asked Questions
What Dual-VAN Reconciliation Really Is
Dual-VAN reconciliation is a process organizations use to confirm, with concrete evidence, that each EDI document legitimately left their system, passed through their provider, crossed a VAN interconnect, and arrived at the recipient's system. It works by matching records from both the sending and receiving networks, checking transport status, control numbers, and acknowledgment messages. It's especially important when trading partners, routes, or providers change, or when you're running dual operations during a migration.
Why Dual-VAN Reconciliation Matters in EDI Operations
Sending an EDI document isn't proof it arrived. Unverified deliveries can lead to financial losses, partner disputes, or compliance gaps. Network errors, failed acknowledgments, and partial acceptances can all slip by unnoticed in a single-VAN environment, leading to chargebacks, missed shipments, or accounting headaches that surface only after the fact.
The biggest risk usually isn't a document that fails to send. It's a document that sends successfully but is never acknowledged or accepted on the other end, and goes unnoticed until a chargeback or missed shipment forces the issue.
Dual-VAN reconciliation gives your team a documented audit trail to resolve these issues quickly and gives everyone a clear answer to where and why a document failed, instead of researching or debating an EDI gap after a partner has already flagged it.
How Dual-VAN Reconciliation Works: The Core Steps
The process is built on a structured comparison of outbound and inbound EDI records across two networks. A robust dual-VAN reconciliation process typically involves:
- Capturing outbound document control numbers (ISA, GS, ST), timestamps, and sender or receiver IDs in your EDI or ERP system
- Recording acceptance and handoff confirmations from your source VAN
- Monitoring intermediate routing and interconnect status as documents move between networks
- Collecting inbound acknowledgments, such as X12 997s, or receipt logs from the destination side
- Matching each acknowledgment to its originating document using control numbers and timestamps
- Flagging any documents with missing receipts, partial acceptances, errors, or timing issues for immediate review
Critical Data Points You Need to Capture
Effective reconciliation depends on consistent, unique identifiers and reliable status information for every message.
| Data Point | Why It Matters |
|---|---|
| ISA, GS, ST control numbers | Matches acknowledgments back to the original transaction |
| Sender and receiver IDs | Verifies correct routing between trading partners |
| Document timestamps | Measures latency and flags SLA breaches |
| Transmission and acknowledgment status (both VANs) | Confirms both legs of the exchange completed |
| Functional acknowledgment codes (AK2, AK5, AK9 for X12) | Identifies partial acceptances and errors |
| Rejection or error codes | Supports root cause analysis |
Where Dual-VAN Reconciliation Catches Issues Single-VAN Monitoring Misses
Single-VAN visibility usually only tells you whether your message left your side. It doesn't confirm it was delivered, processed, or accepted by the final trading partner. Dual-VAN reconciliation checks both ends of the transaction. For example:
- An 810 invoice was sent but never acknowledged by a retailer's EDI system, pointing to a transmission or mapping failure
- A batch of ASNs is partially accepted, letting you zero in on the exact documents that need resubmission or correction
- An expected 997 acknowledgment doesn't arrive within the SLA, triggering a proactive alert before a chargeback or missed shipment
For more on handling acknowledgments day to day, see EDI 997 and 824 Acknowledgments in Daily Exception Management.
Setting Up an Effective Reconciliation Control Process
Manually comparing logs or spreadsheets will break down at scale. A stronger process includes:
- Defined SLAs for each document type and trading partner, such as 30 minutes or next business day
- Automated matching checks running at 5 to 15 minute intervals for high-volume flows
- Exception lists and clear escalation protocols for missing, delayed, or error-prone messages
- Systematic storage of control numbers and timestamps for audit purposes
- Separate triage paths for partially accepted versus fully rejected documents
- A centralized archive of reconciliation results to support dispute resolution and compliance needs
Role of Dual-VAN Reconciliation During Migration and Consolidation
Any time you switch providers, merge business units, or onboard new trading partners, dual-VAN reconciliation becomes an essential safety net. Running parallel networks, even for a short overlap, lets you compare legacy and new traffic and match document counts and exception rates before decommissioning the old solution. This is especially useful for teams consolidating multiple VANs, since it confirms every message, acknowledgment, and exception forwards correctly during the changeover. For practical steps, see Consolidating Multiple EDI VANs.
What a Good Reconciliation Dashboard Should Show
An effective EDI portal makes document status instantly obvious to finance, EDI operations, and management reviewers. At a glance, you should be able to see:
- Sent and received status with timestamps
- Accepted and error statuses by both VANs and trading partners
- Inbound and outbound 997s for each document or batch
- Exceptions, partial acceptances, or outright rejections
- Alerts for any document missing beyond SLA
If your current VAN can't provide this level of visibility, dual-VAN reconciliation helps bridge the gap, even if you have to collect and match logs from multiple locations manually at first. See EDI Portal Search Features That Help Teams Find Failed Documents Faster.
Cost Control and Transparency: The Pricing Connection
Full visibility isn't just about operational control. Opaque billing, particularly when providers round up document sizes or charge overage fees, adds unnecessary expense that compounds across multiple VANs. Billing by exact kilo-character usage aligns costs to actual activity and shows exactly what was transmitted rather than an estimate. See Overage Fees in EDI VANs, Explained.
Checklist: Implementing Dual-VAN Reconciliation in Your Business
- Map all EDI document types and trading partners
- Confirm acknowledgment requirements and expected response types for each document flow
- Standardize collection of ISA, GS, and ST control numbers across your EDI and ERP landscape
- Define and document SLAs for all critical flows
- Enable automated matching to pair acknowledgments to source transactions
- Set up alerting for missing or late acknowledgments, including partial acceptances
- Pilot the new process in parallel before any cutover
- Review and improve monthly based on trends in exceptions or rejections
How Nexus VAN Supports Reconciliation
Nexus VAN supports AS2, SFTP, and REST API connections, along with interconnects to VAN networks globally, so reconciliation isn't limited by which network a given partner happens to use. The management portal tracks transaction and acknowledgment status in one place, the same data dual-VAN reconciliation depends on. Pricing is based on exact kilo-character volume rather than rounded document sizes, so usage data lines up with what shows on the invoice.
Spanx moved to Nexus VAN after their previous VAN's hidden fees, per-message rates, and archived-data access charges became unmanageable, and needed predictable, transparent pricing instead. Read the Spanx case study. TIGI, which manages EDI across a large retail network spanning partners like Ulta, Walmart, Target, and Kroger, needed to control per-partner onboarding fees and improve internal systems integration. Read the TIGI case study.
Best Practices for Ongoing Reconciliation and Risk Prevention
- Continually monitor inbound and outbound logs for each VAN connection
- Centralize document control data and exception handling in dedicated tools or dashboards
- Train finance, operations, and technical teams to read, match, and investigate EDI control numbers
- Perform regular internal audits of acknowledgment timing and exception rates
- Work with providers known for transparent billing to minimize surprises during reconciliation
- Consult your VAN provider when critical trading partners change systems or protocols, since those are high-risk moments
More on EDI auditing can be found in How to Audit EDI Processing Fees Before Your Next Budget Meeting.
Frequently Asked Questions
What is dual-VAN reconciliation, and why is it important?
Dual-VAN reconciliation is the process of proving that each EDI document sent from your organization has passed through both the origin and destination VAN, and has been acknowledged or processed by your trading partner. It matters because it provides hard evidence of delivery, reduces disputes, cuts down on exceptions, and supports audit and operational integrity.
What control numbers are needed for reconciliation?
You need to track ISA, GS, and ST control numbers, along with sender and receiver IDs and accurate timestamps. These identifiers let you correlate each outbound message with its corresponding acknowledgment or error notice.
What risks are addressed by dual-VAN reconciliation?
It prevents missed, delayed, or lost EDI documents from going undetected, reducing the likelihood of chargebacks, unfulfilled orders, partner disputes, and difficult audits. It also saves staff time that would otherwise go into manually investigating every exception.
How does Nexus VAN support dual-VAN reconciliation?
Nexus VAN offers interconnects to VANs globally, multi-protocol support, and a portal that keeps transaction and acknowledgment status in one place, so teams can implement reconciliation controls without manual overhead.
How does transparent kilo-character pricing impact reconciliation?
Billing on actual data transmitted, instead of rounded document sizes, lets you reconcile usage against your monthly invoice directly. That eliminates billing disputes and confirms charges match real EDI activity.
See Dual-VAN Reconciliation in Action
Get a walkthrough of how Nexus VAN's portal tracks control numbers, acknowledgments, and exceptions across every trading partner.
Schedule Demo