> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.middesk.com/verify-business/tin/monitoring/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.middesk.com/_mcp/server.

# Monitor TINs for newly formed businesses

> Learn how to monitor TIN registrations for newly formed businesses using TIN Discovery.

TINs for newly formed businesses may take up to two weeks to appear in the IRS database.
As a result, initial TIN verification through Middesk may fail, even if the business information is correct.

TINs associated with new businesses are sometimes unverifiable, yielding an `unknown` status when initially verified through Middesk's TIN Match.
This is due to a data lag in the IRS's TIN matching program.
When a TIN returns an `unknown` status, it's typical to request documentation from the business.

Middesk's TIN Discovery feature provides an alternative approach that seamlessly attempts to re-verify a business's TIN without further friction imposed on the customer.
If a TIN is not found and the business was formed within the last 30 days, Middesk continues verification attempts for up to two weeks after the initial attempt.
With TIN Discovery, Middesk attempts to verify the businesses TIN multiple times, at 1, 3, 7 and 14 days after the business is subscribed to monitoring.

> **Info**
>
> When running businesses with unknown TINs through TIN Discovery, Middesk found 87% of TINs within 14 days for newly formed businesses less than 1 year old.

## TIN Discovery lifecycle

Here's the typical lifecycle of TIN Discovery:

1. A business gets created with the [POST /businesses endpoint](/api-reference/business-verification/businesses/create-a-business).

2) The business is subscribed to TIN monitoring.
3) A TIN verification is attempted at 1, 3, 7 and 14 days after subscribed.
4) Middesk sends a webhook event to registered webhook endpoint(s) if it finds a new TIN status.
5) The client application ingests and evaluates the change in the business record.

Middesk runs checks on a set cadence for 2 weeks to find TINs for businesses whose TINs were previously unknown.

## Enable TIN monitoring

#### Submit a business

Start by [submitting a business for verification](/api-reference/business-verification/businesses/create-a-business).

> **Note**
>
> The business must have the TIN property included in the request body in the `tin` field.

#### Subscribe a business

You can enable monitoring on Middesk businesses using four different strategies.

#### With an automatic monitoring subscription

Automatically subscribe all businesses when a business verification order completes.

#### With a policy action

[Policies](/use-rulesets-policies) provide a rule-based system for automation within the Middesk platform. Use a custom policy action to subscribe Middesk businesses when certain conditions are met.

![Policies for TIN Discovery monitoring](/_fern-img/88981281e29c02fa7c77ae96efe10a2f0bcb5f23ff4e1d84f59a7902be002e14.webp)

#### With the API

Use the [POST /monitor API](/api-reference/business-verification/monitoring/create-a-monitor-for-a-business) to create, update, and delete business monitors for fine-grained control within your application.

#### With the Dashboard

Manually enable monitoring on a business with a completed business verification order on the **Monitoring** tab of the Middesk [Dashboard](https://app.middesk.com/).

Using [webhooks](/build/webhooks), watch for `tin.retried` events to receive updates whenever a discovery attempt is made.

> **Get a demo**
>
> Contact your account manager or [contact sales](https://www.middesk.com/contact-sales) to inquire about access.

> Learn how to monitor TIN registrations for newly formed businesses using TIN Discovery.