# Create an Aggregation Comparison Check

Source: https://userguide.qualytics.io/data-quality-checks/aggregation-comparison/how-tos/create-a-check/

*Requires the Data Quality (DQ) module.*

Step-by-step tutorial for creating an Aggregation Comparison check between a target container and a reference container. For what each property means and how the rule evaluates the data, see the [How It Works](https://userguide.qualytics.io/data-quality-checks/aggregation-comparison/deep-dive/how-it-works/) page.

> **Note: Permission Required**
>
> You need the **Author** team permission on the datastore to create an Active check, or **Drafter** to create it as a Draft. See the [Permissions](https://userguide.qualytics.io/data-quality-checks/aggregation-comparison/deep-dive/permissions/) page for the full matrix.

> **Tip: Show me how**
>
> The app can walk you through this. Click **Show me how**  in the check creation form's header, or press `H` while it is open, and the **Add a Check** walkthrough highlights each step while you fill in the real form.

## Field reference

The **Authored Check Details** form is organized in the sections below. Fill them in as you follow the [Steps](https://userguide.qualytics.io/data-quality-checks/aggregation-comparison/how-tos/create-a-check/#steps).

### Target

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Associate with a Check Template** | No | Toggle | Links the check to a Check Template. Enabling it replaces the **Rule Type** dropdown with a **Template** dropdown where you pick an existing template, which then controls the check's properties. When off, you configure everything on this form. |
| **Rule Type** | Yes | Option | The validation logic to apply. Select **Aggregation Comparison** for this check. Shown only while **Associate with a Check Template** is off. |
| **Table / File** | Yes | Option | The target the check runs against. The label follows the datastore, reading **Table** on a database and **File** on a file system. Locked after the check is saved. |
| **Fields** | No | Option | Shown once a table or file is selected. Leave it empty and the fields are derived from the two expressions when you save. Select fields only to replace that list; it decides which fields the check is associated with and does not change the comparison. When editing a check, the input shows the fields saved on it; if you change an expression, click the re-derive button next to the input (or clear it) so the fields are worked out again. |
| **Filter Clause** | No | Text | A SQL `WHERE` expression applied to the target container before its aggregation runs. |
| **Custom Anomaly Description** | No | Toggle | Appears under **Advanced**, at the end of this section, once a table is selected. It has no effect on this rule, because the option replaces the message on Record Anomalies and Aggregation Comparison emits Shape Anomalies only. |

> **Tip: Create the table or file from the form**
>
> If the table or file you need does not exist yet, click **Add Computed Table**  next to the **Table / File** field while it is empty (**Add Computed File** on a file-based datastore). Once saved, the new one is selected and pinned to the top of the list with a  icon until you close the form. The button appears only with the **Author** or **Editor** team permission on the datastore, and not when you add a check from Explore.

> **Note: A filter that can never run**
>
> **Validate** refuses a filter clause that can never convert a value, such as `amount <> ''` on a number field, or that uses a function Qualytics does not allow, and names the reason. This applies to every rule type that accepts a filter, including checks that compute one value for the whole table, such as **Sum**, and checks with a coverage below 100%. If a check with such a filter reaches a scan, it is reported as **Not Asserted** with that reason, and the other checks on the table still run.

### Properties

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Aggregation** | Yes | SQL | The target aggregation expression, evaluated against the target container. Must produce a single aggregate value (for example, `SUM(amount)`, `COUNT(*)`, `ROUND(AVG(score), 2)`). Accepts Check Variables. |
| **Comparison** | Yes | Option | The operator applied from the target to the reference. One of **Less Than**, **Less Than Or Equal To**, **Equal To**, **Greater Than Or Equal To**, or **Greater Than**. See [Comparison Operators](https://userguide.qualytics.io/data-quality-checks/aggregation-comparison/deep-dive/how-it-works/#comparison-operators) for what each one asserts. |

### Right Reference

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Datastore** | No | Option | The datastore holding the reference container. Leave it empty to use the target's own datastore. |
| **Table / File** | Yes | Option | The table or file holding the reference data. It can be the same one as the target. The label follows the reference datastore, the same way the target's does. |
| **Aggregation** | Yes | SQL | The reference aggregation expression. Must also produce a single aggregate value. Accepts Check Variables. |
| **Filter Clause** | No | SQL | A SQL `WHERE` expression applied to the reference container before its aggregation runs. Accepts Check Variables. |

### Ownership

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Owner** | Yes | Option | The user responsible for the check. Already filled in with the check creator. |
| **Anomaly Assignee** | No | Option | The user automatically assigned to anomalies the check produces. |

### Metadata

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Description** | Yes | Text | A plain-language description of what the check enforces. Supports Markdown formatting: click the field to open the Markdown editor. Click the **Apply suggested description**  button for a suggestion based on the rule type. |
| **Tags** | No | Option | Tags applied to the check for filtering and organization. |
| **Additional Metadata** | No | Key-value | Custom key-value pairs, typically links to catalog entries, tickets, or governance records. |

> **Info: No Pass Criteria section**
>
> Aggregation Comparison does not use coverage, so the form shows no **Coverage** slider. The check asserts a single relationship between two aggregates: either it holds or it does not.

> **Tip: Let AgentQ fill in the form**
>
> When [AgentQ](https://userguide.qualytics.io/agentq/getting-started/) is configured for your deployment, the **Check Assistant** panel in the check form can author the check for you: describe the reconciliation in plain language (for example, "order totals must match the line-item roll-up") and it proposes a configuration you can apply to the form. Review the filled-in fields, then Validate and Save as usual.

## Steps

Each field is described in the [Field reference](https://userguide.qualytics.io/data-quality-checks/aggregation-comparison/how-tos/create-a-check/#field-reference) above.

**Step 1**: Select the source datastore from the left menu, then click the **Checks** tab.

**Step 2**: Click **Add** in the top-right corner and select **Check** from the dropdown. The **Authored Check Details** form opens.

> **Warning: No tables available**
>
> On a datastore that has no tables yet, for example one that was just added and has not been synced, the form shows a **No tables available** warning (**No files available** on a file-based datastore) that reads **Run a Sync on this datastore before adding checks.** instead of the check fields. When you open the form from the datastore page and you can run operations on the datastore, the warning also offers a **Run Sync**  button, which closes the form and opens the Sync dialog. Add the check once the Sync finishes. The warning does not appear when you add a check from a check template.

**Step 3**: Select **Aggregation Comparison** in the **Rule Type** dropdown.

**Step 4**: Fill in the remaining [Target](https://userguide.qualytics.io/data-quality-checks/aggregation-comparison/how-tos/create-a-check/#target) fields: the target table or file and, optionally, a **Filter Clause** that scopes the target aggregation.

**Step 5**: Under [Properties](https://userguide.qualytics.io/data-quality-checks/aggregation-comparison/how-tos/create-a-check/#properties), write the target **Aggregation** expression and pick the **Comparison** operator.

**Step 6**: Fill in the [Right Reference](https://userguide.qualytics.io/data-quality-checks/aggregation-comparison/how-tos/create-a-check/#right-reference) panel: the reference **Table / File** (and its **Datastore** when it lives elsewhere), the reference **Aggregation**, and an optional **Filter Clause** for that side.

**Step 7**: Fill in the [Ownership](https://userguide.qualytics.io/data-quality-checks/aggregation-comparison/how-tos/create-a-check/#ownership) and [Metadata](https://userguide.qualytics.io/data-quality-checks/aggregation-comparison/how-tos/create-a-check/#metadata) sections. Only the **Description** is required.

**Step 8**: Click **Validate** to test the rule against the selected data without saving it. A success message confirms the rule can run on that data. If validation fails, see [Troubleshooting](https://userguide.qualytics.io/data-quality-checks/aggregation-comparison/troubleshooting/#validation-fails-when-creating-the-check).

**Step 9**: Click **Save**. A success message confirms that the check was created.

*Last updated: November 10, 2026.*
