Guides

Finance agents

Extract invoice → match PO/ERP → draft journal entry → escalate exceptions. agent_id: invoice.

Scenario

An ERP field rename silently broke line matching — TraceForge showed tax_code_lookup disappearing from traces while HTTP still looked healthy. DriftWatch + FineForge adapter fix close the loop.

What Inferix gives you

TraceForge tool taxonomy for extract → match → ledger → HITL
DriftWatch on tool schema drift (D03) and format drift (D16)
FineForge adapter + fixture updates (F03/F04)
LensAI cost per reconciled invoice (business success)

Tools & intents

Tools	Intents
docs.extract_invoice, erp.find_po, erp.match_line, erp.get_tax_code, ledger.draft_entry, human.escalate	match_po, partial_match, tax_exception, duplicate_invoice, currency_mismatch, missing_po

Setup

routing:
  rules:
    - name: invoice-match
      when: { agent: invoice, intent: match_po }
      model: owned/general-llm
    - name: invoice-tax
      when: { agent: invoice, intent: tax_exception }
      model: owned/general-llm
      escalate_if: { ambiguity: true, model: provider/strong }

# tool_schema_version required on all erp.* spans
# HITL escalate tagged so exclusive wait ≠ hang (T20)

Watch & failures

Tool 4xx schema errors (T03) → FineForge adapter
Skipped erp.get_tax_code on tax_exception
Parse fail rate on extract (D16)
Poison retrieval of PO docs (D05)

Schema remediation at scale is the API healing wedge; finance agents are the ERP-shaped proof of the same TraceForge + FineForge pattern.

Cost routing and cache for sales agents.

GTM & outbound →