> For the complete documentation index, see [llms.txt](https://qash.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qash.gitbook.io/docs/transactions/transaction-lifecycle.md).

# Transaction Lifecycle

Every action on Qash: paying a bill, sending funds, or claiming incoming tokens goes through a multisig proposal lifecycle. This ensures that no single person can move funds without the required approvals.

## Overview

```
Create Proposal → Sign → Coordinate → Execute → Settle
```

All transactions follow this flow regardless of how they're triggered (payroll, invoicing, bills, or claiming incoming funds).

## Stage 1: Create Proposal

A proposal is created when you initiate any financial action:

| Trigger                  | What happens                                                     |
| ------------------------ | ---------------------------------------------------------------- |
| **Pay bills**            | Select pending bills and click Pay, a send proposal is created   |
| **Batch send**           | Send to multiple recipients in one transaction                   |
| **Claim incoming funds** | Create a consume proposal to receive tokens sent to your account |

## Stage 2: Sign

Team members with signing authority (Owner, Admin, or Reviewer roles) review and sign the proposal.

* Each signer reviews the proposal details (recipient, amount, token) then sign
* You can also **reject** a proposal if you disagree with it

The proposal remains in **Pending** status until enough signatures are collected.

## Stage 3: Coordinate

Once the required number of signatures reaches the threshold (e.g., 2 of 3 signers), the proposal moves to **Ready** status. 

* Any authorized member can proceed to execute

> Example: If your account requires 2 of 3 approvals, the proposal becomes Ready as soon as any 2 members sign.

## Stage 4: Execute

A team member executes the fully-signed proposal on-chain.

* The signed transaction is submitted to the Miden network
* For bill payments, the linked bills and invoices are automatically marked as **Paid**
* Email notifications (e.g., payslips) are sent where applicable

## Receiving Funds (Consume Flow)

Receiving funds on Miden works differently from most blockchains. Instead of tokens appearing in your wallet automatically, incoming funds arrive as [notes](https://docs.miden.io/core-concepts/notes) that you need to explicitly consume.

### How it works

1. **Someone sends you funds**: A note is created on-chain targeting your account
2. **Note appears in your Pending Receiv:** We detects the incoming note
3. **Create a consume proposal:** Select which notes to claim
4. **Sign and execute**: Same multisig flow as any other transaction
5. **Funds in your vault:** Tokens are now available to spend

> This consume model is a core feature of Miden's architecture. [Learn more about Miden notes](https://docs.miden.io/core-concepts/notes).

## Proposal Statuses

| Status        | Meaning                                   |
| ------------- | ----------------------------------------- |
| **Pending**   | Created, waiting for signatures           |
| **Ready**     | Threshold met, can be executed            |
| **Executed**  | Successfully submitted on-chain           |
| **Rejected**  | Enough team members rejected the proposal |
| **Cancelled** | Cancelled before execution                |