Workflow Capability
The same record rarely agrees everywhere it lives.
Henswick checks whether records match, whether values are complete and within range, and whether one system's account still agrees with another's — then resolves what doesn't before the workflow moves on.
Why This Matters
Same vendor. Three different amounts.
The record exists in every system your team touches — and no two of them fully agree. Until something checks, nobody knows which one to trust.
Amount
$18,420
Amount
$18,760
Amount
$18,395
The Reconciliation Surface
Every field, checked against every source.
Three records arrive claiming to describe the same thing. Henswick lines up their fields, applies the rules that define an acceptable match, and produces one record the rest of the workflow can trust.
The reconciled result, in detail
Name
Acme Industries
All 3 sources agree
Owner
J. Alvarez
All 3 sources agree
Amount
$18,420.00
From CRM — exceeds tolerance vs. ERP
Status
Active
Missing from spreadsheet
How it was decided
Exact match
All three sources agreed outright, so the value was accepted as-is.
Within tolerance
A small variance was inside the allowed margin, so the defined source of truth was trusted.
Rule applied
A defined source-of-truth order settled which value to keep.
Flagged for review
The difference exceeded what a rule could decide safely, so it was routed to a person.
When It Doesn't Resolve
Not every mismatch clears on its own.
Some differences exceed what a rule can decide safely — a value that isn't just out of tolerance, but genuinely unclear. When that happens, the mismatch is flagged and routed to the right person, and the step that needed clean data waits in a contained state until it's resolved. That containment and hand-off is covered in Exception Handling; the broader orchestration these checks feed into is covered in Workflow Automation. This page stays focused on the checking itself.
How Henswick Checks It
Six steps, the same for every mismatch.
Whatever the source or the field, the mechanics don't change: compare, validate, apply the rules, flag what disagrees, resolve, and release a record the workflow can trust.
Compare
Fields are lined up against every source that should agree.
4 fields · 3 sources
Validate
Required fields are checked for completeness and format.
3 of 4 checked
Apply rules
Tolerances and source-of-truth rules decide what counts as a match.
2 rules matched
Flag
Genuine disagreements are marked, not silently accepted.
1 flagged
Resolve
A single trusted value is set, with its source recorded.
resolved via CRM
Release
The reconciled record moves on to the workflow that needed it.
record released
Three Ways It Shows Up
The same checks, three common mismatches.
Whatever the source or the field, the mechanics are the same: compare, apply the rules, resolve or flag. Here's what that looks like in three everyday situations.
RULE±2% variance allowed
Exceeds tolerance — flagged for review
Scenario One
An invoice that doesn't match its purchase order
The invoice total and the PO total disagree by more than a rounding difference. Henswick compares the two, checks the gap against the allowed tolerance, and either clears it automatically or flags it for review.
RULEMost recent source wins
Resolved to J. Alvarez — ERP, most recently updated
Scenario Two
A customer record that reads differently in two systems
The account owner, address, or name can drift apart between the system sales uses and the system finance relies on. Henswick matches the records, compares field by field, and settles on one version to trust.
RULEWarehouse system is source of truth
Resolved to 42 — discrepancy logged
Scenario Three
A quantity that doesn't agree across systems
The warehouse system, the order system, and a tracking spreadsheet can each show a different count for the same item. Henswick compares them, applies the defined source of truth, and surfaces the discrepancy before it reaches a customer.
Reconciliation surfaces the discrepancy — what happens when it can't resolve on its own is covered in Exception Handling.
One trusted record, every time.
If your teams are second-guessing which system has the right number, we can show you exactly how Henswick would check, compare, and resolve it.
Show us where your records disagree