# Enable Company Product Match Verification

With the 23R2 release, Vault now supports advanced product match coding verification when importing E2B or JSON files to generate _Inbox Items_. This  allows you to configure product coding criteria to consider additional matching scenarios. Vault verifies whether generated _Inbox Items_ meet the  coding criteria and determines whether to proceed with _Product_ matching.

After completing the configuration on this page, see the following for more information:
* <a href="/en/gr/01191/">Configure Company Product Match Verification</a>
* <a href="/en/gr/01145/#company-product-match-verification">Inbox Item Study and Product Matching</a>

### Updates {#updates}

We have added the following updates to this feature:

* **Company Product Match Verification for Deprecated Product Registrations**: With the 26R1 release, to more accurately verify whether a reported product is a company product during import, Vault now considers the lifecycle state of _Product Registrations_. When matching, Vault prioritizes active registrations and populates the _Product Match Confidence_ based on your confidence criteria. However, when the best match is a <a href="/en/gr/01215/#inactive">deprecated _Product Registration_</a>, Vault populates _4-Unlikely Match_ as the _Product Match Confidence_, regardless of which confidence criteria have been met. This feature is Auto-on in Vaults with the [_Enable Advanced Product Coding Verification_ intake setting][1] and the <a href="/en/gr/672883/">_Inactivate Product & Study Registrations_ feature</a> enabled.
* **Exclude Concomitant Products from Auto-Coding**: With the 25R3 release, Vault offers the option to exclude all concomitant products from <a href="/en/gr/01162/">auto-coding</a> to _Products_ in the _Product_ library during structured intake. Excluding concomitant products from auto-coding eliminates the need to manually reclassify products that match with _Products_ to _External Products_, saving time verifying company products that will not be assessed based on their drug role. To configure your Vault for this feature, enable the _Exclude Concomitant Products from Auto-Coding_ setting.
* **Extend Company Product Match Verification to All Suspect Products**: With the 25R1 release, Vault offers the option to extend company product match verification to all company products with a _Drug Role_ evaluated as suspect imported from structured source files to _Inbox Items_. To configure your Vault for this feature, enable the _Intake Settings with the Enable Advanced Product Coding Verification_ setting.

## Enable Product Coding in Intake Settings {#intake-settings-must-should-match-fields}

Configure the following <a href="/en/gr/740208/#prod-coding">product coding intake settings</a> on the **Admin > Settings > Intake Settings** page:

* **Exclude Concomitant Products from Auto-Coding**: Excludes concomitant products from auto-coding on _Inbox Items_ created through structured source file intake.
* **Enable Advanced Product Coding Verification Auto coding Override**: Prevents auto-coding of any primary _Company Product_ <a href="/en/gr/01294/">with a _Drug Role_ evaluated as suspect</a> that does not meet the specified _Auto code min Product Confidence level_ value. To apply this setting, you must also select the _Enable Advanced Product Coding Verification_ checkbox.
* **Enable Advanced Product Coding Verification**: Calculates primary _Product_ match <a href="/en/gr/01145/#company-product-match-verification">confidence level</a> and populates the  _Product Match Confidence_ and _Product Match Criteria_ fields on _Inbox Items_ generated from imported E2B and JSON files.
* **Must Match**: Specifies which _Inbox Item_ fields must match a registration to be a confident match level (_2-Confident Match_). For Vault to find a match, all specified fields must include values and must be an exact match. 
* **Should Match**: Specifies which _Inbox Item_ fields must match a registration to be a likely match (_3-Likely Match_). Vault compares the specified field values if populated, but blank fields do not prevent matching. When values are present, they must be an exact match.
* **Auto code min Product Confidence level**: Specifies the minimum confidence level required for Vault to auto-code _Company Products_. Updating this setting does not affect previously generated _Inbox Items_. To apply this setting, you must also select the _Enable Advanced Product Coding Verification_ checkbox. You can select from the following options:
  * _1-Exact Match (ID Match)_
  * _2-Confident Match_
  * _3-Likely Match_
  * _4-Unlikely Match_
  * _5-Unknown_
  * _6-No ID or Name Match_
* **Extend Advanced Product Coding verification to all Suspect/Interacting**: Extends advanced product coding verification criteria to all company products with a _Drug Role_ of _Suspect_ imported from structured source files. When the _Extend Suspect Definition to Include Drug Not Administered_ <a href="/en/gr/740208/#metrics-other">general setting</a> is also enabled, this extends advanced product coding verification criteria to all company products with a _Drug Role_ of _Interacting_.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: The <em>Product Match Confidence</em> must meet or exceed your setting for Vault to code the <em>Company Product</em> on an <em>Inbox Item</em>. If this field is blank, Vault considers <em>1-Exact Match (ID Match)</em> as the minimum confidence required during evaluations. If the product’s <em>Country Obtained</em> is not populated, Vault attempts to match the <em>Country</em> using the primary reporter’s <em>Country</em>.</p>
    </div>
  </div>
</div>



## Update the Inbox Item Layout

<a href="/en/gr/26387/#how-to-add-object-fields">Add</a> the _Product Match Confidence_ and _Product Match Criteria_ fields to the _Inbox Item_ object layout. 

## Update the Product Registration Layout

<a href="/en/gr/26387/#how-to-add-object-fields">Add</a> the _Dose Form_ field to the _Product Registration_ object layout.

[1]: #intake-settings-must-should-match-fields