Reconcile invoices.
Account for every USDC.
Reconcile invoices, resolve unallocated payments, and keep the evidence.
Invoice ledger
| Invoice | Expected | Allocated | Remaining / extra | Status | Evidence |
|---|
All amounts in USDC. “Fully allocated” describes this local ledger; it does not prove commercial settlement. A possible match never changes the invoice status.
Payments to reconcile
| Payment / source | Amount | Available | Resolution | Possible matches / warnings | Source | Action |
|---|
Saved explicit allocations
Allocations JSON supports lossless re-import. Spreadsheet CSV prefixes formula-leading IDs and reasons with an apostrophe, which the importer preserves.
Your records & public evidence
Example records are synthetic and unverified. Import replaces one collection; clear the ledger first to start with only your own data.
Import invoices, payments or allocations
CSV or JSON, processed locally. Invalid data leaves the ledger unchanged. Imported payments remain unverified.
Schema and sample files
Invoice: invoice_id,expected_amount,sender,receiver,start_at,end_at. Payment: payment_id,amount,sender,receiver,occurred_at,invoice_id. Allocation: invoice_id,payment_id,amount,reason. Optional columns may be empty. Amounts are exact decimal strings; dates are ISO UTC. Limit: 5,000 rows per collection, 2 MB per import and 5,000 candidate links across the report. Exceeding a limit rejects the operation; narrow address/date filters or split imports.
Read public Arc transfers
Optional, read-only mainnet receipts. Only your selected public hashes go to the chosen RPC. Transfer data never supplies an invoice reference.
8 second timeout; at most one transient retry. Re-reading replaces the same observed event. ERC20 mirrors add no principal.
RPC evidence & separate gas fees (0)
No live RPC reads yet.
Full reproducible report
JSON contains inputs, allocations, provenance and raw RPC observations. Keep exports private when your invoice metadata is sensitive.