In modern B2B integrations, maintaining data accuracy and operational efficiency is critical. One of the key decisions EDI B2B Manager users face is how to handle inbound/export files—whether to process only fully valid files or allow partial processing when some records fail validation.
This article explores both approaches and how they can be effectively implemented using the Process parsed data option in EDI exports/listeners.
EDI transactions often contain multiple records within a single file. The records may represent orders, invoices, shipment notices, or other business documents. However, at times some EDI files might have invalid records due to reasons, such as:
-
Missing mandatory fields
-
Incorrect formatting
-
Business rule violations
-
Partner-specific data inconsistencies
The decision then becomes whether to' process: the entire file only, or valid records and ignore the invalid records in the file, based on compliance terms with Trading Partners and frequency of the issues.
In this approach, the system processes a file only if all records pass validation. If even a single record fails, the entire file is rejected.
This approach helps to:
-
Avoid any process complexities as all files are processed consistently
-
Simplify reconciliation and makes it easier to track file-level success or failure
But, you might need to consider:
-
Processing delays due to holding back valid records along with the invalid ones
-
Operational overhead because it requires correction and reprocessing of entire files
This approach could be useful in:
-
High-compliance industries (for example., healthcare, finance)
-
Critical transactions, where partial data is unacceptable
-
Strict partner agreements that require full file validation
In this model, valid records are processed while only invalid ones are separated for error handling and processing. When an EDI file has multiple transaction sets ( STs in the case of X12, and UNHs in the case of EDIFACT ); then, if at least one transaction set or more are valid, the partial processing will pass the valid STs or UNHs to the next step , ignoring the invalid ones.
This approach helps to:
-
Ensure that valid transactions are not delayed for faster processing
-
Reduce backlog in high-volume environments for improved throughput
-
Provide a better partner experience by timely execution of valid records
But, you might need to consider:
-
Tracking failed records separately
-
Complexity in reconciliation by separately managing processed and rejected records
This approach could be useful in:
-
High-volume EDI environments
-
Scenarios where partial fulfilment is acceptable
-
Retail, logistics, and supply chain operations
Note
For any invalid records in a file that are not processed, the trading partner can check the acknowledgment (997/CNTRL) sent from the Celigo platform (Send Functional acknowledgmentbox must be checked). The trading partner can then reshare the EDI file with any required changes so that the records can be successfully processed.
If for any reason, the acknowledgment box is not checked, then you could view the error details in the EDI parser helper and request the trading partner to reshare the EDI file with any required changes.
EDI exports/listeners in the Celigo platform support both approaches with the UI option Process parsed data. For details, see Configure EDI listener and import steps.
When configuring your EDI export, choose either option while also keeping in mind the following points:
-
Define clear validation rules: Align with partner specifications
-
Use the EDI parser helper: Launch the EDI parser helper to view and troubleshoot errors early. See also the parser helper FAQs
-
Enable notifications: Enable notifications for flow errors, if required
-
Monitor the dashboard: Track both successful and failed transactions with the acknowledgments/the EDI dashboard. See (EDI X12 or EDIFACT) to monitor details.
-
Choose strategy based on business needs: Not all exports or flows require the same approach.
Choosing between full file validation and partial processing depends on your business priorities—whether you value strict reconciliation processes or operational speed. Your choice could depend on your need to balance accuracy, efficiency, and scalability in your EDI operations.