> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Closeout and payouts

> The after-the-show recipe — mark the gig completed, clear the close-out checklist, pay the crew over ACH or card, and close the books as Settled.

The show is over — now finish the gig. This recipe takes an **Active** gig through **Completed**, the close-out checklist, crew payouts, and finally **Settled**: fully paid, on the books, done. For the concepts behind each state, see [post-event closeout](/features/gigs/closeout) and the [event lifecycle](/reference/event-lifecycle).

## Before the first gig: payout setup

Do this once, not on show night:

* **Organization** — add a payout funding method under organization **Settings → Payments**. ACH-funded payouts are free to the organization (Soundcheck absorbs the fee); card-funded runs show the platform fee before you confirm. Bank accounts show a verification badge — only a **Verified** account can fund ACH runs.
* **Members** — each person you'll pay completes payout onboarding from their [profile](/features/user-guide/profile). A member with a verified bank account is payable by direct deposit from day one.

See [gig payments](/features/gigs/payments) for the full setup guide.

## The flow

<Steps>
  <Step title="Mark the gig Completed">
    Once the show has happened, flip the status picker in the gig header from **Active** to **Completed**. This moves the gig out of active operations and into closeout — delivery is done, the money isn't yet.
  </Step>

  <Step title="Work the close-out checklist">
    Open the gig's **Closeout** tab. The checklist tracks the business back-half: **contract signed, quote approved, deposit received, invoice sent, payment received, feedback logged**. If your organization enforces close-out gates, the blocking steps lock **Settle** until they're complete — the lock message tells you exactly what's missing (*"Locked until the invoice is sent"*).
  </Step>

  <Step title="Capture reviews">
    Closeout is also where you rate the event, the venue, and the crew. These become part of the gig's permanent history and the reputation record that follows people and venues across future gigs.
  </Step>

  <Step title="Run the payouts">
    From the gig's **Finances** tab, review the payables — every accepted invitation and crew offer with a fee. Select who to pay, choose the funding method (ACH for free runs, card when speed matters), and confirm. Payouts move **Processing → Paid** as they settle; ACH takes longer than card, which is normal. Members paid outside Soundcheck (cash, checks) can be recorded as paid manually so the ledger stays truthful.
  </Step>

  <Step title="Mark the gig Settled">
    When every payable has cleared and the checklist is done, flip the status to **Settled**. That's the final state: everyone's been paid, the books are closed, and the gig is a complete, verified record. The tour roll-up and your finance totals now reflect real money.
  </Step>
</Steps>

## Common pitfalls

<AccordionGroup>
  <Accordion title="Settle is greyed out with &#x22;Settle all payouts in Finances first&#x22;">
    At least one payable is unpaid or still processing. Open the Finances tab, find the outstanding rows, and either run the payout or record it as paid manually. Settlement is blocked by design until nothing is owed — you can't close the books on a gig someone's still owed money on.
  </Accordion>

  <Accordion title="Settle is locked with &#x22;Complete N close-out steps first&#x22;">
    Your organization enforces close-out gates and blocking steps are incomplete. Finish them on the Closeout tab — or, if the books genuinely need to close early, an owner or admin can use **Override & settle**, which logs a reason. The override skips the checklist, never the payouts.
  </Accordion>

  <Accordion title="A member shows as ineligible in the payout run">
    They haven't completed payout onboarding, haven't accepted their invitation, or were already paid. The payout review shows the reason per row — fix the setup and re-run; eligible members can be paid without waiting for stragglers.
  </Accordion>

  <Accordion title="The checklist doesn't lock anything for us">
    Enforcement is an organization opt-in (**Enforce close-out gates** in organization settings) and applies to gigs created after it's enabled — existing gigs stay tracking-only. Until it's on, the checklist is a shared to-do list, not a gate.
  </Accordion>

  <Accordion title="The gig was cancelled — do I still close it out?">
    No. **Cancelled** is a terminal state outside the lifecycle — a called-off show never needs the checklist or settlement. Payouts not yet initiated are stopped when you cancel.
  </Accordion>
</AccordionGroup>

## Why bother settling?

Every settled gig is a verified record: who worked, what they were owed, and that they were paid. That record powers your finance roll-ups (including per-[tour](/features/gigs/tours) totals), keeps year-end accounting honest, and builds the work history that follows your crew from gig to gig.

## Related

<CardGroup cols={2}>
  <Card title="Post-event closeout" icon="clipboard-check" href="/features/gigs/closeout">
    The checklist, gates, and reviews in depth.
  </Card>

  <Card title="Gig payments" icon="money-check-dollar" href="/features/gigs/payments">
    Funding methods, fees, and payout statuses.
  </Card>

  <Card title="Event lifecycle" icon="diagram-project" href="/reference/event-lifecycle">
    Every state a gig moves through.
  </Card>

  <Card title="Gigs FAQ" icon="calendar" href="/faq/gigs">
    Quick answers on statuses and cancellation.
  </Card>
</CardGroup>
