If you can’t easily explain your EDI VAN bill, that’s a problem. Pricing models—per document, per transaction, or per kilo-character—directly shape what you pay, especially during growth or seasonal spikes.
Before you renew or forecast another quarter, here’s how to break down each model and see which one truly reflects your usage.
Three EDI VAN Billing Models in Detail
Most providers use one of three methods for invoicing their data exchange service. Each approach is structured around a basic feature of your usage: document count, transaction count, or raw data volume.
- Per Document: You pay a fixed amount for every document sent or received, regardless of its size. An invoice and a purchase order are counted equally, even if the actual character counts are vastly different. This method simplifies forecasting if your transaction types are consistent but can become expensive as your volume climbs.
- Per Transaction: Here, the bill is based on every EDI transaction—typically aligning with unique business events such as an invoice or an advance ship notice. Test transactions, high-volume peaks, or misconfigured integrations can quickly inflate the bill without you realizing it until month-end.
- Per Kilo-Character (KC): This model charges you based on actual data sent and received, measured in 1,000-character blocks. If your documents vary in detail or line item counts, you’re billed accurately for the true amount of data transmitted, not the number of files. Whether a document is a few lines or several pages, you only pay for what crosses the wire. At Nexus VAN, this is always an exact count—we never round up your data size, so you’re not paying extra for empty fields.
How These Models Change What You Pay
Understanding where the costs come from is the foundation for realistic budgeting. Here’s what typically affects each model:
- Per Document: Costs grow proportionally as your business exchanges more files. High volumes, especially seasonal, can make bills unpredictable. Since every document type is billed equally, your costs can feel disconnected from real business activity, especially if you increase testing or onboard more partners.
- Per Transaction: This model might sound similar to per document since most transactions represent actual business events. But test or duplicate transactions count, and surges due to batch processes or trading partner quirks will show up as increased costs.
- Per KC: Costs rise only with the amount of data you transmit. Short shipping confirmations cost less. Long, itemized invoices cost more. In practical terms, if you process a lot of simple, short documents, this model can be very cost-effective. If your documents are large due to compliance or supply chain complexity, it reflects your true usage, not an arbitrary file count.
Why Predictability and Transparency Matter
Finance and IT leaders want monthly costs they can explain and defend—not just to their own team but to board-level stakeholders. Models that track data volumes rather than document counts tend to align with this goal for growing businesses. The two biggest pain points with per document or per transaction models:
- Extra (unexpected) fees from transaction spikes, like annual audits, partner onboarding, or test traffic.
- Difficulty forecasting bills when partners or supply chain events drive variance in your message volume.
Per KC pricing produces a tighter link between what you pay and how your EDI system is actually used. This is especially true at Nexus VAN, since the exact character count is used (and never rounded up to the next block).
How to Perform a Real Side-by-Side Comparison
You do not need specialized tools—just your VAN portal data and access to your rate sheet. Here’s how to do an apples-to-apples check in less than an hour:
- Export Usage Data: Download usage for the last month or quarter. Collect the total number of documents, number of transactions (if available), and the total number of kilo-characters transmitted. For a sense of document size variation, average your document size in KC or KB.
- Review Your Rates: Check your contract. Note the per document, per transaction, or per KC price points. Also check for add-ons—it's common to see charges for extra mailboxes, user accounts, or onboarding that are not discussed up front. For up-to-date reference on legitimate and hidden EDI fees, see our detailed fee guide.
- Run the Numbers: Multiply your actual volumes by your provider’s rates under each model. If you’re billed for extra features, factor those in. When testing per KC, always check if your provider rounds up data sizes. At Nexus VAN, you’re only billed for the exact data sent and received—no padding, no rounding.
- Project Growth: Account for growth or seasonal increases. If your document volumes jump by 20 percent, what happens to your cost? With per KC, only the data volume affects your bill. With the others, unused documents or test files may also be charged, inflating costs faster than actual business growth.
Recognizing Red Flags and Hidden Costs
It’s easy to miss small details that add up to big numbers on an invoice. When reviewing EDI VAN bills, keep an eye out for the following:
- Setup or "onboarding" fees for new partners or connections
- Mailbox fees, user seat surcharges, and mailbox license costs
- Volume overage surcharges—often triggered if you grow 10-20 percent beyond your old baseline
- Rounding up data size charges, or bill padding by rounding every message to the next KB or MB
- Support and mapping rates, which can appear as hourly or per-incident charges
Nexus VAN bills never include setup, onboarding, mailbox, support, or rounding fees. You see only the actual data you transmit, and you know up front what each pricing tier costs. For a deep dive on avoiding hidden costs, read our expert breakdown of hidden billers.
Case Examples: Transparent Billing in Practice
The need for predictable, transparent billing is not limited to one industry. Nexus VAN customers across retail and consumer goods have seen significant EDI savings by switching from opaque "per document" or "per transaction" plans to tiered, per KC pricing. These organizations gained ongoing visibility into their true usage, empowering teams to manage data costs as business activity shifted. Read more on company wins and cost management in our past insights about the real cost of EDI VANs.
Switching with Confidence
Questions about risk often keep organizations on legacy plans that no longer fit their scale or business needs. But with the right partner, migration can be seamless and risk-free. At Nexus VAN, we have moved clients with zero downtime and complete migration support. Your team can track progress in a live dashboard, test connections to every trading partner, and use the platform with a 90-day free trial before committing. We support all data exchange protocols and maintain interconnects worldwide—meaning you never have to worry about coverage, reliability, or support once you decide to make a change. You can compare that experience to the practical steps we’ve discussed in our guide on minimizing risk during EDI VAN migrations.
Takeaway: Let Your Actual Data Do the Talking
You do not need to take billing estimates or marketing claims at face value. Download your actual usage, apply the three main pricing models, and test the results against multiple months of data. Look at add-ons, rounding, and growth triggers—these details make all the difference, especially if you manage budgets or operational costs at scale. We built Nexus VAN specifically for professionals who want to save, simplify, and never have to guess what their bill will be next month. Start by reviewing your own billing report, then see for yourself what you could be saving. Ready to learn more or see a demo in action? Schedule a demo with Nexus VAN and experience transparent EDI where every KC counts, and every migration is guaranteed.
