{"id":2119,"date":"2026-08-07T08:54:56","date_gmt":"2026-08-07T13:54:56","guid":{"rendered":"https:\/\/www.mtsu.edu\/fusion\/?page_id=2119"},"modified":"2026-10-22T23:38:32","modified_gmt":"2026-10-23T04:38:32","slug":"freeze-dates","status":"publish","type":"page","link":"https:\/\/www.mtsu.edu\/fusion\/freeze-dates\/","title":{"rendered":"Freeze Dates"},"content":{"rendered":"\n
<\/div>\n\n\n\n

What Are Freeze Dates?<\/h2>\n\n\n\n

Freeze dates are planned milestones that temporarily pause specific Human Resources, Finance, and Payroll activities as MTSU prepares for the launch of True Blue Fusion on January 4, 2027. These pauses create a stable point in time for data to be moved from legacy systems into Oracle, allowing the project team to complete final conversion, validation, testing, and readiness activities before go-live. <\/p>\n\n\n\n

\n\n\n\n

Why Do Freeze Dates Matter?<\/h2>\n\n\n\n

Freeze dates help ensure that the information moving into Oracle is accurate, complete, and reliable. Without a freeze period, data could continue changing while it is being converted and tested, increasing the risk of errors and inconsistencies. By temporarily pausing selected transactions and updates, MTSU can protect data integrity, reduce implementation risk, complete final system testing, and prepare for a successful transition to Oracle. <\/p>\n\n\n\n

\n\n\n\n

How Will Freeze Dates Impact Me?<\/h2>\n\n\n\n

Activities that currently occur in Banner, PageUp, or other legacy systems will have deadlines or temporary restrictions before go-live. Depending on your role, this may affect actions such as submitting HR changes, updating employee information, creating job postings, processing financial transactions, approving invoices, or making payroll-related updates. The freeze schedule is designed to allow university operations to continue while ensuring that the data and processes supporting those operations are ready for launch in Oracle. Employees and departments should review upcoming freeze dates carefully and complete affected activities before the applicable deadlines. <\/p>\n\n\n\n

\n\n\n\n

Key Takeaway<\/h2>\n\n\n\n

Freeze dates are a normal and necessary part of every major ERP implementation. While certain activities may be temporarily paused, these planned milestones help ensure that True Blue Fusion launches with accurate data, stable processes, and the best possible experience for the MTSU community. <\/p>\n\n\n\n

\n\n\n\n

IMPORTANT: TENTATIVE DATES SUBJECT TO CHANGE<\/h4>\n\n\n\n

Unless otherwise noted, all dates are considered Close of Business (COB)<\/p>\n\n\n\n

\n
\n
\n<\/i>\n\n\n\n

HUMAN RESOURCES<\/h3>\n<\/div>\n\n\n\n
\n
\n
<\/span>
\n

JULY 24, 2026<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

Freeze department names and department numbers.<\/strong><\/p>\n\n\n\n

Changes to Department names, numbers, and any organization restructuring will be frozen during the transition period. No additions or changes will be permitted until Oracle go-live on January 4, at which time updates may be submitted through the new Oracle process.\u200b<\/p>\n<\/div>\n\n\n\n

\n
<\/span>
\n

SEPTEMBER 16, 2026<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

Deadline for the campus to submit position reclassification requests to HR.<\/strong><\/p>\n\n\n\n

Position reclassification requests will continue to follow the current process through September 16. A blackout period for all reclassification requests will be in effect from September 17 through January 3. Beginning January 4, managers may submit position reclassification requests using the new Oracle process.\u200b<\/p>\n<\/div>\n\n\n\n

\n
<\/span>
\n

OCTOBER 31, 2026<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

Deadline for HR to communicate the outcomes of position reclassification requests to employees and their supervisors.<\/strong><\/p>\n\n\n\n

HR will also communicate the effective dates for all approved reclassifications at this time.\u200b<\/p>\n<\/div>\n\n\n\n

\n
<\/span>
\n

NOVEMBER 2, 2026<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

Banner Production Employee Self Service Freeze related to Employee Personal Data.<\/strong><\/p>\n\n\n\n

MTSU will determine an interim process for employees to communicate to HR any personal data changes and how that will be entered in Banner (e.g., changes to address, name, phone, email, etc..)\u200b<\/p>\n<\/div>\n\n\n\n

\n
<\/span>
\n

NOVEMBER 7, 2026<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

Deadline for the campus to submit new job posting requests in PageUp.<\/strong><\/p>\n\n\n\n

This is the final day new staff job postings may be submitted in PageUp. Requests submitted after this date will not be approved. A job posting blackout period will be in effect from November 7 through January 3. Beginning January 4, all new job postings must be created in Oracle Recruiting Cloud (ORC).\u200b<\/p>\n<\/div>\n\n\n\n

\n
<\/span>
\n

NOVEMBER 23, 2026<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

Deadline for campus to submit EPAFs for HR data changes. \u200b<\/strong><\/p>\n\n\n\n

Only for HR transactions that need to be processed in Banner before go-live. Future dated changes (i.e. spring-semester staffing changes) will be handled after employees are converted into Oracle.<\/p>\n<\/div>\n\n\n\n

\n
<\/span>
\n

DECEMBER 7, 2026<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

Deadline for applicants to apply through PageUp.<\/strong><\/p>\n\n\n\n

<\/strong>MTSU will close all job postings in PageUp, and no additional applications will be accepted after this date. Any remaining recruiting activities for existing PageUp job postings including candidate review, interviews, selection, and offer cards, will continue to be managed in PageUp.\u200b<\/p>\n\n\n\n

If a department wishes to extend its search and accept additional applicants, the PageUp job posting will be closed and reposted in Oracle Recruiting Cloud (ORC) on January 4. Because this will be a new posting in ORC, no recruiting data from the original PageUp posting will be converted into Oracle Recruiting Cloud.\u200b<\/p>\n\n\n\n

Deadline to complete employee hires.<\/strong><\/p>\n\n\n\n

This is the final day to complete and submit employee hires before the transition period. Any hires not submitted by this date will not be permitted to start until January 4th or later.\u200b<\/p>\n\n\n\n

Deadline to update labor distribution costing. <\/strong><\/p>\n\n\n\n

This is the final day to submit or update labor distribution funding changes in Banner. Any new or revised costing updates after this date must be entered in Oracle.\u200b<\/p>\n<\/div>\n\n\n\n

\n
<\/span>
\n

DECEMBER 8, 2026 – JANUARY 4, 2027<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

Hiring Freeze<\/strong><\/p>\n\n\n\n

No employees permitted to start between December 8th and January 3rd \u200b<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

\n
\n<\/i>\n\n\n\n

FINANCE<\/h3>\n<\/div>\n\n\n\n
\n
\n
<\/span>
\n

NOVEMBER 2, 2026<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

CoA Freeze.<\/strong><\/p>\n\n\n\n

Last day for campus to request new indexes.\u200b<\/p>\n<\/div>\n\n\n\n

\n
<\/span>
\n

NOVEMBER 16, 2026<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

Deadline for Supplier Entry.<\/strong><\/p>\n\n\n\n

Last day to create or update supplier records in the legacy system.\u200b<\/p>\n\n\n\n

Deadline for Contract and Requisition Entry.<\/strong><\/p>\n\n\n\n

Final day to submit contracts and requisitions through MT Source for processing in the legacy system.\u200b<\/p>\n\n\n\n

Deadline to submit travel authorizations.<\/strong><\/p>\n\n\n\n

(Dynamic Forms). Last day to submit travel authorizations through Dynamic Forms; submissions after this date must be entered in Oracle.\u200b<\/p>\n\n\n\n

Deadline for Sponsored Awards and Faculty Funds Entry.<\/strong><\/p>\n\n\n\n

Final day to create or update sponsored awards and faculty fund information in the legacy system. After this date, a backlog of awards and Faculty funds will be created for manual entry in Oracle after January 4.\u200b<\/p>\n\n\n\n

Deadline to create\/modify awards and Capital Projects.<\/strong><\/p>\n\n\n\n

Last day to create or modify capital project awards before the transition to Oracle. After this date, a backlog of modifications and Capital Projects will be created for manual entry in Oracle after January 4.\u200b<\/p>\n\n\n\n

Deadline for Customer Creation.<\/strong><\/p>\n\n\n\n

Last day to create customers in Banner. Any new customers required past this date will need to be entered into Oracle after January 4. \u200b<\/p>\n<\/div>\n\n\n\n

\n
<\/span>
\n

DECEMBER 7, 2026<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

Budget Revisions<\/strong>.<\/p>\n\n\n\n

Deadline to submit 2027 budget revisions.<\/p>\n\n\n\n

Cutoff for pcard November statement transactions.<\/strong><\/p>\n\n\n\n

Last day for November statement period transactions to be completed and approved in the legacy system.<\/p>\n\n\n\n

*Card transactions that post 11\/28\/2026 or after will be completed in Oracle after the go live date.<\/p>\n<\/div>\n\n\n\n

\n
<\/span>
\n

DECEMBER 11, 2026<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

Last day for travel to receive payment in 2026.<\/strong><\/p>\n\n\n\n

Final date for travel expenses to be submitted and processed for payment during 2026.\u200b<\/p>\n\n\n\n

Deadline to submit AP invoices.<\/strong><\/p>\n\n\n\n

This is the final day to submit invoices for processing in the legacy system. Invoices submitted after December 11 must be entered in Oracle. An invoice processing freeze will be in effect from December 12 through January 3. Beginning January 4, all remaining invoices must be created and processed in Oracle.\u200b<\/p>\n\n\n\n

Deadline to submit AR invoices.<\/strong> \u200b<\/p>\n\n\n\n

Deadline to submit expenses in Chrome River.<\/strong><\/p>\n\n\n\n

Final day to submit expense reports in Chrome River for processing before the Oracle transition.\u200b<\/p>\n\n\n\n

Deadline to submit expenses in Dynamic Forms.<\/strong> <\/p>\n\n\n\n

Last day to submit expense-related requests through Dynamic Forms before Oracle go-live.\u200b<\/p>\n\n\n\n

Deadline to Return Cash Advances.<\/strong> <\/p>\n\n\n\n

Last day to return cash advances to MTSU on all associated expense reports.<\/em> \u200b<\/p>\n<\/div>\n\n\n\n

\n
<\/span>
\n

DECEMBER 18, 2026<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

Deadline for all invoice approvals in Banner Production. <\/strong><\/p>\n\n\n\n

All invoices must receive final approval by 4:30 p.m. on this date. Departments will be notified if any invoices are still pending approval after 4:30 p.m. They will be closed in Banner and must be recreated and resubmitted in Oracle.\u200b<\/p>\n<\/div>\n\n\n\n

\n
<\/span>
\n

DECEMBER 23, 2026<\/strong><\/p>\n<\/div><\/div>\n\n\n\n

Last expense payment run in Banner.<\/strong><\/p>\n\n\n\n

Final scheduled expense reimbursement payment processed through Banner.\u200b<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n\n

<\/div>\n","protected":false},"excerpt":{"rendered":"

What Are Freeze Dates? Freeze dates are planned milestones that temporarily pause specific Human Resources, Finance, and Payroll activities as MTSU prepares for the launch of True Blue Fusion on January 4, 2027. These pauses create a stable point in time for data to be moved from legacy systems into Oracle, allowing the project team […]<\/p>\n","protected":false},"author":4,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-2119","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.mtsu.edu\/fusion\/wp-json\/wp\/v2\/pages\/2119","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mtsu.edu\/fusion\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.mtsu.edu\/fusion\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.mtsu.edu\/fusion\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mtsu.edu\/fusion\/wp-json\/wp\/v2\/comments?post=2119"}],"version-history":[{"count":3,"href":"https:\/\/www.mtsu.edu\/fusion\/wp-json\/wp\/v2\/pages\/2119\/revisions"}],"predecessor-version":[{"id":3024,"href":"https:\/\/www.mtsu.edu\/fusion\/wp-json\/wp\/v2\/pages\/2119\/revisions\/3024"}],"wp:attachment":[{"href":"https:\/\/www.mtsu.edu\/fusion\/wp-json\/wp\/v2\/media?parent=2119"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}