# Royalties Payments

**Sales Reporting Schedule**

We aim to report all sales on the 20th of the third month following each download or stream. For example, sales from January will appear in the report issued on April 20th. The three-month period allows us to collect and process all data from digital services, as follows:

* **Month 1**: Music fans download or stream your music.
* **Month 2**: Music services compile the data and create reports to send to us.
* **Month 3**: We process and verify the data to generate your report.

Please note that some digital services only provide quarterly sales reports. In these cases, sales from January will be combined with February and March sales in a single report released on June 20th.

Occasionally, older sales data may appear in your reports if a digital service delays report submission or payment.

While rare, some sales might be delayed due to technical processing issues. If this occurs, the sales will appear in the following cycle, and we will clarify the reason for the delay.

<figure><img src="/files/rNcWJWT1JWEuAR2Z9yr9" alt=""><figcaption><p>Royalties Withdrawal</p></figcaption></figure>

**Payment Information**

* **If you signed the self-billing agreement**: Payments are made monthly for all ASIA labels and upon reaching a $50 threshold for non-ASIA labels. Funds are transferred by the 15th of the month following the report's issuance (see reporting schedule).
* **If you did not sign the self-billing agreement**: Payments are processed on the 15th of the month after your invoice is received.

{% hint style="info" %}
Payout Method :
{% endhint %}

* Paypal
* Bank Transfer&#x20;


---

# Agent Instructions: 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:

```
GET https://labelmiraclestudioapps.gitbook.io/labelmiraclestudioapps/payments/royalties-payments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.