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.
|
|
Rejection handling during the Migration Period.
Hi,
This is about handling of rejections during the Migration Period.
Let's suppose the following scenario:
1. We moved to SIS.
2. The other company which is NOT yet SIS, sends us a physical "rejection stage 1".
3. According to ISPG, we respond with "rejection stage 2" by SIS.
Here's the problem:
SIS is not aware about the "rejection stage 1" because it came NOT by SIS.
Will SIS accept the "rejection stage 2" from us?
Thank you, Michael |
 |
Dear Michael,
You may migrate your transaction to SIS at any billing stage. So yes, if rejection stage 1 was done outside of SIS, the following rejection stages can be done in SIS. However, once a transaction has been responded to in SIS, it has to stay there (please see also the FAQ section on the SIS website). So in this case, rejection stage 3 and any following correspondence must be done in SIS if you have submitted stage 2 rejection in SIS.
In addition, the IS-Validation is set up to check if the carrier you are rejecting with RM stage 2 has already migrated at the time of its RM stage 1.
Please note that when you create your RM stage 2, you have to refer to the RM stage 1 (your invoice date, your invoice number, etc.). Hence SIS is validating if the carrier who has sent you the RM stage 1 was a migrated or a non-migrated carrier at that time.
Best regards
From: Posted: Monday, June 06, 2011 9:05 AM Subject: Rejection handling during the Migration Period.
Hi,
This is about handling of rejections during the Migration Period.
Let's suppose the following scenario:
1. We moved to SIS.
2. The other company which is NOT yet SIS, sends us a physical "rejection stage 1".
3. According to ISPG, we respond with "rejection stage 2" by SIS.
Here's the problem:
SIS is not aware about the "rejection stage 1" because it came NOT by SIS.
Will SIS accept the "rejection stage 2" from us?
Thank you, Michael |