Forge Json
Get Started
normalize

Normalize Payment Reconciliation Data

Flatten and normalize provider settlement records into reconciliation-ready rows

  • Flattens nested settlement records
  • Normalizes reconciliation amounts and dates
  • Produces deterministic reconciliation row schemas

Paste provider settlement records — instantly generate reconciliation-ready rows locally in your browser.

Continue

Why this package exists

Common problems

  • Payment providers frequently nest settlement metadata one or more levels deep while reconciliation systems expect flat transaction rows.
  • Different providers use inconsistent field names for the same reconciliation concept (`id` vs `reference_id`, `provider` vs `source`).
  • Amounts often arrive as strings while downstream reconciliation and warehouse systems require stable numeric types.
  • Settlement dates and transaction timestamps vary across providers and internal systems.

When to use

Use this when reconciling payment-provider settlement records against internal ledgers, finance systems, analytics pipelines, warehouses, or downstream reporting workflows.

Expected outcome

A flat array of normalized reconciliation rows containing `{ reference_id, source, amount, currency, settlement_status, event_date }` with deterministic keys and stable numeric/date types.

Automatically detects

  • Nested settlement objects
  • Provider-specific field names
  • String amounts
  • Mixed settlement dates

What the wizard asks

4 steps

Each step shows your input, the question, and a preview of the output.

  1. 1

    Flatten nested settlement objects into reconciliation fields?

    Collapse nested settlement objects into flat reconciliation fields downstream finance systems can reliably process.

  2. 2

    Rename provider-specific fields into reconciliation field names?· Optional

    Map provider-specific fields into one canonical reconciliation vocabulary downstream systems can rely on.

  3. 3

    Normalize reconciliation amounts into numeric JSON values?· Optional

    Convert string amounts into stable numeric values reconciliation systems can safely aggregate and compare.

  4. 4

    Which fields should land in the final reconciliation rows?

    Keep only the canonical reconciliation fields downstream systems require.