Loading Settler...
Loading Settler...
Loading documentation...
This guide walks you through your first reconciliation run end-to-end: account setup, data source connection, running the engine, reviewing exceptions, and downloading a proofpack artifact. Each step has a time estimate and explicit checkpoints.
Sign up and create your tenant workspace. Your workspace is the isolated scope for all your runs, exceptions, and proof artifacts.
Checkpoints
The fastest path to your first result is a CSV upload — no credentials required. If you have a Stripe account, connect it directly for a live integration.
Checkpoints
Start a reconciliation run from the Runs page or via the API. Settler will apply your matching rules and surface every record that couldn't be matched.
Checkpoints
Every record that couldn't be matched automatically becomes an exception. Open the exceptions queue to see what the engine flagged, understand why, and make a resolution decision.
Checkpoints
Open the run detail, go to the Proof & Provenance tab, and download the proofpack artifact. This JSON file is the hash-linked evidence record for the run — the same artifact you would share with an auditor.
Checkpoints
From the run detail, click 'Export results' to download the full reconciliation output as CSV. This is your portable record of matched and unmatched records.
Checkpoints
Once you have a completed run and a downloaded proofpack, you have validated the core workflow. Here's what to explore next.
Set up a schedule
Configure your reconciliation to run automatically on a cron schedule. Daily, weekly, or at close.
Review your audit trail
Every operator action — exception resolution, status changes, exports — is logged in the audit trail with a timestamp and actor.
Connect your second data source
The real power of reconciliation is matching across two systems. Add your second adapter (bank, accounting system, ERP) to run cross-system matching.
Explore the API
Trigger runs, retrieve results, and manage exceptions programmatically. Settler has a full REST API with API key authentication.
Invite your team
Add teammates to your workspace. Multiple operators can review exceptions and access the audit trail within the same tenant scope.
Read the architecture guide
Understand how Settler's deterministic engine, proof generation, and tenant isolation model work under the hood.
Most first-run issues have straightforward fixes. Here are the most common ones.
Run shows 'Failed' status
Open the run detail and check the error message. Common causes: adapter credentials invalid, CSV format not recognized, or a required field is empty. Fix the root cause and re-run.
Zero exceptions but data looks wrong
Check your tolerance settings. If tolerance is very wide (e.g., ±100%), most records will match. Tighten the tolerance or add a field-level rule to surface discrepancies.
Proofpack shows 'posture: unavailable'
This is normal for the first run in a new workspace — there's no prior run to compare against. Run a second reconciliation to see historical comparison signals.
CSV upload shows no records
Ensure the CSV has a header row and that column names include recognizable fields (date, amount, reference, id, description). Settler will map standard column names automatically.
'Setup required' in the Console dashboard
Open Console → Setup Check (or Diagnostics). Each item shows the exact requirement and recovery path. Most are resolved by adding missing environment variables.
If you're stuck, have a question about your specific data sources, or want to review your reconciliation setup before going live — reach out. We respond within one business day.