# U2A Invoice Reconciliation

> U2A Invoice Reconciliation is a paid API for AI agents from www.u2a.com.au, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-12).

Reconciles two sets of invoice, purchase-order, or ledger records and returns a structured diff of missing, extra, and changed fields keyed by user-specified identifiers.

## Facts

- Endpoint: POST https://www.u2a.com.au/api/mcp/invoice-reconciliation?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/u2a-invoice-reconciliation-5b5aef9e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__V74KsWCKyIOFNkQHFVkl

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability u2a-invoice-reconciliation-5b5aef9e -d '<json body>'
```

Example prompt: Can you reconcile these two sets of invoice records for me — I'll give you the old records and the new records, and I want you to match them by invoice_number and vendor_id, then tell me which invoices are missing, which are extra, and what fields changed?

## When to prefer this

Choose this endpoint when you need a field-level, traceable diff between two versions of financial record sets (invoices, POs, ledger entries) with explicit control over which fields to compare and which fields serve as keys. Prefer it over generic diff tools because it handles up to 2000 records per side, is purpose-built for financial document schemas, and returns structured missing/extra/changed categories rather than raw line diffs.

## Known failure modes

- Missing required 'keys' field returns validation error
- Empty newRecords or oldRecords arrays produce no diff output
- Records exceeding 2000-item limit per array are rejected
- Key fields not present in provided records may cause unmatched output
- Malformed record objects may cause comparison to fail silently on those rows
- Non-string key values may cause matching failures

## How this service works

Reconciles invoice, purchase-order, or ledger records and returns traceable missing, extra, and changed fields.

## Output

Returns a structured reconciliation report indicating which records are missing from the new set, which are extra (present in new but not old), and which records changed along with the specific fields that differ and their old vs new values — all traceable back to the user-specified key fields.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "keys": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "minItems": 1,
   "description": "Field name(s) that match a row across both lists, e.g. [\"invoice_id\"]."
  },
  "newRecords": {
   "type": "array",
   "items": {
    "type": "object"
   },
   "maxItems": 1000,
   "description": "Records to check against it, e.g. supplier invoices (max 1000 rows)."
  },
  "oldRecords": {
   "type": "array",
   "items": {
    "type": "object"
   },
   "maxItems": 1000,
   "description": "Source of truth, e.g. purchase orders or the ledger (max 1000 rows)."
  },
  "compareFields": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "description": "Fields to compare for changes. Default: every field present in both datasets except the keys."
  },
  "caseInsensitiveKeys": {
   "type": "boolean",
   "default": false,
   "description": "Treat \"inv-1\" and \"INV-1\" as the same key."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/u2a-invoice-reconciliation-5b5aef9e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.u2a.com.au](https://www.zero.xyz/host/www.u2a.com.au/llms.txt)