Marketplace Settlement Ledger Normalizer

Convert settlement CSV, TSV, or JSON exports into exact, currency-separated ledger rows with source provenance. Missing amounts stay unresolved instead of being guessed or forced into a balance.

Start in 30 seconds

1. Select Try for free and run the packaged demonstration fixture.
2. Paste or upload an authorized settlement export.
3. Export normalized ledger rows and review the reconciliation summary.

Price: $0.001 per reconciled row, plus a $0.00005 start event. Unresolved rows, failed runs, and the demo fixture are free.

The Actor does not connect to marketplaces or banks, and its output is not accounting, tax, or compliance approval.

Overview & Background (W2-18)

Marketplace settlement reports present major hurdles for self-bookkeeping sellers and ecommerce bookkeepers:

• Complex withholding and release mechanics (e.g., Amazon DD+7 reserve policies).
• Unexplained fee and debit line items (e.g. Amazon seller forum reports of unexpected "OTHER" charges).
• Opaque fee breakdowns spanning FBA fulfillment, weight handling, storage, advertising, refund commissions, and marketplace facilitator tax withholdings.
• Format breaks and silent omissions in spreadsheets leading to balance mismatches.

This Actor accepts uploaded settlement files and deterministically produces an itemized normalized ledger, verifies stated deposit totals against item sums, and explicitly buckets unresolved items without guessing or forcing matches.

Core Guarantees

1. Stateless Processing: Operates entirely in-memory with file-in and ledger-out semantics. No credentials, tokens, external databases, or third-party connections required.
2. Exact Decimal Representation: Money is represented strictly with exact integer minor units (BigInt cents) and decimal-safe strings. Zero IEEE-754 floating-point rounding errors.
3. Zero Silent Drops, Zero Forced Matches: Every row in the input file is either matched to standard ledger categories or explicitly quarantined into a labeled unresolved bucket (e.g. unresolved_unexplained_charge, unresolved_unknown_type, unresolved_missing_reference).
4. Complete Source Provenance: Every generated ledger line retains the 1-based source file row number, original transaction identifier, raw input record, and matching rule identifier.
5. Reconciliation Balancing: Stated deposit totals (from settlement file headers or user declaration) are compared against the exact sum of line items. If a discrepancy exists, an explicit balancing gap line is emitted under unresolved_reconciliation_gap rather than silently ignored or force-allocated.

Supported Formats & Categories

Input Formats

• Delimited Text (TSV / CSV): Generic multi-column settlement records. Quoted or multiline CSV must be qualified before use.
• JSON Array: Array of settlement record objects.

Standard Normalized Categories

• revenue: Product principal sales, shipping revenue, gift wrap revenue.
• fee: Referral commission, FBA per-unit fulfillment, weight handling, monthly subscriptions, storage, return postage, removal order disposal, PPC advertising.
• refund: Return principal refunds, referral fee rebates, refund administration fees, restocking fee credits.
• tax: Sales tax collected, marketplace facilitator tax withheld at source.
• promotion: Merchant promotion discounts, shipping concessions.
• reserve: Reserve withholdings (e.g. DD+7 policy hold) and prior reserve releases.
• adjustment: Warehouse lost/damaged inventory reimbursements, customer concessions, foreign exchange adjustments, liquidation proceeds.
• transfer: Net disbursement bank transfer lines.
• unresolved: Explicit buckets for items requiring bookkeeper review.

Explicit Unresolved Buckets

• unresolved_unexplained_charge: Labeled "Other" or "OTHER" without item details.
• unresolved_unknown_type: Unrecognized transaction type strings.
• unresolved_missing_reference: Fee or adjustment missing mandatory order or adjustment reference.
• unresolved_malformed_amount: Non-numeric or invalid amount strings.
• memo_non_financial: Informational zero-value lines.
• unresolved_reconciliation_gap: Balancing gap when stated deposit differs from line sums.

Outputs

• Default Dataset: One item per normalized ledger line.
• Key-Value Store (OUTPUT): Run envelope with stated deposit, calculated total, exact delta, category totals, unresolved bucket breakdown, and audit counts.
• Key-Value Store (LEDGER): Exportable JSON snapshot of the complete ledger.

Local Development & Testing

Run all unit and integration tests using Node's built-in test runner (no external test dependencies):

$npm test

Execute a local run with the built-in 35-row representative settlement fixture without network or Apify credentials:

$npm start

Non-Goals & Boundaries

• No external API integrations, banking connections, or credential storage.
• No legal, tax, or professional accounting advice or compliance certification.
• No fuzzy or forced matching on ambiguous money amounts.

Financial rows and raw source records can be sensitive. Minimize uploads, never place customer exports in public samples, and delete datasets and stores under the customer's retention policy. Mixed currencies remain separate and a missing stated deposit remains unverified. Support owner: Mehdi Badawi through the Apify Store support channel, with an initial-response target of two business days.