Aggregation Period

Note: Once configured, Aggregation Period is the same across the platform and cannot be configured by request type. 

Default configuration for multi-recipient and single recipient requests is an aggregation period of one year, starting Jan 1st. However, aggregation can be configured by your organization's specifications to cover a specific period by a certain number of months and/or with a specific start date. 

• Period in Months (for example, 6 months, 12 months, 72 months, etc.)
• Start Date (for example, Dec 1, Dec 30, Jan 1)

Example: Aggregate Analysis threshold can be configured to start on the 15th of each month or for every 12 months starting on June 30th, if the customer's fiscal year runs June to June

Threshold Amounts

For both Aggregate Spend and Aggregate Count different threshold amounts are configurable for each support category and for the request total. 

• Support category total (amount/frequency) or customers may also choose not to set a threshold for a particular support category. 
• Request total (amount/frequency)

The Aggregate Threshold is based on the Activity Date value in the questionnaire. If the Activity Date is in the next configuration period for aggregation (next fiscal year, next calendar year, next quarter), the amount will not be counted for the current period but will be counted for the next one. If the Activity Date in the questionnaire is a date range, then the start date will be the date for aggregation. 

Example: If the date range begins December 30th, 2023 and ends January 2nd, 2024 the aggregation will be included in the 2023 totals.

Things to Note

Is there Aggregate Spend and Count for Organizations? Aggregate spend and count analysis in requests where the recipient is an organization ( e.g. External Funding, Donations & Sponsorships, etc.) is done at the overall request level and not at the type of funding level.

Which request statuses are included in the Aggregation? The aggregated calculation includes only Approved, Recorded, Reviewed, Awaiting Approval and Update Pending recipients. The calculation is updated when a request or recipient is submitted or updated and resubmitted.

(Note: The Aggregate Analysis table is viewable within requests in Draft status, however, the table will not include that specific request and amounts until the request is submitted.)

Is the Total Amount within Request Type and Support Categories done across all request types? The aggregate spend and count analysis is done for each request type individually. It does not do aggregation across all different request types. 

For example, the totals for meals provided in an HCP Engage request and will not combine meals from Provide a Gift, Hospitality, or Transportation request.  

For RGEH requests, aggregate amounts are displayed for both the party giving the gift and the individual receiving the gift. 

Note: The submitter (individual receiving the gift) is added to the Aggregate Analysis table when the request is still in Draft status. The provider of the gift, is added to the Aggregate Analysis when the request is submitted.

 

Are translations available for the Aggregate Analysis page? No. Translations are currently unavailable for Aggregate Analysis.

Do users need a specific privilege to view Aggregate Analysis? No. The ability to view Aggregate Analysis is a default privilege for both submitters and approvers.