EDI errors, operations and security

How do I confirm a document was delivered to the recipient?

When you send a document, your partner's system automatically returns a 997 acknowledgment (a reply confirming the document was received), and EDI-VAN checks and records it every time. Registered customers can view the documents they have sent and received, along with their status (delivered, acknowledged, error), directly on screen. There is no charge for received documents and acknowledgments. With the Dedicated plan, if an acknowledgment is missing or your partner rejects a document, EDI-VAN looks into it first and contacts you first.

Who fixes errors in documents?

Who fixes errors depends on the service type. In all cases, EDI-VAN checks the format and content before sending and notifies you if there is a problem.

• Self-service: You handle format mapping and testing yourself, so we respond to errors when you request it.
• Custom: EDI-VAN supports format mapping, and we handle errors together with you when you request it.
• Dedicated: EDI-VAN finds errors first, contacts you, and leads the resolution.

If the source data itself is wrong, such as quantities or prices, you need to correct the data on your side and send it again.

Is our company's data managed securely?

Yes. EDI-VAN is a closed network where only registered partners exchange documents with each other. Not just anyone can join; only trading partners that have gone through consultation and registration are connected.

• Each trading partner uses unique connection credentials.
• Documents travel through encrypted channels.
• Access logs and processing logs are kept.

Detailed contract terms on security are provided at the contract stage.

How long are exchanged documents retained?

The document retention period varies by plan; the SCALE plan retains documents for 3 years. The service information page states that exchanged documents and records are retained for 1 year. While documents are retained, registered customers can look up the documents they have exchanged, along with their status, on screen. We will confirm the exact retention period for the plan you intend to use during a consultation. Please leave a message via Contact us or at help@edi-van.com.

Are documents exchanged at night and on weekends?

Yes. Documents are exchanged automatically, 24 hours a day, including nights and weekends, even when no one is at their desk. When a retailer sends a purchase order, it is received right away, and the acknowledgment is sent back automatically. Registered customers can view the documents they have sent and received, along with their status, on screen at any time. With the Dedicated service, EDI-VAN watches for problems such as missing acknowledgments or rejections by the trading partner and contacts you first. Service levels, such as the hours when a contact person is available, are explained at the contract stage.

What happens if the recipient rejects a document?

If the recipient rejects a document, this is shown on screen as an error status, so you can see it right away. How it is handled depends on your service type.

• Direct and Custom services: on request, EDI-VAN helps you find the cause.
• Dedicated service: EDI-VAN spots the rejection first and contacts you first.

Once the cause has been found and fixed, simply send the document again. Retailers may charge fees for documents that are late or incorrect, so it is best to check rejection alerts quickly.

What happens if the retailer changes its requirements?

When a retailer changes its document rules, EDI-VAN applies the change and adjusts to the format the trading partner requires. As a result, in most cases you can keep using your ERP and your current ways of working. When the retailer sends a change notice, EDI-VAN adjusts based on that notice and tests again if needed. If the change is large, the schedule and cost are confirmed in a consultation.

What causes Walmart EDI chargebacks?

A chargeback is a fee a retailer charges a supplier when documents or goods do not arrive according to the retailer's rules. It generally occurs in cases such as these:

• The shipment notice (856, a document that tells the buyer in advance what has been shipped before the goods arrive) is late or missing
• The document contents do not match the actual goods or the order
• The carton label does not meet the specification

Walmart's current requirements may change, so we adjust based on the guidance Walmart sends. Testing thoroughly before opening trading is the best way to prevent chargebacks.

How can I avoid late ASN and invoice errors?

Late advance ship notices (ASN) and invoice errors can be greatly reduced by thorough testing and checking before sending.

• Before trading opens, exchange test documents from start to finish and adjust until they match.
• EDI-VAN checks the format and contents of documents before sending them and lets you know if there is a problem.
• With the Dedicated service, EDI-VAN watches for approaching deadlines and missing acknowledgments and contacts you first.

Your part is to enter or provide shipped quantities and carton information accurately and on time.

Why was my 997 rejected, and how do I fix it?

If a 997 comes back as rejected, it means the other party's system received the document but could not accept it because of its format or contents (a 997 is a reply confirming that a document was received correctly). The cause differs from document to document, so the actual document and the reply need to be reviewed together. EDI-VAN takes care of checking and handling each error.

• Custom service: on request, we help identify the cause and make the correction.
• Dedicated service: EDI-VAN spots the rejection first and contacts you.

Please check the document on screen and then let your contact person know.

Why is my ASN (856) being rejected by the retailer?

The 856 ship notice is the most demanding of the EDI documents, so rejections are common. It has to carry packing information at several levels, such as cartons and pallets, the box label format has to match, and each retailer's requirements differ slightly. A document that does not match what was actually shipped can also be rejected. The exact cause can only be determined by looking at the actual document together with that retailer's guide. With the Custom plan, we look into it when you ask; with the Dedicated plan, EDI-VAN finds the cause first and makes the corrections for you. Please leave your inquiry through Contact us.

How do I fix invoices rejected for not matching the PO?

If an invoice is rejected because it does not match the purchase order, first check that the items, quantities and unit prices are the same as the order and the actual shipment. Many retailers compare the order, the receipt and the invoice with each other before paying, so if even one of them differs, the invoice can be put on hold or rejected. EDI-VAN checks the format and content of an invoice before sending it and tells you about any problems. Which values need to be fixed, and how, is confirmed together with you by looking at the actual document (Custom plan: when you ask; Dedicated plan: we contact you first). All you need to do is keep your order and shipping records accurate.

How can I find which EDI document failed and the rejection reason code?

Registered customers can see the documents they have sent and received, and the status of each document (delivered, acknowledged, error), on the EDI-VAN screen. You can see at a glance which document stopped at which stage. If you need to look further into the cause, with the Custom plan we support you when you ask, and with the Dedicated plan EDI-VAN looks into it first and contacts you.

What does an EDI coordinator do day to day?

An EDI coordinator usually spends each day checking that documents have been exchanged correctly and handling any problems.

• Checking newly received purchase orders (850) and replying with order acknowledgments (855)
• Checking that ship notices (856) and invoices (810) went out on time
• Checking for missing 997 acknowledgments or rejections from the trading partner, and taking action
• Checking for notices of rule changes from retailers

With EDI-VAN, document conversion and delivery happen automatically, and you only need to check the status on the screen. With the Dedicated plan, EDI-VAN takes on the checking and spotting of problems first and contacts you.

