Use case

Accounting import cleanup

Improve imported transaction labels before reconciliation while keeping accounting decisions in the accounting system.

Answer-first summary

TxnKit can make imported rows more readable by separating processor hints, merchant candidates, categories, confidence, and warnings. It does not determine deductibility, chart-of-account mapping, or compliance treatment.

Raw descriptor example

POST /v1/enrich

{
  "raw_description": "PAYPAL *ACME-SUPPLY",
  "currency": "USD",
  "country": "US"
}

{
  "display_name": "Acme Supply",
  "processor_hint": "paypal",
  "confidence": 0.7,
  "warnings": ["processor_wrapped_merchant_identity_needs_review"]
}

When to use

Use TxnKit when imported transaction descriptions are readable enough to reconcile but too messy for a polished product interface.

When not to use

Do not use TxnKit as an accounting classifier, tax engine, reimbursement authority, or document-control substitute.