BASESCAN EXPORT WORKFLOW
How to export BaseScan USDC transfers to CSV
A clean export is the evidence boundary for reconciliation. Preserve the original file, verify the token contract, and avoid mixing other wallets, networks or look-alike tokens into the close.
1. Open the receiving address on BaseScan
Navigate to the Base address that receives customer payments. Open its ERC-20 token-transfer view. BaseScan exposes a CSV export control on address and token-transfer pages; its exact placement may change as the explorer UI evolves.
2. Verify native Base USDC
The native USDC contract on Base used by StableMatch is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. Do not rely on token names or symbols alone: look-alike assets can display a similar “USDC” label. Confirm the contract address before treating a row as settlement evidence.
3. Choose a defensible period
Export the month or close period being reconciled. Include a documented late-payment window if invoices issued near period-end may settle afterward. Record the time zone used by the export and do not silently mix local timestamps with UTC.
4. Download and preserve the original CSV
Use BaseScan's CSV export control. Save the untouched export as source evidence before filtering, renaming columns or opening it in spreadsheet software. Spreadsheet applications may rewrite timestamps, large identifiers or leading zeros.
5. Check the fields before matching
Useful transfer evidence includes transaction hash, timestamp, from address, to address, token amount and contract address. StableMatch's BaseScan adapter recognizes common export headers including Txhash, DateTime, From, To, TokenValue and ContractAddress.
6. Reconcile conservatively
Load the export with an invoice CSV in StableMatch. Explicit transaction hashes are checked first. Without a hash, an automatic match requires one unique payer wallet and exact amount after the invoice issue time. Repeated amounts and amount-only candidates remain exceptions.
Common mistakes
- Exporting the wrong receiving wallet or another network.
- Trusting the token symbol without checking the contract.
- Dropping duplicate transaction hashes before investigating them.
- Editing the only copy of the source export.
- Assuming equal amounts prove invoice identity.
Open the free reconciliation tool · Read the complete month-end workflow · Download the invoice template