How do you monitor EDI transactions for errors and missing acknowledgments?

You can check errors and missing acknowledgments as the status of each document on the EDI-VAN screen. Registered customers can see the delivery, acknowledgment (997 acknowledgment, a reply confirming that the other party received the document correctly) and error status of every document sent and received. Documents are checked for format and content before they are sent, and you are told if there is a problem. With the Dedicated plan, EDI-VAN looks first for problems such as missing acknowledgments, rejections by the other party and approaching deadlines, and contacts you first.

How do you verify whether an EDI file was transmitted and received successfully?

You can tell whether a document was transmitted from its status on the screen and from the 997 acknowledgment sent by the other party. The 997 is a confirmation reply that the other party's system sends automatically to say it received the document correctly. EDI-VAN checks whether this reply has arrived for each document and shows it on the screen as delivered, acknowledged or error. Received documents and 997 acknowledgments are free of charge.

What is the process for resending an EDI document?

If you need to resend a document, just send a request to EDI-VAN. With the Custom plan, we respond to errors when you submit a request. With the Dedicated plan, EDI-VAN finds problems first and contacts you. The specific steps for resending on screen, and how a resent document is counted toward your document volume, are confirmed during a consultation. If you have any questions, contact us or write to help@edi-van.com.

How do you correct an EDI document after it has already been sent?

In general, an EDI document that has already been sent cannot be edited in place. Instead, you send a new document containing the correction or cancellation. How corrections are accepted differs by retailer, so we follow the guide issued by that retailer. The specific way EDI-VAN handles correction documents is confirmed during a consultation.

How do you handle missing 997 acknowledgments and why do they stop coming?

If a 997 acknowledgment does not arrive, the document shows a missing acknowledgment status on screen. A 997 is the reply confirming that the other party received your document, so if it does not arrive, the document may not have been processed on their side. With the Custom plan, EDI-VAN checks the cause and responds when you submit a request. With the Dedicated plan, EDI-VAN finds the missing acknowledgment first and contacts you.

What happens if the label data does not match the ASN?

If the box label does not match the 856 Advance Ship Notice (ASN), the retailer may delay receiving or charge you a fee. The ASN is a document that tells the retailer in advance what was shipped and how it was packed, before the goods arrive. Retailers compare the box label with the ASN at receiving, so the two must match. EDI-VAN checks the format and content of documents before sending and lets you know if there is a problem. We recommend testing thoroughly and getting everything aligned before you go live.

How do I monitor live EDI orders after go-live?

After you go live, you can check the status of each real order document one by one on the EDI-VAN screen. Documents are exchanged automatically 24 hours a day, with no one needing to be present. On screen you can see delivery, acknowledgment, and error status. With the Dedicated plan, EDI-VAN watches and contacts you first about missing acknowledgments, rejections from the other party, files that normally arrive but did not, approaching deadlines, and similar issues.

What should I do if an EDI purchase order does not match my inventory?

If you are short on stock, you can reply to the retailer with an 855 Purchase Order Acknowledgment to accept, partially accept, or reject the order. EDI-VAN converts this reply into the format the retailer requires and delivers it. Whether partial acceptance or rejection is allowed, and how it is handled, differs by retailer, so we follow that retailer's guide. If you do not have a system, you can check inventory in EDI ERP and send your accept or reject reply right away.

Why does my trading partner reject my ISA control number?

The ISA control number is a reference number attached to the envelope that holds a batch of documents. Your trading partner uses this number to check for duplicates or gaps, so they may reject a document if the number does not match their own rules. EDI-VAN handles the specific cause and the fix. If you are on a Custom or Dedicated plan, where EDI-VAN supports format conversion, check the rejected status on the screen and then send us a request. If you prefer to handle it yourself, the Self-service plan provides standard templates and guidance.

Is FTP secure enough for EDI, even if encryption is added separately?

Plain FTP does not encrypt its content, so we do not recommend it for sending business documents. EDI-VAN offers a method that encrypts files and sends them automatically (SFTP). You can also use a method that encrypts documents and exchanges them directly over the internet (AS2), as well as system integration (API). EDI-VAN is a closed network where only registered partners exchange documents. Documents travel through an encrypted channel, and connection and processing logs are kept.

How should a warehouse handle partial shipments in an EDI 945?

The basic rule is to send the 945 Warehouse Shipping Advice with the quantities that were actually shipped. How to report the remaining quantity and how to follow up with later shipments should be aligned with the guide provided by the shipper or distributor. You only need to prepare the actual shipped quantity data. EDI-VAN handles converting that data into the format your partner requires.

How should EDI 944 handle received quantities that do not match the 943?

The basic rule is that the 944 Warehouse Stock Transfer Receipt Advice should contain the quantities actually received, not the expected quantities. How to show the difference when it does not match the 943 Warehouse Stock Transfer Shipment Advice should be aligned with the shipper's guide. The 943 and 944 are "consultation" documents that need additional preparation before trading can begin. We will confirm the process and scope with you in a consultation. Please contact us and include the shipper's information.

How often should a 3PL send EDI 846 inventory updates?

There is no single fixed standard for how often to send 846 inventory updates. Follow the frequency stated in the guide sent by the shipper or distributor. The 846 is a document that tells your trading partner how much stock is available to sell. Requirements differ by partner, such as once a day or several times a day, and may change, so we do not state a fixed frequency in advance. EDI-VAN sets up the connection so that inventory for each shipper is sent automatically on the frequency your partner specifies. The 846 is an outbound document and counts toward your document volume, so the sending frequency affects your annual fee. You can check the cost for your conditions right away with the calculator in the pricing guide or through AI consultation.

Why does my EDI 846 inventory not match the warehouse system?

A difference between the 846 inventory and the warehouse system quantity is usually caused by the two sides counting inventory by different rules. Common cases include:

• The time the inventory was pulled differs from the time it was actually sent
• The two sides differ on whether to include or exclude quantities scheduled for shipment or on hold
• Item codes or units (each or box) are set up differently on each side

On the EDI-VAN screen, you can see the content and status of the 846 inventory that was actually sent. Which item differs and why can only be determined by looking at the actual data together. Please contact us, and we will check it with you in a consultation.

How should a carrier respond when it cannot accept an EDI 204?

