feat(fixed-deposits): FD interest posting approval with pooled GL postings

Adds a maker-checker approval report in front of fixed deposit interest posting, mirroring the existing savings interest posting report: a report is generated per branch and product (SINGLE/DOUBLE/SPECIAL), a second user approves it, and it posts when the branch closes its day. Day close is blocked until deposit interest due that day is approved. Ledger entries are pooled per the report's interestPostingDate rather than raised per deposit: Dr Interest Expense and the Payable/Paid legs are each raised once for the group's total, and only the final leg crediting each deposit's own GL is per account — the same pattern the savings interest posting report already uses, instead of repeating the full three-stage chain for every deposit. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-08 00:06:00 +05:30
parent 6c7c0f8445
commit 949f45c4cd
18 changed files with 2383 additions and 4 deletions
@@ -68,6 +68,18 @@ public interface SavingsAccountReadPlatformService {
    List<SavingsAccountData> retrieveAllSavingsDataForInterestPosting(boolean backdatedTxnsAllowedTill, int pageSize, Integer status,
            Long maxSavingsId);

+    /**
+     * The active fixed deposits of one branch — and one product, where given — whose interest may be
+     * due for posting on the date. The interest engine settles whether any actually is.
+     *
+     * @param officeId
+     *            the branch the deposit's customer belongs to, or null for every branch
+     * @param productId
+     *            one fixed deposit product, or null for every product
+     */
+    List<SavingsAccountData> retrieveFixedDepositsDueForInterestPosting(boolean backdatedTxnsAllowedTill, LocalDate postingDate,
+            Long officeId, Long productId);
+
    List<SavingsAccountTransactionData> retrieveAllTransactionData(List<String> refNo);

    Long retrieveAccountIdByExternalId(ExternalId externalId);