SYNTHETIC PROOF WALKTHROUGH

Stop an exact duplicate before the invoice reaches payment review

A browser-only walkthrough of deterministic duplicate evidence, a blocked decision, and the safe reviewer handoff.

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 same normalized vendor, invoice number, amount, and currency already exist.

  1. 01

    Submit authorized invoice data

    The workflow sends one structured invoice or one verified private upload with a stable idempotency key.

  2. 02

    Compare deterministic evidence

    AP Control checks the document hash and normalized vendor, invoice number, total, currency, date, and customer-owned history.

  3. 03

    Stop and route the match

    An exact prior record produces BLOCKED with the matching invoice and rule evidence; the customer decides what happens next.

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
{
  "vendor_name": "Northstar Supply",
  "invoice_number": "INV-1042",
  "total": "1250.00",
  "currency": "USD"
}
Agent-readable output
{
  "status": "COMPLETED",
  "decision": "BLOCKED",
  "exceptions": [
    {
      "code": "DUPLICATE_EXACT",
      "severity": "CRITICAL",
      "message": "This invoice exactly matches a recorded invoice.",
      "evidence": {
        "matched_invoice_id": "inv_previous_1042",
        "match_basis": "vendor_invoice_number_total_currency"
      }
    }
  ],
  "next_action": "Do not route for payment; send the matching record to an AP reviewer."
}

WHAT THIS PROVES

Evidence for a stop point—not permission to act.

The result identifies duplicate evidence. It does not accuse a vendor of fraud, delete an invoice, or touch a payment system.

Decision
BLOCKED
Named exception
DUPLICATE_EXACT
Evidence
matched invoice idinv_previous_1042match basisvendor_invoice_number_total_currency
Next action
Do not route for payment; send the matching record to an AP 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.

Create a workspace, issue a scoped key, and test the control with synthetic or authorized data.

Start free workspaceExplore all four demos →