@zeniai/client-epic-state 5.2.11-betaRD6 → 5.2.11-betaRD7

package/lib/entity/jeSchedules/jeSchedulesState.d.ts

@@ -149,7 +149,12 @@ export interface OneTimeAccrualEdits {
     jeDebitAccountingClassId?: ID;
     jeDebitAccountingClassName?: string;
     memo?: string;
-    reversalPolicy?: OneTimeAccrualReversalPolicyType;
+    /**
+     * The Auto Reversal toggle, modelled as the same boolean the New form and the create payload use
+     * rather than a policy string: `reverse_next_month` alone decides the policy server-side, and
+     * sending both would be two sources of truth for one control.
+     */
+    reverseNextMonth?: boolean;
 }
 export interface JEOneTimeAccrualCreator {
     userId: ID;

package/lib/esm/view/expenseAutomationView/epics/jeSchedule/oneTimeAccrualActionsEpic.js

@@ -63,7 +63,10 @@ export const promoteOneTimeAccrualEpic = (actions$, state$, zeniAPI) => actions$
     // vendor_id, vendor_name and service_month are deliberately absent: promote takes them from
     // the stored draft and ignores them in the body, so sending them would imply a reassignment
     // that never happens.
-    const reversalPolicy = edits?.reversalPolicy ?? accrual?.reversalPolicy;
+    // Untouched falls back to the stored policy, so posting without editing cannot silently
+    // flip a scheduled reversal to on-bill-match.
+    const reverseNextMonth = edits?.reverseNextMonth ??
+        accrual?.reversalPolicy === 'scheduled_date';
     const expectedReversalDate = edits?.expectedReversalDate ?? accrual?.expectedReversalDate;
     const debitClassId = edits?.jeDebitAccountingClassId ?? accrual?.jeDebitAccountingClassId;
     const debitClassName = edits?.jeDebitAccountingClassName ??
@@ -77,9 +80,10 @@ export const promoteOneTimeAccrualEpic = (actions$, state$, zeniAPI) => actions$
         ...(debitClassName != null
             ? { je_debit_accounting_class_name: debitClassName }
             : {}),
-        ...(reversalPolicy != null ? { reversal_policy: reversalPolicy } : {}),
-        // Only meaningful for the scheduled-date policy; agent-je derives it for on_bill_match.
-        ...(reversalPolicy === 'scheduled_date' && expectedReversalDate != null
+        // Mirrors the create payload: reverse_next_month alone decides the policy, and the date is
+        // only meaningful when it is true -- agent-je derives the reversal from the bill otherwise.
+        reverse_next_month: reverseNextMonth,
+        ...(reverseNextMonth && expectedReversalDate != null
             ? {
                 expected_reversal_date: expectedReversalDate.format(DEFAULT_DATE_FORMAT),
             }

package/lib/view/expenseAutomationView/epics/jeSchedule/oneTimeAccrualActionsEpic.js

@@ -66,7 +66,10 @@ const promoteOneTimeAccrualEpic = (actions$, state$, zeniAPI) => actions$.pipe((
     // vendor_id, vendor_name and service_month are deliberately absent: promote takes them from
     // the stored draft and ignores them in the body, so sending them would imply a reassignment
     // that never happens.
-    const reversalPolicy = edits?.reversalPolicy ?? accrual?.reversalPolicy;
+    // Untouched falls back to the stored policy, so posting without editing cannot silently
+    // flip a scheduled reversal to on-bill-match.
+    const reverseNextMonth = edits?.reverseNextMonth ??
+        accrual?.reversalPolicy === 'scheduled_date';
     const expectedReversalDate = edits?.expectedReversalDate ?? accrual?.expectedReversalDate;
     const debitClassId = edits?.jeDebitAccountingClassId ?? accrual?.jeDebitAccountingClassId;
     const debitClassName = edits?.jeDebitAccountingClassName ??
@@ -80,9 +83,10 @@ const promoteOneTimeAccrualEpic = (actions$, state$, zeniAPI) => actions$.pipe((
         ...(debitClassName != null
             ? { je_debit_accounting_class_name: debitClassName }
             : {}),
-        ...(reversalPolicy != null ? { reversal_policy: reversalPolicy } : {}),
-        // Only meaningful for the scheduled-date policy; agent-je derives it for on_bill_match.
-        ...(reversalPolicy === 'scheduled_date' && expectedReversalDate != null
+        // Mirrors the create payload: reverse_next_month alone decides the policy, and the date is
+        // only meaningful when it is true -- agent-je derives the reversal from the bill otherwise.
+        reverse_next_month: reverseNextMonth,
+        ...(reverseNextMonth && expectedReversalDate != null
             ? {
                 expected_reversal_date: expectedReversalDate.format(timePeriod_1.DEFAULT_DATE_FORMAT),
             }

package/lib/view/expenseAutomationView/payload/jeSchedulesPayload.d.ts

@@ -70,7 +70,7 @@ export interface PromoteOneTimeAccrualPayload {
     je_credit_accounting_class_name?: string;
     je_debit_accounting_class_id?: ID;
     je_debit_accounting_class_name?: string;
-    reversal_policy?: string;
+    reverse_next_month?: boolean;
 }
 /**
  * Ignore body. `scope` is deliberately absent — the API returns 400 if it is sent, which is why the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zeniai/client-epic-state",
-  "version": "5.2.11-betaRD6",
+  "version": "5.2.11-betaRD7",
   "description": "Shared module between Web & Mobile containing required abstractions for state management, async network communication. ",
   "main": "lib/index.js",
   "module": "lib/esm/index.js",