> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/product-news/2026/september/organisation-supplied-milestones.md).

# Organisation-supplied milestones

## What problem does this solve?

Contracts often include obligations the organisation owes the counterparty: reports, resources, training, or payment instalments due back to the organisation. Until now every milestone belonged to the counterparty, so these internal obligations had to be tracked outside the system.

## How it works

With the org setting **Enable organisation-supplied milestones** turned on (Settings, milestone section; off by default), each milestone in the contract setup gains a **Supplied by** choice:

* **Counterparty** (default): behaves exactly as today, completed in the counterparty portal
* **Your organisation**: an internal milestone, completed and submitted by admins

Organisation-supplied milestones reuse the full milestone toolkit: deliverable forms, due dates, the review workflow, reminders, and payments.

### Internal completion and review

An admin fills in and submits the deliverables (the call to action reads **Complete** rather than "Complete on Behalf"), and a reviewer approves through the standard review screen. If the reviewer requests changes, the resubmission request goes back to the admin who submitted it, with a link to complete and resubmit.

### The counterparty never sees them

Organisation-supplied milestones do not appear anywhere in the counterparty portal (milestone lists, contract milestones tab, dashboards), and the counterparty receives no notifications, tasks, or emails about them: not on publish, submission, approval, decline, or payment. Milestone email reminders aimed at the Applicant or Application Owner skip them; reminders aimed at the Contract Manager or Admins include them.

### Payments and direction

Payments on organisation-supplied milestones are tracked as **incoming** (money owed to the organisation), while all existing payments remain **outgoing**. Incoming payments:

* are never synced to Xero/QuickBooks/MYOB as bills (they are income, not payables)
* can sit in payment batches for bulk processing, but are excluded from bank payment file exports

### Admin visibility

The admin milestones list badges organisation-supplied milestones with "Supplied by us".

## UI changes

* Org settings: new **Enable organisation-supplied milestones** toggle (milestone settings section)
* Contract wizard milestones step: **Supplied by** radio per milestone (only when the setting is on)
* Admin milestones list: "Supplied by us" chip; primary row action shows **Complete** for organisation-supplied milestones awaiting completion
* Milestone page: **Complete** action label for organisation-supplied milestones
