> For the complete documentation index, see [llms.txt](https://help.rafflelink.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rafflelink.com.au/managing-your-raffle/proceeds-and-finances/weekly-installments.md).

# Weekly Installments

### State Requirements

* Mandatory for permitted raffles in:
  * Victoria (VIC)
  * Western Australia (WA)
* Required by state gaming regulations

### Payment Schedule

* Week defined: Saturday to Friday inclusive
* Disbursement: Following Monday
* Tracks credit card sales only

### Tracking Payments

* Access via Account Tab
* Features:
  * Weekly installment records
  * Individual invoices
  * Payment status checkboxes

<figure><img src="/files/gPo9pCJCfyazF3PaRkl3" alt=""><figcaption></figcaption></figure>

### Activation Fee Handling

* If "Pay Later" selected:
  * Deducted from first installment
  * Rolls over to next week if insufficient funds

### Opting Out for One Lump Sum Payment at the End

Two methods:

1. Edit Raffle Tab -> Payment Details
2. Contact RaffleLink support


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.rafflelink.com.au/managing-your-raffle/proceeds-and-finances/weekly-installments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.