Payouts is your worklist of everything the company's signed documents owe. Production creates a payout from a document; you decide when and how it gets paid. Connie prepares the data and keeps the record. It never moves money: the payment itself still happens in your own bank or salary system.

You will find Payouts in the main menu, with four tabs: To pay, On hold, Paid and Archived.

Open Payouts settings before you start working the list. Three things live there.

Every field is Required, Optional or Not used:

This is the most consequential setting in the module. A payout missing a Required field cannot be moved to Paid at all, and it shows a Details missing badge so you can see why. Set this to match what your salary system actually needs, no more: every Required field you add is one more thing to chase before anyone gets paid. Saving recalculates every payout in the account straight away.

Your own lists, your own words. They become the options on each payout and columns you can export.

Auto-archive paid payouts after a number of days, so the Paid tab stays current and finished work moves itself out of the way.

Each row tells you what is blocking it. Details missing means required beneficiary data is absent. A bank-change badge means the beneficiary's account details changed and want a human look before anything is paid against them.

Moves are named for the tab they land in, so the row menu offers Move to To pay, Move to On hold, Move to Paid and Move to Archived. Select several rows to move them together. Move to Paid is unavailable while a payout is not payable, which is the required-fields setting doing its job.

Sensitive values such as CPR, bank account and BIC are encrypted on the payout and hidden by default. Nothing is decrypted until you ask for one payee's one field, and asking is written to the audit trail.

When details are missing, use Request beneficiary information on the payout. The payee gets a secure personal link, fills in only the fields you asked for, and the payout updates itself. Bank details are checked as they are typed, so typos never reach a payment run.

You can resend a request that has gone quiet, or revoke one you sent by mistake. Requests expire on their own.

This is the part worth ten minutes of setup.

Open the column editor and turn on exactly the columns your salary system or bank expects, in the order it expects them. Save that as a named view, for example "Salary import" or "Bank transfer file". A view can be kept for yourself or saved for everyone, so the whole team runs the same file every month rather than rebuilding the columns from memory.

The export then follows the list rather than fighting it:

So the sequence is always the same:

The slideout opens on the columns you are already looking at, and you can untick a column or drag one into a different position for this file only. Your saved view stays as it was.

Run the payment in your own bank or salary system as usual. Come back, select the payouts that went out and Move to Paid. Each one records the date and keeps its payout reference, which is what production sees on the document.

If a payment turns out to be wrong, reverse it from the payout. The reference is kept, so the record still shows what happened rather than pretending it never did.

Payouts needs the Manage Payouts permission, which also enables Create Payout on signed documents. Guests and collaborators never get it. The worklist is account-wide rather than per project, because paying what the company owes cuts across productions.