This is a read-only copy of the discussions. To view the original, where you can reply, go here. For info on how to log in, please see the instructions.
|
|
Format of 2nd Stage Rejection
Hi Ashley,
If a non-migrated carrier rejects a billing from a migrated carrier through IS-WEB, how will the migrated carrier receive these rejections? Will SIS take any rejections submitted via IS-WEB and convert them into an IS-IDEC/XML format file for the migrated carrier? Or will the migrated carrier need to carry on the Rejection process directly in IS-WEB?
Thanks,
Michael. |
 |
Dear Michael,
In general, regardless of the input format of the billing entity (IS-WEB, IS-IDEC, IS-XML), the billed entity will receive the formats defined in their Member Profile: always IS-WEB, IS-IDEC and/or IS-XML. Also, regardless of the migration status, the billed carrier can select to receive old IDEC down-converted file and IS-Formats.
Hence, the answers to your questions are:
If a non-migrated carrier rejects a billing from a migrated carrier through IS-WEB, how will the migrated carrier receive these rejections? Will SIS take any rejections submitted via IS-WEB and convert them into an IS-IDEC/XML format file for the migrated carrier? Yes – as per the general statement, any input format is converted in all output formats.
Or will the migrated carrier need to carry on the Rejection process directly in IS-WEB? No, I migrated carrier chooses the “input” format.
Best regards
From:
Posted: Monday, June 13, 2011 7:47 AM
Subject: Format of 2nd Stage Rejection
Hi Ashley,
If a non-migrated carrier rejects a billing from a migrated carrier through IS-WEB, how will the migrated carrier receive these rejections? Will SIS take any rejections submitted via IS-WEB and convert them into an IS-IDEC/XML format file for the migrated carrier? Or will the migrated carrier need to carry on the Rejection process directly in IS-WEB?
Thanks,
Michael. |