Reconciliation Exceptions
Identify and resolve settlement discrepancies.
Reconciliation is under construction on the platform, and no exceptions read API exists
— the endpoint formerly shown on this page (/v1/reporting/exceptions) was never real. The
settlement.batch.closed and settlement.exception_detected webhook events are catalogued
but not yet emitted. This page describes the planned capability.
Reconciliation exceptions appear when a settlement doesn't match the expected amount. Common causes include timing differences, fee adjustments, returns, and chargebacks.
Viewing exceptions (planned)
The planned surface would live alongside Payments → Settlements; no such page exists today.
Exceptions are flagged automatically when:
- A settlement batch amount differs from the sum of individual transactions
- A return or chargeback reduces a previously settled amount
- A fee adjustment is applied outside the normal schedule
Exception types
| Exception code | Description | Suggested action |
|---|---|---|
EXC-001 | Batch total mismatch — timing difference | Check for same-day returns |
EXC-014 | Chargeback deduction from settlement | Review dispute.created events for the period |
EXC-031 | Fee adjustment | Review fee schedule with Cresora |
EXC-044 | Return deducted from settlement | Match to transaction.returned events |
EXC-099 | Manual adjustment by Cresora | Contact Cresora for explanation |
Resolving an exception
- Click the exception to view the detail
- Match against the suggested source event (chargeback, return, etc.)
- Mark as Resolved once your books reflect the adjustment
Unresolved exceptions older than 30 days are escalated to your Cresora account manager.
Exception reports via API
Planned; no read API exists yet. Until it ships, the closest primitive is
GET /api/v1/transactions/export filtered by period and state —
compare the settled totals against your books to surface discrepancies yourself.