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

# Lifecycle of a Business

> Learn about the stages of a Business object in Middesk--submission, verification, and approval--and how the status property tracks progress through each stage.

The Middesk API operates on a single primary object: a Business. A Business object is the Middesk representation of the business entity that you engage with in your platform.

As in the real world, a Business is not a static entity. When you create and manage Business objects in your Middesk account, pay attention to the Business lifecycle and its key properties.

The lifecycle of a Business object in Middesk has three stages:

#### Submission

You--"client" in the image below--create the Business in Middesk.

#### Verification

Middesk researches a business to appropriate depths.

#### Approval

You decide what happens next, based upon Middesk's verification results.

Verification flow · 3 stages

How a business moves through Middesk

<title id="md-lob-title">
  Lifecycle of a Business
</title>

<desc id="md-lob-desc">
  A business moves through three stages: Submission (client submits business),
  Verification (Middesk processes the business, either auto-resolving or routing
  to an analyst, then delivers insights), and Approval (client reviews and
  approves or rejects).
</desc>

<defs>
  <path d="M 0 0 L 10 5 L 0 10 z" fill="var(--md-sky)" />

  <path d="M 0 0 L 10 5 L 0 10 z" fill="var(--md-violet)" />

  <path d="M 0 0 L 10 5 L 0 10 z" fill="var(--md-lime)" />

  <path d="M 0 0 L 10 5 L 0 10 z" fill="var(--md-success)" />

  <path d="M 0 0 L 10 5 L 0 10 z" fill="var(--md-rose)" />
</defs>

<line x1="24" y1="36" x2="246" y2="36" />

<g transform="translate(320, 36)">
  <rect x="-72" y="-13" width="144" height="26" rx="13" />

  01 · Submission
</g>

<line x1="394" y1="36" x2="616" y2="36" />

<g transform="translate(200, 72)">
  <rect width="240" height="100" rx="10" />

  <text x="20" y="22">
    Client
  </text>

  <text x="20" y="48">
    Submits Business
  </text>

  <g transform="translate(20, 62)">
    <rect width="60" height="18" rx="4" />

    open
  </g>
</g>

<g transform="translate(320, 214)">
  <rect x="-130" y="-13" width="260" height="26" rx="4" />

  Submit Business: POST /v1/businesses
</g>

<line x1="24" y1="284" x2="236" y2="284" />

<g transform="translate(320, 284)">
  <rect x="-80" y="-13" width="160" height="26" rx="13" />

  02 · Verification
</g>

<line x1="404" y1="284" x2="616" y2="284" />

<g transform="translate(200, 320)">
  <rect width="240" height="100" rx="10" />

  <text x="20" y="22">
    Middesk
  </text>

  <text x="20" y="48">
    Processes Business
  </text>

  <g transform="translate(20, 62)">
    <rect width="60" height="18" rx="4" />

    open
  </g>
</g>

<g transform="translate(80, 500)">
  <rect width="220" height="96" rx="10" />

  <text x="20" y="22">
    Path A
  </text>

  <text x="20" y="48">
    Auto resolved
  </text>

  <g transform="translate(20, 58)">
    <rect width="78" height="18" rx="4" />

    pending
  </g>
</g>

<g transform="translate(340, 500)">
  <rect width="220" height="96" rx="10" />

  <text x="20" y="22">
    Path B
  </text>

  <text x="20" y="48">
    Analyst in the Loop
  </text>

  <g transform="translate(20, 58)">
    <rect width="78" height="18" rx="4" />

    in\_audit
  </g>
</g>

<g transform="translate(180, 680)">
  <rect width="280" height="120" rx="10" />

  <rect x="256" y="16" width="8" height="8" rx="2" />

  <text x="20" y="22">
    Middesk · Result
  </text>

  <text x="20" y="50">
    Delivers Insights
  </text>

  <text x="20" y="68">
    Verification findings ready for review
  </text>

  <g transform="translate(20, 80)">
    <rect width="88" height="20" rx="4" />

    in\_review
  </g>
</g>

<g transform="translate(320, 840)">
  <rect x="-125" y="-18" width="250" height="36" rx="4" />

  Process business.updated

  events via Webhooks
</g>

<line x1="24" y1="916" x2="254" y2="916" />

<g transform="translate(320, 916)">
  <rect x="-64" y="-13" width="128" height="26" rx="13" />

  03 · Approval
</g>

<line x1="384" y1="916" x2="616" y2="916" />

<g transform="translate(200, 952)">
  <rect width="240" height="96" rx="10" />

  <text x="20" y="22">
    Client
  </text>

  <text x="20" y="48">
    Reviews business
  </text>

  <g transform="translate(20, 58)">
    <rect width="88" height="18" rx="4" />

    in\_review
  </g>
</g>

<g transform="translate(80, 1132)">
  <rect width="220" height="96" rx="10" />

  <text x="20" y="22">
    Client
  </text>

  <text x="20" y="48">
    Reviews business
  </text>

  <g transform="translate(20, 58)">
    <rect width="88" height="18" rx="4" />

    rejected
  </g>
</g>

<g transform="translate(340, 1132)">
  <rect width="220" height="96" rx="10" />

  <text x="20" y="22">
    Client
  </text>

  <text x="20" y="48">
    Reviews business
  </text>

  <g transform="translate(20, 58)">
    <rect width="88" height="18" rx="4" />

    approved
  </g>
</g>

Middesk tracks the lifecycle of a Business, and always provides auditable records of how a Business object changes over time.

## Business status

The Business object has a `status` property that reflects the Business' state in the Middesk system. The value of this property changes during the lifecycle, so you can build workflows tailored to your platform.

| Status      | Description                                                                                         |
| :---------- | :-------------------------------------------------------------------------------------------------- |
| `open`      | The Business has been created, but Middesk has not yet begun verification.                          |
| `pending`   | Middesk has begun but not yet completed verification.                                               |
| `in_audit`  | Middesk is required to audit and ensure the quality of this Business.                               |
| `in_review` | The Business is ready to be reviewed by you. Your action items are listed in the `review` property. |
| `approved`  | You approved the Business.                                                                          |
| `rejected`  | You rejected the Business.                                                                          |

## Other core Business properties

Along with `status`, there are several key properties on the Business object to watch.

When a Business status changes to `in_review`, Middesk has completed its investigation into that Business and is now ready for you to [examine the insights](/review-insights). These insights come from the Business' `review` property.

A Business also has numerous resource-related properties, including:

* `name`
* `addresses`
* `tin`
* `website`

These resource properties represent  people, places, and things associated with the business. They provide additional evaluation factors in various compliance scenarios or to drive different programmatic workflows in your implementation.

> **Tip**
>
> Middesk can help you [monitor](../../monitor-activity/) businesses to watch for relevant activity after the approval stage.

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

> Learn about the stages of a Business object in Middesk--submission, verification, and approval--and how the status property tracks progress through each stage.