SztylerSolution · Process Lenses™
MATCH · EXPLAIN · RECONCILE · DEMONSTRATION CASE STUDY

Finance Reconciliation Lens™

Find the real variances without manually searching every transaction.

Open live demoWatch walkthroughSee the workflow
Export two transaction filesworkflow input
Map references, dates and valuesworkflow input
Search for matches and differencesworkflow input
PROCESS
LENS™rules · checks · exceptions
Matched and unresolved transactions separatedcontrolled outcome
Missing items, duplicates and value variancescontrolled outcome
Traceable matching reason for every classificationcontrolled outcome
Local workflowDesigned to run with controlled files in the browser.
Exception firstReview what needs judgement instead of every line.
Representative exampleIllustrative data and narrative, not a client claim.
ANONYMISED WORKFLOW CASE STUDY

The valuable work was investigating variances — not searching every transaction.

Situation: A finance workflow required repeated comparison of transaction files to find missing references, timing differences, duplicates and value mismatches. Most records were routine, but the full population still had to be worked through before the exceptions were clear.

Before: The reconciliation depended on repeated lookups across separate exports and on the person doing the work knowing which differences were harmless and which needed action. Under month-end pressure, the same checking became harder to complete consistently.

What changed: The workflow was converted into explicit matching rules. Routine matches are separated first, while unresolved items keep the source values and reason for review together.

Result: The user starts with the exceptions instead of rebuilding the reconciliation from line one. Human judgement remains on genuine variances, approvals and accounting interpretation.

Anonymised operational working pattern. Organisation names, people, locations, internal system names and identifying details are intentionally excluded. Any value figures elsewhere on this page are illustrative unless explicitly stated as validated.
BeforeRepeated searching across separate transaction sources.
Rules capturedMatching, tolerance and exception logic made visible.
Review focusMatched records leave the working queue.
OutputControlled exception evidence ready for review.
THE OPERATIONAL CHALLENGE

How the work happens before the Lens

Finance teams repeatedly compare structured transaction files. Most records match, but time is spent locating missing items, duplicates and value differences and then explaining the result.

Export two transaction filesCurrent manual step
Map references, dates and valuesCurrent manual step
Search for matches and differencesCurrent manual step
Prepare reconciliation evidenceCurrent manual step
THE HIDDEN BUSINESS LOGIC

The real value sits in the rules

The Lens is built around agreed conditions, tolerances and actions — not around a prettier spreadsheet.

Exact match on agreed keys → Matched
Value difference within tolerance → Tolerance match
Unmatched source item → Missing counterpart
Repeated reference and value → Potential duplicate
Unresolved difference → Variance requiring review
THE CONTROLLED WORKFLOW

From raw input to action-ready output

1Load digital exports
2Confirm field mapping
3Run matching profiles
4Classify results
5Review unresolved items
6Export reconciliation pack
WHAT THE USER SEES

Clear outcomes with the source detail preserved

Matched and unresolved transactions separated
Missing items, duplicates and value variances
Traceable matching reason for every classification
Reconciliation summary and exception pack
REPRESENTATIVE DEMONSTRATION RESULT

A result that can be explained, reviewed and exported

Figures and labels below describe the demonstration workflow and must be replaced or validated before being presented as a client result.

Matchedtransactions
Categorisedvariances
Exportableevidence pack
WHAT THE CONTROLLED WORKFLOW CHANGES

Better control, earlier visibility and less dependence on memory

The value is not only that the task becomes faster. The workflow becomes easier to cover, explain, review and improve.

01Matched firstRoutine transactions are cleared automatically using agreed keys and tolerances.
02Variance categoriesDuplicates, missing records and timing differences receive a clear reason.
03Resilient coverAnother analyst can understand the queue without inheriting a private spreadsheet method.
04Recovery opportunitiesHistoric data can be screened for older credits, duplicate payments or unresolved commercial items.
ILLUSTRATIVE VALUE MODEL

The analyst investigates exceptions instead of locating them.

This model counts released reconciliation time only. Any recovered credit or duplicate payment is additional and must be validated separately.

156 hoursillustrative annual capacity released
£3,900illustrative annual labour value

Assumptions used

  • 1 analyst
  • 4 hours before per week
  • 1 hour after per week
  • £25/hour
  • 52 weeks

Illustrative only. The final baseline is confirmed during a Process Scan using the client’s actual frequency, time, people and cost.

Historic value: A controlled historical review can surface transactions that deserve commercial follow-up. The Lens does not claim money automatically; it creates the traceable evidence needed for the finance team to decide and recover value where justified.
BOUNDARIES AND TRUST

What this demonstration does — and does not assume

Digital CSV, Excel or structured exports are expected
Scanned statements require OCR preparation
Matching tolerances must be agreed and tested
Direct banking or ERP integration is separate scope

Have a similar manual workflow?

Describe it in plain English and see the first-pass opportunity.

Check your process