3024.9 Expense Report Review and Approval Procedure (for Approvers and Auditors)

This procedure explains how to review and approval expense reports in e-Reimbursement, the Expense module of the Shared Financial System (SFS), from the perspective of an Approver or Auditor.

Procedure #3024.9; Rev.: 0 (Effective Nov. 16, 2023)
Related Policy: UW-3024 Expense Reimbursement Policy
Functional Owner: Accounting Services, Business Services
Contact: Expense Reimbursement Program Manager – Allie Watters, expensereimbursement@bussvc.wisc.edu, (608) 263-3525


Contents

  1. Procedure statement
  2. Who is affected by this procedure
  3. Procedure
  4. Contact roles and responsibilities
  5. Definitions
  6. Appendix
  7. Related references
  8. Revisions

I. Procedure statement

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. When an expense report is ready for approval, approvers and auditors will receive an email notification prompting them to take action. Approvers and auditors must review expense reports for policy compliance, appropriateness of expenses, accuracy of accounting, and necessary supporting documentation.

This document details the required procedures for reviewing and approving an expense report in the Shared Financial System.

Back to top


II. Who is affected by this procedure

Employees who approve or audit expense reports.

Back to top


III. Procedure

To get started, sign into the Shared Financial System (SFS), click the Expense WorkCenter tile, then click the link for Approve Transactions in the Approve Transactions and Reassign menu along the left side of the window. This will populate a list of expense reports, cash advances, and travel authorizations requiring your approval.

  1. Overview Screen: After clicking Approve Transactions, the Overview screen of the approval queue will appear. In Overview format, the queue may contain expense reports as well as cash advances, and less commonly, travel authorizations. The tabs along the top of the page allow you to narrow your queue visibility to see only Expense Reports, Travel Authorizations, or Cash Advances. You may search for pending transactions by clicking the arrow next to Search Pending Transactions near the top of the page; searching by Transaction ID (10-digit expense report number) often proves helpful, but other columns may be selected for search terms as well, such as Name (employee/non-employee claimant name). You may also change the sort order of reports in your queue by clicking the arrow next to Change Sort Order. You may then sort your queue by any selected field (e.g. Total, Date Submitted) in ascending or descending order.
    1. Review columns in the Transactions to Approve table (click image below to enlarge):
      Screenshot showing the Overview and Transactions to Approve section in the Expenses WorkCenter (in e-Reimbursement within the Shared Financial System). Column headers for transactions to approve: Select, Urgency, Transaction Type, Total, Unit, Name, Employee ID, Description, Transaction ID, Date Submitted, Status, Role.

      1. Select: The checkboxes in this column can be used to Send Back or Hold multiple transactions as long as they do not contain an alert icon in the Alert column.
        1. Send Back: If sending back multiple reports at this screen, the same comments will be included with each transaction that is sent back to the Traveler for modification and resubmission. Note: Expand the Comments section at the bottom of the list of expense reports to enter a comment.
        2. Hold: Placing a transaction on hold will make it inaccessible to other approvers/auditors and System Administrators. The only way to remove the hold status is to approve or deny the report or send it back to the Traveler. Be aware of these limitations should you choose to put a report on hold.
      2. Urgency: The Urgency column provides a visual guideline to help you prioritize your approval queue based on the number of days from submission. The categories are defined as follows: green circle (low priority): 0 – 7 Days; yellow triangle (medium priority): 8 – 29 Days; red square (high priority): 30 – 999 Days.
      3. Alert: The Expenses module is programmed to highlight certain alerts to approvers and auditors, e.g. accountable plan violation, lodging limit exceeded, Foundation billing utilization. A yellow triangle with an exclamation point in this column indicates that this report is flagged for having at least one alert.
      4. Transaction Type: Approvers/auditors will see expense reports, travel authorizations and cash advances in their approval queues.
      5. Total: This amount represents the total dollar amount of the report, regardless of the payment mechanism used for each expense line.
      6. Unit: This column displays the form of currency used to enter the expenses.
      7. Name: This column displays the name of the individual claiming reimbursement/payment. Verify that this is the appropriate individual to be reimbursed for the expenses claimed.
      8. Employee ID: This column displays the employee or non-employee ID of the individual claiming reimbursement/payment.
      9. Bus Unit: Business Unit/Institution of the claimant
      10. Description: This column displays the report name entered by the claimant/alternate.
      11. Transaction ID: This column displays a unique 10-digit number that identifies the transaction.
      12. Date Submitted: This column displays the date the claimant/alternate submitted the report.
      13. Status: This column displays the status of the report, which will be Approvals in Process in most cases.
      14. Role: If an approver/auditor is assigned to multiple approval roles, it is important to verify which level of approval the transaction is pending.
  2. Navigate to an individual transaction and review the report:
    1. Click on the Description or Transaction ID link of the report you would like to review.
    2. The content within the displayed Expense Summary section should provide details necessary to determine the appropriateness of the expense lines in an expense report. Review the Business Purpose (See Appendix), Description, Reference, and Dates for accuracy; field should be checked in reference to attachments and supporting documentation at the header level of the expense report. Next, verify that the Justification and Supporting Details section contains a valid and complete UW-Madison business purpose. The UW Summary Report link is available near the top of the expense report and can be used to quickly review the accounting distribution for the expense report.
    3. To review individual expense lines in full detail and to be able to make changes to expense lines, select the Expense Details link in the upper right corner of the expense report. This will take you to the Expense Details page, where each expense line should be reviewed for:
      1. Policy Compliance: It is helpful to refer to the specific policy that pertains to the expense line being reviewed.
      2. Documentation Requirements: Review documentation in accordance with documentation requirements outlined in Policy UW-3024, Expense Reimbursement.
      3. Expense Type and Reference/Billing Type: In the Expense Module, account codes are automatically determined by selecting the appropriate Expense Type and Billing Type. The Expense Type selected also drives the required field completion in the Expense Details panel.
        1. If the Expense Type is incorrect, approvers and auditors can click on the Expense Type field and select the correct Expense Type from the list.
        2. If a single Expense Type needs to be divided into multiple expense types (e.g. Lodging > Lodging, Internet Fee and Parking), see How to Use the Receipt Split Function in the Expense Module.
        3. Note Billing Type is coded based on the Reference selection in the header section of the expense report and cannot be changed at the line-item level. Approvers and auditors can correct the Billing Type for the expense report as a whole by returning to the Expense Summary page and selecting the correct Reference for the expense report.
      4. Payment Type: The payment type determines who will receive payment for the expenses claimed.
        1. US Bank Corporate Card: The My Corporate Card is an individual-liability VISA credit card issued by U.S. Bank to UW-Madison employees for University business use only. For employees who have an open My Corporate Card account, reimbursable expenses are paid directly to US Bank by the University, on behalf of the cardholder when an expense report is submitted and approved.
        2. Personal Funds: When this option is selected, the employee will be reimbursed via the payment mechanism on file. If direct deposit has been set up by the employee, the payment will be delivered via ACH. If not, a paper check will be mailed to the employee. Non-employee payments are issued via a mailed check or via a wire payment (for nonemployees with addresses outside of the U.S. and Canada).
        3. 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.
      5. Funding: Verify that the funding string has budget and funds available for the expenses listed. Confirm expenses are allocable to and allowable on the funding string.
        1. To change the funding on an individual expense line, click on the Accounting Details to expand the funding string for the expense line. Change the funding as appropriate. To use multiple funding sources, click the Plus (+) sign button at the far right of the funding string, enter the additional funding string, and modify the distribution of the expense across the lines.
      6. Additional Required Details (varies by Expense Type): Individual expense types may require verification of additional information, such as Number of Nights, Number of Attendees, Attendees Lists, Currency Exchange Rate, etc.
      7. Tax Compliance: Each expense line should be reviewed for tax compliance. The University of Wisconsin–Madison is exempt from payment of Wisconsin sales and use tax on items purchased within Wisconsin. Additionally, Universities of Wisconsin has tax exempt reciprocity agreements with some other states. if an e-Reimbursement approver or auditor notes an expense line with sales and use tax paid in error, the following steps should be  taken, depending on the dollar amount paid in error:
        1. $25.00 or less: If the amount of sales tax paid in error is $25 or less, the approver or auditor may note the non-compliant amount, but approve the amount for reimbursement, citing the following immateriality clause: “Sales tax paid in error for this transaction does not meet the materiality threshold of $25 for the University of Wisconsin-Madison; as such, immaterial sales tax will be reimbursed.”
        2. Greater than $25:
          1. Includes a documented attempt to obtain exemption: If the amount of sales tax paid in error is greater than $25 and the claimant has documented an attempt to either obtain exemption or obtain a refund (without success), the approver/auditor may approve the amount for reimbursement.
          2. Does not include a documented attempt to obtain exemption: If the amount of sales tax paid in error is greater than $25, but the claimant did not document an attempt to either obtain exemption or obtain a refund, the approver/auditor must reduce the reimbursable amount to the pre-tax total.
    4. Marking an expense line non-reimbursable: Generally, expenses that do not comply with UW–Madison policies will not be reimbursed. Additionally, Policy UW-3026, Non-Payable/Non-Reimbursable Expenses, outlines expenses that are not payable or reimbursable by the University. Expense lines in e-Reimbursement may be marked non-reimbursable by unchecking the box underneath Approve in the upper-right section of an expense line on the Expense Details page. After unchecking the box, a drop-down selection menu will appear, and a reason for not approving the expense for reimbursement must be selected. Reasons in the drop-down list include: Already Paid/Duplicate, No Receipt, Out of Policy, and Personal Expense.
    5. Once line-item review is completed, you must switch back to the Summary and Approve screen to review final summary items and to take action on the expense report. Select the Summary and Approve link in the upper right corner of the expense report.
      1. Note the Expense Report Totals section. The amounts listed indicate the payments to be made to the following:
        1. Employee Expenses: Total of all expense lines, regardless of payment type
        2. Non-Reimbursable Expenses: Total of all expenses marked as non-reimbursable
        3. Prepaid Expenses: Total of all expenses with a payment type of University Prepaid
        4. Amount Due to Employee: Total of all reimbursable expenses with a payment type of Personal Funds
        5. Amount Due to Supplier: Total of all reimbursable expenses with payment type of Corporate Card
      2. Note the Approval History (timeline): This graphic displays the names and roles of all approvers/auditors required to review the report prior to payment/reimbursement. A green check mark indicates that an approval step is complete. If the approver is listed as “Pooled”, multiple individuals are able to approve at this level, but only one is required. If auditor is listed as “Multiple”, all auditors must approve for the report to advance to payment.
      3. Note the Approval History (table): This table shows the history of the report after it was submitted, including a date/time stamp and comment bubbles containing approver/auditor remarks. Be sure to review any comment bubbles listed.
      4. If ready to approve the report, click Approve. On the confirmation pop-up page, click “OK”. If approving as Prepay Auditor, note the report cannot be changed, modified, or returned once this final approval step is complete. If a report has been approved at final audit in error and the report should not be paid, email expensereimbursement@bussvc.wisc.edu to close the report.
      5. If you are not ready to approve the expense report, other actions that may be taken include:
        1. Send Back: Click the Send Back button to save changes and send it back to the submitter. This button sends the report back to the submitter for edits, revisions, and additions. A comment must be entered in the Comments box prior to sending back the report; this comment should outline the reasons for the send-back and the steps the submitter needs to take prior to resubmitting the report.
        2. Hold: Click Hold to put an expense report on hold; this prevents any other individual from acting on the report other than the approver/auditor who placed the report on hold.
        3. Deny: To eliminate an expense report that will not be paid, click the Deny button. Once an expense report is denied, the expense report cannot be resubmitted.
        4. Save Changes: Click the Save Changes button. This saves any changes made to the expense report and routes you back to your approval queue.
      6. After clicking on one of the action buttons above, you will be routed back to your approval queue to select a new report to work on.

