The My Corporate Card is a personal-liability credit card that can be used to pay for UW business-related expenses. Purchases made using My Corporate Card appear in the user’s My Wallet in e-Reimbursement. This procedure details how to use e-Reimbursement to account for your My Corporate Card activity.
The My Corporate Card is a personal-liability credit card that can be used to pay for UW business-related expenses. Purchases made using My Corporate Card appear in the user’s My Wallet in e-Reimbursement. This procedure details how to use e-Reimbursement to account for your My Corporate Card activity.
Click the Expenses tile. Within the Expenses tile, there are three places to access your My Wallet activity:
Add Quick Expense tile
All My Corporate Card expenses which have not been accounted for on an expense report are shown.
This is the only place the Expense Type of a Corporate Card expense can be modified.
Users can add additional expenses to My Wallet using the plus sign icon. Users can manually add Corporate Card, P-Card, or Personal Fund charges to My Wallet which can be accessed when creating an expense report.
Users can delete My Wallet transactions using the trash can icon.
My Wallet tile – this tile is functionally similar to Add Quick Expense except users cannot modify Expense Types here.
Expense History tile – this tile shows Corporate Card expenses which have been accounted for on previously-created expense reports.
Accounting for Corporate Card expenses in e-Reimbursement
My Wallet transactions are imported into the expense report using the Add from My Wallet option on the dropdown list (Option i below) on the General Information page or the wallet icon on the Expense Entry page (Option ii below); click images to enlarge:
Users may also manually enter My Corporate Card transactions in an expense report by selecting “US Bank Corporate Card” as the payment type.
Payment
My Corporate Card expenses – whether imported into an expense report from My Wallet or manually entered – are paid directly to U.S. Bank upon approval of the associated expense report.
To avoid credit balances on the Corporate Card, cardholders must make efforts to avoid duplicate or incorrect payments made to US Bank.
Expense report – contains a categorized and itemized list of expenses that were made on behalf of University of Wisconsin–Madison. This report helps the employer or finance team determine what money was spent, what was purchased, and how much of the expenditure is approved for reimbursement
e-Reimbursement – the Expenses module of the Shared Financial System (SFS), used to create, submit, and approve expense reimbursement claims.
My Corporate Card – individual-liability credit card that can be used for travel and non-travel expenses.
Payments are processed within 3-5 business days of an Expense Reimbursement’s final approval. Employees who receive their paychecks via direct deposit will receive their reimbursement payments via direct deposit as well. The payment will be a separate deposit from the employee’s regular paycheck. Non-employees and employees who do not have direct deposit will receive a check in the mail.
Procedure #3024.3; Rev.: 1 (Effective May 8, 2017) Related Policy:UW-3024 Expense Reimbursement Policy Functional Owner: Accounting Services, Division of Business Services Contact: Expense Reimbursement Program Manager – Allie Watters, expensereimbursement@bussvc.wisc.edu, (608) 263-3525
Payments are processed within 3-5 business days of an expense report’s final approval. Employees who receive their paychecks via direct deposit will receive their reimbursement payments via direct deposit as well. The payment will be a separate deposit from the employee’s regular paycheck. Non-employees and employees who do not have direct deposit will receive a check in the mail.
Expand the View TER’s, TA’s and CA’s menu, then select View Expense Report in the links panel along the left side.
Find the correct expense report by entering the report ID, description, employee ID, or employee name (name searches in e-Reimbursement follow the LastName,FirstName convention, no spaces). This search will provide a read-only view of an expense report.
Check that the status (next to the report ID number in the top middle of the screen) is Paid. If not paid, view the Approval History at the bottom of the page to see where the expense report is in the approval process.
Search for Payment Details:
Using the same navigation links on the left side of the page, expand the Void/Reissue Payment menu, then select the View Payment History link.
Search by employee ID or name. Select the proper expense report from the search results. If there is single search result will automatically take you to the Employee Payment History page.
Payment Reference – for check payments, this will be the check number. This is needed when filling out a Check Action Form.
Payment Amount – the amount the traveler was reimbursed. This may differ from the amount seen elsewhere in e-Reimbursement, which may include items paid on the Purchasing Card or Corporate Card. This amount may include multiple expense reports if they were approved on the same day.
Payment Method – will be either “ACH” for direct deposit payments or “System Check” for paper check payments.
Payment Date – payment will be direct deposited or mailed within 3-5 business days of this date.
Payee Address – this link will display the address the check was sent to.
If payment was made by ACH, the traveler should review their bank history for a deposit that matches the information shown in the Employee Payment History search. Reimbursement payments will post from UWMSN_TRVL_ACH.
Note: If multiple expense reports are paid on the same date, a cumulative ACH will be sent. The traveler should look for the cumulative total of the expense reports paid in their bank history. Individual payments for each report will not be visible.
Reissuing Payment
Payments made via check can be cancelled and reissued by filling out a Check Action Form. To allow time for the check to arrive, Check Action Forms can only be submitted at least 30 days after the payment date.
Traveler (employee)/Claimant/Recipient – the person receiving reimbursement. Employees are responsible for submitting their own expense reports and following all applicable UW travel policies. An employee may assign an alternate to create and modify an expense report on their behalf, but the employee is ultimately responsible for submitting their own expense reports.
Approver: Upon submission, expense report are first reviewed by an approver. Approvers are responsible for reviewing supporting documentation, reviewing expense report for policy compliance, and reviewing funding being charged.
Auditor: Expense reports are reviewed by an auditor after the approver. Auditors are responsible for reviewing expense reports for policy compliance.
Alternates can create Expense Reimbursements on behalf of employees and non-employees and can submit Expense Reimbursements on behalf of non-employees and recently-terminated employees. Current employees must submit their own Expense Reimbursements, even if they were created by an Alternate.
Procedure #3024.2; Rev.: 1 (Effective May 8, 2017) Related Policy:UW-3024 Expense Reimbursement Policy Functional Owner: Accounting Services, Division of Business Services Contact: Expense Reimbursement Program Manager – Allie Watters, expensereimbursement@bussvc.wisc.edu, (608) 263-3525
Alternates can create expense reports on behalf of employees and non-employees and can submit expense reports on behalf of non-employees and recently-terminated employees. Current employees must submit their own expense reports, even if they were created by an alternate.
Current employees are responsible for adding and deleting their own alternates. The UW–Madison Travel Office will not assign alternates for current employees.
Employees who seek reimbursement for out-of-pocket or Corporate Card expenses; alternates who prepare expense reports in the Shared Financial Systems (SFS).
Click the Delegate Entry Authority link in the links panel along the lower right-hand side of the page.
Click the plus sign to add an additional row.
Enter the alternate’s employee ID number in the Authorized User ID field. If you do not know the employee ID, click the magnifying glass next to the blank field, then click on Advanced Lookup. Enter the alternate’s last name in the Description field. Locate the alternate and click on their name.
The Authorization Level should be “Edit.” If an employee chooses “Edit & Submit”, it will revert to “Edit.”
For recently terminated employees: Terminated employees can be reimbursed using their employee ID for up to 365 days after their termination date. Alternates must contact the UW-Madison Travel Office to be granted access to submit expense reports for recently-terminated employees.
Traveler (employee)/Claimant/Recipient – the person receiving reimbursement. Employees are responsible for submitting their own expense reports in a timely fashion and following all applicable UW travel policies. An employee may assign an alternate to create and modify an expense report on their behalf, but the employee is ultimately responsible for submitting their own expense reports.
Alternate – responsible for creating and submitting expense reports on behalf of others. Employees who seek reimbursement can assign an alternate to create and modify expense reports for them, but the employee must submit their own. Expense reports for non-employees or recently-terminated employees are created and submitted by alternates.
e-Reimbursement – the Expenses module of the Shared Financial System (SFS), used to create, submit, and approve expense report claims.
Non-employee – an individual who does not have an active appointment at the University. Non-employees can be reimbursed for travel-related expenses through e-Reimbursement.
Recently-terminated employee – an employee whose last active appointment ended less than 365 days ago. Expense reports for recently-terminated employees can be submitted using their employee ID for up to 365 days after termination. To add an alternate for a recently-terminated employee, contact Accounting Services.
All payments made to employees and non-employees for reimbursement of out-of-pocket expenses are initiated in e-Reimbursement, the Expenses module of the Shared Financial System (SFS). Expense reports are reviewed by an approver and an auditor prior to payment. Approval routing is based on the Department ID referenced in the funding allocation for each expense line.
Employees may delegate an alternate to create and modify expense reports on their behalf. It is the employee’s responsibility to ensure expense reports are submitted on time and in compliance with policy.
This document details the required procedures for submitting an expense report. For a complete how-to guide, visit the Expense Reimbursement website.
To get started, employees/alternates must sign into the Shared Financial System (SFS), click the Expenses tile, then click Create Expense Report. If acting as an alternate for another traveler, click the drop-down arrow next to the employee’s name in the upper left corner of the screen, then select Change Employee. Select the appropriate employee from the resulting list and proceed to the next step.
General Information: The first page is the General Information page, also commonly referred to as the header information. Information entered here applies to the entire expense report.
Business Purpose – Choose the one that best describes the reimbursement. See Appendix A below for definitions and further details on business purposes.
Default Location – Primary location of your trip.
Choose your headquarter city for non-travel expense report.
Locations may be listed by city or county.
For international locations not listed by city or county, select ‘COUNTRY NAME, OTHER LOCATIONS’. Do not select the nearest big city if the trip was not actually to that city.
Reference – Select In-State, Out-of-State, or Foreign.
This is based on where the destination is in relation to the traveler’s headquarter city (for example, if someone headquartered in Atlanta, GA, traveled to Madison, the Reference would be ‘Out-of-State’).
For non-travel expense report, select ‘Not a Travel Related report’.
Date of departure/return – Dates of UW business travel. Do not include personal vacation days in these dates.
Attachments
Receipts are required to be electronically attached to the expense report.
In addition, travelers/alternates must attach additional documentation required for an approver/auditor to fully review each claim (e.g., conference agenda, email correspondence explaining unusual circumstances, map to support mileage claim).
Do not attach anything with protected or confidential information.
Redact credit card and social security numbers.
When reimbursing research subjects, it may be necessary to redact anything with details of the research being done. Map printouts for research subjects may use a nearby location instead of the research subject’s home address.
If no other options are available, hard copies may be saved instead of electronic attachments in order to protect a recipient’s confidentiality. This must be noted in the expense report.
Justification – Notes are added by the traveler or alternate to provide the details of the reimbursement.
Every expense report must have at least one note. That note must include a sufficient business purpose to justify the reimbursement. Any personal time added to the trip must be clearly indicated in the business purpose to validate that only appropriate UW–Madison business expenses are being claimed.
Spell out all acronyms.
Additional notes may be added as needed.
Expense details: This section is where users enter the details of their expenses.
Choose Add expense lines from the Expense Report Action drop-down menu. Users may also choose to add lines from My Wallet or to copy an existing expense report.
Choose the appropriate Expense Type for the expense. See Appendix B below for definitions and further details of expense types.
Payment Type: Choose the appropriate payment type for each expense line:
Personal Funds – Out-of-pocket expenses for which the traveler will be reimbursed.
Prepaid Purchasing Card – Expenses paid on the Purchasing Card. The traveler will not be reimbursed for these expenses. It is not required to include expense lines for prepaid items.
It is recommended that travelers manually convert foreign currency amounts and enter only US Dollars in this field.
For rate-based Expense Types (e.g. Meals and Incidental Expense, Mileage), this field cannot be manually modified.
Non-Reimbursable
Mark an expense non-reimbursable.
This can be used for non-business-related expenses and for expenses that were paid via an outside source (e.g. airfare paid by the host conference).
Red Flags– All red flag error messages must be resolved before an expense report can be submitted. Examples include:
An invalid funding string.
Required information is missing.
Airfare ticket number is a duplicate of a previously-created expense report.
Review and Submit – Alternates and travelers must ensure the accuracy of the expense report prior to submission.
Expense Report Summary – ensure the breakdown between reimbursable, non-reimbursable, Corporate Card, and Prepaid Expenses is accurate. Modify the payment types on individual expense lines if necessary.
Additional Information – If there are Cash Advances or Travel Authorizations available, associate them with the expense report here. For more information on working with Cash Advances, see UW-3025 Cash Advances.
Submit
Current UW employees must submit their own expense reports.
Alternates can submit expense report on behalf of non-employees and recently-terminated employees.
Traveler (employee)/Claimant/Recipient: the person receiving reimbursement. Employees are responsible for submitting their own expense report and following all applicable UW travel policies. An employee may assign an alternate to create and modify an expense report on their behalf, but the employee is ultimately responsible for submitting their own expense reports.
Alternate: responsible for creating and submitting expense report on behalf of others. Employees who seek reimbursement can assign an alternate to create and modify expense report for them, but the employee must submit their own. Expense reports for non-employees or recently-terminated employees are created and submitted by alternates.
Approver: Upon submission, expense report are first reviewed by an approver. Approvers are responsible for reviewing supporting documentation, reviewing expense report for policy compliance, and reviewing funding being charged.
Auditor: Expense reports are reviewed by an auditor after the approver. Auditors are responsible for reviewing expense reports for policy compliance.
e-Reimbursement: the Expenses module of the Shared Financial System (SFS), used to create, submit, and approve expense report/reimbursement claims.
Purchasing Card: University-liability credit card that can be used for travel and non-travel expenses.
Corporate Card: individual-liability credit card that can be used for travel and non-travel expenses.
Business Purpose: When using University funds or requesting a reimbursement from University funds, documentation of a clear business purpose is required so an approver, auditor, site manager, and/or post-payment auditor may reasonably conclude and agree the expenditure is an appropriate business expense. The business purpose, which is defined as one that supports or advances the goals, objectives and mission of the University, adequately describes the expense as a necessary, reasonable, and appropriate business expense for the University. All expenses must support a University business purpose.
Non-employee: an individual who does not have an active appointment at the University. Non-employees can be reimbursed for travel-related expenses through e-Reimbursement.
Business – Expenses for routine business travel not better classified in another category.
Conference – Expenses incurred to attend or host a conference.
Fundraising – Expenses incurred for University fundraising.
Job candidate hosting – Expenses incurred for hosting job candidates.
Local travel – Expenses incurred when traveling within the headquarter city or surrounding area. Expenses can be accumulated and filed weekly, bi-weekly or monthly.
Non-Travel – Expenses incurred on the Corporate Card or out-of-pocket for low-dollar purchases made in compliance with UW purchasing policies.
Professional development – Expenses incurred by employees for education or job/professional trainings.
Recruiting – Expenses incurred for recruiting employees and students to the University.
Relocation – Expenses incurred for employee relocation.
Research – Expenses incurred for research or research-related activities including fieldwork or faculty presentation of papers.
Student travel – Expenses incurred by students for business or educational travel. Does not include study abroad or International Education programs. Employee expenses to accompany students select from other business purposes.
Study abroad – Expenses incurred by travelers (faculty or students) for study abroad or other international education programs.
Team travel – Expenses incurred for sport team travel.
Expense types
Air – Baggage Fees – airline baggage or equipment fees.
Description – if additional baggage beyond the first piece and/or overweight/oversized baggage is claimed, provide justification.
Account codes 2800, 2801, 2802.
Airfare – commercial coach/economy including allowable charges for seat assignments.
Description – if claiming a related fee, provide a justification.
Merchant – select the merchant from the preferred drop-down menu or enter the merchant name in the non-preferred field.
Ticket Number – a unique ticket number is required.
Account codes 2800, 2801, 2802.
Airfare Change/Cancel Penalty – Charge imposed by the airline to change, re-issue or cancel tickets.
Description – provide an explanation of the circumstances.
Merchant – select the merchant from the preferred drop-down menu or enter the merchant name in the non-preferred field.
Account codes 2800, 2801, 2802.
Athletic Pre/Post Game – for use by Athletics only.
Athletics Team Meals – for use by Athletics only.
Day Trip Meal Allowance – meal costs including tax and tip in connection with travel that does not include an overnight stay. The amount is based on the per diem rate and cannot be manually modified.
Account codes 2863 and 2864.
E-Re Estimated Withholding – withholding of estimated taxes. It is required to be used with any Relocation expenses. It must be entered as a negative number and will reduce the net reimbursement.
It can also be used for withholding of taxes for expense reports submitted over 90 days and for tuition reimbursement in excess of allowable limits.
It will require a credit reference to be entered (“Estimated tax withholding” is sufficient).
Account code 7060
Event – Audio Visual Equipment – costs for the rental of audio visual equipment or related technologies for the purpose of hosting a University-sponsored event, Official Function, or educational program such as a conference, reception, workshop, etc., with multiple attendees from both inside and outside the University.
Description – provide a business justification for expenses incurred and specify what type of event was held. Indicate whether or not a fee was collected from attendees.
Merchant – enter the name of the merchant.
Account code 2894.
Event – Catering – cost of food/beverage, service fees, gratuities and/or delivery fees related to hosting a University sponsored event, Official Function, or educational program such as a conference, reception, workshop, etc., with multiple attendees from both inside and outside the University.
Description – provide a business justification for event expenses incurred and specify what type of event was held (reception, conference, etc.) If a meal was served, indicate breakfast, lunch or dinner. Indicate whether or not a fee was collected from attendees.
Merchant – enter the name of the merchant.
Number of People – enter the number of attendees.
Add Additional Attendees – enter the names and affiliations of the attendees. For large events, an attendee list can be attached to the expense report instead.
Account code 2893.
Event – Meeting Space – costs for meeting space or room rental for the purpose of hosting a University sponsored event, Official Function, or educational program such as a conference, reception, workshop, etc., with multiple attendees from both inside and outside the University.
Description – provide a business justification for event expenses incurred and specify what type of event was held (reception, conference, etc.) If a meal was served, indicate breakfast, lunch or dinner. Indicate whether or not a fee was collected from attendees.
Merchant – enter the name of the merchant.
Account code 2895.
Gas for Vehicle Rental/Fleet – purchase of gasoline for rental vehicles or fleet vehicles when State/UW gas card is not accepted.
Description – provide a purpose for the gasoline purchase and indicate the type of vehicle that was used (rental or fleet). For Fleet, explain why the provided fuel card was not used.
Account codes 2810, 2811, and 2812.
Lodging – Group – lodging accommodations for multiple business travelers who share a room and the reimbursement is being claimed on one expense report.
Description – provide the names and affiliations of all individuals included in the lodging payment.
Number of Nights – enter the number of nights stayed.
Merchant – select the merchant from the preferred drop-down menu or enter the merchant name in the non-preferred field.
How Many People – the number of UW business travelers included in the amount reported.
Account codes 2850, 2851, and 2852.
Lodging – Individual – lodging accommodations for individual lodging expenses, including a shared room for which the traveler is claiming only their portion of the charge.
Number of nights – enter the number of nights stayed.
Merchant – select the merchant from the preferred drop-down menu or enter the merchant name in the non-preferred field.
Account codes 2850, 2851, and 2852.
Lodging – Student – track any student lodging expenses for compliance with the Clery Act. This new accounting code should make Clery Act reporting much more efficient.
Description – enter the address of the lodging property.
Number of nights – enter the number of nights stayed.
Merchant – type the name of the lodging property.
How many people – enter the number of students staying in the room.
Expense location – enter the location of the lodging property.
Account codes 2853, 2854, 2855. SFS will automatically select the proper account code (in-state, out-of-state, foreign) based on the REFERENCE selection in the header of the expense report (in-state, out-of-state, foreign).
Meal and Incidental Per Diem – per diem allowance reimbursed to travelers for overnight travel based on location of stay.
Amount – the amount is based on the location, date, and any selected deductions.
Location – enter the location the expense was incurred. When traveling to the destination, this is the location the traveler stayed that night. When returning from the destination, this is the location the traveler stayed the night before.
Per Diem Deductions – select first/last day for first and last day of travel and indicate any meals provided to the traveler (ex: as part of a registration fee).
Account codes 2860, 2861, and 2862.
Meals – Hosted – meal purchased for a group and claimed by a single individual.
Description – provide a business purpose for the purchase and indicate which meal was served (breakfast, lunch or dinner).
How Many People – enter the number of attendees.
Add Additional Attendees – enter the names and affiliations of the attendees. For large events, an attendee list can be attached to the expense report instead.
Account codes 2860, 2861, and 2862.
Mileage – reimbursement for use of a personal vehicle. Do not use this expense type for vehicle rentals or fleet vehicles.
Description – enter information used to determine Transportation ID. Include addresses of originating/destination locations and any additional stops. For situations where privacy is a concern, the exact address is not required.
Transportation ID
Mileage – enter the roundtrip mileage. The amount is automatically calculated based on the rate and the number of miles. The amount cannot be manually modified.
Account codes 2830, 2831, and 2832.
Misc. – Purchases/Supplies – best judgment UW-Madison business-related purchases ($5,000 or less) such as books, copy charges, shipping, etc.
Description – provide a description of the purchase and a UW-Madison business purpose.
Parking – parking charges incurred while conducting UW-Madison business.
Description – enter a reason for the expense and, if applicable, the number of days parked at the location.
Account codes 2870, 2871, and 2872.
Registration Fee – fee charged to attend an event such as a conference, workshop, seminar, training or meeting.
Description – provide the name of the event and a UW-Madison business purpose and identify what is included (meals, etc.) in the fee.
Account codes 2840, 2841, and 2842.
Relocation – Stipend – an Employee Relocation Award provided to cover some or all of an employee’s moving expenses.
Originating Location – the location the traveler is relocating from.
Expense Location – the location the traveler is relocating to.
Account code 2884.
Taxi/Subway/City Bus, etc. – local transportation charges for taxi, shuttle, city bus, ferry, subway, ride sharing services, etc. including tip.
Description – indicate the type of transportation used, the originating location and destination and a business purpose for the trip.
Account codes 2820, 2821, and 2822.
Train/Bus/Other Long Distance – long-distance transportation charges (non-airfare) such as a bus, train, etc. including tip.
Description – indicate the type of transportation used, the originating location and destination and a business purpose for the trip.
Account codes 2820, 2821, and 2822.
Training/Dev-Job –reimbursements to employees for costs related to job-related training not classified as tuition.
Description – indicate the name of the course taken.
Non-Preferred Merchant – enter the name of the merchant.
Account code 2184.
Travel Agency Service Fee – airfare ticket booking-related travel agency service fees.
Travel miscellaneous – allowable travel-related expenses not identified by our specific expense type or included as part of M&IE per diem (tolls, internet, visa fees, currency conversion fees, etc.)
Description – provide a description of the expense and a UW-Madison business purpose.
Account codes 2870, 2871, and 2872.
Travel reduction – reduces the amount of the expense report to a fixed dollar/budget amount for an expense line. Travel reductions cannot be entered by travelers/Alternates; they must be entered by Approvers.
Tuition/Training-Career – tuition and training fees related to taking a class or course, on a UW campus or other accredited University for the purpose of meeting the minimal educational requirements for a job or will qualify the employee for a new trade or business.
Description – indicate the name of the course taken and whether the course is for graduate or undergraduate credit.
Non-Preferred Merchant – enter the name of the merchant.
Account code 2180.
Vehicle rental – cost of renting a vehicle to conduct UW business.
Description – enter a business purpose for the use of a rental vehicle. Provide a justification if a non-preferred vendor was used.
Merchant – select the merchant from the preferred drop-down menu or enter the merchant name in the non-preferred field.
Feb. 26, 2020 – added E-Re Estimated Withholding Expense Type.
Jan. 19, 2021 – Updated Procedure Number to 3024.1 from 320.1.
Oct. 4, 2023 – Added Lodging – Student section. Removed Relocation – Direct Moving Costs and Relocation – Temporary Lodging sections.
March 15, 2024 – Clarification added that justification note must indicate any personal time added, to validate only business expenses are being claimed.
January 31, 2025 – Travel Agency Services Fees definition updated.
Purchasing card site managers are responsible for reviewing purchasing card activity and identifying non-compliance. Examples of non- compliance include using the purchasing card for personal/non-UW business-related purchases, inappropriately using University funds, serial purchasing, and failure to provide required supporting documentation. When a site manager identifies non-compliant use of a purchasing card, the following procedure should be referenced. Non-compliance must be addressed within the 30-day transaction reconciliation requirement.
Non-Compliance Procedure: For audit purposes, all non-compliance identification, acknowledgement, and follow-up activity must be documented with the non-compliant transaction in the Purchasing Card Module of the Shared Financial System (SFS). If non-compliance is identified, the site manager must complete the following steps:
If the compliance issue can be resolved by sending the purchasing card transaction back to the cardholder for further information and verification within the Purchasing Card Module (e.g., expanding on a previously provided business purpose, attaching additional required supporting documentation, documenting an attempt to recover sales tax paid in error), enter a request in the Comment field, change the status of the transaction to Staged, and click Save. Wait for the cardholder to re-verify the transaction, review the supporting documentation, and approve as appropriate. Note:This exchange between the site manager and the cardholder may take place outside of SFS (e.g., via email); however, it is recommended communications are attached to the transaction or summarized in the Comment field for audit purposes.
If the compliance issue cannot be corrected within the Purchasing Card Module, but follow-up activity is occurring outside of the module (e.g., reimbursing the UW for a personal/non-compliant expense, cardholder acknowledgment of policy requirements for future purchasing activity), complete the Purchasing Card Non-Compliant Transaction Acknowledgement Form and route to the cardholder for review, acknowledgment, and approval. The signed form must be attached to the transaction in the Purchasing Card Module prior to approval.
Cardholder: Responsible for responding to site manager requests to ensure compliance with purchasing card policy and procedure.
Site manager: Responsible for identifying non-compliance with purchasing card policy and procedure, notifying the cardholder, and ensuring transactions as reconciled in accordance with policy.
Cardholder: the individual who holds a purchasing card and is responsible for the card and use of it.
Non-compliance: any action or purchase which conflicts with purchasing card policy or procedure.
Site manager: the individual who manages purchasing cards at the departmental or divisional level.
Purchasing Card Non-Compliance Transaction Acknowledgement Form: A form completed and attached to a purchasing card transaction to acknowledge non-compliance and how it was addressed.
The UW-Madison My Corporate Card is an individual-liability VISA card issued by U.S. Bank to a UW-Madison employee for business-use only. The Card Program Office in the Division of Business Services administers the My Corporate Card Program.
Procedure # 3014.1; Rev.:1 (Effective July 1, 2025) Related Policy:UW-3014 Shared Liability Card Policy Functional Owner: Accounting Services, Division of Business Services Contact: Credit Card Program Manager: (608) 262-3300, meghann.grove@wisc.edu
The UW–Madison Shared Liability Card, or Corporate Card, is a shared-liability VISA card issued by U.S. Bank to a UW–Madison employee for business use only. The Travel and Card Team in the Division of Business Services administers the Shared Liability Card Program. Procedural details related to Shared Liability Card application, activation, registration, use and account management are outlined below.
Training: Training is not required to obtain a Shared Liability Card; however, applicants are encouraged to complete Travel Policy Training.
Card application: An employee applies for a Shared Liability Card by submitting the Shared Liability Card Request form in Workday.
Login to Workday.
In the Workday Search bar, enter “Create Request”. Click on the Create Request task.
In the Request Type field, enter “Shared Liability Card Request” and hit Enter.
Click OK.
Complete the request form and click Submit. The form will route automatically for required approvals.
Approval process:
Manager approval: The applicant’s manager reviews and approves the request in their Workday My Tasks inbox.
Credit Card Program Administrator approval: The Credit Card Administrator reviews the request and confirms whether the applicant is eligible to receive a Shared Liability Card. If the applicant is ineligible, the Card Program Administrator notifies the applicant and their manager. If the applicant is eligible and has completed the required training, the Credit Card Administrator approves the request, and the card is ordered through U.S. Bank via integration with Workday.
Card distribution: U.S. Bank mails the Shared Liability Card directly to the applicant at the address indicated on Shared Liability Card Request.
Card activation: Shared Liability Cards must be activated prior to use. Cardholders may activate online (via U.S. Bank) or by calling U.S. Bank Customer Service at (800) 344-5696 and following the automated prompts. The cardholder must also sign the back of the card.
Access Online registration: Registration provides a Shared Liability Cardholder with online access to account information, activity and billing statements. To register, the cardholder follows these steps:
Reporting a Lost/Stolen Card: To report a lost/stolen card to U.S. Bank, the cardholder must contact U.S. Bank Customer Service at (800) 344-5696.
Reporting fraud to U.S. Bank: To report fraudulent activity on a Shared Liability Card, the cardholder must contact the U.S. Bank Fraud Prevention Unit at (800) 523-9078. Fraudulent transactions and subsequent credits must be reconciled. If possible, it is recommended to reconcile them on the same expense report.
Expense Item: Select the UW Credit Card Fraud Expense Item.
Memo: Use the Memo field to describe action taken to report the fraud to U.S. Bank.
Funding: Enter Program PG000023979.
Supporting Documentation: Attach any relevant supporting documentation or simply create an attachment acknowledging the fraudulent transaction and any actions taken.
Shared Liability Card Payment: Shared Liability Card account balances can be paid directly by the cardholder or by the University:
Personal Payments: Personal payments can be made via personal check by remitting a payment with the U.S. Bank monthly statement or electronically via Access Online. Transactions paid personally must be marked as “Personal Expense” on a Workday Expense Report.
University Payments: Shared Liability Cardholders may opt to have the University pay U.S. Bank on their behalf for reimbursable Shared Liability Card expenses via Workday.
Delinquent payment status: U.S. Bank takes the following actions when a Shared Liability Card account becomes past due:
60-Days past due: Account is suspended and moved into M9 (Delinquent) status. The account will automatically decline all authorizations and reissue. The account is automatically reinstated by U.S. Bank when the past due balance has been paid.
90-Days past due: The account is moved into S1 (Cancellation of Cardholder Privileges) status. The account will automatically decline all authorizations and reissue. The cardholder may request reinstatement once the past due balance has been paid by contacting pcard@bussvc.wisc.edu.
120-Days past due: The account is moved to R9 (Revocation) status. The account will automatically decline all authorizations and reissue. The account may not be reinstated per Policy UW-3014 – Shared Liability Card.
Shared Liability Card Cancellation: Shared Liability Card accounts will automatically close when a cardholder terminates employment with UW-Madison. If a cardholder wishes to close their account and are not leaving the UW, they may contact pcard@bussvc.wisc.edu. The card may then be shredded and disposed of.
Applicant/Shared Liability Cardholder: responsible for submitting a request form, activating the Shared Liability Card, registering the account in Access Online, and using the card pursuant to Shared Liability Card Policy.
Manager: responsible for reviewing and approving the Shared Liability Card Request.
Card Program Administrator: responsible for reviewing the Shared Liability Card Request for applicant eligibility, confirming training requirement, requesting the card from U.S. Bank, and serving as a policy and procedure resource.
U.S. Bank: responsible for processing the card request, producing the card, sending the card to the applicant, and making activation and Access Online available to the applicant.
Access Online: the web-based transaction management tool used to support the Shared Liability Card Program at UW–Madison.
Credit Card Administrator: an individual appointed by the Disbursements unit in the Division of Business Services to manage, coordinate, and control Shared Liability Cards for the UW-Madison campus.
Shared Liability Card: a shared-liability VISA credit card (may also be referred to as My Corporate Card) issued by U.S. Bank to a UW–Madison employee for business-related purchases.
August 14, 2019 – Added Delinquent Payment Status procedures
Jan. 19, 2021 – Updated Procedure Number to 3014.1 from 301.1
July 1, 2025 – Updated procedure due to implementation of Workday; rebranded from “My Corporate Card” to “Shared Liability Card”
U.S. Bank will notify cardholders via text and/or e-mail when previously identified or suspicious activity has been detected on a purchasing card. Cardholders can easily confirm whether a transaction is valid or fraudulent, ensuring fewer unnecessary declines and prompt protection in the event of attempted fraud.
Account Number: The 16-digit account number located on the front of the new card.
Account expiration date: The month/year of expiration located on the front of the new card.
Click Register This Account.
Note: If the cardholder has more than one card to register, the cardholder should click Additional Account, enter the additional account information, and click Save List.
Establish a User ID and password.
Select three unique authentication questions and answers to be used if the password is forgotten when attempting to log in.
Note: If a cardholder forgets the User ID, the authentication questions will not be helpful. The cardholder will likely be asked questions that were not previously answered and will be unable to log into the system. If this happens, the cardholder should contact pcard@bussvc.wisc.edu for login information.
Enter the cardholder contact information and click Continue. Then click Save.
Navigate to My Personal Information > Account Alerts.
Confirm or provide the Mobile and Email contact information.
Review the Alert Types tabs and make selections.
Click Terms and Conditions to review.
Select the “I have read and agree to the Terms and Conditions Agreement” box and click “Submit.”
Access Online: U.S. Bank’s web-based transaction management tool used by the Purchasing Card Program Administrator to maintain the purchasing card program at UW–Madison and by purchasing cardholders to manage real-time alerts.
Cardholder: the UW–Madison employee whose name appears on a purchasing card and who is responsible for all purchases made with that card.
Real-Time Alert: communication in the form of a text message or email sent by U.S. Bank to an enrolled purchasing cardholder when U.S. Bank suspects fraudulent use of the purchasing card or when a purchasing card authorization meets previously set criteria established by the cardholder in Access Online.
January 17, 2020 – Updated procedure to include Event and Purchase alerts in addition to Fraud alerts.
January 19, 2021 – Updated Procedure Number to 3013.8 from 300.8
December 11, 2021 – Updated procedure to reflect changes due to Purchasing Card Module implementation.
The UW–Madison Department Card Program is designed to allow employees and enrolled students without a purchasing card the ability to use a Department Card to make infrequent, pre-approved purchases. The Department Card is for UW–Madison business purchases only. There are specific procedures (in addition to those outlined in Procedure 3013.2 – Purchasing Card Use and Account Management) that govern its use, including obtaining pre-authorization to use a Department Card.
Department Card Administrator (DCA); users of a Department Card; site managers; Divisional Business Office staff; the Division of Business Services Purchasing Card Program Administrator; Purchasing Services staff.
Determining who may use a Department Card: The Department Card can be used by the Department Card Administrator (DCA), other authorized employees and authorized enrolled students. Non-employees are not eligible to use a Department Card. The Department Card is intended to be used by those required to make occasional purchases, but not enough to warrant having a purchasing card of their own.
Intended uses of the Department Card: The Department Card is intended for low-dollar, occasional purchases from local or online vendors. It is not recommended the Department Card leave the DCA’s headquarters city, unless necessary (e.g., student group travel).
Obtaining pre-authorization to use a Department Card: No more than five days prior to each request to use the Department Card, purchasers must obtain approval from their supervisor. For enrolled students, this approval may come from a Hoofers Advisor, Club Leader, Department Chair or equivalent. Purchasers must complete the Department Card Pre-Authorization Form with their name, the item(s) intended to be purchased and the UW–Madison business purpose for the intended purchase. Supervisors are to approve the appropriateness of the purchase, not the appropriateness of the use of the Department Card as a payment mechanism. Approval from the supervisor may be in the form of a signature on the Department Card Pre-Authorization Form or in an email which restates the item(s) intended to be purchased.
Requesting the Department Card from the Department Card Administrator: Once a purchaser has obtained approval from the supervisor, the purchaser may request the Department Card from the DCA. The DCA must review the Department Card Pre-Authorization Form and determine if the Department Card is the most appropriate method of payment for the intended purchase(s). If a more appropriate payment method or purchasing mechanism exists (e.g., ShopUW+, internal billing, purchase order) or if it is determined the intended purchase is non-compliant with UW Policy, the DCA must withhold the Department Card from the purchaser and redirect them accordingly. If the DCA determines the intended purchase is compliant with UW policy and is an appropriate Department Card purchase, the DCA may provide the Department Card to the authorized purchaser along with the University’s Tax-Exempt Letter and Certificate or a Tax-Exempt Wallet card, if applicable.
Department Card use in Concur profiles: DCA preapproval is required for all Department Card transactions. If a Department Card account number is stored in a traveler’s Concur profile, the traveler may not use it to make a purchase without obtaining pre-authorization from their supervisor or club leader and the DCA as outlined in Sections B and C above. If a traveler makes a purchase without obtaining pre-authorization from their supervisor or club leader and the DCA, the purchase is considered unauthorized (see Section H. Handling Unauthorized Purchases).
Department Card reconciliation:
DCA responsibilities: Standard purchasing card reconciliation requirements are outlined in Section III.E. of Procedure 3013.2: Purchasing Card Use and Account Management. In addition to these requirements, the DCA must also attach the Department Card Pre-Authorization Forms as part of the supporting documentation for each Department Card transaction initiated by an authorized purchaser (not the Department Card Administrator).
Site Manager responsibilities: Standard purchasing card reconciliation requirements are outlined in Section III of Procedure 3013.5: Purchasing Card Site Manager Review and Reconciliation. In addition to these requirements, the site manager must also ensure each transaction posted to the Department Card account not made by the Department Card Administrator is supported by the Department Card Pre-Authorization Form.
Handling unauthorized purchases: If unauthorized purchases post to the Department Card, the DCA must follow up to determine how the transactions originated. If it is determined a previously authorized purchaser retained the Department Card account number and used it to make a subsequent unauthorized purchase, the DCA must initiate a fraud claim through U.S. Bank and request a cancellation/reissuance of their Department Card. The DCA may not allow the unauthorized purchaser to use the new Department Card or account number to make future purchases, regardless of supervisor approval. Further, the DCA is required to inform the Divisional Chief Financial Officer (CFO) of the unauthorized use and provide additional information as requested.
Note: If the unauthorized purchase was not made by a previously authorized purchaser, the DCA must follow the standard procedures for addressing unrecognizable transactions in Section III.H of Procedure 3013.2: Purchasing Card Use and Account Management.
Department Card Administrator (DCA): responsible for complying with purchasing card policy and procedures and managing the Department Card account.
Authorized purchaser: employee or enrolled student authorized by the supervisor (or equivalent) and DCA to make a purchase.
Supervisor/Club leader/Hoofers Advisor: responsible for reviewing employees’ or enrolled students’ Department Card purchase requests for appropriateness.
Site manager: responsible for reviewing all assigned card activity for policy compliance.
Department Card Administrator (DCA): The UW–Madison employee whose name appears along with a department name on a Department Card and who is responsible for all purchases made with that card.
Department card: A university-liability credit card issued to a UW–Madison employee that may be used by other authorized employees or enrolled students for pre-approved business-related purchases.
Site manager: the individual who manages purchasing cards at the departmental or divisional level.
September 6, 2018 – Removed Accounting Services 100% audit requirement
August 7, 2019 – Update links due to Business Services web redesign
January 19, 2021 – Updated Procedure Number to 3013.7 from 300.7
December 11, 2021 – Updated due to implementation of P-Card Module in the Shared Financial System.
January 25, 2023 – Department Card Tracking Log no longer used.
I. Procedure statement
II. Who is affected by this procedure
III. Procedure
IV. Contact roles and responsibilities
V. Definitions
VI. Related references
VII. Revisions
I. Procedure statement
The UW–Madison Purchasing Card Program is designed to expedite the purchasing process and reduce the costs associated with processing low-dollar, best-judgment purchases. The site manager is the individual responsible for managing purchasing cards at the departmental or divisional level. This procedure provides the site manager with specific instructions on how to review and reconcile the purchasing cards assigned to them. The site manager must not make purchases with a purchasing card they manage.
II. Who is affected by this procedure
Site managers; purchasing cardholders.
III. Procedure
Purchasing card transactions are reconciled in the Shared Financial System (SFS). Transactions are loaded into SFS daily and can be reconciled daily. After a purchasing cardholder verifies a transaction in SFS, the purchasing card site manager (Approver) receives an automated email notification that a transaction is pending approval. Detailed instructions for approving purchasing card transactions are available in the Purchasing Card Approver Business Process Guide (PDF). See below for a summary of the purchasing card transaction approval process.
A. Purchasing card site managers receive an email notification from SFS when a transaction has been verified by a purchasing cardholder. The email is only sent if the cardholder clicks the “Notify My Approver(s)” button after completing their reconciliation. It is recommended site managers routinely review the Reconcile Statement page in SFS for any outstanding transactions for which a notification was not sent.
B. Site managers review transactions for appropriateness and verify all required supporting documentation has been provided.
Review posted transactions for policy compliance:
Verify who made the purchase. A UW-Madison purchasing card may only be used by the employee whose name is embossed on the front of the card.
Verify the purchase is considered best-judgment and within the cardholder’s single purchase limit. The best-judgment purchase limit at UW-Madison is $5,000.
Verify the cardholder did not intentionally split transactions to avoid the single purchase limit and/or the best-judgment purchase limit.
Verify purchases of materials for capital equipment components or fabrication materials are allocated to Account Code 4670 and the appropriate Asset ID is referenced within the provided business purpose.
Verify purchases related to the relocation of an incoming employee (e.g., payments to moving companies, temporary lodging, airfare for employee and family) are allocated to account codes 2880, 2881 or 2883 and enter the new employee’s Employee ID in the Comment field.
Identify purchases that should have been made at ShopUW+.
Identify purchases made with internal vendors and encourage purchasers to use different payment mechanisms for making internal purchases.
Identify sales and use tax paid in error. If sales tax is paid in error in an amount greater than $25, verify the cardholder has documented an attempt to recover the amount from the vendor.
Verify required supporting documentation is included:
Vendor receipts: Invoices, packing slips, cash register receipts, confirmation screens, service agreements, and registration forms are acceptable forms of vendor documentation. All receipts must include the date of purchase, vendor name, items purchased, and pricing information. If the vendor receipt does not contain adequate detail, the cardholder must provide the required information elsewhere in the supporting documentation. Note: The Purchasing Card Missing Receipt Form is available for occasional use only. Repeat use of the form should be addressed with the Purchasing Card Non-Compliant Form.
Other supporting documentation: Other required supporting documentation may include agendas, attendee lists, conference brochures, etc., as required by expense-specific policies.
Business purpose: Cardholders are required to provide a business purpose for each transaction that posts to their purchasing card account. The business purpose must provide adequate detail so the site manager can reasonably conclude the expense is appropriate and business-related.
C. Site managers verify intended funding source(s):
All purchasing card transactions are initially allocated to the cardholder’s default funding source. The cardholder and the site manager can reallocate transactions to other funding sources prior to final approval.
E. After completing the policy review and transaction reconciliation, site managers approve reconciled transactions in SFS.
F. UW–Madison Division of Business Services initiates processing, and approved transactions are posted to WISER.
G. Timeliness of Purchasing Card transaction reconciliation: Cardholders and site managers are required to reconcile transactions within 30 days of the transaction posting date.
If a cardholder has a purchasing card transaction that is not fully approved after 15 days, an automated email reminding the cardholder of the pending transaction will be sent. Emails will continue to send daily until the transaction is fully approved or system closed, including those transactions that have been previously verified by the cardholder, but have not been approved by the site manager. Site managers do not receive reminder emails; therefore, it is the cardholder’s responsibility to either forward the email to their site manager or utilize the Notify Approver(s) button on the Reconcile Statement page of the Purchasing Card module. Site managers may utilize the Transactions Near System Close query available in SFS to monitor aging transactions requiring cardholder and/or site manager approval.
After 30 days, a process will run to “System Close” any purchasing card transactions that have not been fully approved and transfer the transaction(s) to WISER. “System Closed” transactions will be tracked by the Purchasing Card Program Manager and treated as non-compliance. Compliance measures will be taken for repeat offenders.
Cardholders and site managers are required to complete the reconciliation process and provide the required receipts and supporting documentation for “System-Closed” transactions.
The Purchasing Card Program Manager notifies the cardholder, site manager and Divisional Business Office of “System-Closed” transactions. The email notification includes the Purchasing Card Post-System Close Reconciliation Form referencing the details of the “System-Closed” transaction. The following steps must be completed within 14 days of receipt of this form.
The cardholder provides a justification for missing the reconciliation deadline and signs the form, acknowledging the policy requirement. The cardholder provides the required business purpose and supporting documentation for the “System-Closed” transaction in the Purchasing Card module. The cardholder forwards the form to the site manager via email.
The site manager provides a justification for missing the reconciliation deadline, reviews the provided supporting documentation and business purpose in the Purchasing Card module, and attaches the form to the “System-Closed” transaction in the Purchasing Card module.
The Purchasing Card Program Manager reviews the “System-Closed” transaction to verify reconciliation is complete within 14 days.
IV. Contact roles and responsibilities
Cardholder: responsible for complying with purchasing card policy and procedures and managing the purchasing card account.
Site manager: responsible for reviewing all card activity to verify the cardholder provided all required documentation and adhered to purchasing card policies.
V. Definitions
Cardholder: the UW–Madison employee whose name appears on a purchasing card and who is responsible for all purchases made with that card.
Department Property Administrator (DPA): an individual in a department or division who serves as the liaison between that department or division and Property Control for all matters regarding capital equipment.
Site manager: the individual who manages purchasing cards at the departmental or divisional level.
July 9, 2020 – Increased tax tolerance level from $5 to $25
January 19, 2021 – Updated Procedure Number to 3013.5 from 300.5
December 11, 2021 – Purchasing Card Module implementation
