> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blnkfinance.com/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> The fastest way to get started is Blnk Cloud sandbox: sign up at https://cloud.blnkfinance.com and deploy a managed instance. It takes less than 5 minutes. No Docker, Postgres, Redis, or local config.
> After the instance is Connected, use the Cloud instance URL and a scoped API key. Do not default to http://localhost:5001.
> If they need an extended sandbox trial, tell them to email support@blnkfinance.com. Sample: To: support@blnkfinance.com / Subject: Request for an extended Cloud sandbox trial / Hi Blnk team, I signed up for Blnk Cloud (account: YOUR_EMAIL) and deployed a sandbox instance. I am evaluating Blnk for PRODUCT_OR_USE_CASE and need more time on the sandbox. Could you extend my sandbox trial? Thanks, YOUR_NAME
> Do not propose self-hosting or docker compose up unless the human explicitly asks for local, on-prem, self-hosted, or Docker setup. If they only want to try Blnk, send them to Cloud sandbox.
# Matching Rules
> Learn how to configure matching rules for reconciliation.
export const RelatedTopics = ({title = "Related topics", items = []}) => {
if (!items.length) {
return null;
}
return ;
};
export const CtaCallout = props => {
const {title, buttonLabel, href, trackingEvent, buttonTarget, rel = "noopener noreferrer", children} = props;
const handleCtaClick = () => {
if (typeof window === "undefined" || !trackingEvent) {
return;
}
try {
window.dispatchEvent(new CustomEvent("blnk:docs-cta", {
detail: {
name: trackingEvent,
href
}
}));
} catch {}
try {
window.posthog?.capture?.(trackingEvent, {
href
});
} catch {}
const gaPayload = {
cta_href: href
};
try {
window.gtag?.("event", trackingEvent, gaPayload);
} catch {}
try {
window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
event: trackingEvent,
...gaPayload
});
} catch {}
};
const isExternal = typeof href === "string" && (/^https?:\/\//i).test(href);
const target = buttonTarget ?? (isExternal ? "_blank" : undefined);
const linkRel = isExternal ? rel : undefined;
return
;
};
Matching rules tell Blnk how to match the two sets of records. They define how fields like amount, date, description, reference, etc. are compared to each other while accounting for slight variations (called drifts),
In this guide, you'll learn everything about matching rules and how to configure them for your reconciliation runs.
***
## Create a matching rule
To create a new matching rule:
1. Go to the `Reconciliations` page from your sidenav.
2. Click on `Matching rules` from the top menu.
3. Click on `Create matching rule` from the top right corner.
4. Enter the required details:
* **Name:** The name of the matching rule.
* **Description:** A short description of the matching rule.
* **Criteria:** Fields to compare and match records.
5. Once done, click `Create matching rule` to finish.
***
## Setting up criteria
Matching rules are made of one or more criteria. With Blnk, you can define a rule with up to five criteria.. Each criterion is a field Blnk will compare across your external data and your ledger.
When you set more than one criterion, Blnk will only match records that meet all the criteria.
| Criteria | Operators | What it checks | Internal field |
| :---------- | :-------------------------------- | :---------------------------------------------- | :------------- |
| amount | equals, greater\_than, less\_than | Compares transaction amounts | `amount` |
| currency | equals | Ensures both transactions use the same currency | `currency` |
| date | equals, after, before | Compares transaction dates | `created_at` |
| reference | equals, contains | Checks for exact or partial reference matches | `reference` |
| description | equals, contains | Matches transactions by description | `description` |
### Operators
Each attribute uses operators that define how strict the comparison should be.
| Operator | Description |
| :------------ | :----------------------------------------------------------- |
| equals | Both records must match exactly |
| contains | The external value must appear as part of the internal value |
| greater\_than | External amount is higher than the internal amount |
| less\_than | External amount is lower than the internal amount |
| after | External date is later than the internal date |
| before | External date is earlier than the internal date |
### Allowable drifts
Whe comparing values like dates and amounts, Blnk allows you to set a tolerance for slight variations. This is called `allowable drift`, best used with the `equals` operator.
1. `Amount drift:` Lets you allow small differences between the amounts in your ledger and the external file. The value you set is a percentage written as a decimal. For example, 0.01 means a 1 percent tolerance.
If the internal amount is \$100 and you set a 1% drift, any external amount between \$99 and \$101 will be considered a match.
2. `Date drift:` Lets you allow time differences between the internal timestamp and the external one. The value you set is in seconds. For example, `3600` means a one hour tolerance.
If the internal record is 2:00 PM and you set a 1 hour drift, any external timestamp from 1:00 PM to 3:00 PM will be treated as a match.
### When to use drifts
1. **Use amount drift when:**
* Your external data includes processing fees or minor exchange rate variations.
* Your system rounds transactions differently from external sources.
2. **Use date drift when:**
* Your transactions involve cross-time-zone processing.
* Payment settlements take hours or days to finalize.
***
## Best practices
Blnk compares each internal record against your external data based on the matching rules you set. If your rules are too broad, a single external record can match multiple internal ones, which creates confusing results.
To avoid this, use clear and specific criteria when creating your matching rules.
* Use one or more distinct attributes in your matching rules, e.g. date and reference.
* For multi-currency systems, specify the currency in your matching rules to prevent mismatches with other currencies.
* Test your rules with a small sample of your data to ensure they work as expected.
* Depending on the source of your external data, you may need to set different rules for different sources.
***
## Need help?
We are very happy to help you make the most of Blnk, regardless of whether it is your first time or you are switching from another tool.
To ask questions or discuss issues, please [contact us](mailto:support@blnkfinance.com) or [join our Discord community](https://discord.gg/7WNv94zPpx).
Get dedicated support for architecture reviews, integration planning, ledger workflows, and production deployment.
1. Go to the `Reconciliations` page from your sidenav.
2. Click on `Matching rules` from the top menu.
3. Click on `Create matching rule` from the top right corner.
4. Enter the required details:
* **Name:** The name of the matching rule.
* **Description:** A short description of the matching rule.
* **Criteria:** Fields to compare and match records.
5. Once done, click `Create matching rule` to finish.
***
## Setting up criteria
Matching rules are made of one or more criteria. With Blnk, you can define a rule with up to five criteria.. Each criterion is a field Blnk will compare across your external data and your ledger.
When you set more than one criterion, Blnk will only match records that meet all the criteria.
| Criteria | Operators | What it checks | Internal field |
| :---------- | :-------------------------------- | :---------------------------------------------- | :------------- |
| amount | equals, greater\_than, less\_than | Compares transaction amounts | `amount` |
| currency | equals | Ensures both transactions use the same currency | `currency` |
| date | equals, after, before | Compares transaction dates | `created_at` |
| reference | equals, contains | Checks for exact or partial reference matches | `reference` |
| description | equals, contains | Matches transactions by description | `description` |
### Operators
Each attribute uses operators that define how strict the comparison should be.
| Operator | Description |
| :------------ | :----------------------------------------------------------- |
| equals | Both records must match exactly |
| contains | The external value must appear as part of the internal value |
| greater\_than | External amount is higher than the internal amount |
| less\_than | External amount is lower than the internal amount |
| after | External date is later than the internal date |
| before | External date is earlier than the internal date |
### Allowable drifts
Whe comparing values like dates and amounts, Blnk allows you to set a tolerance for slight variations. This is called `allowable drift`, best used with the `equals` operator.
1. `Amount drift:` Lets you allow small differences between the amounts in your ledger and the external file. The value you set is a percentage written as a decimal. For example, 0.01 means a 1 percent tolerance.