Back to top


IV. Contact roles and responsibilities

  • Traveler/Claimant/Recipient: the person receiving reimbursement. Note: 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 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.
  • Approver: Upon submission, expense reports are first reviewed by an approver. Approvers are responsible for reviewing supporting documentation, reviewing expense reports for policy compliance, and reviewing funding being charged.
  • Auditor: Expense reports are reviewed by an auditor after the approver and prior to final payment. Auditors are responsible for reviewing expense reports for policy compliance.

Back to top


V. Definitions

  • 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.
  • 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.
  • 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 business-related expenses through e-Reimbursement. Generally, non-employees are subject to the same policy requirements as employees.

Back to top


VI. Appendix

  1. Business purposes
    1. Business – Expenses for routine business travel not better classified in another category.
    2. Conference – Expenses incurred to attend or host a conference.
    3. Fundraising – Expenses incurred for University fundraising.
    4. Job candidate hosting – Expenses incurred for hosting job candidates.
    5. Local travel – Expenses incurred when traveling within the headquarter city or surrounding area. Expenses can be accumulated and filed weekly, bi-weekly or monthly.
    6. Non-Travel – Expenses incurred for low-dollar purchases made in compliance with UW purchasing policies.
    7. Professional development – Expenses incurred by employees for education or job/professional training.
    8. Recruiting – Expenses incurred for recruiting employees and students to the University.
    9. Relocation – Relocation stipends for employee relocation.
    10. Research – Expenses incurred for research or research-related activities including fieldwork or faculty presentation of papers.
    11. 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 on student travel.
    12. Study abroad – Expenses incurred by travelers (faculty or students) for study abroad or other international education programs.
    13. Team travel – Expenses incurred for sport team travel.

