Solutions / Synthetic workflow example

Find the transactions that need a closer look.

A settlement file and a payment ledger tell different parts of the story. This example compares them and records differences for finance review.

Inputs
A synthetic settlement file and payment ledger.
Preparation
Normalize records and compare transaction amounts with SQL.
Result
Comparison rows and batch totals, including missing matches and differences.

What the walkthrough shows

  1. Read a settlement file and ledger, then normalize the settlement records for comparison.
  2. Use a customer-authored SQL comparison to keep matching entries, amount differences and missing ledger events visible.
  3. In this fixture, a €15 refund is compared with a €20 ledger entry: a €5 difference. Three comparison rows include two matches to ledger events and one missing event.
  4. Write comparison rows and batch totals to two output tables. Inspect the run and lineage to connect the output to its inputs.

What you need to build your version

A technical owner configures access to your systems, defines queries and transformations, and agrees what the output should mean. Connections, permissions, matching rules and schedules depend on your workflow.

Evaluation boundaries

This is an Alpha demonstration using synthetic data, not a customer case study or a measured business outcome. The retained recording shows the product at the time of capture; the current interface may differ.

The comparison rules are authored for this example. Braidplane does not provide universal financial reconciliation or make accounting decisions. A reported financial difference is a result to review, not necessarily a failed run.

Use test data and non-production systems. Verify the output and a failure case for your own evaluation.

Discuss your workflow

Tell us which systems you use, how often the process runs, and which result you need. We reply by email to arrange a free conversation.

Discuss your workflow