In General ledger - Inquiries and report - Ledger transaction list

Current behavior

• The Ledger transaction list report (SSRS) cannot handle large data volumes.
• When users try to extract full-year or high-volume transactions:
• The report execution becomes very slow
• Eventually, it fails with timeout error
• Users are forced to:
• Apply heavy filtering, or
• Switch to Data Management for export
• This creates inconsistency in user experience (report vs data extraction).

Expected behavior

• The system should support large-volume transaction extraction directly from the report, OR:
• Improve performance to avoid timeout, OR
• Automatically handle large data (e.g., batching, background processing)
• Users should be able to:
• Run full ledger transaction reports without manual segmentation

Business impact

• Ledger transaction data is core financial data
• As business grows:
• Data volume increases
• Report becomes unusable
• Users expect reporting tools to scale with data volume
• Current limitation impacts:
• Month-end / year-end analysis
• Audit and reconciliation tasks