Back to top


VII. References

Back to top


VIII. Revisions

Procedure Number 3024.9
Date Approved Nov. 16, 2023
Revision Dates N/A

Back to top

3025.1 How to Obtain and Reconcile a Cash Advance (Traveler Procedures)

How to Obtain and Reconcile a Cash Advance (Traveler Procedures)

Procedure # 3025.1; Rev.: 1 (Effective October 10, 2018)
Related Policy: UW-3025 Cash Advance Policy
Functional Owner: Accounting Services, Business Services
Contact: Expense Reimbursement Program Manager – Allie Demet, expensereimbursement@bussvc.wisc.edu, (608) 263-3525


Contents

  1. Procedure statement
  2. Who is affected by this procedure
  3. Procedure
  4. Contact roles and responsibilities
  5. Definitions
  6. Related references
  7. Revisions

I. Procedure statement

Cash Advance requests are submitted through the Shared Financial System (SFS). Employees must first be approved by their Dean’s/Divisional Business Office and their profiles must be activated by Business Services before requesting cash advances. This process should be initiated at least 7 – 10 business days prior to the travel start date. ACH deposit for approved cash advances may take up to 5 business days. Employees must fully reconcile cash advances within 30 days of the end of the trip.

Back to top


II. Who is affected by this procedure

Faculty and staff seeking cash advances for travel expenses and their alternates.

Back to top


III. Procedure

  1. Pre-Approval: Submit a Cash Advance Activation Request Form to Business Services. These forms must be routed through the Dean’s/Divisional Business Office. Once the form has been submitted and the traveler’s profile has been activated, the traveler can request a cash advance.
  2. Cash advance request:
    1. Sign into the Shared Financial System (SFS), click the Expenses WorkCenter tile.
    2. Select Create/Modify Cash Advance from the cash advance submenu.
    3. Click Add. If you are an alternate requesting a cash advance for a different traveler, enter their employee ID before clicking Add. If you receive an error message, ensure your travel profile has been properly activated (see above).
    4. Enter header information, justification, and add any attachments to the cash advance.
    5. In the descriptions area, enter expense descriptions or select from pre-existing expense types. The amount of expense line detail required will vary by department and division.
    6. Click “Save For Later” to save the cash advance. Note you must click “Save for Later” in order to check the box next to the attestation statement and submit the report.
    7. Check the box next to the attestation statement.
    8. Click “Submit” to submit the cash advance.
  3. Reconciliation: Cash advances must be fully reconciled within 30 days of the end of the trip.
    1. Submit an expense report: Account for the use of advanced funds by submitting an expense report. On the Review and Submit page, there will be a menu showing your available Cash Advances. Apply either the full amount of the expense reimbursement or the full amount of the cash advance, whichever is lower. You will receive a notification if an amount is due back to the University.
    2. Refund Excess Advanced Funds: Any advanced funds not utilized must be promptly refunded to the University. Travelers must submit a check to their departmental or divisional business office for deposit. Once the check has been deposited, the Divisional auditor must reconcile the remainder of the cash advance in the Shared Financial System (SFS) to ensure the cash advance is reconciled in full.

Back to top


IV. Contact roles and responsibilities

  • Travelers – Travelers are responsible for reconciling Cash Advances within 30 days of the end of the trip. Travelers must not seek excessive cash advances and must refund any excess advancements promptly. Advanced funds must be used prudently and in accordance with UW travel and purchasing policies. Travelers are responsible for submitting cash advance requests in a timely enough fashion to allow for approvals and payment.

Back to top


V. Definitions

  • Cash Advance –a request for monetary advancement prior to a trip
  • Expense Reimbursement – An 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.

Back to top


VI. Related references

Back to top


VII. Revisions

Procedure Number 3025.1
Date Approved October 1, 2018
Revision Dates Jan. 19, 2021 – Updated Procedure Number to 3025.1 from 321.1

Back to top

3025.2 How to Approve and Reconcile a Cash Advance (Approver/Auditor Procedures)

How to Approve and Reconcile a Cash Advance (Approver/Auditor Procedures)

Procedure # 3025.2; Rev.: 1 (Effective October 10, 2018)
Related Policy: UW-3025 Cash Advance Policy
Functional Owner: Accounting Services, Business Services
Contact: Expense Reimbursement Program Manager – Allie Watters, expensereimbursement@bussvc.wisc.edu, (608) 263-3525


Contents

  1. Procedure statement
  2. Who is affected by this procedure
  3. Procedure
  4. Contact roles and responsibilities
  5. Definitions
  6. Related references
  7. Revisions

I. Procedure statement

Cash Advance requests are submitted through the Shared Financial System (SFS). Employees must first be approved by their Dean’s/Divisional Business Office to receive Cash Advances. Employees’ profiles must be activated for Cash Advances by Business Services before they can create and submit Cash Advances. Employees must fully reconcile Cash Advances within 30 days of the end of the trip.

Back to top


