Owners, managers & users

Payout History: record and review monthly payments

Maintain independent GBP payout records for managers and let each manager see their own timeline.

Browse all guides

This guide describes the available features. Your account role, assigned modules, signed contract and network plan determine which controls you can use. Reading a guide does not change your access.

Start here

  1. Owners: open Payout History and select the manager who received the payment. Managers: open the page to read your own timeline.
  2. Owners: choose Payout Month, enter a non-negative amount and add optional notes explaining the payment.
  3. Choose Save Payout History once, then check the new record. Every save creates an independent entry, including another payment in the same month.
  4. Use the owner’s month/year filter to review a reporting period, and compare the table with the all-time Total Recorded and Latest Month cards.

Know whose records you can see

The network owner sees records for managers belonging to the network and can add or delete them. A sub-user sees only their connected manager profile’s payout timeline and cannot change records. If a manager session cannot be resolved, sign in again.

The page is a record of amounts entered by the network. Saving an entry does not issue a bank transfer or prove that a payment provider completed a transfer.

Record a monthly payout accurately

Choose the manager carefully, checking both name and email where shown. The searchable manager selector helps when the network has many accounts. If there are no managers, create their accounts before recording payouts.

Manager
The recipient manager account under this network.
Payout Month
The month to which this particular record belongs, chosen with the month field.
Amount
A value of zero or more, saved to two decimal places.
Currency
Records created by this form use GBP. The currency is not a free choice in the save handler.
Notes
Optional explanation such as a payment reference, adjustment reason or separate installment.

Understand independent entries and totals

Multiple payments can be recorded for the same manager in the same month. Saving another amount does not replace that manager’s earlier amount. For example, two separate installments need two rows; accidentally saving the same installment twice also creates two rows and overstates the recorded total.

Total Recorded and Latest Month are all-time summary values. The owner’s Filter by Month / Year narrows the Payout Records table, so a filtered table does not have to add up to the all-time card. Clear the filter to return to all periods.

Review, correct and delete

Each table row includes its month, recipient where applicable, amount, notes and updated date. Owners use Delete on the exact row they need to remove and confirm the removal. There is no inline edit form; correct an erroneous entry by carefully removing it and saving the replacement.

Managers should report an incorrect or missing row to the network owner with the month and amount. No payout history yet means the network has not recorded a row for that account; it is not a calculation of earnings from creator performance.

Frequently asked questions

Will a second save for the same month overwrite the first?

No. Each entry is independent. Check the existing table before saving an installment again.

Why does the total not match my filtered table?

The Total Recorded and Latest Month cards use all-time history. The owner’s month filter affects the record list.

Can a manager change a payout?

No. Managers have a read-only view of their own history. The network owner must correct the record.

Can I select another currency?

The current form saves GBP amounts. Do not enter a foreign-currency number expecting automatic conversion.

Still stuck? Note the page name, the step you tried and the exact message shown. Managers and sub-users should contact their network owner; owners should contact their platform administrator. Never include passwords, webhook URLs, recovery links or private identity documents in a general support message.