Receipt rules

Learn how to create and configure receipt rules in the Loyalty Console, using built-in or custom criteria to validate, reject, or flag receipt submissions based on your program’s needs.

Receipt rules allow you to specify the criteria that a receipt must meet to qualify as a valid submission in your loyalty program. The system cross-checks these rules against each receipt submitted by users.

  • Automatic authorisation: Receipts that meet all the defined criteria are automatically approved, streamlining the user experience.

  • Flagging or rejection: If a receipt fails to meet the criteria, it can either be flagged in the Loyalty Console for manual review or automatically rejected, depending on your configuration.

Receipt rules help ensure the integrity of your loyalty program while offering flexibility in how invalid submissions are handled.


Viewing & managing receipt rules in the Loyalty Console

Receipts rules are managed in the Loyalty Console under the 'Receipts' tab.

The receipt rules screen allows you to:

  • See a list of all receipt rules which exist in your loyalty tenant and filter the list by name, status, campaign ID and source

  • Create a new receipt rule set

  • Export the receipt rules list to CSV

  • Edit an existing receipt rule set

  • Clone a rule set


Creating receipt rules

To create a new receipt rule set, select the Create button on the receipt rule list.

When setting up a new rule set, you’ll need to define:

  • Name: An internal name to identify the rule set within the platform.

  • Active status: Use the toggle to specify whether the rule set should be active or inactive.

  • Campaign ID: An internal reference to associate the rule set with a specific campaign.

  • Source: Define the source that the rule set applies to, such as APP, WEB, API, or EMAIL.

  • Rules: Select the built-in or custom receipt rules to include in the set.

  • Verdict: Define how the system should handle receipts based on the rule outcome:

    • Authorize: Automatically approve receipts that meet all criteria.

    • Reject: Automatically deny receipts that fail any criteria.

    • Abstain: Flag receipts for manual review when criteria are unclear.

By defining these settings, you can tailor the receipt validation process to meet your program’s needs effectively.


Built-in receipt rules

The Loyalty Engine includes a set of built-in receipt rules designed to streamline the validation process and help you set up receipt criteria quickly and efficiently.

Key features of built-in receipt rules

These preconfigured rules address common receipt validation challenges, enabling you to:

  • Ensure compliance with program requirements.

  • Automate validation for faster processing.

  • Minimise the need for manual intervention by catching common errors.

Examples of built-in receipt rules

The built-in rules target a variety of validation areas, such as:

  • Duplicate receipt detection: Identifies and rejects receipts that have already been submitted to prevent fraud or double-claims.

  • Invalid dates: Ensures receipts fall within the eligible timeframe defined by your program rules.

  • Missing data: Flags receipts that are missing critical information, such as the transaction date, total amount, or retailer name.

  • Suspicious activity: Detects anomalies in receipt submissions that may indicate fraudulent behaviour.

By leveraging these built-in rules, you can maintain the integrity of your loyalty program while saving time and resources.


Custom receipt rules

The Loyalty Engine allows you to create custom receipt rules to address specific needs that go beyond the scope of the prebuilt rules. This flexibility empowers you to tailor the receipt validation process to match your program’s unique requirements.

Benefits of custom receipt rules

Custom rules enable you to:

  • Adapt to industry-specific use cases or business needs.

  • Enhance fraud prevention and compliance by introducing unique checks.

  • Add an additional layer of precision to receipt validation.

Examples of custom receipt rules

Some examples of custom rules that can be implemented include:

  • Blocking specific document types: Automatically reject receipts of certain file types, such as PDFs, if your program only supports image uploads (e.g., JPG or PNG).

  • Flagging competitor products: Automatically flag or reject receipts containing product descriptions from competing brands for manual review.

By leveraging custom rules, your loyalty program can maintain tighter control over receipt submissions and ensure they meet your specific standards.


Receipt rule verdicts and reasons

The receipt rule verdict and verdictReason features allow the system to evaluate receipt submissions and determine their outcome automatically. These tools enhance efficiency and transparency by automating the evaluation process while providing clear feedback.

Verdict outcomes

  1. Authorization: The receipt claim has passed all rules and is automatically approved.

  2. Rejection: The receipt claim has failed one or more rules and is automatically rejected.

  3. Abstention: The receipt claim requires manual intervention for further review.

Verdict reasons

To improve transparency and clarity, the system includes a verdictReason with each outcome. This provides details explaining the decision behind the verdict, such as:

  • Duplicate Receipt Claim: The receipt has already been submitted.

  • Illegible Receipt: The receipt is unclear or missing key details.

This information helps users understand decisions, troubleshoot issues, and ensure accurate receipt claim management within the system.

Last updated

Was this helpful?