Partner onboarding slows when an EDI coordinator has to reconstruct identifiers, document rules and test contacts from old messages. A trading partner profile puts those decisions in one record before anyone changes a route. It also helps you assess a lower cost VAN without treating the switch as a leap of faith.
Quick Answer
A trading partner profile template speeds EDI onboarding by collecting each partner's IDs, document types, communication method, contacts, testing requirements and approval in one place. Use a separate profile for each distinct routing arrangement, verify it against the partner's implementation guide and test before production. Nexus VAN makes a later switch low risk through dual-VAN reconciliation, while exact-size kilo-character billing addresses common legacy VAN charges.
In This Article
A complete profile saves onboarding work and exposes avoidable VAN costs
A trading partner profile is the working record for exchanging electronic data interchange, or EDI, documents with a particular business partner. It says who sends what, where it goes, how receipt is checked and who approves production use. An implementation guide defines a partner's own document rules. The profile records how your team will meet those rules, plus the contacts and test results needed to operate the connection.
Think of the profile as a series of decisions, not an address book. If a customer has separate divisions with different routing identifiers or instructions, keep distinct records for those arrangements. If several documents use the same connection, list each document and direction within that profile. This prevents a familiar connection from hiding a new mapping or acknowledgment requirement.
The same inventory has a financial use. Many legacy VANs use practices such as rounding document sizes, minimum charges per document, per-partner fees and archive-access fees. A partner list lets finance match those charges to actual connections and lets IT decide whether an expensive provider still earns its place. Nexus VAN prices by the kilo-character, and we never round up the size of your documents, so you are billed accurately for the exact data you transmit, and nothing more.
Spanx's published case study illustrates why this review matters: its previous VAN charged high per-message rates along with per-partner and archive-access fees. The company moved to predictable, transparent pricing. Your own opportunity depends on your current bill, contract and usage, so start with the charges you can identify rather than an assumed savings figure.
Copy this trading partner profile template before configuring a route
Create one record for each distinct partner routing arrangement. Fill in the fields below, mark unknowns as open and identify where each answer came from. A blank value should stop the relevant configuration decision, not invite a guess. Keep the partner's current published EDI implementation guide alongside the record and confirm any partner-specific requirement there.
| Profile area | Fields to copy into your record | Decision the fields support |
|---|---|---|
| Business identity | Partner legal name; division or facility; business role; internal business owner; internal EDI owner | Which organization and workflow this connection serves |
| Contacts | Partner EDI contact; business approver; support contact; escalation owner; contact source | Who resolves a failed test or approves a change |
| Requirements source | Implementation guide title and revision; partner portal reference; date checked; person confirming any exception | Which instructions are current and who confirmed them |
| Transaction scope | Transaction name and number; sending party; receiving party; standard and version if applicable; business purpose | Which documents need mapping, routing and testing |
| Identifiers | Sender ID and qualifier; receiver ID and qualifier; relevant mailbox or account reference; test and production values | How documents reach the intended partner and environment |
| Communication | AS2, SFTP, REST API or VAN interconnect as applicable; connection owner; test destination; production destination; security ownership | How documents move and who manages access |
| Acknowledgments | Required acknowledgment type; expected sender and receiver; receipt check owner; exception procedure | How the team checks syntax receipt and investigates rejection |
| Internal processing | Receiving application; outbound source; translation owner; business validation owner; exception contact | What happens after transport succeeds |
| Testing and approval | Sample reference; scenario; result; acknowledgment result; open defect; partner approval; internal approval | Whether the specific document flow is ready |
| Migration and cost | Current VAN route; proposed route; reconciliation owner; current charge categories; contract review owner | How to compare routes and identify billing exposure |
This is an intake template, so the examples below describe possible entries rather than a partner's required setup. Record values in the right place, but avoid storing private keys or passwords in a broadly shared profile. Put the secure location and owner of those secrets in the record instead.
Document scope: record direction and business meaning separately
For an order-to-cash workflow, your document list might include an 850 Purchase Order received from a retailer, an 855 Purchase Order Acknowledgment sent in response, an 856 Ship Notice/Manifest sent for shipment details and an 810 Invoice sent for billing. Those are standard ANSI X12 transaction names, not a claim that every retailer requires all four. Check the partner's implementation guide for the applicable version, document sequence and acceptance criteria.
Give each document its own row in the working record. Write direction from your company's point of view, such as inbound 850 or outbound 810. Add the internal owner who can tell you whether the document completed its business purpose. A transport receipt may prove a message arrived, while an internal order exception can still prevent it from being processed.
Identifiers and environment: capture the exact routing context
Sender and receiver identifiers tell an EDI network where a document came from and where it belongs. Qualifiers identify the type of identifier when the relevant standard calls for them. Copy the approved values for each environment rather than relying on a partner's display name or an old spreadsheet. If your organization exchanges under multiple legal entities, make the entity explicit next to each identifier.
Record test and production destinations separately. Also note who can authorize a change. This matters during both onboarding and migration: a correct document sent to a test route is still missing from the production workflow. For more on organizing IDs and related connection details ahead of a switch, see our EDI identifier and certificate inventory.
Acknowledgments: distinguish syntax from business approval
A 997 Functional Acknowledgment tells the sender whether a document passed the receiver's syntax check. It can report acceptance or rejection. It does not mean the order or its content was accepted by the receiving business. Capture which acknowledgment the partner expects, who reviews a rejection and how the team verifies the business result separately. Requirements may differ by partner and version.
Do not approve a connection solely because a test file was delivered. Confirm the intended recipient, applicable acknowledgment, internal processing result and partner approval for each document flow.
Use the profile to reduce backtracking from intake through production approval
A filled-in form alone does not speed onboarding. It helps when each field controls a decision and each open question has an owner. We recommend a sequence that makes missing information visible early, then checks the entire document path before the route is used for live business traffic.
Step 1: Establish the business scope
Ask the business owner which entity is connecting, which trading partner organization is involved and which business process the connection supports. Identify the transactions that are in scope and whether the same partner already has another active route. This prevents a request labeled as a simple new partner setup from quietly introducing a different division, new document type or changed workflow.
Step 2: Verify the partner's instructions
Obtain the current published EDI implementation guide and the partner's testing instructions. Record their revisions and where any direct clarification came from. Compare the requested document types, versions, IDs, connectivity method and approval rules with your profile. When something conflicts, pause that decision and ask the partner. Never carry an old partner's rules into a new connection just because the transaction number is familiar.
Step 3: Assign connection and mapping ownership
Identify who sets up the communication route, who translates incoming and outgoing documents and who validates the internal business result. A value-added network, or VAN, carries documents between trading partners, but transport does not replace the work of matching a partner's document to your application process. Keep the internal system description conceptual in the profile and have the responsible application owner approve detailed mapping separately.
Step 4: Build a test matrix from the document list
Make a row for each transaction and direction. Add representative successful scenarios, a syntax rejection check where appropriate and any business exception the partner requires you to test. Record the input file reference, expected result, observed result, acknowledgment status and owner for a failed scenario. A clear test matrix helps you see whether the connection works for an entire workflow rather than for one sample file.
Keep acceptance evidence tied to the exact document and version tested. If the partner changes its guide or an internal map changes, decide which tests must run again. Our testing and certification acceptance criteria offers a fuller checklist for that decision.
Step 5: Approve production values and assign exception handling
Confirm the live IDs, destination and security owner before turning on production routing. Record who approved the business process and who approved the technical result. Note who investigates a rejected document, a missing acknowledgment or a business processing failure after go-live. Keep an update history so the next coordinator can tell current requirements from a previous configuration.
A verified profile makes switching VANs a low risk, accountable decision
Executives often hesitate to replace a costly VAN because missing orders or duplicated documents could be more expensive than the current bill. That is a real operational concern. The profile helps turn it into a checklist: you know the partners, document types, directions, identifiers and acknowledgments that must be checked before retiring a route.
Nexus VAN uses dual-VAN reconciliation during migration. The old VAN and Nexus VAN run side by side while the team accounts for documents before the old route is retired. Its management portal provides visibility into transaction status, acknowledgments and control numbers, which are identifiers used to trace EDI exchanges. The service supports AS2, SFTP and REST API and interconnects to VANs globally. Those capabilities give the EDI coordinator concrete information to use during the move instead of relying on a single successful connectivity test.
Use the partner profile as the reference for reconciliation. For each in-scope flow, check the expected sender, recipient, transaction type and control information against activity on the old and new routes. Investigate a missing document, unexpected duplicate or rejection before considering that flow complete. Keep a named owner for open exceptions and document the decision to retire each old route. This is why switching can be low risk without pretending routing errors are impossible. Our dual-VAN reconciliation guide goes deeper into the checks.
Give finance a parallel assignment. Review the current contract and invoice for size rounding, document minimums, partner charges and archive-access fees. Match the charges to the partner inventory so you can compare the cost of staying against a plan billed on actual kilo-characters. When several business units or portfolio companies use different VANs, separate their profiles and contract terms first. That makes the cost comparison understandable without assuming every business has the same documents or exposure.
Cutover rule: A completed partner profile is a starting point, not evidence of a successful migration. Keep the old route until the in-scope documents and acknowledgments have been reconciled and the relevant owners have approved the change.
Best practices that keep the profile useful after onboarding
- Make the source visible. Put the implementation guide revision or written partner confirmation next to requirements that could change. A field without a source is hard to trust later.
- Assign an owner to every unknown. Mark an ID or production destination as open until the responsible person confirms it. An apparently complete but guessed profile causes more rework than an honest gap.
- Keep technical and business outcomes distinct. Record syntax acknowledgments, transport status and internal processing results separately. Each answers a different question about the same document.
- Protect sensitive connection information. The profile can identify the owner and storage location for credentials or private keys without copying secrets into an intake sheet.
- Recheck the profile when scope changes. A new document type, changed partner division, revised guide or VAN route calls for a review of IDs, tests and approvals. Do not treat a previous signoff as covering a different flow.
- Keep costs connected to operations. Record the current provider's charge categories next to the partner inventory, then examine whether any charge depends on partner count, document minimums or rounded sizes.
TIGI's published case study shows why partner-by-partner visibility matters in a large retail network: the company managed EDI across retailers while avoiding per-partner onboarding fees and improving internal systems integration. A consistent profile makes that kind of network easier for your own team to understand, regardless of which connection is being added or reviewed.
Frequently Asked Questions
What is a trading partner profile in EDI?
A trading partner profile is a record of the identities, document types, routing details, contacts, testing requirements and approvals for an EDI connection with a specific partner. It helps your team configure and operate the connection consistently.
Which fields are most important in a trading partner profile template?
Start with partner and internal owners, transaction types and direction, sender and receiver IDs, connection method, separate test and production settings, the current implementation guide, acknowledgment expectations and production approval. Add a source and owner for any field that remains open.
Does a 997 acknowledgment mean the order was accepted?
No. A 997 Functional Acknowledgment reports whether the receiver's syntax check accepted or rejected a document. It does not establish that an order or its contents were accepted by the receiving business.
How does a trading partner profile help during a VAN migration?
The profile lists the partners, IDs, document flows and acknowledgments that must be checked. During a switch to Nexus VAN, dual-VAN reconciliation runs the old and new VANs side by side so documents can be accounted for before an old route is retired.
Can a partner inventory help us evaluate VAN costs?
Yes. Match the inventory to your current contract and invoice to identify per-partner charges, document minimums, size rounding and archive-access fees. Comparing those charges with exact-size kilo-character billing shows where your current model may be adding cost.
A good profile gives your EDI coordinator a usable test and routing record, and it gives leadership a clearer view of what switching would involve. If your legacy bill includes rounded document sizes or extra partner charges, reviewing those costs alongside a controlled migration is worth the effort.
Review your partner inventory before your next VAN renewal
Bring your profiles and current bill to a conversation with Nexus VAN. We can discuss exact-size kilo-character pricing and how dual-VAN reconciliation helps keep a move low risk while you account for each document.
Schedule Demo