Payments
How a payment travels
A payment moves through two steps, and both matter.
The school records it
A school administrator enters the amount, the method, and a reference number. This is a claim, not a confirmation. It appears immediately as awaiting confirmation.
A coordinator confirms it
Once the money has actually arrived, a coordinator confirms the payment. Only then does it count.
A recorded payment marks nothing on its own. Until it is confirmed, the school’s teams stay pending and the amount is not counted as collected.
What a school sees
| Figure | Meaning |
|---|---|
| Amount due | Billable teams × the fee per team |
| Confirmed | Payments a coordinator has confirmed |
| Outstanding | The difference |
Waived teams are not billed. Withdrawn teams are not billed.
When teams become paid
Teams are marked paid when confirmed payments cover the full amount due.
A partial payment marks nothing. A school owing 30,000 that pays 10,000 has one third of its balance settled and no teams marked paid — this is deliberate, so a school cannot field unpaid teams by paying a fraction.
Duplicate submissions
If a school records the same reference number twice, iRank returns the original payment rather than creating a second one. A transfer entered twice does not become two payments.
Confirming and rejecting
Confirming sends the school a confirmation email with the amount and reference.
Rejecting marks the payment as failed and sends nothing. Use it when a claimed payment never arrived — and tell the school separately, since a rejection is not self-explanatory.
What a coordinator sees
The finance view shows every school’s position for a tournament, sorted with the largest outstanding balance first, plus the total expected, collected, and outstanding, and how many payments are waiting for review.
School data isolation
A school administrator can see only their own school’s finances. Attempting to view another school’s payments is refused, not merely hidden.