Quickstart
Sign in, import your CSV, see the math — in 60 seconds.
You don't need to set up an agreement, define cohorts, or configure anything. We seed an Acme sample portfolio on your first sign-in so you can validate the math against real data shapes before you bring your own.
- 1
Sign in with your email
No password. We email you a one-time sign-in link that lands you in a fresh tenant with a populated sample portfolio (3 agreements: flat volume rebate, growth incentive, tiered national accounts).
Open sign-in → - 2
Upload your POS CSV (or use ours)
The /import page has a drag-drop file picker plus a sample CSV download. We validate each row and report line-numbered errors. Valid rows insert as pos_rows; the calc engine auto-dispatches against every active agreement on your tenant.
- 3
See the math
Cockpit shows your accrual totals per agreement. Click any agreement to see every calculation event — the bucket that fired, the matched condition record, the source row, and the explanation. Export the full audit trail as CSV when you need to defend a number.
CSV format
Seven columns. UTF-8 encoded. Quoted fields with embedded commas and escaped double-quotes are handled. Header row required.
source_transaction_id,transaction_at,distributor_id,end_customer_id,material_id,quantity,amount_usd INV-0001,2026-06-05,ACME-DIST-EAST,EC-RETAIL-100,ACME-WIDGET-100,12,3600.00 INV-0002,2026-06-05,ACME-DIST-EAST,EC-RETAIL-100,ACME-PRO-LINE,4,8200.00 INV-0003,2026-06-05,ACME-DIST-WEST,EC-RETAIL-200,ACME-CORE-LINE,8,4400.00
| Column | Type | What it means |
|---|---|---|
| source_transaction_id | string | Your invoice / order number. Must be unique within the upload. |
| transaction_at | date or ISO timestamp | Date the sale settled. `2026-06-05` or `2026-06-05T10:30:00Z` both work. |
| distributor_id | string | The channel partner who sold. Matches the customer on your agreement. |
| end_customer_id | string | Who the partner sold to. Used for ship-to-level analytics. |
| material_id | string | Your SKU / material number. Matched against agreement line items. |
| quantity | integer | Units. Used by SPIF / per-unit calculations. |
| amount_usd | decimal | Net sale value in USD. The basis for percent / tiered calculations. |
What makes Aurgus different
Every number ties.
Every accrual writes one calculation event carrying the bucket, the configuration, the snapshot inputs, the matched condition record, and the resulting amount. Reprice posts Adjustment deltas with supersedes_event_id lineage. Nothing is reconstructed; everything is replayed.
Cross-language parity, tested.
The TypeScript calc engine and the Python canonical engine produce identical numbers within 0.005 USD tolerance across all 6 bucket patterns. CI fails if either drifts.
Stops at the calculation boundary.
Aurgus computes the accrual and the settlement document. It does not model your general ledger or your ERP posting logic — those stay where they belong. Export the settlement as CSV; your ERP determines the posting via its own configuration.
That's the whole quickstart.
Sign in to start →