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 Revenue reports and add the first source document.

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 any source

1. Open Revenue reports.
2. Create a sales report and choose its sales year, month and currency (USD, EUR or PLN).
3. Add one amount per game.
4. Record the exact PLN received in the bank. Revenue Ledger shows its proportional allocation and effective exchange rate.
5. Submit the complete report and PLN receipt for acceptance.

The source can be any store, distributor or publisher. Steam, GOG and Epic are examples only. Accept locks both the report and its received PLN. Reject returns the complete set for editing.

Payment arrives later or in parts

1. Keep the report as a draft in its original sales month.
2. Record each actual PLN transfer with its own bank date and reference.
3. Review the per-game allocation after every part.
4. Submit the report for acceptance when its received PLN is ready to be locked.

The sales month and bank date are independent. A later settlement can combine accepted transfers from several sales months.

Add and recover a cost

1. Create an already-paid cost under the correct project.
2. Select the participant who paid it.
3. Enter Source amount in the original currency and Settlement value PLN as the actual PLN cost. Their ratio is shown as the effective exchange rate.
4. Submit and approve the cost.
5. The next project settlement returns the approved value oldest-first before splitting the remaining revenue.

Approval makes the full Settlement value PLN eligible for recovery. Costs never move between projects.

Create a multi-month settlement

1. Open Settlements. All eligible received revenues and approved costs are selected by default.
2. Uncheck anything that should wait for a later closing. Unapproved rows stay visible in grey with a reason.
3. Review each game's PLN revenue, cost recovery and remaining revenue share.
4. Choose a calculation date and select Finalize settlement.
5. Open the saved settlement later or export its CSV.

Finalizing stores the exact selected inputs and calculation fingerprint. A used revenue transfer cannot be selected twice; an unrecovered cost balance can continue into a later settlement.

Correct a mistake

• Draft: edit it directly.
• Awaiting approval: reject it with a reason, then edit and resubmit.
• Approved but unused: create a linked replacement draft; approving it voids the original.
• Already paid or settled: do not rewrite history. Add a new compensating source document and include it in a later settlement.

Review an earlier settlement

1. Open Settlements for the organization.
2. Choose any row under Finalized settlements.
3. Review included revenue, included costs and the per-project result.
4. Export CSV when you need an accounting hand-off or archive.

Finalized settlements are read-only. Correct later discoveries with a new source document or compensating entry so the audit trail remains intact.

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 and its reports.

Editor

Can enter project costs.

Settler

Can add, submit and approve project costs and sales reports, and finalize settlements for assigned projects.

Project admin

Can do everything a settler can, and also manage project members, invitations and revenue splits.

Reset financial data

1. Open Workspace and expand Reset financial data 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. Only the organization owner or a superuser can perform it.