> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/partners/partner-administration/azure-revenue-share-and-payouts.md).

# Azure Revenue Share and Payouts

When Microsoft actually pays your Azure Marketplace revenue share, why CSP and MCA deals pay a month later than EA, and how to track a payment in Partner Center.

Your margin on Archera premiums is real revenue, but it does not arrive the month the usage happens. This page explains the lag so Operations and Finance can forecast it correctly.

Read [Azure Marketplace Offers 101](https://docs.archera.ai/partners/partner-administration/azure-marketplace-offers-101.md) first if you need the underlying economics.

***

## The short version

{% hint style="warning" %}
**Expect premium revenue roughly 3–4 months after the usage month.** For EA customers it is about 3 months. For CSP and MCA customers it is about 4 months, because Microsoft collects from the customer before disbursing. Add a month if the customer pays by credit card.
{% endhint %}

This is Microsoft's payout policy, not an Archera term. It applies to every ISV on the marketplace.

***

## How the flow works

1. Archera authorizes you to resell and applies your tier discount
2. The offer is established — an ISV-to-CSP Private Offer, or an MPO extended to the end customer
3. The customer uses Guaranteed Commitments, generating metered premium usage
4. Microsoft invoices and collects, according to the customer's agreement type
5. Microsoft disburses to Archera and to you
6. **The disbursed amount is the offer price minus Microsoft's listing fee**

{% hint style="info" %}
Archera's offer is categorized as **usage-based**, so the usage-based payout schedules below are the ones that apply — not the subscription schedules.
{% endhint %}

***

## Timeline — Enterprise Agreement customers

Microsoft issues payouts in the next cycle, often **before** it has collected from the customer.

| Event                               | Reporting visibility             | Timing                   |
| ----------------------------------- | -------------------------------- | ------------------------ |
| Usage occurs                        | Usage dashboard                  | Month 1                  |
| Microsoft calculates billing amount | Usage dashboard                  | Month 2                  |
| Transaction reported                | `Unprocessed` in Earnings report | Month 2                  |
| Payout prepared                     | `Upcoming` in Earnings report    | Month 3, first week      |
| **Payout sent**                     | `Sent` in Earnings report        | **Month 3, by the 15th** |
| Customer pays invoice               | No change                        | Months 3–12              |

Because payout can precede collection, Microsoft has a defined [process for customer nonpayment](https://learn.microsoft.com/en-us/partner-center/marketplace-offers/payout-policy-details#process-for-customer-nonpayment) that can claw back amounts already disbursed.

***

## Timeline — CSP and MCA customers

{% hint style="info" %}
**Transactions only become eligible for payment once Microsoft has collected from the customer.** This is the single biggest driver of the extra month.
{% endhint %}

| Event                               | Reporting visibility             | Timing                   |
| ----------------------------------- | -------------------------------- | ------------------------ |
| Usage occurs                        | Usage dashboard                  | Month 1                  |
| Microsoft calculates billing amount | Usage dashboard                  | Month 2                  |
| Invoice sent to customer            | Revenue dashboard                | Month 2                  |
| Customer pays invoice               | Usage dashboard                  | Month 3                  |
| Transaction reported                | `Unprocessed` in Earnings report | Month 3                  |
| Payout prepared                     | `Upcoming` in Earnings report    | Month 4, first week      |
| **Payout sent**                     | `Sent` in Earnings report        | **Month 4, by the 15th** |

Add approximately one month to the final two rows if the customer pays by credit card.

{% hint style="info" %}
Usage dates in Microsoft's reporting show as the **first of the month in which usage occurred** — October usage appears as 10/1 regardless of the day. Payout dates are Pacific Standard Time.
{% endhint %}

***

## From Microsoft to your bank

Microsoft typically sends payments due by the 15th of the month. How long the money takes to land depends on your payout method:

| Payment method | Days to reach your account |
| -------------- | -------------------------- |
| PayPal         | 1 business day             |
| ACH / SEPA     | 2–3 business days          |
| Wire transfer  | 7–10 business days         |

These intervals are approximate.

***

## Tracking a payment

Use the Partner Center [Earnings — Payments report](https://learn.microsoft.com/en-us/partner-center/earnings/earnings-payments), which covers all incentive, marketplace, and store programs.

1. Sign in to [Partner Center](https://partner.microsoft.com/dashboard/home) and select **Earnings**
2. Select **Download report → Earnings | Payments**

Match on `paymentStatus`: `Unprocessed` means reported but not scheduled, `Upcoming` means scheduled for the next cycle, `Sent` means Microsoft has released it.

***

## What this means for Operations

* **Do not book premium margin in the usage month.** Accrue it, but forecast cash 3–4 months out.
* **Segment your forecast by the customer's agreement type.** EA and CSP/MCA customers pay on different schedules; a blended assumption will be wrong for both.
* **Reconcile against the Archera platform.** Premiums shown in the customer's Archera organization, less your tier discount, should tie to the marketplace transaction. Investigate persistent gaps as plan ID issues.
* **For MPO deals, confirm the plan ID before the period opens.** Usage emitted against the wrong plan ID will not bill, and therefore will not pay out. See [Which Azure Offer Type Applies to You](https://docs.archera.ai/partners/partner-administration/azure-marketplace-offer-types.md).

***

## Reference

* [Microsoft: Payout schedules and processes](https://learn.microsoft.com/en-us/partner-center/marketplace-offers/payout-policy-details)
* [Microsoft: Earnings and payments reports](https://learn.microsoft.com/en-us/partner-center/earnings/earnings-payments)

Questions: <partners@archera.ai> or the shared Slack workspace.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.archera.ai/partners/partner-administration/azure-revenue-share-and-payouts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
