/tres-invoice-bill-matching

name: tres-invoice-bill-matching
description: >
  Match TRES ledger transactions to ERP invoices/bills (AP/AR) and optionally sync them to the connected ERP
  (Xero, QuickBooks Online, NetSuite). Trigger this skill whenever the user wants to match, link, close,
  reconcile, or sync an invoice or bill against a blockchain transaction — even if they don't say "skill" or
  use those exact words. Trigger phrases include: "match this invoice to a transaction", "match a bill to tx",
  "close invoice INV-123", "close bill 9988", "link this tx to a bill", "pay this invoice from this transaction",
  "set up this tx as AP", "set up this tx as AR", "sync this transaction as AP/AR", "match AP/AR", "find the
  invoice/bill for this hash", "what bill does this tx pay". Trigger ONLY for explicit AP/AR matching/closing
  intent — do NOT trigger for general transaction explanations (use tres-tx-story), for ingesting an explorer
  link into the ledger (use tres-explorer-tx-to-ledger), or for ERP connection setup itself (use tres-settings-management).

TRES — Invoice/Bill Matching & ERP Sync

End-to-end workflow that lets the user close an open ERP invoice or bill against a blockchain transaction in the TRES ledger, then optionally push the matched entry to the connected ERP.

The flow is the same regardless of which side the user starts from (a transaction hash or an invoice/bill ID). The skill walks through seven conversational steps (verify ERP → identify input → fetch & suggest → user picks → configure payment account & fiat → confirm & apply → loop). Stay terse — show numbered options, capture the user's pick, move on. Never run a mutation without explicit "yes" from the user.

---

Ground rules

1. **Identify the org first.** Begin with `get_viewer` and tell the user "You're connected to **{orgName}**." This makes mistakes recoverable when someone has the wrong token. 2. **Read before write.** Always fetch the current state of the transaction, invoice/bill, and payment account before showing a change summary. Surprises are worse than slow. 3. **Mutations require explicit approval.** Show a summary table (Transaction · Invoice/Bill · Payment Account · Fiat alignment · Sync) and ask "Apply these changes?" before any mutation. Only proceed on a clear yes. 4. **Use schema introspection when in doubt.** Field names, enum values, and argument shapes can drift. If a query/mutation errors with "unknown field" or "invalid enum", call `introspect(<TypeName>)` or `build_query(<operationName>)` and adjust — don't guess. Operations specifically called out as "verify at runtime" below are the ones most likely to need this. 5. **The skill is a loop.** After a successful match, ask "Match another?" and restart from Step 2. Don't re-check the ERP — that only happens once per session.

---

Step 1 — Verify ERP is connected

Run:

query { integration(first: 50) { results { id integratedApp isErp connectionStatus companyName } } }

Filter the results where `isErp == true` and `connectionStatus == "ACTIVE"`. The supported ERPs you should recognize are **Xero**, **QuickBooks Online (QBO)**, and **NetSuite** — `integratedApp` values are `XERO`, `QUICKBOOKS`, and `NETSUITE`. (If you encounter unknown values, `introspect("IntegrationsQueryNode")` will confirm the enum.) Ignore rows where `integratedApp` is empty — the API occasionally returns a null row.

• **No connected ERP:** Tell the user they need to connect one before matching can happen, point them at

`https://app.tres.finance/settings/integrations`, and stop.

• **One connected ERP:** Use it implicitly and just mention "Matching against **{companyName}** ({integratedApp})."
• **Multiple connected ERPs:** Ask which one to use — different ERPs have separate invoice/bill stores.

Cache the chosen ERP's `id`, `integratedApp`, and `companyName` for later steps and the loop.

---

Step 2 — Identify what the user has

Ask whether they have:

• a **transaction hash** (e.g. `0x…`) — best case, pins the match immediately,
• an **invoice/bill ID or number** (numeric internal ID, or the human-facing `invoiceNumber`/`billNumber`),
• or **both**.

If they have neither, require at least one. If they're not sure whether their identifier is an invoice or a bill, accept it and try both lookups in Step 3.

Also accept loose forms — "INV-123", "Bill 9988", "the bill for Acme last week". The `freeText` filter on `erpInvoices` / `erpBills` handles these.

**Before moving on, always ask for the transaction date (or an approximate date range) if they haven't given a tx hash.** Ledger volume is high — date is the single most useful filter for narrowing candidates. Also offer: *"If you happen to have the tx hash, paste it now — it pins the match exactly."* Date matters both directions (tx→bill and bill→tx).

---

Step 3 — Fetch the known object and produce ranked match suggestions

There are two branches. Pick by what the user provided. If they provided both a tx hash *and* an invoice/bill ID, skip ahead to Step 5 (match is already determined).

Branch A — User has a transaction hash

1. Fetch the transaction with its sub-transactions:

   query GetTx($hash: String!) {
     transaction(identifier: $hash, currency: "usd", limit: 1) {
       results {
         id identifier timestamp platform
         children {
           id amount balanceFactor isInternalTransfer
           fiatValue
           sender    { identifier displayName isInternal }
           recipient { identifier displayName isInternal }
           asset { symbol identifier }
         }
       }
     }
   }

2. Pick the **relevant sub-transaction**. Skip gas, skip internal transfers, prefer the one with the user's wallet on one side and an external counterparty on the other. Determine direction:

• `balanceFactor` negative → outflow → look for a **bill** to close.
• `balanceFactor` positive → inflow → look for an **invoice** to close.

If mul