Run reconciliation executes the saved setup: source data, schemas, matching keys, and optional RuleSets. The output points to the next decision.
Before you start
Confirm:
- The source files or records are available.
- Required connection records are active when the run reads from SFTP, NetSuite, or another configured system.
- The selected schemas match the input shapes.
- The saved run points at the right source systems, schemas, primary ID fields, and rules.
- You are in the correct company or tenant context.
What Darpan needs for a run
| Input | Why it matters |
|---|
| Source data | The files, text payloads, or connection-backed records being compared. |
| Schemas | The known shape of source data, especially for JSON inputs and field selection. |
| Primary ID fields | The values Darpan uses to match records across systems. |
| RuleSet and rules | The comparison logic Darpan applies after source records are matched. |
| Saved run setup | The reusable run configuration that ties sources, schemas, primary ID fields, and rules together. |
| Connection records | Saved access details for systems that provide or receive run data. |
Steps
- From Ask Darpan, open Run Reconciliation.
- Select the saved run or source strategy required by the workflow.
- Confirm schemas, primary ID fields, and RuleSet selection.
- Provide source files or connection-backed inputs.
- Start the run.
- Wait for generated output.
If the run setup does not exist yet, start with Set up a reconciliation run.
Expected result
A successful run creates saved output that can be opened from result, history, or generated-output views. The output separates source data fixes, schema corrections, rule adjustments, and accepted variances.
Reusing a run
Use a saved run when the same comparison will happen again. Saved runs keep setup stable so the next execution can focus on fresh source data and reviewable output.
Use Create Reconciliation Flow when the setup itself is still being defined. Use Open Runs Settings when the setup exists but needs a name, schema, source, or rule update before the next run.
Use Set up an automation when the saved run should execute on demand or on a recurring schedule.
If a run completes with zero matches, do not assume the data is clean. Check join keys, source identifiers, schema selection, and file encoding.
