WorksheetsVerification Trade Update - February 1 - March 13
Total questions: 15
Worksheet time: 5mins
In EUA Verifier Trade, eCommerce Support request for creation of Custmer Code in OPUS
Can we proceed to create the code immediately?
Yes, as per special instruction
No, as creation of code is not within verifier scope
No, As we need to validate first the details
Yes, as this is the same process with SPI creation of customer
In all Verification Trade, do we allowed to create Customer code in OPUS?
No, as NA RCA is not allowed to create Code in OPUS
Yes, Case to case basis and special instruction
Yes, as per PIC decision and wants
No, Creation of Customer code is not Verifier Scope
For Verification of Personal Effects.
Which on below is not correct?
Approve if confirmed details of customer is correct
Reject the request if no indication of Personal Effects shipment
Approve even w/o contact number in request but updated in BKG no.
Approve request once confirmed name in the request is person name
For NA Verification
Which on below process is correct?
Ensure all approve code has been validated thru SDN
Can validate the Customer
Thru:
- Valid Website
- Phone Call
- Email confirmation
In updating the To-be Customer Code check first the credit of duplicate code
FMC License Validation is under our scope
What will you do if you have received the UN-APPROVED CUSTOMER Report from
gl Offshore COE
Check if you have an ageing unapproved customer that under your scope
Folder the mail
Check if you have an ageing unapproved customer that under your scope and imform them with the result
Seek assistance to other PIC
What field should be update once confirmed code is for deletion?
To-Be Customer Code
To-Be Customer Cade
To-Be Costumer Code
To-Ba Customer Code
Tu-Be Customer Code
When Mongolia Country has been temporarily added as SPI/REO Scope?
January
February
March
Februery
Do we need to verify the ageing customer under MN Country?
Yes
No
In NA Verification
If customer under TX, MS and LA State with Customer Type BCO
What will be the Admin Office
CHIBB
ATLBB
ATLBB or CHIBB
ALTBB or CHIBB
In NA Verification
If customer under TX, MS and LA State with Customer Type Non-BCO
What will be the Admin Office
ATLBB
ATLBB or CHIBB
CHIBB
For NA Verification, What is process of Re-mapping of duplicate customer
Update the To-be Customer code of duplicate code
Update the To-be Customer code of duplicate code and check the Credit of the customer
Check the Credit of correct code and update the To-Be Customer Code
Check first the Credit of Duplicate code and update the To-Be Customer Code
For NA Verification, we need to inquire with NA BPIT for Re-Mapping Process if:
Confirmed code is duplicate
Confirmed Status of Credit customer is "N"
Confirmed Status of Credit customer is "Y"
Customer has no credit
For NA Verification, we can update the To-Be Customer code field once:
Customer has no credit or Have credit and status is "Y"
Customer has no credit or Have credit and status is "N"
Confirmed code is duplicate
Kosovo is part of EUA Offline Verifier Scope and Location codes will still fall under?
GE
RS
RD
GA
Abkhazia is EUA Offline Verifier Scope and if fall under "GE" Country code
Does it mean all GE Customer will be under our scope?
Yes, as Abkhazia Country Code
Yes, as per our scope
No, as GE for Georgia Country and we only have specific location code to verify
No, as GE for Georgia Country and Abkhazia Country code is BZ
