SquareOS Docs
Integrations

Commission Management

Commission Management defines sales payout plans, staff/location assignments, adjustments, commission runs, approvals, and payout closing for staff incentives.

What this page is for

Commission Management defines sales payout plans, staff/location assignments, adjustments, commission runs, approvals, and payout closing for staff incentives.

Who should use it

Owner, sales manager, finance

Where to find it

/admin/commission-management

Before you start

  • Commission plan fields are Code, Name, Basis, Payout frequency, Rate %, Status, Effective from, Effective to, Description, and Rules JSON.
  • Commission assignment fields are Plan, Staff, Location, Effective from, Effective to, and Active.
  • Commission run fields are Plan, Period start, and Period end, with Add adjustment, Create run, Approve, and Close payout actions.
  • Commission adjustment fields are Run, Staff, Direction, Amount, and Reason.
  • Basis decides whether commission is calculated on Payment received or Invoice finalized.
  • Payout frequency should match the owner payroll process: Monthly, Weekly, or Quarterly.
  • Rules JSON should capture only the approved payout logic. Keep it valid JSON and avoid hidden side deals outside the system.
  • Approve should happen only after manager review. Close payout should happen only when finance is ready to mark payout closed.

Daily workflow

  • Create commission plan, create staff/location assignments, run commission for the period, review earnings, add adjustments if needed, approve, then close payout.
  • Use Credit adjustment to add payout and Debit adjustment to reduce payout. Always write a clear reason.
  • Keep old plans Paused or Archived when policy changes instead of overwriting historical payout rules.

Watch out

  • Do not approve a run before checking refunds, voids, discounts, and payment timing because payout disputes are difficult after close.
  • Use the left menu to open related pages in Integrations.
  • Use Ask Docs for questions that are already covered in this public documentation.

On this page