For a 204 load tender you cannot accept, reply with a 990 Response to Load Tender document marked as "rejected." Although the 990 is named a "load acceptance," it is really the reply that tells the sender whether you accept or reject the dispatch request you received. Once you send this reply, the warehouse or shipper can quickly look for another carrier. With EDI-VAN, when you choose accept or reject in the carrier's dispatch system or an input screen, we connect it so that the reply is delivered in the format the other party requires. Whether the other party wants a reason included with a rejection is handled according to the guide that shipper sent.

Why is my EDI 214 not updating shipment status?

When a 214 Shipment Status does not update, it is usually because the status information was never sent, or it was sent but the other party did not receive it. For example, the status may have changed in the driver app or dispatch system without the automatic transmission following through, or the receiving side may have rejected the document. Registered customers can see the delivery, acknowledgment and error status of each 214 Shipment Status document on the EDI-VAN screen, so you can tell at which step it stopped. For dedicated-service customers, EDI-VAN contacts you first if an acknowledgment is missing or the other party rejects a document. The exact cause can only be determined from the actual records, so please leave a Contact us request and we will check it for you.

Why was my EDI 210 rejected by the broker?

The exact reason a broker rejected a 210 Freight Invoice can only be determined by looking at the rejection details together with the guide that broker sent. The 210 is the document a carrier sends to bill for freight. In general, rejections often happen when the billed amount or shipment information does not match the load tender received earlier, or when the format differs from what the broker requires. The 210 Freight Invoice is included among EDI-VAN's standard documents. If you send us the rejection details through Contact us, we will check them for you in a consultation.

Why is my EDI invoice rejected for price differences?

An invoice is rejected for price differences mostly because the retailer or distributor compares the unit price on the 810 Invoice it received with the unit price on the original 850 Purchase Order. Retailers and distributors usually match the order, receipt and invoice against each other, and pay only when they agree. So an invoice can be rejected if a unit price changed and was not reflected, or if the unit of measure (each or case) or the discount applied is different. EDI-VAN checks the format and content of documents before sending and tells you if there is a problem. The basis for comparing prices differs by retailer or distributor, so it is handled according to the guide that retailer or distributor sent.

What causes duplicate EDI documents, and how do I prevent them?

The most common cause of duplicate documents is resending the same document because you cannot tell whether the other party received it. In some cases your own system exports the same data twice. The way to prevent this is to check whether it was received before you resend. EDI-VAN automatically checks every time whether the other party received a document, using the 997 Functional Acknowledgment (a reply confirming the document was received properly), and its screen shows the delivery and acknowledgment status of each document. We also check the format and content before sending and tell you if there is a problem. If you suspect the cause is on your own system's side, we can look into it with you in a consultation.

Why does my trading partner reject invoices as duplicates?

A trading partner rejects an invoice as a duplicate mostly because an 810 Invoice with the same number as one it already received came in again. Common cases are the same invoice being sent twice by mistake, or an invoice being corrected and then resent under the same number. How to correct an invoice that has already been sent differs by retailer or distributor, so it is handled according to the guide that retailer or distributor sent. On the EDI-VAN screen you can see when each invoice was sent and its acknowledgment status, so you can confirm whether it actually went out twice. If it is hard to tell, leave a Contact us request and we will check it for you in a consultation.

How do I troubleshoot an EDI mapping error?

EDI-VAN finds and fixes mapping errors for you. Mapping means «fitting your company's data to the format your partner requires», and errors occur when the data and the format don't match. With the Custom and Dedicated plans, EDI-VAN supports format conversion. With the Dedicated plan, if a partner rejects a document or a document gets stuck during checking, EDI-VAN looks into it first and contacts you. All you need to do is send us the guide from your partner and the document that caused the error. If you prefer to do it yourself, the Self-service plan provides standard formats and guidance.

Why is my EDI transaction stuck in pending status?

When a document is stuck in pending status, there is usually a reason it could not move to the next step. Common cases are:

• It was held because it failed the check before sending
• It was delivered to your partner, but the 997 acknowledgment has not arrived yet
• There is a problem with your partner's channel

Registered customers can see the status of each document on screen. With the Dedicated plan, if a document fails a check or an acknowledgment is missing, EDI-VAN contacts you first. Why a specific document is stuck can only be determined by looking at its actual status, so please tell us through Contact us or at help@edi-van.com.

What causes EDI envelope or control number errors?

Envelope or control number errors mostly occur when the «outer wrapper» information of a document differs from what your partner expects. An envelope is the outer wrapper that holds several documents and states who is sending to whom. A control number is a sequence number used to check that no document is missing or duplicated. If a number is duplicated, or the sender or receiver information differs from what is registered, your partner may not accept the document. For documents sent through EDI-VAN, EDI-VAN handles this part for you. If errors keep occurring, let us know through Contact us and we will check it with you during the consultation.

What should I do when a trading partner stops accepting my EDI documents?

When a trading partner suddenly stops accepting documents, first check what changed on their side. In many cases the partner has changed their connection details or document rules, or their system has a temporary problem. Registered customers can view delivery, acknowledgment and error status on the EDI-VAN screen and see when the problem started. With the Dedicated plan, if acknowledgments are missing or the partner rejects documents, EDI-VAN contacts you first. If your partner has told you what changed, EDI-VAN will adjust to match their guide. If it is urgent, tell us right away at help@edi-van.com or through Contact us.

How do I fix missing item numbers in an EDI document?

Missing item numbers mostly occur because your company's item data and the item information registered with the retailer don't match, and they are resolved by aligning the data. EDI-VAN checks the format and content of documents before sending them, and tells you right away if there is a problem. Please check that the item list you registered with the retailer (item numbers, barcodes, etc.) is the same as the item data in your own system. Which item numbers the retailer requires is matched according to the guide that retailer sent. We can go over the specific error details with you on the operations screen or during a consultation.

Why are my units of measure causing EDI errors?

Unit errors occur because the units your company uses and the units set by the retailer are different. For example, if you manage items by «each» but the retailer orders by «case», the quantities and amounts won't match and the document may be rejected. When EDI-VAN fits your company's data to the format the retailer requires (mapping), it also reconciles these unit differences. Please prepare accurate packaging information for each item (such as how many pieces are in one case).

How do I validate EDI data before sending it?

Yes, you can. EDI-VAN checks the format and content of a document before sending it, and tells you first if there is a problem. Registered customers can see the documents they have sent and received, along with their status (delivered, acknowledged, error), on screen. Also, before a trading relationship goes live, test documents are exchanged from start to finish until everything matches, so most problems can be found before actual trading begins. EDI-VAN handles the detailed criteria used for these checks.

