Recap of the meeting "Discuss Cancellation case in Tesla case related General refund"
TL;DR skip to the last section.
The case is as follows:
Currently there are 4 booking_ids which cancel with refund requested by customer:
For all those bookings the condition are:
- Success cancel in Aries
- No cancel data in general refund (because failed sending data to here)
- No cancel data in TBI (because has been failed in previous step)
Based on the meeting, what we found:
- Reimbursement data created using TAP will not added to general refund's data (they are separate database and system).
- Reimbursement usually performed before issuance (tho on many cases it also executed after issuance to solve problem case by case)
- Reimbursement only process the paid the amount to customer.
- Refund usually performed after issuance.
- Refund process the paid the amount to customer and deduct it from supplier.
Based on those knowledge which is discussed in the meeting, to be able to finish the cancellation process to TBI what we will do are as follows:
- We will release the feature to be able to execute and retry the cancellation process (https://29022131.atlassian.net/browse/PPR-1130) this week (hopefully).
- After release, for those 4 booking ids we will execute cancellation without refund to simply continue the cancellation data to TBI. Reason: since the paid amount already returned to customer, we only need to process the cancellation amount to the supplier side.
- This execution should be without impact/side effect. We will monitor after execution too.