> For the complete documentation index, see [llms.txt](https://docs.zebec.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zebec.io/zebec-application-suite/enterprise-payroll/funding-your-treasury.md).

# Funding your treasury

Your **treasury** is the on-chain wallet that holds the float for payroll disbursements. You fund it by sending stablecoins from any wallet or exchange that supports the chain you have configured.

## Recommended approach

* **Pre-fund for at least one full pay cycle.** If you pay biweekly and your monthly payroll is $50K, fund at least $25K plus a 5–10% buffer for gas and mid-cycle hires.
* **Top up regularly** rather than holding large balances.
* **Set low-balance alerts** in **Settings → Notifications** so you do not get caught short.

## How payroll checks funding

Payroll settles per **cohort**: a pay group (team, department, or contractor batch) run together on its own schedule. When a run starts, Zebec checks that the cohort's allocation covers every recipient as of the current roster.

* **No partial paychecks.** An individual is never paid a fraction of what they are owed.
* **Within a run, either everyone settles in full or it halts.** Zebec will not pay half a team.
* **Funded cohorts are not blocked by unfunded ones.** If Engineering is funded and Sales is not, Engineering runs and only Sales pauses.
* **Roster changes apply at run time.** Added headcount raises the amount required; offboarded recipients are excluded before the check.
* **One treasury, multiple cadences.** Each run draws its own earmarked allocation, so weekly and monthly runs stay independent.

Zebec alerts you ahead of each run to top up before anything halts.

## Security

Consider enabling multi-sig for the signing wallet. See [Security and compliance](/zebec-application-suite/enterprise-payroll/security-and-compliance.md) for details.