II. Who is affected by this procedure

e-Reimbursement approvers and auditors who review, approve, and reconcile Cash Advances.

Back to top


III. Procedure

  1. Pre-Approval: Prior to advancement, a Cash Advance Activation Request Form must be submitted to Business Services. This form must be approved by the Department and Division. Once the form has been submitted and the traveler’s profile has been activated, the traveler can request a cash advance. Once activated, the traveler’s profile is permanently activated unless the Department or Division specifically requests a traveler to be deactivated.
  2. Cash Advance Approval: Cash advances are approved by an approver and auditor. They appear in approver/auditor queues with expense reports. The level of detail required in a cash advance is determined by the department and division.
  3. Reconciliation: Cash advances must be fully reconciled within 30 days of the end of the trip.
    1. Traveler submits expense report: Travelers must submit an expense report to account for the use of advanced funds.  Expenses post to the general ledger after the expense report is approved; expenses do not post when the cash advance is approved.
    2. Refund of excess advanced funds: Travelers must promptly refund any unused advanced funds to the University. Deposits must be made to the funding used in the cash advance.
      1. Identify the funding string used on the cash advance:
        1. Sign into WISDM.
        2. Navigate to Main Menu > Other > Transaction Search.
        3. Complete the search criteria as follows:
          • Select the Fiscal Year and Accounting Period in which the Cash Advance was paid.
          • Change the Dept drop-down menu to starts with and enter the traveler’s Division code (e.g. 48 for L&S).
          • Change the Account drop-down menu to is exactly and enter account code 6166.
          • Change the Description drop-down menu to is exactly and enter the traveler’s Employee ID.
          • Check the Show Balance Account
      2. Click Submit.
      3. Find the original cash advance payment by locating the Cash Advance ID in the Jrnl Line Ref column and the total sum of the cash advance in the Monetary Amt column. Use this funding string to deposit the refund payment.
        1. Note: Jrnl Line Ref is not a default column in WISER for the Transaction Search and must be manually added. To do this, click the “More Options” when icon next to “Pin to Dashboard.” From the menu that pops up, select “Customize…” Under “Available Columns” menu, select “Jrnl Line Ref” and click the right arrow button to move the field to your “Custom View.” If desired, rearrange “Custom View” by selecting the field you’d like to move, and clicking the up or down arrows. Once complete, click “Save.” The custom layout including Jrnl Ln Ref should now be visible.
      4. Submit a Check Deposit Form utilizing the funding string identified in the step above.
  4. Auditor Reconciliation: The Auditor of the Cash Advance request must reconcile the deposit in e-Reimbursement to fully close the Cash Advance. The refund check must have been deposited prior to the auditor’s reconciliation.
    1. Sign into the Shared Financial System (SFS)/e-Reimbursement, click the Expenses WorkCenter tile.
    2. Select Reconcile Cash Advance from the cash advance submenu. Select the proper cash advance from the list.
    3. Enter the check number and the amount of refunds received. Click Reconcile.

Back to top


IV. Contact roles and responsibilities

  • Travelers – Travelers are responsible for reconciling cash advances within 30 days of the end of the trip. Travelers must not seek excessive cash advances and must refund any excess advancements promptly. Advanced funds must be used prudently and in accordance with UW travel and purchasing policies. Travelers are responsible for submitting cash advance requests in a timely enough fashion to allow for approvals and payment.
  • Approver – Upon submission, cash advance requests are first reviewed by an approver. Approvers are responsible for reviewing supporting documentation, for reviewing cash advances for policy compliance, and for reviewing the funding being charged.
  • Auditor – All cash advances are reviewed by an auditor after the approver. Auditors are responsible for reviewing cash advances for policy compliance. Auditors are responsible for reconciling refunded payments related to cash advances.

Back to top


V. Definitions

  • Cash Advance – a request for monetary advancement prior to a trip.
  • Expense reports – An 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.

Back to top


VI. Related references

Back to top


VII. Revisions

Procedure Number 3025.2
Date Approved October 1, 2018
Revision Dates July 23, 2019 – Updated instructions for depositing refund checks
Jan. 19, 2021 – Updated Procedure Number to 3025.2 from 321.2

Back to top

3031.A Open and Manage an Internet Storefront Merchant Account Procedure

Open an Internet Storefront Merchant Account Procedure

Procedure # 3031.A; Rev.: 2.12.20 (Effective January 1, 2020)
Related Policy: UW-3031 Payment Card Merchant Services and PCI Compliance Policy 
Functional Owner: Cash Management, Business Services
Contact: PCI Mailbox: pci-help@bussvc.wisc.edu


Contents

  1. Procedure statement
  2. Who is affected by this procedure
  3. Procedure
  4. Definitions
  5. Related references
  6. Revisions

I. Procedure statement

The University of Wisconsin–Madison can accept payment cards from customers to pay for goods and services. An Internet storefront is a method of accepting e-commerce payment transactions via a website.

Back to top


II. Who is affected by this procedure

This procedure applies to all UW–Madison departments that accept payment cards online. This procedure should be understood by all Divisional Business Representatives (DBRs), Site Managers, and Operators of the merchant accounts.

Back to top


III. Procedure

Below are the steps for opening an internet storefront merchant account:

  1. Complete and submit the Card Merchant ID Request Form.
    1. The DBR must approve the new merchant account.
      1. The DBR will receive an email upon completion of the Card Merchant ID Request Form. The DBR should then sign into the portal to approve the request.
    2. The DBR should determine which card brands the new merchant will accept.
      1. The standard set up for a new merchant account includes MasterCard, Visa, and Discover. Should the department decide to choose to accept American Express cards, an additional reconciliation and an additional connection is required.
  2. Cash Management will review the submitted Card Merchant ID Request Form and contact the Site Manager to facilitate setting up CASHNet and Merchant Connect.
    1. Each person that will log into CASHNet and Merchant Connect must have a unique operator ID.
    2. The department should provide a logo for the checkout page.
  3. The PCI Site Manager must establish card handling procedures and a contingency plan for processing transactions should the primary system be unavailable. Once complete, these policies and procedures shall be emailed to Cash Management (pci-help@bussvc.wisc.edu).
  4. The PCI Compliance Assistance Team and Elavon will review the website that is being used and ensure that it directs customers to CASHNet for payment. The hosting location must be determined and approved before the Merchant ID (MID) goes into production.
  5. Cash Management will schedule a PCI site visit with the Site Manager once a MID is assigned by Elavon. During the PCI site visit, Cash Management will review the department business policies and procedures and assist with completing the Self-Assessment Questionnaire (SAQ).
  6. Cash Management, or a specific DoIT staff, will activate the MID within CASHNet after the PCI site visit. Once the MID is in production in CASHNet, the storefront website may be used by customers.
  7. The PCI Site Manager must track all live websites in use that redirect to the payment page. Contact pci-help@bussvc.wisc.edu to close the websites that are no longer used for payment.

