[
https://issues.apache.org/jira/browse/FINERACT-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnold Galovics updated FINERACT-2920:
--------------------------------------
Fix Version/s: 1.16.1
1.16.0
> Update Trial Balance Details compares a wall-clock baseline with transaction
> dates and skips days when the business date is behind the clock
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: FINERACT-2920
> URL: https://issues.apache.org/jira/browse/FINERACT-2920
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Arnold Galovics
> Assignee: Arnold Galovics
> Priority: Major
> Fix For: 1.16.0, 1.16.1
>
>
> 🐛 Steps to Reproduce
> 1. Business date enabled, business date behind the wall clock (e.g. business
> date 2026-10-05, today 2026-10-11).
> 2. Post journal entries with transactionDate 2026-10-05, so created_date is
> 2026-10-11.
> 3. Run "Update Trial Balance Details" once the business date has reached
> 2026-10-06, so those rows land in m_trial_balance.
> 4. Advance the business date through 2026-10-06 .. 2026-10-11, posting
> entries each day, and run the job after each.
> 5. Compare m_trial_balance with the journal entry transaction dates.
>
> ❌ Actual Result
> • No trial balance rows are created for transaction dates 2026-10-06 ..
> 2026-10-11.
>
> ✅ Expected Result
> • A trial balance row is created for every transaction date before the
> business date.
>
> ℹ️ Notes
> • Found by reading the code, not executed. Same loop in 1.15.0 (tasklet
> :59-69).
>
> 🔧 Technical Notes
> • m_trial_balance.created_date holds je.createdDate, an audit timestamp
> (JournalEntryRepository.java:64, TrialBalance.java:55, tasklet :83).
> • Baseline = MAX(created_date) (TrialBalanceRepository.java:35), then
> DISTINCT je.transactionDate > baseline (JournalEntryRepository.java:52).
> Wall-clock date vs accounting date.
> • Fix idea: baseline on entry_date, or store the last processed date.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
