Hi @klandry ,
Please find my below response to your queries:
When the Invoice for Vendor A is imported into Concur for PO 12345, can I assume that it will NOT match as the existing PO record in Concur is linked with Vendor B?? In other words, does Concur match on both the PO Number AND Vendor ID?
There are two scenario's here:
Scenario 1: At the capture processor stage, if the system successfully identifies and captures the PO number, it will automatically retrieve the correct vendor details from the imported PO. For example, if PO 1234 is detected, the system will pick up Vendor B associated with that PO.
Scenario 2: At the capture processor stage, if the system fails to identify or capture the PO number (i.e., the PO field is blank), it will instead use the vendor information provided on the invoice itself. In this case, as per your example, the system will pick up Vendor A.
Note - Whenever system identifies correct PO number, all the associated PO field details such as Org unit fields, vendor details, Invoice Owner etc gets copied down from PO to invoice.
In the Concur Invoice Audit Trail, I see an entry "Associated to Purchase Order Number 12345" that is tied to a user. Does this mean that the user manually forced the Invoice to link to this PO Number?
Once the invoice is processed from the capture processor stage, it is submitted and assigned to the corresponding PO owner/user. When the user attempts to perform invoice matching against the related PO, the system compares the invoice details—such as quantity, unit price, vendor, total amount, etc.—based on the configured matching rules.
For example, if the user edits the vendor field and selects Vendor A while the associated PO has Vendor B, the system will display an error message indicating that the selected vendor does not match the PO vendor. Here, you can write appropriate exception message such as "Invoice vendor does not match with PO vendor. Please correct". Once user corrects the vendor, error message will get resolved.
Note: These matching rules are enforced only if vendor comparison is configured under the PO Matching Rules section. If no vendor rule is defined in the configuration, the system will not perform vendor validation during invoice matching.
Sample screenshot:
PO is associated with vendor ABC.
User manually updated/edited vendor as XYZ and matching error got triggered as shown in exception.
If this answers your query, then please marks solution as accepted.
Hi @klandry ,
Please find my below response to your queries:
When the Invoice for Vendor A is imported into Concur for PO 12345, can I assume that it will NOT match as the existing PO record in Concur is linked with Vendor B?? In other words, does Concur match on both the PO Number AND Vendor ID?
There are two scenario's here:
Scenario 1: At the capture processor stage, if the system successfully identifies and captures the PO number, it will automatically retrieve the correct vendor details from the imported PO. For example, if PO 1234 is detected, the system will pick up Vendor B associated with that PO.
Scenario 2: At the capture processor stage, if the system fails to identify or capture the PO number (i.e., the PO field is blank), it will instead use the vendor information provided on the invoice itself. In this case, as per your example, the system will pick up Vendor A.
Note - Whenever system identifies correct PO number, all the associated PO field details such as Org unit fields, vendor details, Invoice Owner etc gets copied down from PO to invoice.
In the Concur Invoice Audit Trail, I see an entry "Associated to Purchase Order Number 12345" that is tied to a user. Does this mean that the user manually forced the Invoice to link to this PO Number?
Once the invoice is processed from the capture processor stage, it is submitted and assigned to the corresponding PO owner/user. When the user attempts to perform invoice matching against the related PO, the system compares the invoice details—such as quantity, unit price, vendor, total amount, etc.—based on the configured matching rules.
For example, if the user edits the vendor field and selects Vendor A while the associated PO has Vendor B, the system will display an error message indicating that the selected vendor does not match the PO vendor. Here, you can write appropriate exception message such as "Invoice vendor does not match with PO vendor. Please correct". Once user corrects the vendor, error message will get resolved.
Note: These matching rules are enforced only if vendor comparison is configured under the PO Matching Rules section. If no vendor rule is defined in the configuration, the system will not perform vendor validation during invoice matching.
Sample screenshot:
PO is associated with vendor ABC.
User manually updated/edited vendor as XYZ and matching error got triggered as shown in exception.
If this answers your query, then please marks solution as accepted.
