tres-invoice-bill-matching

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.