HMSA EDI Mapping Guidelines (File, Functional Group, Transaction Set, and Claim Rejection) HMSA EDI Mapping Guidelines are given for business partners transmitting electronic transactions to HMSA. HMSA EDI Mapping Guidelines cover the following points – File, Functional Group, Transaction Set, and Claim Rejection. A file level reject occurs when an error is detected in the interchange control header … Read More →
Submitting Electronic Transactions to HMSA (General requirements) Submitting Electronic Transactions to HMSA partners should remember that each transmission to HMSA should have a unique Interchange Control Number (ISA13). HMSA will use this number to determine if it is a duplicate file. HMSA will only accept one interchange (ISA/IEA) per input file from a submitter. There … Read More →
EDI Web Vendors Requirements EDI Web Vendors Requirements are given in today’s blog for Town Shoes web partners. As a web vendor, your account is active the day of the on-boarding process. However, Town Shoes is not able to issue a live purchase order until the NPLS Catalog has been submitted and matched by them. On the Town Shoes … Read More →
Town Shoes EDI Connections Requirements Town Shoes EDI Connections require that Town Shoes obtains the correct EDI ID (Alias) information from vendor. Town Shoes will match the account being used by Town Shoes with your Alias so that document flow can be successful. Please update the Connection Details section on the Spice Portal Dashboard as needed. … Read More →