# EDI Program Health Assessment > Source: https://netray.co/tools/edi-program-health-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Score how well your EDI operation is monitored, documented and resilient, and see where to start fixing. ## Category supply-chain ## Audience - EDI coordinator - Supply chain manager - IT manager ## Tool **Kind:** assessment **Questions:** #### How do you find out that an inbound order did not arrive? **Options:** ##### A customer calls us **Score:** 0 ##### Someone notices during daily review **Score:** 1 ##### We compare orders received to ERP counts each day **Score:** 2 ##### Automatic alerts for missing or failed documents **Score:** 3 #### How are 997 acknowledgments handled? **Options:** ##### Not tracked **Score:** 0 ##### Checked when someone remembers **Score:** 1 ##### Matched to documents in a log or report **Score:** 2 ##### Matched automatically with alerts on missing or rejected ones **Score:** 3 #### How is trading partner information documented? **Options:** ##### In people's heads or old emails **Score:** 0 ##### Scattered files and spreadsheets **Score:** 1 ##### One register with IDs, qualifiers and contacts **Score:** 2 ##### A register that also drives the translator configuration **Score:** 3 #### How do you handle a mapping error on a live document? **Options:** ##### Retype it in the ERP **Score:** 0 ##### Fix it ad hoc and resend **Score:** 1 ##### Documented procedure with owner and log **Score:** 2 ##### Documented, logged, with root cause tracking and map fix **Score:** 3 #### How are new trading partners onboarded? **Options:** ##### Informally each time **Score:** 0 ##### Reused from a previous partner by memory **Score:** 1 ##### Checklist and test plan **Score:** 2 ##### Checklist, test plan, templates and sign-off recorded **Score:** 3 #### How do you track retailer or customer chargebacks? **Options:** ##### Finance deals with them when invoices arrive **Score:** 0 ##### We see them but do not trace causes **Score:** 1 ##### Logged by cause and partner **Score:** 2 ##### Logged, disputed on time, and trends feed fixes **Score:** 3 #### How is access to the translator and certificates managed? **Options:** ##### Shared accounts, no expiry tracking **Score:** 0 ##### Named users but no expiry tracking **Score:** 1 ##### Named users and a certificate calendar **Score:** 2 ##### Named users, calendar, and tested key rotation **Score:** 3 #### What happens when the EDI person is out? **Options:** ##### Documents wait **Score:** 0 ##### Someone guesses **Score:** 1 ##### A backup knows the main tasks **Score:** 2 ##### Runbooks and a trained backup **Score:** 3 #### How current are your maps relative to partner guides? **Options:** ##### Unknown **Score:** 0 ##### Some guides are lost or outdated **Score:** 1 ##### Guides stored and reviewed on change **Score:** 2 ##### Guides versioned and linked to each map **Score:** 3 #### How do you test a map change before production? **Options:** ##### We do not **Score:** 0 ##### One sample document **Score:** 1 ##### A set of samples reviewed by a second person **Score:** 2 ##### Regression samples run on every change with partner test when needed **Score:** 3 **Bands:** #### Reactive **Min:** 0 **Max:** 30 **Verdict:** EDI works until something breaks, and then the fix depends on one person. Risk of lost orders and chargebacks is high. **Recommendations:** - Start a single partner register with IDs, qualifiers, contacts and guides. - Add a daily check of orders received versus the ERP. - Log every failed document and its cause for one month. #### Partly controlled **Min:** 31 **Max:** 60 **Verdict:** Basic habits exist but gaps remain in monitoring, testing and coverage when people are away. **Recommendations:** - Match 997s to documents and alert on missing ones. - Write runbooks for the three most common failures. - Introduce a test sample set for map changes. #### Managed **Min:** 61 **Max:** 85 **Verdict:** The program is documented and monitored. Focus on trends, chargebacks and reducing manual intervention. **Recommendations:** - Analyze rejects by cause and fix the top maps. - Track chargeback causes and dispute deadlines. - Rehearse manual fallback and certificate rotation. #### Resilient **Min:** 86 **Max:** 100 **Verdict:** The program has strong controls. Keep guides and tests current as partners change requirements. **Recommendations:** - Review partner guide versions each quarter. - Look at automation for onboarding and monitoring. - Share runbooks with the wider supply chain team. ## Content **Intro:** EDI programs rarely fail on one big event. They fail on missed acknowledgments, stale maps and one overloaded person. This assessment scores ten practical areas so you can see where the weak points are. **Sections:** #### How to use it **Body:** Answer for the situation as it is today, not as it should be. If you manage several partners, answer for your typical partner or run the assessment twice, for the best and the worst one. Each answer scores from 0 to 3, and the total is shown as a percentage band with suggested next steps. #### What the questions look at **Body:** The questions cover detection of failures, acknowledgment handling, documentation, error procedures, onboarding, chargebacks, access and certificates, key person risk, map currency and testing. These are areas where small habits, such as a daily count comparison or a certificate calendar, remove most of the surprises. **Bullets:** - Detection: do you know before the customer does? - Documentation: could someone else take over? - Testing: can a map change break a partner? - Cost: are chargebacks linked to causes? #### Reading your result **Body:** A low score does not mean EDI is broken. It means there is little protection if something goes wrong. Pick the two lowest scoring questions and fix them first, because a daily reconciliation and a partner register typically remove the largest share of manual firefighting. Revisit the assessment after a quarter and compare. **Cta:** Netray can review your EDI setup and suggest where monitoring, matching of acknowledgments to ERP documents, or an assistant for exceptions would help, with no obligation. **Faq:** #### Is this assessment specific to X12? **Answer:** No. The questions apply to X12, EDIFACT and other B2B formats, including AS2 and SFTP connections. They are about operations and controls rather than a specific standard. #### Does a high score guarantee compliance? **Answer:** No. It shows that your program has good habits. Partner compliance depends on each guide and scorecard, so keep checking those separately. #### Who should fill it in? **Answer:** The person who runs EDI day to day, ideally with their manager. Different answers from the two of them are useful, because they show where documentation is missing. #### How often should I repeat it? **Answer:** Quarterly is enough for most teams, or after a new major partner, a translator change or an ERP upgrade. ## Search terms edi maturity assessment, edi health check, edi program assessment, edi self assessment, edi operations review, edi monitoring checklist, b2b integration assessment, edi audit questions --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json