> ## Documentation Index
> Fetch the complete documentation index at: https://zenorent.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Development

> Projects, buyers, unit sales, milestone payments, vendor costs, and development documents

Development is for real-estate projects where buyer receivables and vendor costs need to stay tied to the same project. Projects hold milestones and sales activity; buyers and vendors hold the money movement on each side.

## Sidebar

| Item | What it's for |
| - | - |
| **Dashboard** | Project summary, pending documents, and development tasks |
| **Projects** | Projects, milestones, unit sales, and project documents |
| **Buyers** | Buyer records, payer entities, unit sales, invoices, and payments |
| **Receivable** | Buyer invoices and balances |
| **Vendors** | Development vendors, contracts, estimates, bills, credits, and payments |
| **Estimates** | Vendor proposals before they become contracts or bills |
| **Payable** | Vendor bills |
| **Payments** | Buyer payments and vendor payment activity |

## Setting up projects

Create a project in **Projects**, then add milestones for the construction phases you bill or track against. A milestone can activate buyer payment schedule items when it is marked complete.

Project pages also hold sales, costs, documents, activity, and notes. See [Development Sales](https://zenorent.com/docs/management/development-sales.md) for the project hierarchy and milestone workflow.

## Tracking buyers and unit sales

Create buyers from **Buyers** or from a project page. Add payer entities when payments come through an LLC or another related name.

Unit sales connect a buyer to the unit designations, contract values, amendments, additional charges, and payment schedule. The schedule can use fixed due dates or project milestones.

## Billing and collecting

Use **Receivable** for buyer invoices. Use **Payments** to record buyer money received by check, wire, cash, or another method, then apply it to the right schedule item or invoice.

If a check bounces after it cleared, mark it as bounced from the payment detail. Use **Replace** when the buyer sends a new payment so the history stays connected.

## Managing vendor costs

Use **Vendors** for subs, suppliers, and other project payees. A vendor page groups contracts, estimates, bills, credits, payments, documents, and activity.

Scanned vendor documents can start in the [Inbox](https://zenorent.com/docs/workflow/inbox.md), move through the Development queue, and become a bill, estimate, or contract after review.

## Reviewing reports

Development reports live in [Reports](https://zenorent.com/docs/reports.md#development). Use them for payable aging, cash flow, project costs, contract status, payment history, sales payments, and unit sales.

Development invoices, bills, payments, and credits post to [Books](https://zenorent.com/docs/books.md), so financial reports can include development activity alongside the rest of the organization.

## Working with documents

Contracts, promissory notes, mortgages, plans, receipts, amendments, and vendor files can attach to projects, buyers, unit sales, and vendors. Each record shows its own files on its page.

To search across everything, use [Document Center](https://zenorent.com/docs/workflow/document-center.md) from **More → Documents** and filter to the Development module.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.