Finance Transactions

Purpose and access

Transactions is the immutable ledger workspace. Viewers inspect permitted rows; makers can create allowed manual entries; reconcilers manage links; approvers and auditors inspect evidence and receipts. The API rechecks partner/event scope and capability for every action.

Page anatomy and controls

The header identifies partner, currency, source, cutoff/timezone, and freshness. KPI values and table totals remain currency-scoped. Search covers safe reference/description fields. Filters cover date, account, event, counterparty, category, state, amount, reconciliation, and evidence. Sort and cursor belong to the server query; a visible page is not a complete export.

Rows show posting date, reference, description/source, event/category, account effect, amount/currency, reconciliation/evidence state, and status. Detail shows balanced debit/credit lines, dimensions, allocations, statement links, evidence history, approval chain, reversal/correction links, request/correlation IDs, and audit receipt.

Actions and validation

Manual entry requires posting date, reference, description, currency, and balanced account lines. Allocate/unallocate, attach/detach evidence, reverse/correct, and export are separate accountable actions. Unknown accounts, cross-partner/event scope, mixed-currency lines, imbalance, duplicate payload, stale state, or locked period fail without a partial journal.

Posted rows are never edited or deleted. Correction posts a new balanced linked entry with reason, actor, server time, and audit evidence.

Errors and recovery

On timeout, search by reference/idempotency and inspect the receipt before retrying. Refresh stale state and compare before intentionally reapplying. For a locked period, use the controlled reopen/correction process. Escalate any unbalanced entry, unauthorized row, duplicate authoritative posting, or result that cannot be reproduced.

Keyboard users must reach filters, rows, detail actions, and dialogs in logical order. Status cannot depend on color alone; dialogs require labelled controls, initial focus, pending lockout, visible validation, Escape behavior when safe, and focus return.