Merchant account fees

Any fees associated with the acceptance of payment cards in a campus department will be charged to the related merchant on a monthly basis. These fees can be seen in WISER/WISDM once they have been posted. Expenses may include a monthly account maintenance fee of $5.00, Elavon processing fees of approximately 2% of each transaction, and $7.50 for chargeback fees. American Express charges a fee of 2.1% of each transaction.

Back to top


IV. Definitions

  • Campus Merchant Department – Manage the daily operations of the merchant account(s) and maintain PCI compliance.
  • CASHNet – A third-party, e-commerce service provider contracted by the University of Wisconsin that is used to process credit card payments.
  • Divisional Business Representative (DBR) – An individual within the dean or divisional office. This individual has the highest level of PCI responsibility including approving the initial merchant account request and annually reviewing the SAQ as the executive officer.
  • Merchant Connect (MCP) – An online tool from Elavon, the credit card processor, which displays transaction activity and monthly statements.
  • Site Manager – This individual is the point of contact for the campus department merchant account(s) and should have influence to establish procedures for the day-to-day handling of payment cards to ensure compliance.

Back to top


V. Related references

Back to top


VI. Revisions

Procedure Number 3031.A
Date Approved January 1, 2020
Revision Dates Jan. 19, 2021 – Changed Procedure Number to 3031.A from 404.A

Back to top

3031.B Open and Manage a Merchant Account using an EMV Chip or Swipe Machine Procedure

Open a Merchant Account using an EMV Chip or Swipe Machine

Procedure #3031.B; Rev.: 2.12.20 (Effective January 1, 2020)
Related Policy: UW-3031 Credit Card Merchant Services and PCI Compliance Policy
Functional Owner: Cash Management, Business Services
Contact: PCI Mailbox: pci-help@bussvc.wisc.edu


Contents

  1. Procedure statement
  2. Who is affected by this procedure
  3. Procedure
  4. Definitions
  5. Related references
  6. Revisions

I. Procedure statement

The University of Wisconsin–Madison can accept payment card payments from customers to pay for goods and services in person. A payment card terminal is used for processing payments in-person or over-the-phone by a merchant at the point-of-interaction. In some cases, payments can be made via fax communication if proper security is in place and is properly documented.

Back to top


II. Who is affected by this procedure

This procedure applies to all UW–Madison departments that accept payment cards via payment card terminals. This procedure should be understood by all Divisional Business Representatives (DBRs), Site Managers, and Operators of the merchant accounts.

Back to top


III. Procedure

Below are the steps for opening a merchant account that uses an approved PCI P2PE or an approved EMV payment card terminal with no electronic cardholder data storage:

  1. Complete and submit the Card Merchant ID Request Form.
    1. The Divisional Business Representative (DBR) must approve the new merchant account.
      1. The DBR will receive an email upon completion of the Card Merchant ID Request Form. The DBR should then sign into the portal to approve the request.
    2. The DBR should determine which card brands the new merchant will accept.
      1. The standard set up for a new merchant account includes MasterCard, Visa, and Discover. Should the department decide to choose to accept American Express cards, an additional reconciliation and an additional connection is required.
  2. Cash Management will review and approve the submitted Card Merchant ID Request Form and contact the Site Manager to facilitate setting up Payments Insider access.
    1. Cash Management will provide information on payment card machines, including pricing information. Standalone payment card machines will ship directly from Elavon to the campus department. The cost of the new payment card machine will be charged directly to the merchant account.
    2. Each person who logs into Payments Insider for settlements and monthly statements is required to have a unique operator ID.
    3. Complex Point of Sale Systems will require additional PCI review and approval, signed contracts, and annual AoC documentation. Please contact pci-help@bussvc.wisc.edu for additional information.
  3. The PCI Site Manager is required to establish card handling procedures and a contingency plan for processing transactions should the primary system be unavailable. Once complete, these policies and procedures shall be submitted to Cash Management via email (pci-help@bussvc.wisc.edu).
  4. Cash Management will schedule a PCI site visit with the Site Manager once a Merchant ID (MID) is assigned by Elavon. During the PCI site visit, Cash Management will review the department business policies and procedures and assist with completing the Self-Assessment Questionnaire (SAQ).
  5. When the equipment is received, verify the machine has the correct address, merchant name, and MID on the machine.
  6. The PCI Site Manager is responsible to document:
    1. Make and model of the device(s)
    2. Physical location of the device(s)
    3. Device Serial number(s) or other methods of unique identification
    4. Physical inspection of each device periodically to detect tempering, skimming devices, and unauthorized substitution; Record your device information and inspection dates (charge.wisc.edu/users)
  7. Call Elavon Training at (866) 451-4007 to schedule a training on how to use the payment card terminal; training includes daily transactions and settlements. Note: the payment card terminal will not auto settle unless the terminal is turned on.
  8. Elavon terminals are factory shipped and contain incorrect information on each terminal. The merchant is required to add the correct information directly on the terminal containing this information:
    1. Equipment problems – Relationship Premier Services: (800) 725-1245
    2. Supplies such as thermal paper – Customer Service Center: (800) 725-1243
    3. Elavon Training: (866) 451-4007

Merchant account fees

Any fees associated with the acceptance of payment cards in a campus department will be charged to the related merchant on a monthly basis. These fees will post to WISER on the first of the month for the prior month’s transactions. Expenses include a monthly account maintenance fee of $5.00, Elavon processing fees of approximately 2.5% of each transaction, and in some cases $7.50 for chargeback fees (rare). American Express charges a fee of 2.1% of each transaction.

