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

ÃÛÌÒapp

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); })(); Collection of Funds From Grantor | ÃÛÌÒapp

ÃÛÌÒapp

Skip to main content

Collection of Funds From Grantor

ÃÛÌÒapp collects money for its sponsored projects in several ways, including advance payments, payments made on prearranged schedules, payments made on completion of project or sponsor's acceptance of certain project tasks, cost reimbursement of ÃÛÌÒapp prepared billings and other request for funds. The Gift and Grant Staff Accountant is responsible for preparing the billings and other requests for funds, depositing all funds received and for maintaining the accounts receivable for all billings and for performing the follow-up with any non-paying sponsors. 

All Federal Grant fund requests will be initiated by the Gift and Grant Staff Accountant on a quarterly basis. The PI will be notified once funds are received.

All State Grant fund requests will go through the Gift and Grant Staff Accountant. The PI will be notified when funds are requested and received.

Private Grants and Foundation Grants will be funded per agreement with funding organization. Gift and Grant Staff Accountant will be familiar with each agreement and request funds accordingly. The PI will be notified when funds are requested and received.

Loading...