Enhance ERN Notifications to Deliver Complete and Precise Error Information
Priority
High
Ask
• Enhance ERN emails to include detailed error information (segment, element, position, envelope details, etc.) exactly as shown in the Translation Report, instead of generic messages such as “Invalid input file, modify the input file and resend the file,” “No matching envelope found,” or “Input file structure does not match the map in use.” We can include three clear pointers in ERN emails — where, why, and fix — so the trading partners/customers receives all the required information needed to resolve the issue independently, without reaching out to support, using only these three pointers.
Details of Ask
Current Behavior:
ERN notifications provide only generic guidance such as:
• Invalid input file
• Input file structure does not match the map
• No matching envelope found
• Input file structure does not match the map in use
This does not help customers identify the actual cause of the error, understand how to resolve it, or determine where and why the error is occurring.
Requested Enhancement:
Include the same detailed error information available in the Translation Report within the ERN notification, along with three clear pointers — where, why, and fix — so the customer receives clear guidance on how to resolve the issue independently.
Example (currently visible only in Translation Report):
****INPUT ERROR: Conditional Relationship Error****
Block Count: 6
Map Iteration Count: 1
Block Name: IT1
Block Signature Id Tag: IT1
Field Name: 0358
Field Number: 2
Element Position: 2
Subelement Position: -1
Location Index: 02
Proposed ERN should display:
• Segment/Block Name (IT1)
• Field Name & Number (0358 / 2)
• Element & Sub-element position
• Error type (Conditional Relationship Error / Mandatory Data Missing)
• Location Index
Where: (Shows the exact location of the error (segment, field/element, envelope details, etc.)
• Error occurs at IT1 segment, Field 0358, Element Position 2, Location Index 02
Why: (Explains the reason for the error (missing data, rule failure, envelope mismatch, etc.)
• Conditional Relationship rule failed due to missing or invalid data in required field
Fix: (Indicates what needs to be corrected so the file can be successfully reprocessed.)
• Populate or correct IT1 element 0358 in input file as per map requirement and resend document
This will allow customers to receive actionable error context directly in the notification email, enabling them to clearly understand how to resolve the error independently after reading the message, without requiring guidance from the support team.
Impact to Clients
• Customers/TPs currently receive ERN messages stating generic errors such as “Invalid input file,” “Matching envelope not found,” “Input file structure does not match the map in use,” etc. There are also many other error types for which ERN notifications are sent, but they do not provide enough information for customers to resolve the issue on their own. Customers are not informed about:
– which segment failed
– which field is missing
– the sender ID and receiver ID of the missing envelope
– the exact reason for the failure (conditional relationship error, mandatory data missing, envelope mismatch, etc.)
• This lack of detail delays business transactions and partner processing.
Impact to Support
• When customers request support guidance for ERN notifications, Support teams must manually:
– Open the Translation Report
– extract segment, element, and envelope details
– re-explain the issue to the customer
• This increases handling time for simple mapping, envelope, and other common errors.
Current Challenge
• Translation Report contains correct technical error details
• ERN notification hides this information
• Customers only see generic error text and cannot self-troubleshoot
• Support becomes a mandatory middle layer for basic error interpretation
Use Case
• Customer raised case TS021432072
• Customer had to reach out to support for finding the reason behind this failure for which ERN was triggered.
