, 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); })(); Payment Process Financial Services | ÃÛÌÒapp

ÃÛÌÒapp

Skip to main content

Payment Process

Payments to foreign nationals are complicated due to the interaction of immigration and tax laws. We must determine the category of payment to be made.

Wages

Wages paid to foreign nationals means cash compensation paid to the individual from which appropriate tax and other deductions are taken. This does not include other payments, such as housing or living allowances or reimbursements.

All foreign nationals appointed to payroll must obtain a U.S. social security number and complete the Foreign National Information Form so that ÃÛÌÒapp can analyze U.S. tax status and provide any exemptions that might apply. 

Business expenses

In order to treat a payment as a non-taxable reimbursed business expense, the visitor should be employed in a professional capacity in their home country (i.e. not a student) and the visitor should not be located at ÃÛÌÒapp for more than three months. If the visit exceeds three months, contact the Payroll Office for guidance.

ÃÛÌÒapp will reimburse the business expenses (transportation, meals, lodging) for short-term visitors as long as the voucher includes business purpose and original receipts supporting the expense(s) are included with the request. . Please email Accounts Payable at accountspayable@calvin.edu for additional information.

Honoraria

An honoraria should be used to pay an amount of money paid to an individual for services performed.

For a better understanding of forms needed for particular types of payment, please contact us at payroll@calvin.edu.

Questions?

For questions regarding payment to foreign nationals, please contact the Payroll office at payroll@calvin.edu.