Weekly settlement, weekly closed.

Cycle import

Upload a CSV (or POST via API) with cycle number, period start, period end, remittance date, and transaction lines. The platform creates the cycle, matches each transaction line to issued tickets in your booking history, and surfaces any unmatched or variance lines for review.

Three-state matching

• Matched — ticket found, amount within tolerance, ready to settle
• Variance — ticket found but amount/tax/commission differs, queued for review
• Unmatched — no booking line in our records for this ticket number

ADMs and ACMs

Agency Debit Memos and Agency Credit Memos are not buried in suspense — they become first-class line types in the cycle, route to the supplier dispute workflow if you choose, and roll into the net remit calculation.

Settlement journal

One click posts the cycle settlement journal:

DR  103000  BSP Clearing                  (total sales − refunds + ADM − ACM)
    CR  101000  Operating Bank                 (net_remit)
    

The cycle status moves to settled with an immutable link to the journal id, and the journal is hash-chained into the per-tenant ledger.

What you get

• BSP and ARC cycle imports via CSV or API
• Auto-match against issued tickets with tolerance bands
• ADM/ACM line tracking with dispute workflow
• Single-click settlement with audited journal
• Per-cycle variance reporting
• Void window monitoring and exchange/reissue trails
• Coupon-status and EMD accounting

See it on your data