> ## 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.
# Payouts
> Turn approved commission into partner payouts - grouped, approved, paid, and documented with statements partners can see.
export const Headless = ({prompts = []}) => {
const PromptRow = ({prompt}) => {
const [copied, setCopied] = useState(false);
const copy = () => {
try {
navigator.clipboard?.writeText(prompt);
} catch {}
setCopied(true);
setTimeout(() => setCopied(false), 1600);
};
return ;
};
return <>
Introw is headless by design: run everything here in plain language from Claude, ChatGPT,
Slack, Teams, or your own CRM through Introw's MCP server, with every
action written straight back to your CRM source of truth. The portal is one surface, never the only one.
{prompts.length > 0 ? :
The agentic playbook - lifecycle deep dives and a Claude Code skill library that run your partner program
from Claude, ChatGPT, Slack, and your CRM.
}
;
};
> Payouts turn approved commission lines into money in partners' hands: group lines into a payout, move it through approval to paid, generate a statement, and let partners track it in the portal.
## What it does
A payout groups a partner's approved commission lines into one amount to be paid. You create
payout batches by period, filter, or selection, then move each partner's payout through clear
stages, from draft through approval and invoicing to paid. Along the way Introw generates
statements, and you can request a partner invoice and record purchase order numbers, keeping the
whole payment process organized in one place.
Partners are not left guessing. They see their potential, expected, upcoming, and paid amounts in
the portal, can upload an invoice and set a PO when asked, and can even query commission status
through an AI assistant. Finance gets a documented, auditable trail, and the same payout data is
available through the API for downstream systems.
## The problem it solves
Paying partners from spreadsheets is slow, opaque, and error-prone:
* **Payments are assembled by hand** → Group approved lines into payout batches automatically.
* **Approval is ad hoc** → Move payouts through clear, auditable stages.
* **Partners chase you for status** → Partners see and track their payouts in the portal.
* **Statements are manual** → Generate payout statements in-product.
## From problem to solution
Payouts give the payment process structure. Batch the approved lines, run each through approval to
paid, and generate statements partners can see. Finance gets an auditable trail and partners get
transparency, all without spreadsheets.
```mermaid theme={"theme":{"light":"github-light","dark":"github-dark"}}
flowchart LR
batch["Batch approved lines"] --> approve["Run through approval"]
approve --> paid["Paid"]
paid --> statement["Statement partners see"]
```
## Use cases
Group approved lines into partner payouts.
Move payouts through documented stages.
Let partners track payouts in the portal.
Generate statements and record invoices and POs.
## Impact
* **Low total cost of ownership** - Partner ops runs payouts end to end with no engineering.
* **Work where you already are** - Partners track earnings in the portal or via an AI assistant.
## Who it's for
Creates and manages partner payouts.
Approves payouts and reconciles statements.
## Works with
{/* CONNECTS:START - generated content goes here */}
Payouts batch the approved lines.
Reconcile payouts to invoices.
Pay each partner in their currency.
## Headless
## Going deeper
Setup, configuration, and all how-to guides.
Integration surface and code.