Requirements to manage a Merchant Account

  1. Annual completion of a Self-Assessment Questionnaire every calendar year.
  2. Participation in assessments of your environment by the designated PCI Compliance Analyst and/or Internal Security Assessor.
  3. Completion of mandatory annual payment card industry (PCI) merchant training.
  4. Maintaining documentation of employees who have participated in the annual training, with the ability to produce to the PCI Compliance Analyst upon request.
  5. In some instances, maintaining relationships with third party vendors for departmental specific payment applications, to receive compliance documentation from the vendors (AOCs, ASV Scans, etc.).
  6. Review annually the University Policies and Procedures related to the PCI compliance environment. UW-3031 Credit Card Merchant Services and PCI Compliance Policy
  7. Maintain accurate lists of individuals within your organization directly involved in the credit card processing environment.
  8. Reconcile the transactions from the merchant account to WISER, at a minimum, monthly.

Back to top


IV. Definitions

  • Campus Merchant Department – Manage the daily operations of the merchant account(s) and maintain PCI compliance.
  • Divisional Business Representative (DBR) – An individual within the divisional or dean’s office. This individual has the highest level of PCI responsibility, including approving the initial merchant account request and annually reviewing the SAQ as the executive officer.
  • Payments Insider – An online tool from Elavon, the credit card processor, which displays transaction activity and monthly statements.
  • Site Manager – This individual is the point of contact for the campus department merchant account(s) and should have influence to establish procedures for the day-to-day handling of payment cards to ensure compliance.

Back to top


V. Related references

Back to top


VI. Revisions

Procedure Number 3031.B
Date Approved January 1, 2020
Revision Dates Jan. 19, 2021 – Changed Procedure Number to 3031.B from 404.B
Sept. 14, 2023 – Small tweaks related to language change (terminal vs. machine) and added a section with what is needed to manage a merchant account.

Back to top

3031.C PCI Non-compliance Procedure

PCI Non-compliance Procedure

Procedure # 3031.C; Rev.: 1 (Effective September 1, 2020)
Related Policy: UW-3031 Credit Card Merchant Services and PCI Compliance Policy 
Functional Owner: Cash Management, Business Services
Contact: PCI Mailbox: pci-help@bussvc.wisc.edu


Contents

  1. Procedure statement
  2. Who is affected by this procedure
  3. Rationale
  4. Procedure
  5. Supporting tools
  6. Related references
  7. Revisions

I. Procedure statement

The University of Wisconsin-Madison has merchant accounts which accept payment for goods sold and services rendered via payment card transactions. All merchants who accept payments via payment card must comply must comply with Policy UW-3031 and the Payment Card Industry Data Security Standards (PCI DSS). The purpose of this procedure is to provide a framework for the disciplinary steps that will be taken in the event a UW–Madison merchant account is found to be non-compliant with Policy UW-3031 and the PCI DSS. Persistent noncompliance after the enactment of the disciplinary steps described in this procedure may result in the suspension or termination of the non-compliant merchant account.

Back to top


II. Who is affected by this procedure

This procedure applies to all UW–Madison departments that accept payment cards via payment card terminals. This procedure should be understood by all relevant personnel including Divisional Business Representatives (DBRs), Site Managers, and Operators of the merchant accounts.

Back to top


III. Rationale

If a merchant does not appropriately store, process, or transmit cardholder data as defined by Policy UW-3031, deficiencies exist in that merchant account’s standard operating procedures. As a result, these deficiencies deem the merchant account non-compliant with the PCI governance framework. Deficiencies in a merchant’s ability to appropriately secure cardholder data is the foundation of a potential data breach. Acts of PCI noncompliance and data breaches may result in reputational damages, loss of customer confidence and loyalty, and a potential loss of gift and grant donors.

The ability to accept payment card transactions is a convenient and efficient method of collecting revenue owed to the University. This method of payment is a privilege granted to the University by the contracted acquirer, Elavon, and the payment card brands Visa, MasterCard, Discover, and American Express. If a merchant account is not in compliance with the PCI DSS or a data breach occurs, these agencies have the authority to assess fines for noncompliance. These fines begin anywhere between the range of $5,000 to $100,000 per month for violating PCI DSS, depending on the length of noncompliance. These fines would accumulate quickly and could result in hundreds of thousands of dollars in monetary damages.

Further, if Elavon or the payment card brands find the University noncompliant, UW–Madison’s ability to accept payment cards could potentially be revoked. This decision would require departments to find alternative ways to collect revenue and could result in a decline in sales.

Back to top


IV. Procedure

The Division of Business Services Cash Management team and Division of Information Technology (DoIT) Cybersecurity team will jointly conduct a review of campus merchant accounts’ level of compliance on an annual basis and complete a risk assessment. Each risk assessment will document the review team’s opinion of the merchant’s level of compliance with the PCI DSS. A disciplinary step would be implemented if any non-compliant practices are identified.

All risk assessments  which have a level of noncompliance will be presented to the merchant’s Divisional Business Representative for review and signature. Below are examples of possible noncompliance:

Level 0 – No instances of noncompliance identified.

Level 1 – Minor instance(s) of noncompliance identified. Compliant procedures must be implemented as of the next annual review.

  • Incomplete PCI Security Awareness Training
  • Incomplete PCI Operator Training
  • Missing or incomplete device inspection logs
  • Missing merchant standard operating procedures

Level 2 – Significant instance(s) of noncompliance identified. Compliant procedures must be implemented as of a designated deadline which has been agreed upon with the merchant.

  • Working with unsupported technology or non-approved Service Providers
  • Lack of security regarding access to physical devices and technology
  • Inability or neglect to provide documentation indicating appropriate security of e-commerce merchant accounts(s); missing the signed Service Provider’s Attestation of Compliance (AoC)
  • Unauthorized or unsecured storing of cardholder data
  • Inappropriate use of e-commerce merchant accounts or inappropriate use of in-person or over-the-phone transaction processing
  • Failure to implement appropriate procedures to resolve Level 1 noncompliance
  • Failure to complete the annual Self-Assessment Questionnaire (SAQ)

