| Vendor ID: | {{ sourceData.Vendor_ID }} |
| Vendor Name: | {{ sourceData.Vendor_Name }} |
| Address: |
{{ sourceData.Address_1 }}
{{ sourceData.Address_2 }} {{ sourceData.City }} {{ sourceData.Postal_Code }} {{ sourceData.Country }} |
| IBAN: | {{ sourceData.IBAN }} |
| Bank Country: | {{ sourceData.Bank_Country }} |
| Match Type: | {{ sourceData.Match_Type }} |
| Match Details: | {{ sourceData.Match_Details }} |
| 1. |
Verify vendor details in SAP system. Is there an explanation for the bank country mismatch?
|
| 1. |
Verify vendor details in SAP system. Is there an explanation for the employee match?
|
|
| 1b. |
Contact staff investigations team. Ask them to identify whether there is an explanation for the employee match in the employee master file?
|
| 1. |
Verify vendor details in SAP system. Is there an explanation for the legal form mismatch (e.g. foreign subsidiary or branch that is not marked as such, translation error)?
|
| 1. |
Verify vendor details in SAP system. Can it be confirmed that this is NOT a duplicate (false positive in fuzzy matching)?
|
| 2. |
Verify vendor change records in SAP system. Is there evidence of wrongdoing (e.g. change-and-change-back, changes prior to payments not evidenced by documentation)?
|
|
| 3. |
Verify payments history (click on "Payments" above). Is there evidence of wrongdoing (e.g. abnormal payment amounts or destinations, missing PO or GR confirmations)?
|
|
| 4. |
If wrongdoing is suspected, contact lead auditor and discuss next steps. If no wrongdoing is suspected, contact employee responsible for change that lead to mismatch and ask for his/her explanation. Is the explanation plausible?
|
|
| 5. |
Document the final results of your analysis under "Final Results" below. |
|
| 6. |
For non-malicious but real duplicates: Inform vendor master team to merge vendor entries. |
{{ sourceData.Last_Payments }}
| Vendor ID: | {{ sourceData.Vendor_ID }} |
| Vendor Name: | {{ sourceData.Vendor_Name }} |
| Address: |
{{ sourceData.Address_1 }}
{{ (sourceData.Address_2 ? ' ' : '') }} {{ sourceData.Address_2 }} {{ sourceData.City }} {{ sourceData.Postal_Code }} {{ sourceData.Country }} |
| IBAN: | {{ sourceData.IBAN }} |
| Bank Country: | {{ sourceData.Bank_Country }} |
| Match Type: | {{ sourceData.Match_Type }} |
| Match Details: | {{ sourceData.Match_Details }} |
| 1. |
Verify vendor details in SAP system. Is there an explanation for the bank country mismatch? {{ resultsData.checklist_1_details }} |
Yes (add details) No |
| 1. |
Verify vendor details in SAP system. Is there an explanation for the employee match? {{ resultsData.checklist_1_details }} |
Yes (add details) No |
| 1b. |
Contact staff investigations team. Ask them to identify whether there is an explanation for the employee match in the employee master file? {{ resultsData.checklist_1b_details }} |
Yes (add details) No |
| 1. |
Verify vendor details in SAP system. Is there an explanation for the legal form mismatch (e.g. foreign subsidiary or branch that is not marked as such, translation error)? {{ resultsData.checklist_1_details }} |
Yes (add details) No |
| 1. |
Verify vendor details in SAP system. Can it be confirmed that this is NOT a duplicate (false positive in fuzzy matching)? {{ resultsData.checklist_1_details }} |
Yes (add details) No |
| 2. |
Verify vendor change records in SAP system. Is there evidence of wrongdoing (e.g. change-and-change-back, changes prior to payments not evidenced by documentation)? {{ resultsData.checklist_2_details }} |
Yes (add details) No |
| 3. |
Verify payments history (click on "Payments" above). Is there evidence of wrongdoing (e.g. abnormal payment amounts or destinations, missing PO or GR confirmations)? {{ resultsData.checklist_3_details }} |
Yes (add details) No |
| 4. |
If wrongdoing is suspected, contact lead auditor and discuss next steps. If no wrongdoing is suspected, contact employee responsible for change that lead to mismatch and ask for his/her explanation. Is the explanation plausible? {{ resultsData.checklist_4_details }} |
Yes (add details) No |
Vendor evaluation: False positive (analytics error) Explained positive Investigation initiated Pending response
Comments:
{{ resultsData.evaluationComments }}