> ## Documentation Index > Fetch the complete documentation index at: https://docs.introw.io/llms.txt > Use this file to discover all available pages before exploring further. # Pay a payout cycle with Introw Pay > Take a payout batch from review to paid partners with one invoice: check the batch, choose Pay now, pay the consolidated invoice, and watch Introw Pay send every partner their share. This is the cycle Introw Pay was built to shorten. A batch is waiting, one payout per partner, with the earned lines and a statement behind each. You review it, choose **Pay now**, and pay one invoice. Introw Pay sends every partner their money in their own currency, moves each payout to **Paid**, and emails them. This guide runs that job end to end, including the partners who are not ready yet and the rare payment that bounces, so you finish every cycle with a clean batch and a matching record on the **Payments** tab. ## What you'll achieve A payout batch settled with a single payment. Every ready partner is paid in their own currency, and every payout sits at **Paid** with a statement the partner can download. Partners who were not ready are reminded and held for the next run. The invoice and each partner payment are visible on the **Payments** tab for finance. ## Before you start **Introw Pay** is your payout method and billing info is complete. See [Activate Introw Pay](./activate-introw-pay). You need write access to commissions to choose **Pay now**. On a scheduled cadence the batch is created for you when the period closes. On a manual schedule, choose **Create payout** on the Payouts list and select the period; see [Run a payout cycle](/features/commissions/payouts/guides/run-a-payout-cycle) for the batch itself. ## Steps ### Phase 1 - Review the batch Go to [Payouts](https://app.introw.io/commission?section=payouts) and open the batch for the period you are paying. The **Payout details** page lists one row per partner with **Amount**, **Commission**, **Status**, **Last modified** and **Invoice**. Use the **All**, **Pending**, **Paid** and **Declined** tabs to see what is still open. Open a partner's payout to see the lines behind it. **Decline** a line with a reason, such as **Duplicate commission** or **Disputed by partner**, to void it; **Postpone to next cycle** to hold a valid line back without voiding it; **Restore** anything declined in error. A partner whose lines are all declined drops to **Declined** and is left out of the run. Whole payouts can be declined or postponed the same way from the row actions. Filter the table on **KYC ready** to see which partners Introw Pay can pay. A partner reads **Verified** on the **Payment details** row of their payout when they can be paid. Anyone at **Not connected**, **Incomplete**, **Restricted** or **Deauthorized** cannot receive money yet. Select them and choose **Remind partners to set up payouts**, then **Send reminders**: each partner champion gets a **Set up payouts** email, at most once per payout per day. See [Get partners ready to be paid](./get-partners-ready-to-be-paid) for what they do next. ### Phase 2 - Pay the batch Choose **Pay now** in the batch header to pay every ready partner, or select partners and use the bulk **Pay now** action to pay a subset. The **Pay commissions** dialog shows exactly what is about to happen: * **Total commission** - the sum of the ready partners' payouts, in your company currency. * **Introw Platform fee** - the fee your arrangement bills to you, if any. When your arrangement deducts the fee from partners instead, this line is zero and partners receive the commission net of it. * **Total due** - what your invoice will say. * **Pending payout setup** - partners who are not **Verified**. They are left out of this invoice and stay in the batch. Nudge them from here; the dialog previews the reminder email. Confirm with **Pay** the amount **now**. Introw Pay locks the lines it covers and issues one invoice to your company, with one line per partner. The header now reads **Waiting for payment**, and **View and pay invoice** opens your invoice. Pay it by bank transfer from your own bank, as you would any supplier invoice. On the **Payments** tab it appears as a **Customer Collection** at **Open** until the funds arrive. If you need to stop the run before paying, choose **Void invoice** in the dialog; the lines are released back into the batch and nothing is owed. ### Phase 3 - Let Introw Pay settle it When your payment lands, the header switches to **Processing**. Introw Pay creates one payment per partner, in the partner's currency, and each payout moves from **Pending payment** through **Scheduled** to **Paid** on its own. On the **Payments** tab your collection reads **Completed** and each **Partner Disbursement** moves from **Processing** to **Completed**. Every partner gets an email that the money is on its way, naming the masked bank account it went to, with the statement regenerated in their currency. If a partner's bank rejects the payment, the header reads **Action required** and that payout shows **Blocked** or **Failed** with the reason, most often bank details that need updating. The partner corrects them from the **Payment details** row in the portal; then you choose **Retry transfer** (or **Retry transfers**) on the batch. Nothing else in the batch is held up by one partner. If the invoice was only partially paid, every payout on it stays blocked until finance settles the remainder. ## Verify it worked The batch moves into the **Paid** tab on the Payouts list and **Total paid** on the commission dashboard reflects the run. Each partner's payout reads **Paid** with a **Commission Statement** they can download from the portal, and they have received the payout email. On the **Payments** tab, the **Customer Collection** for the run and every **Partner Disbursement** read **Completed**, which is the record finance reconciles against your one bank transfer. ## Related What partners do once, and how to nudge the ones who have not. Creating the batch, and the stages a payout moves through. Export the run, or read it through the API. Every setting, status and failure state.