If a deficiency in compliance was identified and agreed upon by the merchant in a previous review, the PCI review team will follow up and evaluate the merchant’s progress towards achieving compliance. If measurable progress has not been made towards achieving compliance, the following disciplinary steps will be executed in this order:

  1. Requirement to attend an in-person PCI Training
  2. Notification from PCI review team of Level 1 noncompliance
  3. Notification from PCI review team of Level 2 noncompliance
  4. Temporary suspension of merchant account for up to 9 months
  5. Permanent termination of merchant account

Back to top


V. Supporting tools

Back to top


VI. Related references

Back to top


VII. Revisions

Procedure Number 3031.C
Date Approved September 1, 2020
Revision Dates Jan. 19, 2021 – Changed Procedure Number to 3031.C from 404.C

Back to top

3077.1 Shared Customer Procedure

UW-Madison Non-Sponsored AR and Billing has a shared customer file that is managed centrally by the Division of Business Services (DoBS).

Procedure #3077.1, Rev.: 7.1.20 (Effective July 1, 2020)
Related Policy:  UW-3077 Non-Sponsored Centralized Accounts Receivable Policy
Functional Owner: Director of Financial Information Management
Contact: Supervisor Central AR for Non-Sponsored Billing, (608) 890-1328, uwmsnar@bussvc.wisc.edu


Contents

  1. Procedure statement
  2. Who is affected by this procedure
  3. Procedure
  4. Related references
  5. Revisions

I. Procedure statement

UW–Madison Non-Sponsored AR and Billing has a shared customer file that is managed centrally by the Division of Business Services (DoBS). Departments can request new internal or external customers by submitting the Customer upload file. Customers can have multiple contacts and locations. Modifications to existing customer information including additional contacts or locations should be requested through the uwmsnar@bussvc.wisc.edu mailbox. DoBS will review each customer request to ensure compliance with export control lists such as OFAC.

Back to top


II. Who is affected by this procedure

Any department that is using Billing and Accounts Receivable modules in SFS for invoicing to non-sponsored customers either within the UW–Madison community or externally.

The SFS Accounts Receivable and Billing System is currently being rolled out to UW–Madison departments for all non-sponsored accounts receivable, including internal and external customers. The use of SFS for non-sponsored billing and receivables was launched in November of 2018 and will be introduced campus-wide in the coming months/years – unless otherwise agreed upon with the Division of Business Services.

Back to top


III. Procedure

The following steps represent the overall process for requesting new customers:

  1. Fill out either the Internal or External customer upload file.
  2. If the customer is already set up but a different contact or location is needed, fill out the Customer Update Form.
  3. Email to DoBS – uwmsnar@bussvc.wisc.edu.
  4. DoBS will review the customer information and ensure the customer is not on any export control lists such as OFAC.
  5. DoBS will reply via email when customers have been set up.

Back to top


IV. Related references

  • Internal Customer request form
  • External Customer request form
  • Customer Update form

Back to top


V. Revisions

Procedure Number 3077.1
Date Approved July 1, 2020
Revision Dates Jan. 19, 2021 – Procedure number updated from 100.1 to 3077.1 in new numbering system.

Back to top

3077.2 Creating a Bill Procedure

Departments are responsible for entering bills into SFS. The Division of Business Services (DoBS) will generate invoices from the bills entered. Bills can be entered as either one-time or installment. Payment terms generally will be Net30, unless an exception has been approved by DoBS.

Procedure # 3077.2; Rev.: 7.1.20 (Effective July 1, 2020)
Related Policy: UW-3077 Non-Sponsored Centralized Accounts Receivable Policy
Functional Owner: Director of Financial Information Management
Contact: Supervisor Central AR for Non-Sponsored Billing, (608) 890-1328 or uwmsnar@bussvc.wisc.edu


Contents

  1. Procedure statement
  2. Who is affected by this procedure
  3. Procedure
  4. Definitions
  5. Related references
  6. Revisions

I. Procedure statement

Departments are responsible for entering bills into Shared Financial Services (SFS). The Division of Business Services (DoBS) will generate invoices from the bills entered. Bills can be entered as either one-time or installment. Payment terms generally will be Net30, unless an exception has been approved by DoBS.

Back to top


II. Who is affected by this procedure

Any department selling goods or services for non-sponsored activities should use this procedure.

The SFS Accounts Receivable and Billing System is currently being rolled out to UW–Madison departments for all non-sponsored accounts receivable, including internal and external customers. The use of SFS for non-sponsored billing and receivables was launched in November 2018 and will be introduced campus-wide in the coming months/years – unless otherwise agreed upon with the Division of Business Services.

Back to top


III. Procedure

The following steps represent the overall process for creating a bill:

  • Use the bill upload template to import bills
  • Follow the instructions to upload bills

The following journal entries are a sample of what will post when the bills are generated:

Internal customer:

Debit: Buying Department Expense XXXX
Credit: Selling Department Revenue XXXX

External customer:

