SYNTHETIC PROOF WALKTHROUGH

Hold a remittance when selected open invoices do not equal the payment

A synthetic match over customer-provided remittance references and an open-invoice baseline.

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.

The remitted amount is 100.00 USD while the selected supplied open invoice totals 90.00 USD.

  1. 01

    Supply the remittance and baseline

    The customer provides the remitted amount, references, currency, and its own open-invoice records.

  2. 02

    Select exact compatible candidates

    The control filters the supplied baseline by references, currency, and optional vendor evidence.

  3. 03

    Explain the amount gap

    A total mismatch identifies both amounts and requires review before any posting workflow.

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
{
  "remittance_reference": "REM-2201",
  "remitted_amount": "100.00",
  "currency": "USD",
  "invoice_references": [
    "INV-2201"
  ],
  "open_invoices": [
    {
      "invoice_reference": "INV-2201",
      "open_amount": "90.00",
      "currency": "USD"
    }
  ]
}
Agent-readable output
{
  "status": "COMPLETED",
  "decision": "REVIEW_REQUIRED",
  "exceptions": [
    {
      "code": "REMITTANCE_AMOUNT_MISMATCH",
      "severity": "HIGH",
      "message": "The selected open-invoice total differs from the remitted amount.",
      "evidence": {
        "remitted_amount": "100.00",
        "selected_open_amount": "90.00"
      }
    }
  ],
  "evidence": {
    "remittance_reference": "REM-2201",
    "candidate_invoice_references": [
      "INV-2201"
    ],
    "candidate_open_amount": "90.00",
    "currency": "USD"
  },
  "next_action": "Reconcile partial payments, credits, discounts, and fees with a reviewer."
}

WHAT THIS PROVES

Evidence for a stop point—not permission to act.

The API does not connect to a bank or ledger, post cash, apply credits, split a payment, mark an invoice paid, or make an accounting decision.

Decision
REVIEW_REQUIRED
Named exception
REMITTANCE_AMOUNT_MISMATCH
Evidence
remitted amount100.00selected open amount90.00
Next action
Reconcile partial payments, credits, discounts, and fees with a reviewer.

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 every synthetic demo →