Pull both sides
Scheduled automations call each system's API and land the records in your data — the comparison becomes live data you can act on.
Reconciliation and exception management
Match records across systems on a schedule, surface exceptions in a review queue, and track resolutions — all in one place.
For: Operations and finance teams with cross-system data · Example concept
The problem
Two systems disagree and a human finds out late. Matching logic lives in fragile scripts, exceptions in inboxes, and resolution history nowhere.
What it produces
- Exceptions surface reliably, on a schedule
- Every resolution leaves an inspectable trail
- Match logic lives in reviewed platform configuration
data: exception
| source_a | source_b | field | status |
|---|---|---|---|
| INV-8842 | PO-10231 | amount | open |
| INV-8839 | PO-10228 | date | resolved |
| INV-8835 | — | missing | open |
- 1 Pull source A
- 2 Pull source B
- 3 Match records
- 4 Queue exceptions
automation · resumable · schedulable
Exception queue
Compare view
Resolution form
screens · connected to data and automations
How it comes together
Declare the match
Matching and exception rules are queries and automation steps you can read, version, and adjust as the systems evolve.
Work the queue
An exception screen lists mismatches with both records side by side; resolution actions are automations that write back and record what happened.
The pieces involved
- Source record and exception data
- Scheduled sync and match automations
- Exception queue and comparison screens
- Resolution and write-back automations
Other concepts
Is this your problem?
Waitlist teams will help shape which application concepts we prove first.
Join waitlist