Debit: Selling Department Accounts Receivable (#6200) XXXX
Credit: Selling Department Revenue XXXX

Back to top


IV. Definitions

  • Bill – A bill is a document created when a sale is made. A bill becomes an invoice when a balance is due. For the purpose of this policy, intra-unit bills (Madison department to Madison department) never become invoices because the bill is paid at the same time the bill is created.
  • Invoice – A bill becomes an invoice when the bill is delivered to the customer and creates a balance due.

Back to top


V. Related resources

Back to top


VI. Revisions

Procedure Number 3077.2
Date Approved July 1, 2020
Revision Dates Jan. 19, 2021 – Procedure number updated from 100.2 to 3077.2 in new numbering system.

Back to top

3077.3 Cancellation or Adjustment of an invoice Procedure

Cancelations and adjustments of open invoices are processed centrally in the Division of Business Services (DoBS). Adjustments and cancelations need to include explanation for the adjustment.

Procedure #3077.3; Rev.: 7.1.20 (Effective July 1, 2020)
Related Policy: UW-3077 Non-Sponsored Centralized Accounts Receivable Policy
Functional Owner: Director of Financial Information Management
Contact: Supervisor Central AR for Non-Sponsored Billing, (608) 890-1328 or uwmsnar@bussvc.wisc.edu


Contents

  1. Procedure statement
  2. Who is affected by this procedure
  3. Procedure
  4. Definitions
  5. Related references
  6. Revisions

I. Procedure statement

Cancellations and adjustments of open invoices are processed centrally in the Division of Business Services (DoBS). Adjustments and cancellations need to include explanation for the adjustment. This procedure should not be used to write off a debt. For instructions on how to write off a debt, please refer to 3077.4 Write off and Collection Procedure. Please review the definitions section of this procedure to help determine which process to use.

Back to top


II. Who is affected by this procedure

Any department that has an invoice outstanding in the SFS AR module and has found an error in the bill.

The SFS Accounts Receivable and Billing System is currently being rolled out to UW–Madison departments for all non-sponsored accounts receivable, including internal and external customers. The use of SFS for non-sponsored billing and receivables was launched in November of 2018 and will be introduced campus-wide in the coming months/years – unless otherwise agreed upon with the Division of Business Services.

Back to top


III. Procedure

The following steps represent the overall process for requesting a cancelation or adjustment of an invoice:

  • Fill out the Invoice Cancel_Adjust Form including your signature and the signature of the reviewing party for your area.
  • Submit form to DoBS via email – uwmsnar@bussvc.wisc.edu
  • Adjustments and cancellations over $1,000 need additional review from the Dean or Director and DoBS.
  • DoBS will create a credit memo in SFS. The credit memo will be matched up to the original invoice to correct the balance due. The customer will receive a copy of the credit memo.

The following journal entries are samples of what will post after a cancellation or adjustment is processed:

Internal customer:

Debit: Selling Department Revenue XXXX
Credit: Buying Department Expense XXXX

External customer:

Debit: Selling Department Revenue XXXX
Credit: Selling Department Accounts Receivable (#6200) XXXX

Back to top


IV. Definitions

  • Cancellation – Canceling an invoice should only be used when an error has been made on the bill. An error can include the incorrect customer, contact or location identified on the bill. A duplicate bill for services already invoiced would be a good reason to cancel the bill.
  • Adjustment – Adjusting the bill should be reserved for errors in amounts invoiced. Such as charging the wrong rate for a service or the wrong quantity ordered.
  • Write-off – Write off relevant to this policy means that we cannot collect on the outstanding balance for an invoice. Types of reasons for a write off would include a customer in bankruptcy or deceased, or the debt has reached the age where we can legally no longer attempt to collect payment (statute of limitations).

Back to top


V. Related resources

Back to top


VI. Revisions

Procedure Number 3077.3
Date Approved July 1, 2020
Revision Dates Jan. 19, 2021 – Procedure number updated from 100.3 to 3077.2 in new numbering system.

Back to top

3077.4 Write off and Collection Procedure

Non-Sponsored receivable balances will be managed centrally by the Division of Business Services

Procedure # 3077.4; Rev.: 7.1.20 (Effective July 1, 2020)
Related Policy: UW-3077 Non-Sponsored Centralized Accounts Receivable Policy
Functional Owner: Director of Financial Information Management
Contact: Supervisor Central AR for Non-Sponsored Billing, (608) 890-1328 or uwmsnar@bussvc.wisc.edu


Contents

  1. Procedure statement
  2. Who is affected by this procedure
  3. Procedure
  4. Definitions
  5. Related references
  6. Revisions

Back to top


I. Procedure statement

(Non-Sponsored receivable balances will be managed centrally by the Division of Business Services.)

Once an invoice is generated the customer will receive a monthly statement. If payment is not received, the customer will receive dunning letters each month after the due date. Once the invoice reaches 90 days past due, write offs and collection activities will be managed centrally by the Division of Business Services (DoBS) in collaboration with UW–Madison divisions and departments. Write off and collection activities need to be processed timely to ensure responsible stewardship of UW–Madison resources.

Write offs and collection activities are only for External customers. All intra-unit invoices are paid immediately so no collection activities are needed.

Back to top


II. Who is affected by this procedure

Any department that has an invoice outstanding in the SFS AR module and has become a doubtful account.

The SFS Accounts Receivable and Billing System is currently being rolled out to UW–Madison departments for all non-sponsored accounts receivable, including internal and external customers. The use of SFS for non-sponsored billing and receivables was launched November 2018 and was introduced campus-wide in the following months/years – unless otherwise agreed upon with the Division of Business Services.

Back to top


III. Procedure

The following steps represent the overall process for collection efforts:

  • Statements will be sent for all outstanding invoices regardless of due date on or around the 15th of the month.
  • Dunning letters (reminder notices) will be issued by DoBS monthly on or around the 15th. Dunning letters will begin after 30 days past due and will continue to be sent until the debt is cleared.
  • At 90 days, DoBS will reach out to the billing department to discuss collections. Decision needs to be made at that time if the invoice should be sent to a collection agency, the state of Wisconsin Department of Revenue or written off. If the department is working with the customer on payment, a note can be placed on the account providing detail on the expected date of resolution.

The following steps represent the overall process for requesting a write off:

  • Write -off transactions are initiated through workflow in SFS. Follow instructions on how to initiate a write-off.
  • Write-offs over $1,000 require Dean or Director and DoBS approval.
  • Write offs must include explanation.

The following journal entry is a sample of what will post after a write off has been processed:

Debit: Selling Department contra-revenue account (#9312) XXXX

Credit: Selling Department accounts receivable account (#6200) XXXX

Back to top


IV. Definitions

  • Doubtful account – a doubtful account refers to outstanding balances that we do not expect to be paid. Typically, a doubtful account takes many things into consideration such as age of the invoice, ability to make contact with the customer or bankruptcy notification.
  • Dunning letter – The word dunning stems from a 17th century word dun which means to demand payment of a debt. Dunning letters are reminder notices that are sent periodically when an accounts receivable balance is past due.
  • Write-off – Write off relevant to this policy means that we cannot collect on the outstanding balance for an invoice. Examples of reasons for a write off would include a customer in bankruptcy or deceased, or the debt has reached the age where we can legally no longer attempt to collect payment (statute of limitations).

Back to top


V. Related resources

Back to top


VI. Revisions

Procedure Number 3077.4
Date Approved July 1, 2020
Revision Dates Jan. 19, 2021 – Procedure number updated from 100.4 to 3077.4 in new numbering system.

Back to top