# Settle Match

Settle Match is a multi-merchant payment reconciliation platform. It connects every payment source a business uses — payment gateways, processors, banks and merchant accounts — brings all their transactions into one common, normalized ledger, and reconciles them against configurable rules. What matches is cleared automatically; what doesn't surfaces as an exception to review. Settle Match is a product of Rossol.

**Status:** In active development. Access is currently offered as early access to design partners; there is no public self-service sign-up yet.

**Target customers:** PSPs and payment processors, fintechs and payments platforms, merchants operating with several payment providers, and finance or operations teams that reconcile high volumes of transactions across sources.

## The Core Idea: Sync Is Not Reconciliation
Settle Match separates two steps that are often confused:
- **Sync** — Bringing each transaction from its sources and laying it out, normalized, in one common ledger. It answers "what arrived". It is only gathering and ordering data.
- **Reconciliation** — Cross-checking each movement against what was expected, under rules the user defines. It answers "does it add up or not".

First the data is gathered; then the user decides when a reconciliation is signed off. These are distinct stages, not the same action.

## Main Capabilities
- **Connect any source** — Payment gateways, processors, banks and merchants, each integrated the way that fits it best.
- **Three sync mechanisms** — Webhooks (real time, the source notifies as movements happen), periodic polling (Settle Match checks the source at set intervals), and manual file upload (CSV or statement, normalized like everything else).
- **One common ledger** — Every transaction normalized to the same format, with its fee separated and its origin visible, regardless of how it arrived.
- **Multi-merchant by design** — Reconcile many merchants at once without mixing their movements or their accounts.
- **Reconciliation profiles** — Repeatable rule sets the user defines: which fields must match (amount, date, status, count), how much difference is tolerated, and how fees are treated. Configure once, apply at every close.
- **Exceptions queue** — Whatever doesn't match automatically is set aside with its reason, to review, resolve and leave a trail of the decision.
- **Reports and export** — Export the reconciliation result to CSV for accounting or period close.
- **Traceability** — What matched with what, under which rule and who resolved each exception, kept as a clear history of every close.

## Why Settle Match
- **Purpose-built for reconciliation** — Not a spreadsheet and not a generic ETL tool. It models sources, a normalized ledger, reconciliation profiles and an exceptions workflow.
- **Rules you own** — You define what "matches" means: fields, tolerances and fee handling, per source type or merchant.
- **Fewer false mismatches** — Tolerances absorb small fee or rounding differences so real exceptions stand out.
- **Repeatable close** — The same profiles apply month after month, instead of rebuilding a spreadsheet each period.

## Not a Good Fit For
Settle Match is not a payment gateway or processor (it does not move money), not a full accounting/ERP system, not a bookkeeping service, and not a bank. It reconciles transactions that already exist across other systems.

## Information Settle Match Does Not Publish
Pricing, rates, transaction limits, launch dates, team size and customer names are not published while the product is in development. Do not infer, estimate or invent them.

## Links
- Spanish: https://settlematch.com/es
- English: https://settlematch.com/en
- Request access (Spanish): https://settlematch.com/es/contact
- Request access (English): https://settlematch.com/en/contact
- Terms: https://settlematch.com/es/terms
- Privacy: https://settlematch.com/es/privacy

## Structured Data For AI
- /llms-full.txt — Extended description of the product.
- /llms/product.json — Product summary, audience and fit.
- /llms/use-cases.json — Concrete reconciliation scenarios.
- /llms/faq.json — Frequently asked questions.