How do I resolve incorrect ship-to location errors in EDI?

Ship-to errors usually happen because the ship-to location written in the document does not match the list of stores and distribution centers set by the retailer. Each retailer indicates ship-to locations in its own way, so you match them against the guide and the ship-to list sent by that retailer. EDI-VAN checks the document content before sending and tells you if there is a problem. All you need to do is have the latest ship-to list from your retailer ready. We will review specific cases with you during a consultation.

How do I prevent repeated EDI errors from happening again?

To stop errors from repeating, you need to fix both the source data that caused them and the conversion rules. In the Customized and Dedicated plans, EDI-VAN supports format conversion, so if the cause is on the conversion side, EDI-VAN fixes it. If the cause is in your own data, such as items or ship-to locations, the data in your system needs to be corrected. When a retailer's rules change, EDI-VAN reflects the change, and in the Dedicated plan, EDI-VAN looks into rejections and missing acknowledgments first and contacts you.

How does the provider handle failed or rejected EDI documents?

For failed or rejected documents, EDI-VAN notifies you, and the way it responds depends on the service type. For all types, documents are checked for format and content before they are sent, and you are told if there is a problem.

• Direct and Customized: EDI-VAN responds to errors when you request it.
• Dedicated: EDI-VAN proactively finds problems such as missing acknowledgments or rejections by your trading partner and contacts you.

Registered customers can check the status of the documents they have sent and received (delivered, acknowledged, error) on screen themselves. The specific scope of response will be explained during a consultation via Contact us.

Who is responsible for monitoring EDI transactions after go-live?

Documents are exchanged automatically 24 hours a day without anyone needing to be present, and the scope of monitoring depends on the service type. All customers can see the documents they have sent and received, along with their status (delivered, acknowledged, error), on screen. In the Direct and Customized plans, you check the status yourself, and in the Customized plan, EDI-VAN responds to errors at your request. In the Dedicated plan, EDI-VAN looks first at things such as missing acknowledgments, rejections by the other party, and approaching deadlines, and contacts you first.

What disaster-recovery and business-continuity protections does the provider have?

Specific details about disaster recovery and business continuity are provided at the contract stage. Within what is publicly available, EDI-VAN is a closed network where only registered partners exchange documents, documents travel through an encrypted channel, and access and processing records are kept. Service-level figures such as uptime, and detailed measures, cannot be shared here. If you need them, please leave a Contact us inquiry and we will confirm them with you in a consultation.

How long does the provider retain transaction data?

The retention period depends on your plan. Based on our public information, documents you exchange and their records are kept for 1 year and then destroyed. The SCALE plan keeps them for 3 years. You can use the retained records to trace the documents you exchanged. If you need a longer retention period, we can check this with you during a consultation.

How does the provider protect EDI data in transit and at rest?

EDI-VAN documents travel through an encrypted channel inside a closed network where only registered partners exchange documents with each other. Each trading partner uses its own unique access credentials, and we keep access and processing logs. Exchanged documents are kept for the period set by your plan and then destroyed. For more detailed security information, such as how data is stored, we will provide guidance during a consultation or at the contract stage.

Does the EDI provider have independent security certifications or audit reports?

Whether we hold security certifications or audit reports is something we will confirm with you during a consultation. Within what we publicly disclose, we describe a closed network that connects only registered partners, an encrypted transmission channel, and the retention of access and processing logs. If your company has a list of materials required for its security review, please send it to us via Contact us or at help@edi-van.com. Our team will review it and get back to you.

What time zone should be used for international EDI timestamps to avoid date errors?

As a rule, follow the guide set by your trading partner (the retailer or distributor) for which time zone to use. In international trade, time zones differ by country and region, so if a date or time is off by a day, shipping and arrival schedules can appear to be wrong. When EDI-VAN converts your company's data into the format your partner requires, we also reconcile these differences. Which standard each trading partner uses is something we will confirm with you during a consultation, using that retailer's guide.

How do I manage cross-border EDI failures when our teams are in different time zones?

Even with time differences, documents are exchanged automatically 24 hours a day, and you can check progress on screen at any time. Registered customers can see the delivery, receipt confirmation, and error status of each document exchanged. Documents are checked for format and content before they are sent, and we notify you if there is a problem. With the dedicated-support option, EDI-VAN monitors situations such as missing receipt confirmations, rejections by the partner, and approaching deadlines, and contacts you first. Supported languages are Korean and English, and service levels such as support hours and response times are provided at the contract stage.

How secure are cloud-based EDI platforms?

EDI-VAN is a closed network where only registered partners exchange documents, so not just anyone can connect. Documents travel through an encrypted channel, and access logs and processing logs are kept. To start trading, you go through an inquiry, a consultation, and partner registration and testing. Document retention periods depend on your plan, and SCALE keeps documents for 3 years. Internal information, such as server and software configuration, is not disclosed.

Can AI automatically create EDI mapping rules?

