Bring a clear CSV. Keep the assumptions visible.
The first release supports a generic, configurable CSV and the Wrekonn sample template. No vendor-specific report or API adapter has been validated in this release. If your ticketing system exports a CSV, check its exact structure against these requirements before using it.
Download sample data · Download a starter template
| Field | Meaning / requirements |
|---|---|
| gross | Reported gross revenue; not already net of deductions. |
| fees, refunds | Separate deductions. Select positive or negative convention. |
| payout | A payout amount appearing once, not a repeated settlement header. |
| event, date | Event grouping and activity date in YYYY-MM-DD. |
| currency | One consistent currency: USD, CAD, GBP, EUR or AUD. |
| payout_status | paid / deposited / completed, or expected / scheduled / pending. |
| payout_date | Source-reported date in YYYY-MM-DD. Required for scheduled expectations. |
Limits and validation
UTF-8, comma delimiters, a unique header row, up to 1 MB, 10,000 data rows, 80 columns, 500 event groups and 120 reporting months. Use dot decimals with at most two decimal places and correctly grouped comma thousands. Parentheses and a leading minus indicate negative amounts. Individual and aggregate amounts must not exceed 100 billion currency units. Blank mapped amounts require explicit consent to treat as zero.
Do not mix transaction and settlement row types. Remove totals and subtotals. Include each fee, refund and payout once. Do not upload card numbers, patron details, credentials or unnecessary personal data.