Retrieves a paginated list of accounting transactions with optional date range filtering.

Accounting Transaction Overview

An accounting transaction represents a group of accounting entries that together
form a balanced operation (total debits equal total credits).

Each transaction:

• Has an effective date when the financial impact occurs
• Contains one or more accounting entries (each with debit_in_cents or credit_in_cents)
• May be linked to accounting events and other business objects (leases, bank transactions, billing)
• Has a nature describing its type (e.g., manual_entry, import, rent_call)
• May be classified under a journal (allocation or fees)

Business Significance

Accounting transactions are the core unit for:

• Understanding the financial impact of business operations
• Building general ledger views
• Reconciling accounts and audits

Key Concepts

• Effective Date: When the transaction takes effect in the books
• Nature: The type/category of the transaction
• Journal: Classification of the transaction (allocation or fees)
• Entries: Individual debit/credit lines that make up the transaction. Each entry includes
  denormalized fields from its parent transaction (nature, description, effective_date) for convenience.
• Events: Higher-level business events that may group one or more transactions
• UUID: Unique identifier that can be used for idempotency and cross-system references

Filtering Capabilities

The API supports filtering transactions by:

• Effective date range (using from_date and to_date parameters)

Response Format

The response contains a paginated list of accounting transactions with their
associated entries (including denormalized transaction fields) and related event identifiers.