You are here:
Considerations for Payout Periods
Review these considerations when you define payout periods for a rebate program.
Required Editions
| Available in: Enterprise, Unlimited, and Developer Editions that have Rebate Management enabled. |
- If the payout frequency of the rebate program is Custom, you can’t generate payout periods automatically. Create each payout period with start and end dates of your choice.
- You can’t generate payout periods automatically when a rebate program is in Active status. However, you can create payout periods manually.
- The names of the generated payout periods are shown in the Frequency Fiscal Year format. For monthly, quarterly, and yearly programs, the names of the periods are according to the program’s frequency and fiscal year of your org. For biannual programs, the names are according to the period start and end dates.
- Total Approved Amount, Total Rejected Amount, and Number of Member Payouts are read-only fields. The application auto-populates the values in these fields based on the transactions in an active payout period. These fields are derived and computed via SOQL at sync time. Syncing this object via a Data Manager connection can result in a QUERY_TIMEOUT error in orgs with large data volumes (~25,000+ records). See Considerations and Limitations for Rebate Management.
- When you create a payout period, the Last Calculation Date and Payout Amount fields aren't populated. You can view these details when the payout is calculated for the period. The application updates the payout amount whenever the scheduled flow runs.
Did this article solve your issue?
Let us know so we can improve!
