Vendor Derivation Test Scenarios

Invoices with POs

The scenarios below all relate to invoices which have a purchase order. All the DERIVED scenarios will still need to complete
the final test that the PO on the invoice exists and the vendor on the PO is the derived vendor.
In the table below each line represents one or more invoices. The essential requirement is that we have one unique
match.
U = Unique ie there is only one vendor with a matching field
D = Duplicate ie there is more than one vendor with a matching field
A dash (-) indicates no data or not required.
PASSED indicates that the vendor has successfully been derived and the PO on the invoice exists for the derived vendor.
FAILED indicates that the vendor was not successfully derived and the invoice will be dropped for manual intervention.
Scenarios
VAT CODE

IBAN

BANK DETAILS

POST CODE

RESULT

DERIVED

FAILED

DERIVED

FAILED

DERIVED

FAILED

PO MATCH SUCCESSFUL

YES - PASSED

NO-FAILED

YES-PASSED NO-FAILED

YES-PASSED NO-FAILED

DERIVED

FAILED

DERIVED

10

FAILED

11

DERIVED

12

FAILED

13

DERIVED

14

FAILED

15

DERIVED

16

FAILED

17

DERIVED

18

FAILED

19

DERIVED

20

FAILED

21

FAILED

YES-PASSED NO-FAILED

YES-PASSED NO-FAILED

YES-PASSED NO-FAILED

YES-PASSED NO-FAILED

YES-PASSED NO-FAILED

YES-PASSED NO-FAILED

YES-PASSED NO-FAILED

Invoices without PO

In the table below each line represents one or more invoices. The essential requirement is that we have one unique
match on VAT code PLUS one other.
Scenarios
VAT CODE

IBAN

BANK DETAILS

FAILED

FAILED

FAILED

DERIVED

FAILED

FAILED

DERIVED

FAILED

DERIVED

POST CODE

RESULT