Mapping (the work of reshaping your company's data into the format your trading partner requires) is handled by EDI-VAN under the Custom and Dedicated plans, so you do not need to build the rules yourself. We do not disclose which tools or technologies are used for this work. If you choose the Direct plan, you receive the standard X12 and EDIFACT formats along with guidance, and you can do the conversion yourself. Whether a separate AI auto-mapping feature exists can be confirmed in a consultation.

Can AI or machine learning detect errors and predict failed EDI transactions?

EDI-VAN checks the format and content of a document before sending it, and notifies you right away if there is a problem. We do not disclose which technology is used for these checks. Under the Dedicated plan, EDI-VAN watches for cases where an acknowledgment does not arrive, the partner has rejected a document, a file that normally arrives is missing, or a deadline is approaching, and contacts you first. The best way to reduce errors is to test thoroughly before opening a trading relationship.

Who is responsible when an EDI error occurs?

The scope and limits of responsibility are set by the terms of your contract and will be explained at the contract stage. The roles are divided as follows. EDI-VAN handles format conversion, delivery to the partner's channel, acknowledgment of receipt, and problem notifications. The customer prepares the original data that goes into the documents and handles development inside the customer's own ERP. For details, please leave a Contact us request.

How is EDI security managed?

EDI-VAN is a registration-based closed network, in which only registered partners exchange documents with each other. Documents travel through encrypted channels, and access logs and processing logs are kept. Registered customers can check the documents they have exchanged and their status directly on screen. The document retention period varies by plan; SCALE retains documents for 3 years.

What happens if an EDI order fails or an invoice is rejected?

When a problem occurs, an error or the partner's rejection status is shown on screen, and EDI-VAN notifies you. How we respond depends on the service type.

• Direct and Custom plans: EDI-VAN works with you on the response when you request it.
• Dedicated plan: EDI-VAN finds rejections and missing acknowledgments first and contacts you.

Because retailers may charge fees when documents are late or incorrect, we recommend that you test thoroughly before opening the trading relationship.

Who owns EDI support after go-live?

EDI-VAN continues to support operations after go-live, and the scope of support depends on the service type. On every plan, you can view documents and their status (delivery, acknowledgment of receipt, errors) on screen, and documents are exchanged automatically 24 hours a day.

• Direct and Custom plans: EDI-VAN responds to errors during operation when you request it.
• Dedicated plan: EDI-VAN monitors first and, if it sees a problem, contacts you first.

You can compare the differences between plans on the pricing page.

What alerts and exception monitoring should be set up for failed or delayed EDI documents?

Registered customers can see the delivery, acknowledgment, and error status of each document right on the screen. If EDI-VAN finds a problem in its pre-send check, it will let you know. With the managed service, EDI-VAN watches for missing acknowledgments, rejections by your trading partner, files that normally arrive but are missing, and approaching deadlines, and contacts you first. We can go over how alerts are delivered and how you can choose who receives them in a consultation.

What should you do when an 850 or 856 fails in production?

If a problem comes up in production, first check the document's status on the screen, then ask EDI-VAN to help. The 850 purchase order is a document you receive, and the 856 ship notice (a document that tells your partner in advance what was shipped and how, before the goods arrive) is a document you send. For both documents, EDI-VAN handles format checking, delivery, and acknowledgment. With the managed service, EDI-VAN looks for rejections by your partner and missing acknowledgments first and contacts you. The 856 is an especially tricky document, so we recommend testing it thoroughly before you go live with a partner.

Who should own an EDI issue: the retailer, the provider, or your internal team?

The exact scope of responsibility depends on your contract terms and is explained at the contract stage. In general, roles are divided like this:

• Retailer: sets the document requirements (the guide).
• EDI-VAN: handles conversion, delivery, acknowledgment, and problem alerts based on that guide.
• Your team: prepares accurate source data and handles development inside your ERP (your ERP vendor or IT staff).

If a problem occurs, EDI-VAN will work with you to identify the cause based on the records on the screen.

How do you decide when and how to escalate recurring or urgent EDI issues?

If the same problem keeps happening, send it through the Contact us form or to help@edi-van.com, and a team member will review it and get back to you. You can also reach us via KakaoTalk channel in Korea or WhatsApp outside Korea. With the managed service, EDI-VAN looks into problems first and contacts you first. The step-by-step handling process and service levels such as response times are explained at the contract stage.

What daily reports should an EDI coordinator review?

What to check every day is the documents sent and received, and their status (delivery, acknowledgment, error) shown on the EDI-VAN screen. Registered customers can see how far each document has progressed. It helps to look at these three things first:

• Documents you sent for which the 997 acknowledgment (a reply confirming the document was received properly) has not arrived yet
• Documents your partner rejected or that stopped because of an error
• 856 ship notices and 810 invoices with approaching deadlines

With the managed service, EDI-VAN watches for these situations first and contacts you first. We can show you the screen layout in detail in a consultation.

How do you keep EDI orders from getting stuck in a queue or delayed overnight?

If an order stalls or is late, first check the document's status (delivery, acknowledgment, error) on the EDI-VAN screen. EDI-VAN checks the format and content of documents before sending them and lets you know if there is a problem. If you don't know the cause or it is urgent, send the document and trading partner name to help@edi-van.com or the KakaoTalk channel (WhatsApp outside Korea), and we will check it with you. With the managed service, EDI-VAN finds delays and missing documents first and contacts you. Service levels such as response times are explained at the contract stage.

How do you train a new EDI coordinator?

We go over the specifics of training a new coordinator in a consultation. EDI-VAN's web entry screens are built so that no developer is needed, so a new coordinator can start by learning how to check document status and how to get in touch when a problem comes up. If you also build an EDI ERP with us, staff training is included in the basic plan. Please tell us what training scope you need through Contact us.

What skills does someone need to manage EDI operations?

For someone managing EDI operations, knowing your own company's order, shipping, and billing flow matters more than technical knowledge. In the Custom and Dedicated plans, EDI-VAN handles technical work such as format conversion. Useful skills include:

• Understanding what each of these is: 850 purchase order, 855 purchase order acknowledgment, 856 advance ship notice, 810 invoice, and 997 functional acknowledgment
• Knowing the requirements and deadlines in the guides sent by your trading partners (retailers)
• Being careful about checking that order, shipment, and invoice quantities match
• Communicating quickly: when you see a problem, tell EDI-VAN and your internal contact right away

How do you document EDI procedures, partner requirements, and a support runbook?

The key to a procedure document is to set out who sends which document, for which trading partner, by when, and who to notify if something goes wrong. It is generally organized like this:

• The types of documents exchanged with each trading partner and their deadlines
• What to check every day (missing 997 acknowledgments, documents with errors or rejections)
• Where the retailer guides are stored, and a record of what has changed
• Contacts for when a problem occurs (help@edi-van.com, etc.) and your internal contact

EDI-VAN handles its own side of the processing, so your document only needs to cover your internal work and contact flow.

How do you handle an EDI outage during business hours?

If you suspect an outage, first check on the EDI-VAN screen which documents have stopped and in what status, then notify EDI-VAN right away. You can reach us at help@edi-van.com, through the KakaoTalk channel in Korea, or on WhatsApp overseas. Including the trading partner name, document type, and time will speed up the check. With the Dedicated plan, EDI-VAN finds the problem first and contacts you. Service-level figures such as response times are provided at the contract stage.

What is the best way to reduce manual follow-up in EDI operations?

You can greatly reduce manual follow-up with automatic checks and automatic integration.

• 997 acknowledgments are recorded automatically, so you don't have to phone to ask whether the other side received a document
• Before sending, EDI-VAN checks the format and content and tells you if there is a problem
• Using automatic file transfer (SFTP) or system integration (API) instead of web entry removes the need to retype data
• With the Dedicated plan, EDI-VAN watches for missing 997s, rejections, and approaching deadlines first and contacts you

We will decide together with you in a consultation which approach fits.

What are the most common mistakes in daily EDI processing?

Most common mistakes in daily processing come down to being late and mismatches.

• Sending the 856 advance ship notice late, or leaving it out
• Order, shipment, and invoice quantities not matching
• No 997 acknowledgment arriving, and moving on without checking
• Missing that a retailer guide has changed

Retailers may charge fees when documents are late or wrong, so we recommend testing thoroughly before going live and checking status every day.

How do I make sure the barcode on the label scans correctly?

For a barcode to scan well, use the standard box label specified by the retailer as-is, print it clearly, and make sure the label number matches what you sent in the 856 ship notice. Detailed requirements such as label size and placement differ by retailer, so follow the guide that retailer has sent you. EDI-VAN sends the ship notice containing the box numbers according to the retailer's rules, and if you use the warehouse management (WMS) module of EDI ERP, you can handle barcode receiving, packing and shipping on a single screen. We will confirm printing equipment and label printing methods in a consultation.

What are common GS1-128 label printing mistakes?

With GS1-128 (the international standard number label attached to each box, also known as UCC-128), a common mistake is when the label number and the 856 ship notice do not match. Other common problems include:

• Reusing the same number on a different box
• Printing that is blurry or cut off and cannot be read
• Applying the label in a position or format different from what the retailer specified

Follow the retailer's guide for detailed specifications. We will confirm the printing method in a consultation.

What are common problems in EDI operations?

There are four main problems that come up often during operations:

• The 997 acknowledgment does not arrive
• A trading partner rejects a document
• Ship notices or invoices are late or the quantities do not match
• A retailer changes its rules

EDI-VAN checks documents before sending and tells you if there is a problem, and when a retailer changes its rules, EDI-VAN applies the changes. With the dedicated plan, we find these problems first and contact you.

What is the best way to handle duplicate EDI 214 messages?

Even if duplicate 214 transportation status messages (documents that report pickup, in transit, arrival and delivery complete) come in, there is no charge because they are received documents. The same status arriving multiple times often originates in the carrier's system. How to identify and clean up duplicates depends on the trading partner and your system, so we will confirm this in a consultation. If you have an actual case, please send it to help@edi-van.com or use Contact us, along with the name of the trading partner involved.

How do I know if the issue is in mapping or partner setup?

EDI-VAN takes care of identifying the cause. You do not need to work it out yourself. Mapping is the work of fitting your company's data to the format the other party requires, and partner setup is the connection information used to exchange documents with the other party. Registered customers can see the delivery, acknowledgment and error status of each document on screen, and EDI-VAN notifies you if a problem occurs. With the custom plan, EDI-VAN responds to errors when you request it, and with the dedicated plan, EDI-VAN checks first and contacts you first. With the direct plan, you handle format conversion yourself, so you also handle much of the problem checking yourself.

What causes EDI acknowledgments to fail timing requirements?

When a 997 acknowledgment (a reply confirming that a document was received) is late, the cause is mostly on the other party's side or in the delivery process. For example, the other party's system may process documents in batches, there may be a temporary problem with the connection, or the other party may not have accepted the document. Registered customers can see on screen, for each document, whether it was delivered and whether an acknowledgment has arrived. With the dedicated plan, EDI-VAN finds missing acknowledgments first and contacts you, and with the custom plan, we help you check the cause when you request it. The reply time set by the other party follows the guide that retailer has sent you.

How often does the provider back up EDI data?

We have not published a specific backup frequency; we can confirm it in a consultation. Here is what we do publish: we keep records of the documents you exchange and of access and processing activity, and the document retention period depends on your plan (SCALE keeps documents for 3 years). If you need detailed backup terms, please describe your requirements in a Contact us inquiry. We will go over them with you at the contract stage.

Can we retrieve archived EDI documents quickly for audits?

Yes, documents within the retention period can be viewed on screen. Registered customers can see the documents they have exchanged and their status (delivered, acknowledged, error) on screen, and access and processing records are also kept. The retention period depends on your plan; SCALE keeps documents for 3 years. If you have a specific audit period or a required way of submitting materials, we can confirm the right plan and method in a consultation.

Where is our EDI data stored?

We do not disclose server locations or system configuration, and we appreciate your understanding. Here is what we do publish about security: EDI-VAN is a closed network where only registered partners exchange documents, documents travel over encrypted channels, and access and processing records are kept. If your company or your trading partners have requirements about where data is stored, please describe them in a Contact us inquiry. We will confirm them during consultation and at the contract stage.

How should an international EDI system handle daylight-saving-time changes?

Documents are exchanged automatically 24 hours a day, even when no one is present, so exchange itself does not stop when daylight saving time changes. However, how to align the time reference used in documents or deadline times can differ by trading partner. We follow the guide provided by the retailer for this. We can confirm how each trading partner handles it in a consultation.

What happens when an EDI acknowledgment arrives outside the buyer's business hours?

Usually this is not a problem. EDI documents and acknowledgments (997) are exchanged automatically between systems 24 hours a day, even when no one is present, so they are recorded regardless of the buyer contact's working hours. You can check received documents and acknowledgments on screen at any time. However, if the retailer has set its own criteria, such as a processing cutoff time, we follow that retailer's guide.

How are EDI logs and audit trails kept?

EDI-VAN automatically keeps access records and processing records, so there is nothing you need to set up. Registered customers can see the documents they have exchanged and the status of each document (delivered, acknowledged, error) on screen, which lets you trace the step at which something stopped. The document retention period depends on your plan; SCALE keeps documents for 3 years. If you have requirements for audit readiness, we can go over them with you in a consultation.

Do I need to hire someone to monitor EDI every day?

In most cases, you do not need to hire a dedicated person just for EDI. Documents are exchanged automatically 24 hours a day, you can check their status on screen, and EDI-VAN will notify you if a problem occurs. With the Custom plan, EDI-VAN responds to errors when you request it. With the Dedicated plan, EDI-VAN looks into things like missing acknowledgments, rejections by your trading partner, and approaching deadlines first, and contacts you first. However, your own staff will still need to handle company decisions, such as whether to accept an order or confirm a shipment.

How do you track open EDI incidents and follow up on them?

Each document keeps its status on screen, so you can follow open issues there. Statuses are shown as delivered, acknowledged, or error. Documents are checked for format and content before they are sent, and EDI-VAN notifies you if there is a problem. With the Custom plan, EDI-VAN responds when you request it, and with the Dedicated plan, EDI-VAN finds issues first and contacts you. Service levels such as response times are explained at the contract stage.

What is the best way to prioritize multiple EDI errors at once?

In general, start with the errors that directly affect the transaction. For example, documents with a retailer-set deadline coming up, or documents the other party has not accepted, come first. This is because retailers may charge fees when documents are late or incorrect. Registered customers can see all documents with errors at a glance on screen, and EDI-VAN notifies you of problems. With the Dedicated plan, EDI-VAN looks into missing acknowledgments, rejections by your trading partner, and approaching deadlines first, and contacts you, so you don't have to worry about deciding where to start.

How much EDI knowledge does a customer service or operations team need?

You don't need deep technical knowledge. The following two things are enough:

• What the main documents mean: 850 Purchase Order, 855 Purchase Order Acknowledgment, 856 Advance Ship Notice, 810 Invoice, 997 Functional Acknowledgment
• How to read document statuses (delivered, acknowledged, error) on screen

Technical work such as format conversion and connection setup is handled by EDI-VAN in the Custom and Dedicated plans. With the Direct plan, you handle format conversion and testing yourself, so more understanding is needed. Support is available in Korean and English.

How do you communicate EDI changes to internal teams?

Because all trading documents and their statuses are kept on the EDI-VAN screen, you can use this screen as the basis for sharing information within your company. Registered customers can see the documents they have sent and received, along with their statuses (delivered, acknowledged, error), on screen. When a retailer's rules change, EDI-VAN applies the changes, so your own way of working does not change much. With the Dedicated plan, EDI-VAN looks into problems such as approaching deadlines or rejections by your trading partner first and contacts you. How to give several people in your company access to the screen, and how you receive notifications, are confirmed in a consultation.

How do you track SLA performance for EDI transactions?

You can check whether EDI transactions meet the agreed times and rules through the document statuses on screen. With the Dedicated plan, EDI-VAN monitors this for you. The screen shows each document's status (delivered, acknowledged, or error), so you can immediately see where something is delayed or stuck. With the Dedicated plan, EDI-VAN looks into problems such as missing acknowledgments, rejections by your trading partner, and approaching deadlines first, and contacts you first. EDI-VAN's own service levels (such as uptime and response times) are explained at the contract stage.

How do I print labels for partial shipments or backorders?

Labels for partial shipments or backorders must be printed according to the rules in the guide issued by that retailer. The exact printing method depends on the system you use, and we will confirm it with you in a consultation. Labels are printed from your own warehouse or shipping system, and EDI-VAN converts the matching 856 Advance Ship Notice into the retailer's format and delivers it. If you don't have a system, you can also consider the barcode shipping function of EDI ERP or the WMS logistics module (packing and shipping). The 856 Advance Ship Notice is the most demanding document because the carton and pallet information must match the labels, so we recommend testing thoroughly before going live.

Who can see and access our EDI data on a cloud EDI platform?

EDI-VAN is a closed network where only registered trading partners exchange documents with each other. Documents are delivered only to the trading partner who is meant to receive them. Documents travel over an encrypted channel, and access and processing logs are kept. Registered customers can view the documents they have sent and received, and their status, directly on screen. For detailed criteria on who accesses what scope during operations, we will confirm with you in a consultation.

Do you support message-level encryption for EDI, and who can decrypt the messages?

On EDI-VAN, documents travel over an encrypted channel and are exchanged only between registered partners. For example, AS2 is a method of exchanging encrypted documents directly over the internet, so only the intended recipient can decrypt and read a document. EDI-VAN handles the encryption-related settings. If you need each document to be encrypted individually, or need to divide decryption permissions in detail, we will confirm with you in a consultation.

How long are EDI messages retained by default?

The retention period for exchanged documents and records depends on your plan. Under the default terms published on the site, they are kept for 1 year and then destroyed. The SCALE plan keeps them for 3 years. If you need longer retention, we will confirm with you in a consultation.

Can we set custom retention and deletion rules for EDI files by document type?

A feature for setting retention or deletion periods by document type is not described in our public materials, so we will confirm with you in a consultation. Currently, the retention period depends on your plan. The default is 1 year of retention followed by destruction, and the SCALE plan keeps documents for 3 years. If you list the document types and periods you need in your Contact us request, we will review it and get back to you.

How do you handle EDI data retention for compliance audits?

Whether records can be kept for the period your audits require is something we will confirm with you in a consultation. The published retention period depends on your plan. The default is 1 year, and the SCALE plan is 3 years. EDI-VAN also keeps access and processing logs. If you list the retention period you need and the documents concerned in your Contact us request, we will work out the approach together with you.

Can trading partners view each other's EDI data on the same platform?

No, other trading partners cannot see your documents. EDI-VAN is a closed network where only registered partners exchange documents with each other. Each document is delivered only to the trading partner who is meant to receive it. In addition, each trading partner uses its own unique access credentials, and documents travel through an encrypted channel.

How does role-based access control work in EDI?

The details of how permissions are assigned per user on the EDI-VAN screen are not described in the public materials, so we will confirm them in a consultation. For reference, if you also build an EDI ERP, user permission management is included in the basic version. If you tell us which roles you need (for example, order handler or invoice handler) when you contact us, we will guide you accordingly.

Does the EDI service support MFA for user logins?

Whether the EDI-VAN screen login supports two-step authentication (MFA) is not described in the public materials, so we will confirm it in a consultation. The security features currently described are these three: it is a closed network used only by registered partners, each trading partner uses its own unique access credentials, and access and processing records are kept. If you have security requirements, please include them when you contact us.

Can we restrict EDI access by IP address or network?

Whether access can be limited to specific IP addresses or your internal network is something we will confirm in a consultation. EDI-VAN is a "closed network" where only registered partners exchange documents with each other. Each trading partner uses its own unique access credentials, and documents travel through an encrypted channel. If your company has an access restriction policy, please include it when you contact us. A representative will confirm which methods are possible.

Is EDI data ever shared with subcontractors or third parties?

Documents are delivered only to the trading partners you have registered. EDI-VAN is a closed network where only registered partners exchange documents with each other. However, if your trading partner uses another network (a VAN, such as a mailbox service that receives documents on its behalf and forwards them), your documents are delivered to that partner through that network. Detailed criteria on other data processing outsourcing or provision to third parties will be explained in the privacy policy and at the contract stage. If you have questions, please contact us.

Are EDI backups encrypted, stored offsite, and regularly tested?

How backups are encrypted, stored offsite, and recovery-tested is something we will confirm in a consultation. Within what is publicly stated: documents travel through an encrypted channel, and access and processing records are kept. The document retention period depends on the plan, and the SCALE plan retains documents for 3 years. If your company has security checklist items, please send them along when you contact us.

How quickly are deleted EDI files removed from backups?

The point at which files are fully removed from backups is confirmed during a consultation. How long exchanged documents and records are kept depends on your plan. The standard policy is to keep them for 1 year and then destroy them, and the SCALE plan keeps them for 3 years. The detailed criteria for deletion and destruction are explained at the contract stage, so please leave a request through Contact us.

What happens to EDI data if the system goes down?

For each document, you can check on screen whether it was delivered and whether the other party received it, so you can find documents that have stalled. Registered customers can see the status of the documents they exchange (delivered, receipt confirmed, error) on screen. The 997 acknowledgment is a confirmation reply from the other party saying they received the document, so a document without this reply is treated as not having arrived. With the dedicated-support option, if an acknowledgment is missing, EDI-VAN looks into it first and contacts you. The detailed way incidents are handled is confirmed during a consultation.

What notifications do we get if the EDI service is interrupted?

If a problem occurs, EDI-VAN will let you know. However, the channel used to announce a service interruption is explained at the contract stage. Registered customers can see document status (delivered, receipt confirmed, error) directly on screen. With the dedicated-support option, EDI-VAN looks into problems such as missing acknowledgments or rejections by the other party first and contacts you. If you have a preferred notification method, please write it in Contact us.

What business continuity and disaster recovery plans do you have for EDI?

The details of the disaster recovery and business continuity plans are explained at the contract stage. Within what has been made public: documents are exchanged automatically 24 hours a day, and access and processing records are kept. How long documents are kept depends on your plan. If your company has security or continuity checklist items, please send them through Contact us.

What is your incident response process for EDI security breaches?

The security incident response process is explained at the contract stage. EDI-VAN is a closed network where only registered parties exchange documents, and documents travel through an encrypted channel. Access and processing records are also kept. If there are specific items you would like to check, please leave them through Contact us.

What happens if a trading partner is compromised?

EDI-VAN is a closed network that connects only registered parties, and each trading partner uses its own unique access credentials. Documents travel through an encrypted channel, and access and processing records are kept. Also, documents are checked for format and content before they are sent, and you are notified if there is a problem. The specific response if a trading partner is hacked is confirmed during a consultation.

Can you provide a SOC 2 report or your security policies for EDI?

Whether we can provide a SOC 2 report or security policy documents is confirmed during a consultation. Here is what we can say from our public information: EDI-VAN is a closed network where only registered partners exchange documents with each other. Documents travel through encrypted channels, and access and processing records are kept. If your company has its own security review form, please send it through Contact us or to help@edi-van.com.

Is your EDI platform GDPR compliant, and do you sign a data processing agreement?

GDPR compliance and signing a data processing agreement (DPA) are confirmed during consultation and the contract stage. We do not include contract terms in our public information; they are provided separately at the contract stage. The security points we have made public are as follows: it is a closed network where only registered partners exchange documents, documents travel through encrypted channels, and access and processing records are kept. If you trade with European partners, please tell us the documents and requirements you need through Contact us or help@edi-van.com.

How do you protect personal data in EDI messages?

Personal data in EDI messages is protected by a closed network and encrypted channels. EDI-VAN is a "registration-based closed network" where only registered trading partners exchange documents. Each partner uses its own unique access credentials. Documents travel through encrypted channels, and we keep records of who accessed the system and what was processed. Exchanged documents are destroyed once the retention period for your plan has passed (1 year by default, 3 years for SCALE). If you need more detail on how data is protected, we can confirm it in a consultation.

Can EDI logs or exception files expose sensitive data, and are they encrypted?

How sensitive information in logs or error files is handled is confirmed during a consultation. What we can state publicly is this: registered customers see on screen only the documents they have exchanged and their status (delivered, receipt confirmed, error). The system keeps access and processing records, and documents are destroyed after the retention period. Details such as how specific information is masked in error files are not in our public materials. Please leave your requirements through Contact us or help@edi-van.com.

How do you prevent unauthorized access to archived EDI files?

Archived EDI files are protected so that only registered parties can access them. EDI-VAN is a registration-based closed network that not just anyone can enter. Each partner uses its own unique access credentials, and customers can see only their own documents on screen. Access and processing records are kept. Documents are destroyed after the retention period (1 year by default, 3 years for SCALE). The detailed standards for internal access control are provided during the consultation and contract stage.

Can EDI files be tampered with in transit, and do you use digital signatures to verify integrity?

Documents travel through encrypted channels, which are designed to prevent tampering in transit. For example, we use AS2 (a method of exchanging encrypted documents directly over the internet) or SFTP (automated encrypted file transfer). When the other party receives a document, a 997 acknowledgment (a reply confirming "the document was received properly") is returned. This lets us check every time that a document arrived, and we notify you if a problem occurs. You can trace the records of exchanged documents on screen.

What security standards do you use for AS2 and SFTP?

All AS2 and SFTP connections use an encrypted channel and connect only with registered partners. Each trading partner uses its own unique access credentials. If your trading partner (retailer) has security requirements, we follow the guide that retailer provides. We do not disclose specific settings or methods for security reasons. EDI-VAN handles the connection work for you. We will review your trading partner's requirements with you during the consultation.

How do you manage certificate rotation for EDI connections?

Who handles certificate renewal, and on what schedule, is confirmed during the consultation. A certificate is like an «electronic ID card» used to verify each other's identity and open an encrypted channel. If it expires, the connection can be cut off, so it needs to be managed. EDI-VAN handles the connection work of delivering documents through the channel your partner requires. However, we do not disclose renewal procedures or settings. Please tell us your trading partner and current connection method through Contact us.

How do you monitor suspicious access to EDI data?

EDI-VAN keeps access and processing records, and the specific monitoring methods are confirmed during the consultation. It is a closed network that only registered partners can enter, and each trading partner uses its own unique access credentials. With the Dedicated type, EDI-VAN looks for irregularities in the document flow, such as a missing acknowledgment or a rejection by the partner, and contacts you first. However, we do not disclose the criteria we use for security-related access monitoring. Please send your requirements through Contact us or to help@edi-van.com.