Background

FLW-1145 removed all fixed time limits from the Mitanin Trainer and ANM review workflow (the MT's 24 hour window, the ANM's 5th of month due date, and the Overdue status tied to it). This left a gap: nothing defines what should happen if a Mitanin corrects and resubmits a rejected activity very late, since the old fallback (Section 13.1/17 of the BRD, tied to the ANM's due date) no longer applies once that due date was removed.

Raised after review of the BRD (Confluence page 164692128, Revision 2 Section 18.7: "Resubmission after a rejection, by either role, has no fixed time requirement") alongside the recent FLW-1171 discussion.

Why this flexibility exists (context, not a permanent gap)

The Mitanin app is being piloted in Chhattisgarh. For the first 2-3 months, submission and review are intentionally kept flexible, with no fixed cutoff dates, so the team can observe how Mitanins, Mitanin Trainers, and ANMs actually use the app before deciding on permanent cutoff dates and restrictions. This ticket documents the interim rule for that pilot window, it is not asking for a new permanent cutoff to be built.

Interim rule (pilot window)

• Within a calendar month, a Mitanin can submit or resubmit a claim/activity at any time during that month.
• Within that same calendar month, the Mitanin Trainer and the ANM can approve or reject at any time.
• If an activity is rejected and the Mitanin does not correct and get it approved again before that calendar month ends, that specific activity's claim goes to Unclaimed for that month. It does not roll over into the next month.
• This is per activity, not per whole claim: the rest of that month's correctly claimed and approved activities are unaffected and are counted for incentive as normal.

What's needed

• Confirm whether the existing Mitanin Unclaimed status/derivation logic (previously tied to the ANM's 5th-of-month due date, now removed per FLW-1145) still correctly transitions a single rejected-and-uncorrected activity to Unclaimed at calendar month end under the new activity-level, time-unbound review model, without affecting the rest of that month's approved activities.
• If that logic no longer exists or was tied to the removed due date, this needs to be rebuilt against calendar month end instead.
• QA to verify: one activity missing the month-end cutoff does not block or delay payment of the Mitanin's other approved activities for that month.

Reference

BRD: https://pmp.piramalswasthya.org/confluence/pages/viewpage.action?pageId=164692128 - added as Revision 5 (Section 21), version 15.