, but this code // executes before the first paint, when

fb88

is not yet present. The // classes are added to so styling immediately reflects the current // toolbar state. The classes are removed after the toolbar completes // initialization. const classesToAdd = ['toolbar-loading', 'toolbar-anti-flicker']; if (toolbarState) { const { orientation, hasActiveTab, isFixed, activeTray, activeTabId, isOriented, userButtonMinWidth } = toolbarState; classesToAdd.push( orientation ? `toolbar-` + orientation + `` : 'toolbar-horizontal', ); if (hasActiveTab !== false) { classesToAdd.push('toolbar-tray-open'); } if (isFixed) { classesToAdd.push('toolbar-fixed'); } if (isOriented) { classesToAdd.push('toolbar-oriented'); } if (activeTray) { // These styles are added so the active tab/tray styles are present // immediately instead of "flickering" on as the toolbar initializes. In // instances where a tray is lazy loaded, these styles facilitate the // lazy loaded tray appearing gracefully and without reflow. const styleContent = ` .toolbar-loading #` + activeTabId + ` { background-image: linear-gradient(rgba(255, 255, 255, 0.25) 20%, transparent 200%); } .toolbar-loading #` + activeTabId + `-tray { display: block; box-shadow: -1px 0 5px 2px rgb(0 0 0 / 33%); border-right: 1px solid #aaa; background-color: #f5f5f5; z-index: 0; } .toolbar-loading.toolbar-vertical.toolbar-tray-open #` + activeTabId + `-tray { width: 15rem; height: 100vh; } .toolbar-loading.toolbar-horizontal :not(#` + activeTray + `) > .toolbar-lining {opacity: 0}`; const style = document.createElement('style'); style.textContent = styleContent; style.setAttribute('data-toolbar-anti-flicker-loading', true); document.querySelector('head').appendChild(style); if (userButtonMinWidth) { const userButtonStyle = document.createElement('style'); userButtonStyle.textContent = `#toolbar-item-user {min-width: ` + userButtonMinWidth +`px;}` document.querySelector('head').appendChild(userButtonStyle); } } } document.querySelector('html').classList.add(...classesToAdd); })(); Budgets & Guidance | Department of Education

fb88

|
|
|

Department of Education

Home → Funding → Budgets & Accounting → Budgets & Guidance → Budgets & Guidance

Budgets & Guidance

School Finance Budgets Web Banner

Card image cap

Warrant Articles

Card image cap

Tax Assessments

Card image cap

Budgets

��

Annual Budget Reporting
For the fiscal year��July��1 - June��30

Reporting Requirements
All School Administrative Units

Upload the following files to fb88 Education Financial System��(MEFS) Financial by August 15:
- ��Budget Revenue
- ��Budget Expenditure
Before submitting, check that all files:
- Contain data for all funds
- Contain revenue and expenditure transactions for all funds
- Are created for the full year budget under Quarter 1
Email the following to the Fiscal Compliance Specialist - denise.towers@maine.gov
- Warrant Articles
- Budget Meeting Minutes
- Voter declaration of the referendum (if required)
After submitting:
- Sign into fb88 Education Financial System and check file status:
  - If there are errors, resolve and resubmit
  - If the file is in approved status, complete the file submission by electronic certification
  - NOTE: Only file submissions in migrated status are considered received by fb88 DOE.

SADs, RSUs, CSDs

Submit the EF-M-46 in NEO

CTE Regions

Submit the EF-M-46V in NEO

��