VAN vs. AS2 vs. API: The Real Cost-Per-Transaction Math Nobody Publishes
Every EDI connectivity vendor will tell you their model is cheaper. None of them will show you the full math. VAN providers quote per-kilocharacter fees and bury the mailbox and interconnect charges. AS2 vendors sell you on “no per-transaction fees” and skip the certificate renewal, monitoring, and troubleshooting labor. API evangelists promise real-time efficiency while ignoring the engineering hours it takes to build and maintain a dozen partner-specific integrations.
If you’re choosing a connectivity model for a new trading partner program, or evaluating whether to migrate off a model you’ve outgrown, you need the actual cost-per-transaction, not the marketing number. Here’s how to calculate it.
Why the Published Numbers Are Misleading
Vendors quote the cost that makes their model look best, which usually isn’t the cost that matters to your operation. A VAN’s per-kilocharacter rate looks trivial until you multiply it across every 850, 856, and 810 you exchange in a month, and add mailbox fees, interconnect fees for partners on a different VAN, and annual minimums. An AS2 connection has no per-message fee, but somebody has to stand up the AS2 server, manage certificate rotation, and get paged when a partner’s endpoint changes its cert without notice. API connectivity eliminates translation overhead for partners who support it, but every partner with a different schema means a new integration to build and maintain, and most of your trading partner base still doesn’t offer a modern API.
The only honest comparison factors in transaction fees, infrastructure and maintenance costs, and the labor required to keep each connection running, divided by actual transaction volume.
Building the Real Cost-Per-Transaction Formula
Cost-per-transaction = (Fixed infrastructure costs + Variable transaction costs + Labor/maintenance costs) ÷ Total transaction volume
Break each component down before you compare models.
Fixed infrastructure costs
- VAN: mailbox setup, monthly mailbox fees, annual minimums
- AS2: server or gateway software licensing, SSL/AS2 certificates, firewall and network configuration
- API: API gateway or middleware licensing, developer environment setup
Variable transaction costs
- VAN: per-kilocharacter or per-document fees, interconnect fees for cross-VAN partners
- AS2: typically none per message, but bandwidth costs at high volume
- API: often none per call, but rate-limit overage fees on some partner platforms
Labor and maintenance costs
This is where most cost comparisons fall apart, because it’s the hardest to quantify and the easiest to underestimate.
- VAN: minimal — the VAN handles delivery, retries, and much of the partner troubleshooting
- AS2: moderate to high — certificate renewals, MDN monitoring, connectivity troubleshooting when a partner changes IPs or certs
- API: high and partner-specific — each integration needs custom mapping, authentication handling, and ongoing maintenance as partner APIs version
Running the Math: A Realistic Comparison
Take a mid-size supplier processing 50,000 transactions a month across 30 trading partners.
VAN model: Mailbox fee of $300/month, plus $0.03 per kilocharacter averaging roughly $0.08 per transaction, plus $500/month in interconnect fees for partners on competing VANs. Labor is minimal since the VAN absorbs most delivery issues. Monthly cost lands around $4,800, or roughly $0.096 per transaction.
AS2 model: No per-transaction fee, but the server and certificate management require an estimated 15 hours/month of IT labor at a fully loaded rate of $75/hour, plus $200/month in infrastructure. Monthly cost is around $1,325, or roughly $0.0265 per transaction — a clear win at this volume, assuming the internal team has the AS2 expertise on staff.
API model: No per-call fee for partners on modern APIs, but only 8 of the 30 partners currently support one. Building and maintaining those integrations runs an estimated 25 hours/month at $75/hour, or $1,875/month, covering only 15,000 of the 50,000 transactions. The remaining 35,000 transactions still route through VAN or AS2. Isolated to the API-capable volume, cost is $0.125 per transaction — higher than AS2, because the labor is spread across fewer transactions and partner-specific maintenance doesn’t scale down.
The numbers shift meaningfully with volume, partner mix, and in-house technical capability, but the exercise itself is the point. Run it with your own figures before committing.
Where Each Model Actually Wins
VAN makes sense when:
- Transaction volume is moderate and predictable
- Trading partners are fragmented across many different VANs
- You lack in-house AS2 or API infrastructure expertise
- Reliability and built-in partner support outweigh per-transaction savings
AS2 makes sense when:
- Volume is high enough that per-kilocharacter VAN fees add up fast
- You have (or can build) internal capability to manage certificates and monitor connections
- Your major trading partners standardize on AS2 (common in retail and automotive)
API makes sense when:
- Partners support modern REST/JSON APIs and real-time data exchange matters
- You’re building new digital-first partner relationships rather than migrating legacy ones
- The integration effort is justified by transaction volume with that specific partner, not spread thin across many
Most mature EDI operations end up running a hybrid — VAN for long-tail partners, AS2 for high-volume standardized partners, and API for select strategic integrations. The connectivity model isn’t a single decision; it’s a portfolio decision made partner by partner.
Migration Considerations
If the math points toward migrating off your current model, the cost calculation doesn’t stop at the new steady-state number. Factor in:
- Parallel run costs — most migrations require running old and new connections simultaneously during partner cutover, doubling infrastructure costs temporarily
- Partner testing and certification cycles — AS2 and API migrations typically require partner-by-partner testing, which can stretch a migration timeline to months
- Retraining — staff comfortable troubleshooting VAN mailbox issues need new skills for AS2 certificate management or API authentication debugging
A migration that looks like it pays for itself in six months on paper often takes twelve to eighteen once partner testing cycles and parallel-run overhead are factored in.
There’s no universally cheapest connectivity model. Only the model that’s cheapest for your specific volume, partner mix, and internal capability. Run the full formula, not the vendor’s version of it, before you choose or migrate. And revisit the calculation periodically: transaction volume, partner API adoption, and labor costs all shift over time, and the model that made sense two years ago may not be the most cost-efficient one today.
Understanding connectivity economics is one of the practical skills covered in EDI Academy’s CEDIAP certification, alongside transaction set standards, trading partner onboarding, and integration architecture — the operational depth that goes beyond vendor sales decks.