Configure per-request and cumulative spend limits
Configure per-request rules and cumulative thresholds, import limits, and understand warnings, blocks, and recorded results.
Table of Contents
Use spend limits to apply your organization's gifts, hospitality, and other spending policies. Configure the rules for the relevant form, then review the limit findings and cumulative analysis on submitted requests. The examples below use illustrative amounts and categories; use the categories, currencies, and thresholds in your own policy.
Choose the right kind of limit
| Limit | What it checks | Example |
|---|---|---|
| Per-request — Individual | Each recipient allocation of a benefit. | A meal may cost up to 100 USD per recipient. |
| Per-request — Event | The total of the recipient allocations for a single benefit. | A meal shared by several recipients may total up to 500 USD. |
| Cumulative — category | A party’s accumulated amount or benefit count in a category during the tracking period. | A recipient may receive up to 1,000 USD in gifts during the year. |
| Cumulative — Total (all categories) | A party’s combined amount across categories or distinct request count during the tracking period. | A recipient may be associated with no more than five requests during the year. |
Individual and Event rules can both apply. For example, a meal shared by two people at 85 USD each is evaluated as two individual allocations of 85 USD and an event total of 170 USD.
Understand when changes take effect
Changes on Limits take effect immediately. Adding, editing, importing, or retiring limits and changing the cumulative tracking period do not require publishing the form. These changes are recorded in the audit log.
Changes to the form itself—including spend-check settings, geography mappings, offered categories, and the activity-date question—require publishing. Complete those prerequisites before relying on the live rules.
Prepare the form
- Open Form builder and select the form you want to configure.
- Confirm that the form offers the benefit categories you intend to limit. A category must be available on the form before you can use it for a category-specific rule.
- Open Settings and find Spend limits. Enable Check submissions against spend limits to evaluate per-request limit rows.
- For country-specific rules, select the appropriate Country question. It must be a single-value country question on the main form.
- For location-specific rules, select the appropriate Location question on the main form. A location rule uses the answer to this question.
- For cumulative limits, ensure the main form has a date question designated as the activity date. Select Edit form, select the date question on the main form, and open its question settings. Set Standard reporting concept to Activity period. A question's name alone does not establish this designation.
- Publish the form configuration. Return to Limits and verify the country and location mappings, spend-check status, and Activity date question.

Publishing prerequisites: a form with active cumulative thresholds needs a designated activity-date question. Category-specific thresholds must refer to categories offered by the form. Resolve these issues before publishing.
Add a per-request limit
- On Limits, find Per-request limits and select Add limit.
- Select the Category.
- Choose Geography: Any for a general rule, Country for a specific country, or Location for a mapped location. For Country or Location, select the corresponding value.
- Set Healthcare professional and Government official to Yes, No, or Any. Any applies regardless of that attribute. An unknown attribute does not match a Yes or No rule.
- Choose Individual to evaluate each recipient allocation, or Event to evaluate the benefit's combined allocations.
- Enter the required Upper amount and select Currency. If your policy needs a lower bound, enter Lower amount; otherwise leave it blank. A supplied lower amount must be below the upper amount.
- Choose Warn or Block, using the behavior described below.
- Review the complete rule and select Add limit. Verify the saved range, currency, scope, and action in the table.

How Quantum chooses a matching rule
Quantum matches the category, level, geography, and recipient attributes. Among matching rules, a Location rule takes precedence over a Country rule, which takes precedence over Any. For the same geography specificity, an explicit healthcare-professional attribute takes precedence over Any, followed by an explicit government-official attribute. Currency preference is applied after those scope rules.
For example, an Any-country rule of 100 USD and a matching United States rule of 250 USD do not combine into a 350 USD allowance. The United States rule is the more specific match.
Understand Warn, Block, and amount boundaries
| Result or action | Behavior |
|---|---|
| Within | The evaluated amount is between the configured bounds, including amounts exactly equal to either bound. |
| Over + Warn | Quantum records the exceeded limit and allows submission to continue, provided no other rule blocks it. Warn does not approve the request or bypass its approval workflow. |
| Over + Block | Quantum prevents submission while the applicable upper limit is exceeded. The submitter must correct the request before submitting. |
| Below | An amount below the optional lower bound is recorded as Below. The upper-limit Warn or Block action does not turn a below-bound result into an over-limit blocker. |
| Unresolved | Quantum could not complete the comparison, for example because an amount or required currency conversion was unavailable. Investigate the underlying data; Unresolved is not a Within result. |
Per-request example: with an Individual upper limit of 100 USD, 100 USD is within the limit and 125 USD is over it. Warn permits the over-limit submission to proceed for review; Block prevents it.
Import per-request limit rows
Use Import spreadsheet to validate and apply a CSV containing up to 2,000 data rows. Include all ten column headers, even where individual values are blank.
category,country,location,hcp,government_official,level,lower_amount,upper_amount,currency_code,action
Food & Beverage,,,any,any,individual,,100,USD,warn
Gift,US,,any,any,individual,,275,USD,warnThese example rows require Food & Beverage and Gift to be offered by the selected form, and USD and US to be available in the workspace. Replace them with your own valid values.
| Column | What to enter |
|---|---|
| category | An offered category key or an unambiguous category label. |
| country / location | Use one or neither. Leave both blank for Any geography. Use a valid country code or label, or the location value appropriate to the mapped location question. |
| hcp / government_official | yes, no, or any. Blank defaults to any. |
| level | individual or event. Blank defaults to individual. |
| lower_amount | Optional nonnegative decimal amount, strictly below upper_amount. Blank means no lower bound. |
| upper_amount | Required nonnegative decimal amount. Use a decimal point and no currency symbol or thousands separators. Amounts support up to four decimal places. |
| currency_code | An available currency code, such as USD. |
| action | warn or block. Blank defaults to warn. |
- Select Import spreadsheet, then choose the CSV file.
- Select Check file. Validation does not change the saved limits.
- Review every proposed result: Create adds a rule; Update changes an existing rule; Unchanged requires no change; Rejected identifies a row that will not be applied.
- Correct unintended updates and rejected rows in the CSV, then choose the corrected file and check it again. Avoid duplicate rows with the same category, geography, recipient attributes, and level.
- Select Apply when the accepted changes match your policy. Apply writes the Create and Update rows immediately; rejected rows are skipped. An import does not remove existing rules omitted from the file.
- Review the outcome and verify representative rules in the limits table. If the limits changed after validation, check the file again and review the refreshed report before applying.

