> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/monitoring/dashboard-actions/programmable-checks.md).

# Programmable Checks

Build automated checks that compare records across two systems, such as billing against delivery, or change tickets against a ticketing system.

Standard automated checks evaluate one entity at a time. Cross-system checks go further: they **join records from two entities** and evaluate them together. This lets you reconcile data between systems and automate controls that previously needed manual evidence.

This is especially useful when:

* A control depends on two systems agreeing with each other, such as every delivery having a matching bill.
* You need to confirm a record in one system has a counterpart in another, such as every network change having an approved change ticket.
* You want to catch duplicates or timing gaps across a dataset.

{% hint style="info" %}
This feature is only available for Advanced and Enterprise plans.
{% endhint %}

***

### Before You Begin

To create a cross-system check, make sure:

* Both systems are connected, or their data is ingested into Sprinto. Only entities with data for your organisation appear.
* You can identify a **key** that exists in both entities, such as a delivery number or ticket ID.
* You are an Admin or have permission to access the **Monitoring** page.

***

### How Cross-System Checks Work

A cross-system check does three things:

1. **Joins** records from two entities using a shared business key, for example a delivery number or a change ticket ID. The key does not need to be a declared relationship, so this also works for entities you ingest from CSV files or custom sources.
2. **Compares** fields across the joined records. You can use aggregates (`sum`, `min`, `max`, `avg`, `length`) and calculate the gap between two dates with `days_between(a, b)`.
3. **Evaluates** each record as its own pass/fail result, so you can see exactly which invoices, deliveries or changes need attention.

Any entity available to your organisation can be joined, including integrated entities, native Sprinto entities and entities brought in through Ingestion.

***

### Example 1: Financial Controls

**Control goal:** Make sure every delivery is billed correctly, and that no vendor invoice is paid twice.

Bring your ERP data (for example SAP delivery, billing and vendor invoice records) into Sprinto, then create checks that join these records on a business key such as the delivery number.

| Check                                                     | What it flags                                            |
| --------------------------------------------------------- | -------------------------------------------------------- |
| Delivery dispatched but not billed                        | A delivery with no matching billing document             |
| Delivery partially billed against dispatched quantity     | Billed quantity is lower than dispatched quantity        |
| Delivery not billed within 5 days of goods issue          | Billing was raised later than your SLA allows            |
| Duplicate vendor invoice                                  | The same vendor and invoice number appear more than once |
| Vendor invoice repeats an amount under a different number | Same vendor and amount, different invoice number         |
| Near-duplicate vendor invoice                             | Same vendor and amount within a set number of days       |

<figure><img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FmQKUIAT4WFb6cVksfork%2Freconciliation-checks-monitoring.webp?alt=media" alt="Reconciliation checks listed on the Monitoring page" width="563"><figcaption><p>Reconciliation checks listed on the Monitoring page</p></figcaption></figure>

Each invoice or delivery is evaluated individually. Open a check to see which records pass and which are due.\ <br>

<img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2F5ZXeDOzcrjgrwExy0dA9%2FCheck%20details%20showing%20individual%20records%20as%20passing%20or%20due.png?alt=media&amp;token=885a15cb-d71c-44fb-90c6-f08ea41e0bb8" alt="Check details showing individual records as passing or due" height="360" width="460">

***

### Example 2: Change Management Controls

**Control goal:** Every network configuration change should have a matching approved change ticket in your ticketing system.

In this example, changes recorded in **Cato Networks** are checked against change tickets in **ServiceNow**. The check *Config change has a corresponding ServiceNow change ticket* fails when a Cato change has no ticket number, or when the number does not match any synced ServiceNow ticket.\ <br>

***

<img src="https://3220032727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEsyn5VMU6e0OyGjRtKgx%2Fuploads%2FwxQfIq6YpLj4zAaDrXUk%2FCato%20change%20records%20checked%20against%20ServiceNow%20change%20tickets.png?alt=media&amp;token=8ba0b3b0-617c-4695-9e6c-238a4493f395" alt="Cato change records checked against ServiceNow change tickets" height="288" width="560">

### What Happens After

Cross-system checks behave like other automated checks:

* They appear on the **Monitoring** page under **Automated Checks**.
* Failing records create tasks that move through **Due**, **Critical** and **Failing**.
* Evidence is collected from the moment the check runs.

{% hint style="warning" %}
To appear in an audit, the check must be mapped to a control that is linked to the audit.
{% endhint %}

***

### Best Practices

| Tip                              | Why it matters                                                                                       |
| -------------------------------- | ---------------------------------------------------------------------------------------------------- |
| Join on a single, consistent key | Free-text fields (descriptions, titles) can hold several IDs or none, which can cause false failures |
| Run **Test** before activating   | Confirms the join finds matching records                                                             |
| Set a clear owner and SLA        | Failed records are assigned to the owner automatically                                               |

***

### Related Pages

* [Create Automated Checks](https://docs.sprinto.com/monitoring/dashboard-actions/create-automated-checks.md)
* [Ticket-Based Change Management](https://docs.sprinto.com/data-library/change-management/ticket-based-change-management.md)
* [Ingestion Overview](https://docs.sprinto.com/ingestion/overview.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sprinto.com/monitoring/dashboard-actions/programmable-checks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
