Pay-run and payouts

Pay-run creation, lifecycle, payment methods, audit trail

Pay-run and payouts

A pay-run is the salon's "pay batch." Aggregate commission, wages, and tips for a period (weekly, bi-weekly, monthly) and pay it out to staff.

Where to find it

/manager/staff/pay-runs. Sidebar Team → Pay Runs.

Create a new pay-run

Steps

  1. + New pay-run button
  2. Period: start-end dates (e.g., 2026-04-16 to 2026-04-30)
  3. Select staff (default: all active)
  4. Save → status: PENDING

System aggregates for the period:

  • Approved commission records
  • Working hours (Wages)
  • Tip items
  • (Overtime included)

Pay-run statuses

PENDING

Created, awaiting review.

PROCESSING

You're reviewing, possible last edits.

COMPLETED

Payout done. Immutable (no edits).

Pay-run table

One row per staff:

  • Name
  • Wage (hourly × hours worked)
  • Overtime (separate column if any)
  • Tip (collected during period)
  • Commission (Approved status records)
  • Deductions (if any: loan repayment, etc.)
  • Net (total payable)

Payout flow

Review

On the PENDING pay-run:

  • Numbers correct?
  • Any bad records?
  • Deductions right?

If something's off, manually adjust the record (in Commission Activity), then return to pay-run.

Process

If OK: Process button. Status PROCESSING. Reversible from here.

Complete (payout)

Per staff or bulk: Mark as Paid:

  • Payment method: Cash / Bank transfer / Custom
  • Reference number (bank transfer)
  • Note (optional)

Pay-run status COMPLETED, related commission records jump to PAID.

Audit trail

COMPLETED pay-run is immutable:

  • Any modification needs a new pay-run (compensation, rectification)
  • Data and payment methods all stored
  • Recallable for labor law / tax authority

Staff view (Staff Portal)

Staff sees in Staff Portal:

  • Own current (open) pay-run (live calculation)
  • Past (completed) pay-runs
  • Payment method, reference number

Only own data, not others'.

When to use it

Scenario 1, classic bi-weekly pay-run 1-15 and 16-end. Two pay-runs per month. 30-min routine bi-weekly.

Scenario 2, monthly pay-run Whole month (1-end). One big pay-run instead of bi-weekly. Usually for larger salons.

Scenario 3, ad-hoc bonus pay-run Christmas bonus as separate pay-run, only bonus items. Independent of normal pay-run.

Scenario 4, dispute on a completed pay-run Staff complains about a 2-month-old pay-run. Immutable, no edits. New pay-run with compensation (or rectification).

Scenario 5, multi-location pay-run L1 and L2 separate pay-runs (different bookkeepers). Or one combined if same bookkeeper.

Tips

  • Before creating pay-run, always verify all are Approved status. Pending records don't go in.
  • Can't edit a COMPLETED pay-run, so pre-Process review is key.
  • Payment method should record reference, bank transfer = transaction ID. Audit-grade.
  • Staff sees pay-run in Staff Portal, transparency given. Dispute → data is there.
  • Weekly vs monthly is a cash-flow question: weekly = staff satisfaction, monthly = admin ease.
  • Deductions (loan, advance) are a separate record type, don't mix with normal commission.

Related articles

#payouts#pay-run#kifizetés#audit
💬

Have a question? Ask the AI assistant

The Bookinda AI knows the entire help center and can answer in seconds.

B

Bookinda AI Assistant

Ask anything about features, settings, or integrations.

Hi! I'm the Bookinda assistant. I can answer questions about features, billing, integrations, and more. What would you like to know?

Still need help?

Get in touch with our support team.

Contact us