Skip to main content
All CollectionsProjects Page: Guides and How-Tos
How to Determine Why a Contract (Vendor) is Not Compliant
How to Determine Why a Contract (Vendor) is Not Compliant
Kelsey VanSleen avatar
Written by Kelsey VanSleen
Updated over 7 months ago

As vendors submit documents that are reviewed in Billy, sometimes they remain non-compliant. Let's review how you can figure out why a contract (vendor) is non-compliant.

Where to Look: Contract Coverages

  1. On a project, click on any contract (vendor).

  2. The coverages tab for a contract (vendor) shows the status of each requirement.

  3. Any requirement listed as Inactive or Unreviewed is why they are non-compliant. The next section goes into these differences.

  4. For Inactive requirements, click the down arrow on the right to uncover whether a requirement is Expired or Rejected.

    1. Rejection Notes are visible in the bottom right underneath the Limit amounts.

Understanding Contract Coverage Statuses

Here is what each requirement status means:

No document has been submitted or reviewed for this requirement.

Compliant, approved requirement.

Either the requirement is expired or has been rejected. Click the dropdown arrow button on the right to view the Notes sent to the vendor.

The requirement has been marked by one of your Admin/Standard users as not required.

PRO TIP (not applicable for Managed Plan partners)

If a contract (vendor) is non-compliant after a document has been reviewed and a requirement is "unreviewed" in the contract coverages tab, a Standard or Admin user needs to navigate to the Documents tab, view the recently submitted document (ideally one with a current rejection, if applicable), and reject the requirement that hasn't been submitted. WHY? This puts the ball back in the vendor's court, and Billy will send 3 reminder emails once a week until a document has been uploaded.

If you have any questions about this, please use the in-app chat or email support@billyforinsurance.com to speak with our Partner Success team.

Did this answer your question?