Arc Ledger Match
AboutBrowser-only · no walletLoading example…
USDC RECONCILIATION / ARC MAINNET 5042

Reconcile invoices.
Account for every USDC.

Reconcile invoices, resolve unallocated payments, and keep the evidence.

Use your own records
Review your ledger

Start with the invoices that need attention.

01 / RECONCILIATION

Invoice ledger

Needs attention first
InvoiceExpectedAllocatedRemaining / extraStatusEvidence

All amounts in USDC. “Fully allocated” describes this local ledger; it does not prove commercial settlement. A possible match never changes the invoice status.

03 / SOURCE RECORDS

Payments to reconcile

Source ≠ invoice association
Payment / sourceAmountAvailableResolutionPossible matches / warningsSourceAction
Saved explicit allocations

Allocations JSON supports lossless re-import. Spreadsheet CSV prefixes formula-leading IDs and reasons with an apostrophe, which the importer preserves.

Keep a record of your review.

Export before closing. This workspace is held in browser memory.

More exports
04 / WORKSPACE TOOLS

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.

Invoices CSV · Payments CSV · Allocations JSON

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.


  

    

      
05 / ABOUT
About Arc Ledger Match
A clear view of what each client payment covers.
Compare existing USDC invoices with payment records and public Arc mainnet receipts. Intended for freelancers checking client payments, small businesses reviewing receivables, and operations teams resolving unclear transfers.

      
Understand what still needs a decision.
The ledger highlights possible matches, partial payments, overpayments and unassigned amounts. A transfer alone cannot identify its invoice: your invoice references or explicit allocations determine what counts toward each invoice. Split payments and record why, with exact amounts throughout.

    

    
    
      
  1. Import your records
    Start with the example, or bring invoices and payment records as CSV or JSON.
    2. 
      
  2. Review & allocate
    Check possible matches and optional public receipts. Assign amounts with a reason.
    3. 
      
  3. Export the evidence
    Save the JSON report with your inputs, allocations and source records.
    4. 
    

    
Your workspace. Your records.
Invoice data is processed in browser memory and isn’t saved automatically. Export the JSON report before closing or refreshing. Optional receipt reads send selected public transaction hashes to your chosen RPC provider.
No wallet connection or signature is needed, and the tool doesn’t move funds. Ledger status records your allocations; it doesn’t certify settlement.