SYNTHETIC PROOF WALKTHROUGH

Route an ambiguous reconciliation match without posting it

A browser-only example of explainable candidates, a review-required decision, and a strict no-posting boundary.

See the three stepsRead the product contract →
NO KEY · NO UPLOAD · NO CUSTOMER DATAThis demonstration runs entirely in your browser using the visible synthetic fixture below.

THREE STEPS

Put the control before the consequential action.

Two customer-supplied records match the same source amount, currency, and date window.

  1. 01

    Supply both record sets

    The customer provides source and target records; AP Control does not connect to a bank or ledger.

  2. 02

    Build deterministic candidates

    Exact amount and currency plus the configured date and counterparty rules determine candidate pairs.

  3. 03

    Hold ambiguous results

    More than one candidate produces REVIEW_REQUIRED with the source reference and candidate count for human resolution.

VISIBLE SYNTHETIC CONTRACT

Inspect exactly what the workflow sees.

The input and output are representative of the named product contract. Copy them into an architecture note, test fixture, or internal review—never treat this browser-only demonstration as a live control result.

Customer-authorized input
{
  "source_records": [
    {
      "record_reference": "BANK-42",
      "amount": "500.00",
      "currency": "USD",
      "posted_on": "2026-08-08",
      "counterparty": "Northstar Supply"
    }
  ],
  "target_records": [
    {
      "record_reference": "LEDGER-17",
      "amount": "500.00",
      "currency": "USD",
      "posted_on": "2026-08-08",
      "counterparty": "Northstar Supply"
    },
    {
      "record_reference": "LEDGER-18",
      "amount": "500.00",
      "currency": "USD",
      "posted_on": "2026-08-09",
      "counterparty": "Northstar Supply"
    }
  ],
  "date_tolerance_days": 3
}
Agent-readable output
{
  "status": "COMPLETED",
  "decision": "REVIEW_REQUIRED",
  "exceptions": [
    {
      "code": "RECONCILIATION_AMBIGUOUS_MATCH",
      "severity": "HIGH",
      "message": "More than one supplied counterpart matches this record.",
      "evidence": {
        "source_record_reference": "BANK-42",
        "candidate_count": 2
      }
    }
  ],
  "evidence": {
    "matched_count": 0,
    "unmatched_source_references": [
      "BANK-42"
    ]
  },
  "next_action": "Have a reviewer select the correct counterpart; do not auto-post an ambiguous match."
}

WHAT THIS PROVES

Evidence for a stop point—not permission to act.

The API returns candidates only. It never connects to a bank, posts a journal entry, or marks a record reconciled.

Decision
REVIEW_REQUIRED
Named exception
RECONCILIATION_AMBIGUOUS_MATCH
Evidence
source record referenceBANK-42candidate count2
Next action
Have a reviewer select the correct counterpart; do not auto-post an ambiguous match.

KEEP BUILDING

Move from the synthetic fixture to the exact API contract.

Review the product inputs, outputs, errors, and safety boundary before using authorized data. The related implementation guide explains the design decisions behind the control.

Product contract →Implementation guide →Security posture →

Try the control through the supported buyer path.

RapidAPI provides the subscription, key, quota, and capped marketplace plan for this synchronous control.

Get an API key on RapidAPIExplore all four demos →