Customer-facing EDI Resolved Issues
Summary of Recently Resolved Customer-Facing EDI Integration Issues
✅ Resolved Issues
Issue: Phone Number Validation Blocking EDI Load Creation
Date Resolved: 10/06/2025
Root Cause: Public API update pushed on Friday, 10/02/25, did not account for all EDI phone number formats.
Reported: 10/06/2025 – 9:06 AM ET
Resolved: 10/06/2025 – 9:51 AM ET
Resolution: Tai Development team was alerted and deployed a fix to support all phone number formats.
⚡ Recently Resolved / Monitoring
Issue: JT AS2 Certificate Change
Date Resolved: 10/14/2025 – 10:00 AM CST
Root Cause: Annual AS2 certificate renewal; prior notification emails were sent to all existing AS2 partners.
Resolution: Partners were instructed to update to the new JT AS2 certificate file provided in earlier communications.
Issue: UF 990 “A” Rejections
Date Resolved: 10/15/2025
Root Cause: Public API naming convention mismatch (“Booked” vs. “Committed”).
Resolution: Updated affected mappings and verified that Acceptance messages are now transmitting correctly