Skip to content
CommissionSight Docs

CommissionSight

CommissionSight ingests monthly commission statements (CSV/XLSX) from many carriers on behalf of many accounts, maps them into a unified superset member table, and computes a green / yellow / red status for every member, month over month.

What it gives you

  • One consistent view across every carrier. However each carrier formats its statement, every member lands in the same unified table — so you compare and report across carriers in one shape.
  • No code to onboard a carrier. A new carrier is just a JSON config (mapping + transforms); upload a sample and CommissionSight even drafts it for you.
  • Fast, async processing. Uploads return immediately and ingest runs in the background; poll the job or receive a signed webhook when it’s done.
  • Per-customer isolation. Each account’s data lives in its own database, encrypted at rest, reachable only by that account’s token. See Security.

Four ways to adopt

Not another tool to adopt — one reconciliation engine that ships four ways, so it fits the smallest shop and the largest operation alike. The scoring underneath is identical; pick the surface that matches how you already work.

  • Clean UI — for agencies that just want answers. Upload a statement and go: dashboard, grids, comparisons, and CSV export, no setup or integration.
  • API — drop reconciliation straight into your own stack. A clean, self-describing REST API (OpenAPI 3.1 at GET /v1/openapi.json) with signed webhooks — push statements, pull scored results anywhere.
  • SDKs — for large operations and CRM / AMS platforms to embed. Typed TypeScript, Python, and C# / .NET clients that wrap the full API surface, every endpoint fully typed.
  • CLI — a native command-line interface for terminals and AI agents: machine-readable output, deterministic exit codes, and fully non-interactive flags, built on the TypeScript SDK. Authenticate, manage workspaces, and upload statements from a script or an agentic harness like Claude Code.

Concepts

  • Account — your organization. Each account’s statement data lives in its own dedicated database (per-account isolation).
  • Carrier — an insurance carrier with a fixed column layout, described by a JSON config.
  • File — one uploaded statement, bound to a carrier + calendar month/year.
  • Job — the async ingest + delta computation triggered by an upload.
  • Status — per member, per period: 🟢 green (continuous, unchanged), 🟡 yellow (a tracked field changed), 🔴 red (dropped). Flags add detail: NEW, COMMISSION_CHANGED, DATA_CHANGED, DROPPED, REAPPEARED, REAPPEARED_WITH_DELTA, CHARGEBACK.

Base URL & auth

https://api.commissionsight.com/v1

API requests use a bearer account token in the Authorization: Bearer <token> header. The API is self-describing — start at GET /v1 and read the _links, or fetch the spec at GET /v1/openapi.json.

Continue with Authentication or jump to the end-to-end walkthrough.