From platform report to partner payout.

First project setup

1. Add every person or company that can receive revenue or recover a cost as a participant.
2. Create the game as a project.
3. Open the project and create a revenue split totaling exactly 100%.
4. Optionally create invitation links for people who need access.
5. Open the first monthly period.

Participant ≠ user. A participant receives money. A user is an account that can log in. A participant does not need an account.

Add revenue from a platform

1. Open the month shown on the platform report.
2. Create a sales report with its platform, number, date and source currency.
3. Add one line per game and assign each line to its project.
4. Submit the draft and have an authorized user approve it.
5. When the bank transfer arrives, record the exact PLN amount. Revenue Ledger allocates it between games proportionally.

A platform can be any store, distributor or publisher—for example Steam, GOG or Epic. Drafts can be edited; approval locks the source data and preserves the audit trail.

Payment arrives later or in parts

1. Leave the approved report in its original sales month.
2. Open the month in which cash actually reached the bank.
3. Choose Record PLN received and select the older approved report.
4. Enter each partial transfer separately.

The sales month can be closed while the report remains unpaid. Cash participates in the settlement month in which it arrived.

Add and recover a cost

1. Create a cost under the correct project.
2. Select the participant who paid it and enter its PLN settlement value.
3. Submit and approve the cost.
4. Record the amount actually paid by that participant.
5. The next project settlement returns eligible costs oldest-first before splitting the remaining revenue.

An approved but unpaid cost is recorded, but it does not enter cost recovery yet. Costs never move between projects.

Settle a project and record payouts

1. Review the preview: PLN revenue, cost recovery and remaining shared revenue.
2. Resolve any warning, such as a missing active revenue split.
3. Select Finalize and lock.
4. Record transfers made to each participant; partial payouts are allowed.
5. Export CSV when you need a hand-off or archive.

Finalizing stores the exact calculation inputs. Later changes do not silently rewrite an old settlement.

Correct a mistake

• Draft: edit it directly.
• Awaiting approval: reject it with a reason, then edit and resubmit.
• Approved but unused: choose Create correction. A linked replacement draft is created; approving it voids the original.
• Already paid or settled: do not rewrite history. Add a compensating adjustment in a new open period.

Close a period

1. Resolve every draft and item awaiting approval.
2. Finalize every active project settlement.
3. Review the closing checklist.
4. Close the period to make it read-only.

Unpaid approved reports and costs do not block closing. Record their later cash movement in the period in which it happens.

Participants, users and roles

Participant

Person or company named in a revenue split or as the payer of a project cost.

Viewer

Can inspect a project.

Editor

Can enter project costs.

Settler

Can approve costs and finalize settlements.

Project admin

Can also manage project members, invitations and revenue splits.

Reset test settlement data

1. Open Workspace and expand Testing tools under the organization.
2. Read the deletion summary carefully.
3. Enter the exact organization name and the phrase DELETE SETTLEMENTS.
4. Confirm the browser warning.

The reset removes periods and all financial history beneath them. It keeps the reusable setup: organization, projects, participants, users, permissions and revenue splits. The control is hidden unless an administrator explicitly enables the environment flag.