Code-defined matching
Implement exact, tolerance, grouping, or domain-specific comparison rules in code your engineering team can review.
Reconciliation operations
Turn mismatched records into an owned resolution queue.
Build reconciliation consoles that compare source records, classify differences, assign exceptions, and record the final decision. Run filters and pagination server-side so operators can work against real datasets.
assignments · dev 12 columns · 5 rows
| Employee | Project | Status | Alloc |
|---|---|---|---|
| Mina Alvarez | Northwind Rollout | ACTIVE | 40% |
| Jonah Kim | Atlas Migration | ACTIVE | 75% |
| Priya Nwosu | Northwind Rollout | PLANNED | 30% |
| Lena Richter | Mercury Support | BLOCKED | 55% |
server-side SQL · statement + lock timeouts on every transaction
The reconciliation problem
A mismatch report is not an operating process.
Differences between ledgers, settlements, orders, inventory, or partner records need ownership, evidence, resolution actions, and review. Exporting the mismatches to another spreadsheet separates the decision from its source data.
Reconciliation controls
Keep comparison logic and operator decisions in the same governed application.
Relpin supports code-defined matching, server-side work queues, scoped actions, and row-level audit.
Server-side exception queues
Filter, sort, paginate, and prioritize reconciliation items in SQL instead of loading the working dataset into the browser.
Governed resolutions
Limit write-offs, remaps, approvals, and close actions by permission while retaining before-and-after change evidence.
Resolution model
Compare the records, isolate the differences, and close them with evidence.
The console can support scheduled runs, manual investigation, or workflow-driven review without hiding the underlying records.
- 01
Create a reconciliation run
Load or query the relevant source records and apply the matching rules defined for that operational process.
- 02
Assign the unresolved set
Create owned work items for unmatched, duplicate, late, or out-of-tolerance records with the source context operators need.
- 03
Resolve and attest
Record the corrective action, reviewer, timestamps, and resulting state so the next run starts from explainable data.
Reconciliation evidence
Reviewable matching logic
Server-side exception dataset
Permission-scoped resolutions
Before-and-after row audit
Reconciliation questions
Where Relpin fits in the reconciliation stack.
Does Relpin ship a financial matching engine?
No. Relpin is the governed platform for building the reconciliation application. Your team implements the matching rules and source integrations required by the process.
Can the console handle datasets larger than the browser should load?
Yes. Relpin is designed for server-side SQL filtering, sorting, and pagination so operators retrieve the working slice instead of evaluating the full dataset client-side.
Can sensitive resolutions require approval?
Yes. Resolution actions can be permission-scoped, and durable workflows can introduce approval nodes before a write-off, remap, or final close proceeds.
Exceptions with ownership
Build reconciliation operations that remain explainable after close.
Keep comparison logic, investigation context, resolution rights, and audit evidence in one code-first internal tool.
Open beta · Solution pattern