Multi-player Acts - Player Invoices Paid by Venue

Modified on Fri, 26 Sep at 9:49 AM


Audience: Venues (hirers)
Applies to: Multi-member acts (duo, trio, 4-piece, etc.)


1) Who this is for

Venues that book multi-member acts and want each player to invoice the venue directly, while the act owner keeps control of lineup, splits, invites and subs.


2) Why this matters

If one invoice is issued for the whole act, the invoice submitter (act owner) is treated as the payee for the full super amount, leaving the act owner to redistribute SG to players later.


Hot Giggity solves this with player-to-hirer invoicing: SG is calculated and shown per player, and the venue pays each player’s fund directly.

The act owner still controls the booking, splits, invites and subs - you just receive one invoice per player and pay each player’s SG fairly and on time.


3) What it does (at a glance)

  • Per-act, per-venue toggle: applies to future bookings your venue creates for that act.

  • Player → Hirer invoicing: you receive one invoice per player; SG (12%) is calculated per eligible sole trader and shown so you can pay each fund directly.

  • The act owner remains in control, managing the lineup, splits, invites, and subs; players only see their own fee.

  • Industry-first: SG being paid by the hirer is more equitable and solves headaches by removing re-distribution risk and disputes.

Note: Act owners can also enable/disable this for their acts with your venue. If either party turns it ON, bookings created after that point follow the player-to-hirer model.


4) Where to turn it on 

Path: Manage → My Act Roster → (⋯) → Update Invoice Setting → “Act Player Invoices paid by Venue” (toggle ON) → Save.


5) Scope & timing

  • Applies to current and future bookings/requests for that act created by your venue after the toggle is ON.

  • Does not change completed bookings.

  • Independent per act, per venue (enable for some acts, not others).

  • Artists can also toggle it; the latest saved state at booking creation is what applies.


6) What happens in a booking (with toggle ON)

  1. You create the booking for the act; the act owner accepts.

  2. The act owner invites players and sets per-player fees (splits).

  3. Hot Giggity calculates each player’s invoice amount and SG (if Sole Trader with fund details).

  4. Players accept.

  5. You receive one invoice per player showing:

    • Fee (+ GST if the player is GST-registered)

    • SG (GST-free) in the SG Payable panel so you can pay direct to that player’s fund

  6. Your Super I Owe ledger lists each player’s SG for reconciliation and payment.


7) Comparison: When toggle is OFF (default)

  • You receive one invoice from the act owner.

  • SG for eligible players sits in the act owner’s Super I Owe (the act owner remits SG to players’ funds).

  • Players are paid by the act owner, not by the venue.


8) Legal/compliance notes

  • SG is GST-free and must be paid to each eligible sole-trader player’s fund.

  • If a player hasn’t provided fund details in HG, invoice payment may be delayed for that player until details are supplied (include your PO/booking clause).

  • Keep invoices + SG payment confirmations (PRNs) with your records for audit.


9) Edge cases & FAQs

  • Mixed entities: SG appears only for sole traders; companies/partnerships/trusts don’t trigger SG.

  • Missing super details: Booking can proceed, but the player’s payment/SG may be delayed; HG flags missing details.

  • Inclusive vs Plus: You still choose the fee model per booking; SG remains GST-free either way.

  • Rounding: Per-line rounding; totals reconcile to the cent.

  • Who can toggle? Both Venue and Act Owner for their relationship. Changes affect future bookings only.


10) Related links (Venues)



Got questions?

If you have any questions about anything in this article, please email support@hotgiggity.com.









Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article