StableMatch

BASE USDC MONTH-END CLOSE

Match USDC transfers to invoices without uploading your books.

For Base-native freelancers, agencies and small teams: compare an invoice CSV with a Base USDC transfer export in about 60 seconds. StableMatch isolates missing, ambiguous, duplicate, underpaid and unassigned payments using conservative, explainable rules.

✓ Files stay local✓ No wallet connection✓ No subscription✓ Every match explained
Invoice templateTransfer template

Using BaseScan? Choose “BaseScan token-transfer export” above. Export the token-transfer CSV for your receiving address, then use it directly; StableMatch checks the native Base USDC contract before matching.

Two CSVs are required. Nothing is uploaded.

Need the workflow first? Read the free Base USDC month-end reconciliation guide.

CONSERVATIVE BY DESIGN

StableMatch refuses weak automatic matches.

01

Direct evidence first

An explicit transaction hash is checked before any inference.

02

Safe automatic match

Without a hash, both payer wallet and exact amount must identify one transfer after invoice issue.

03

Ambiguity stays visible

Amount-only candidates and duplicate hashes are never silently matched.

Scope and limits

StableMatch compares files; it does not fetch your wallet history, create accounting entries, provide tax/audit/compliance conclusions, or prove the economic purpose of a transfer. It does not automatically combine split payments. Review every exception against your wallet, invoices and accounting policy.

Supported launch format: comma-separated CSV, Base/EVM addresses, USDC amounts up to six decimals. In normalized mode the file must explicitly provide chain, contract, log index and confirmation status. In BaseScan mode, Base Mainnet and confirmed status are assumptions derived from your source selection—not facts contained in every export row—while the USDC contract is still checked from the CSV. Version: stablematch-1.1-free-beta. Operated transparently as an AI-built microtool; no customers or accuracy guarantees are claimed.

Feedback and reproducible defects can be reported to the public Nostr support identity. Include only a non-sensitive run summary and report hash—never private keys or confidential files.