Review updates carefully: importing a matching rule can replace its amounts, currency, and action. It is not necessarily an add-only operation.
Set the cumulative tracking period
- In Cumulative limits, review the tracking-period summary and the designated Activity date question.
- Select Edit period.
- Enter the Start date that anchors your policy periods.
- Set Length in months to a whole number from 1 to 120.
- Select Save period. The change takes effect immediately.

The start date anchors repeating periods. A January 1 start and a 12-month length create calendar-year periods. A July 1 start and a 12-month length create July-through-June periods. Quantum uses the activity date to select the applicable period; when no activity date is available for a record, it falls back to the submission date. This is a sequence of fixed periods, not a rolling lookback from today's date.
Add a cumulative threshold
- In Cumulative limits, select Add threshold.
- Choose a specific Category, or select Total (all categories) for a combined threshold.
- Enter a positive Amount cap, a positive whole-number Count cap, or both. Amount caps use the organization's default currency, identified in the field label.
- If only one measure needs a cap, leave the other blank. A blank cap means that measure is tracked without a ceiling. At least one cap must be supplied; both cannot be blank, and zero is not a valid cap.
- Choose Warn to flag an exceeded threshold without preventing submission, or Block to prevent a submission that contributes to an exceeded threshold.
- Select Add threshold, then verify the saved category, caps, and action.

A category count measures benefits in that category; the Total count measures distinct requests. Adding several benefits to one request can increase category counts while increasing the Total request count only once. A threshold is exceeded when the evaluated amount or count is greater than its cap. When both caps are set, exceeding either one is sufficient.
Cumulative example: a recipient has 900 USD counted in the applicable period and the new request adds 150 USD. The projected total is 1,050 USD, which exceeds a 1,000 USD cap. Warn allows the request to proceed for review; Block prevents submission. A projected total of exactly 1,000 USD is within the cap.
Edit or retire a rule
- Find the rule in the appropriate limits table and open its Actions menu.
- Choose Edit to change the rule's editable terms. For per-request limits, these are the amounts, currency, and action. For cumulative thresholds, these are the caps and action.
- Review and save the changes. They take effect immediately.
- To stop using a rule, choose Retire and review the confirmation before completing it.
A per-request rule's category, geography, recipient attributes, and level cannot be changed through Edit. A cumulative threshold's category also cannot be changed through Edit. To change this scope, create the intended replacement and retire the obsolete rule. Plan the sequence carefully because each change is live. Retiring a rule removes it from active evaluation; historical findings and audit records remain available.
Read the result on a request
- Open the submitted request and review its answers and benefits.
- Find Limits as of submission. Compare the entered amount, converted amount, limit that applied, and result for each evaluated line.
- Find Cumulative analysis. Read the snapshot label and timestamp: the analysis may be captured at submission, a decision, or stage completion.
- Check the period, party, category, count, amount, caps, and Over threshold? result. Tracked means there is no numeric cap for that measure; it does not mean zero.
- Where a category is available as a link, open it to review the contributing requests.

Snapshot results describe the recorded evaluation at that time. Later policy changes do not rewrite that historical evidence. When investigating differences, compare the snapshot moment, activity period, party identity, category, and currency. Canceled or rejected records and benefits are excluded from counted totals; drafts are not historical submitted spend.
Troubleshooting
| Problem | What to check |
|---|---|
| Spend limits are off | Enable per-request checking in Settings and publish the form configuration. Adding limit rows alone does not enable checking. |
| Location cannot be selected | Map the main-form location question and publish the configuration. Confirm that the intended location is offered. |
| A category is missing or publishing is blocked | Confirm that the form offers the category. With active cumulative thresholds, also verify the designated activity-date question. |
| A cumulative threshold will not save | Supply at least one positive cap. The count cap must be a whole number. |
| The wrong per-request rule seems to apply | Check category, level, geography, recipient attributes, and the matching-rule precedence described above. |
| An amount is Unresolved | Check the amount, currency, organization default currency, and available exchange-rate conversion. |
| Cumulative totals differ from expectations | Check the activity-date period, party identity, category versus Total count, currency, record status, and snapshot time. |
| CSV rows are rejected | Read the row-level reason. Check offered categories, geography conflicts, allowed values, amount ordering, currency codes, and duplicates. |
| Apply requires a new check | The saved limits changed after validation. Recheck the CSV and review the refreshed results. |
See Find forms and understand their configuration for related settings and publishing behavior.