Skip to main content
D
DeniseShang
Member
July 8, 2026
Question

Connecting Task Manager Close Calendar / Close Map to RCM Due Dates

  • July 8, 2026
  • 2 replies
  • 21 views

I am looking for suggestions or shared experience on connecting the close calendar / close map used in Task Manager with RCM / Account Reconciliation due date logic.

In our OneStream application, Task Manager already uses a close map based on the corporate close calendar and workday schedule. I am trying to understand whether that same close calendar logic can be leveraged or referenced for Account Reconciliation due dates, instead of maintaining separate due date logic manually in RCM.

I am still investigating whether this is driven by configuration, business rules, underlying tables, or another design approach behind the scenes.

Has anyone successfully connected Task Manager close calendar/workday logic to RCM due dates or reconciliation timing? If so, I would appreciate any guidance on:

  • Whether this was handled through configuration or custom business rules
  • Whether Task Manager calendar information can be referenced directly by RCM
  • Any limitations or maintenance concerns
  • Recommended design approach or lessons learned

Thank you in advance for any suggestions or examples you can share.

2 replies

J
jbrem
Contributor
July 9, 2026

I believe they are using different tables.  Is it the calendar itself that is a problem?  Or the due dates?  I just set up the calendars once a year for both and then the local admins manage their own lists and due dates from there.

H
Haritha_Dev
Member
July 10, 2026

Hi,
 

In our implementation, we don't try to link Task Manager's close calendar directly to RCM's due date logic they're separate tables/objects under the hood, and there's no native reference from one to the other.

What we do:

Calendar setup: I set up the close calendar/workday schedule once a year for both solutions. For RCM, that's the Close Date at the Workflow Profile/Scenario/Time level; for Task Manager it's the close schedule itself.
Due dates: Once the calendars are in place, local admins own due date logic from there — task due dates in Task Manager, and Preparer Workday Due / Approver Workday Due offsets on the Reconciliation Definitions in RCM.

To directly answer the "is it the calendar or the due dates" question — it's not the calendar/workday math that's duplicated, since both solutions are just computing business-day offsets off an anchor date. The gap is that RCM's anchor (Close Date) and Task Manager's close schedule are two separate data points that each need to be set independently.

This is actually confirmed by OneStream's own Community KB — there's a direct answer stating Task Manager and RCM live independently: a task can be configured to navigate to the Account Recs workflow page, but there's no data-level link (not even down to a specific reconciliation, let alone a shared due-date calc). So this isn't a gap in our setup — it's how the two solutions are architected.
 

We looked at writing a custom business rule to push Task Manager's close schedule into RCM's Close Date automatically, but decided against it — the Close Process Management schema isn't a documented integration point, it'd need re-validation on every upgrade, and since we only set the calendar once a year, the automation wasn't worth the maintenance risk. If your calendar changes frequently (ad hoc holiday shifts, many profiles that need to move in lockstep), that tradeoff might land differently — but for an annual setup, keeping them as two manually-synced anchors is simpler and safer.

Thanks!
Haritha

Terms & ConditionsAccessibility statement