Eshelman School of Pharmacy: P-Card Workflow

Summary

This Procedure establishes the step-by-step process for submitting and approving P-Card transactions at the Eshelman School of Pharmacy, including receipt submission and monthly reconciliation deadlines. It also sets out a tiered disciplinary framework for infractions such as missing receipts, invalid justifications, or split transactions.

Body

Unit Procedure

Title

Eshelman School of Pharmacy: Procedure for Purchases Using P-Cards

Introduction

Purpose

The purpose of this document is to explain the required steps involved in reconciling P-Card purchases.

Scope

This Procedure applies to Eshelman School of Pharmacy P-Card holders.

Procedure

Pharmacy P-Card Workflow

  1. Cardholder purchases an item.
  2. Cardholder scans the receipt and submits a P-Card Submittal request into TeamDynamix. If the receipt came via email, please submit that as an attachment when submitting the request. The request requires both the chartfield string to charge and the business justification for the charge. A P-Card Receipt Submittal Form is optional and can accompany each receipt submission.
  3. Procurement staff will upload receipts and update charges in the P-Card Works system by adding transaction data and the chartfield string.
    1. Reminder emails are sent each Tuesday to notify cardholders of transactions lacking a receipt
    2. Additional reminder sent on the 19th of each month.
  4. Accounting staff update the default chartfield string when needed and approve/reject the transaction(s).
  5. Each monthly P-Card cycle runs from the 16th to the 15th. Charges must be approved by the 20th to post.

The University's Policy on P-Card Infractions includes:

  1. Failure to reconcile transactions prior to the 1st of the month following the end of the billing cycle. Account will be suspended until all outstanding transactions are reconciled.
  2. Failure to provide a valid business justification for purchase (i.e. reason for purchase).
  3. Splitting transactions to circumvent transaction limits.
  4. Failure to supply valid receipt, invoice, or other support documentation.
  5. Using P-Card to purchase non-allowable items per the P-Card policy or misuse of any temporary exception to Purchasing Card restrictions.
  6. Other infractions warranting disciplinary actions, as deemed appropriate by P-Card Administrator or the Accountholder’s Business Manager or Department Head.

1st Offense - Courtesy email warning to Accountholder, Group Approver and Accountholder's direct supervisor

2nd Offense - Email notification of infraction to Accountholder, Accountholder's direct supervisor, unit Business Manager, and MOU Financial Lead or Dean

3rd or Greater Offense - Immediate thirty (30) to ninety (90)-day suspension of Accountholder's P-Card.

NOTE: The P-Card team reserves the right to reduce or escalate disciplinary actions at its sole discretion.

Time Period: Rolling 12 Months.

Abuse and Fraud Rule (Personal purchase made intentionally)

  1. Immediate revocation of P-Card. The Accountholder, Group Proxy Reconciler, Group Approver, Direct Supervisor, MOU Lead and Dean or Department Head will receive an email notification.
  2. Department Head or Dean is responsible for taking appropriate disciplinary action after consulting with Human Resources, up to and including termination of employment.

Related Requirements

External Regulations

Contact Information

Primary Contact

Name: Matt Rivenbark

Title: Executive Director of Finance and Facilities Services

Telephone: 919-966-7558

Email: jmriven@unc.edu

Other Contacts

Name: Pam Morrison

Title: Director of Finance

Telephone: 919-843-2499

Email: pamm@unc.edu

Details

Details

Article ID: 161030
Created
Mon 3/23/26 1:19 PM
Modified
Mon 7/27/26 2:57 PM
Responsible Unit
School, Department, or other organizational unit issuing this document.
Eshelman School of Pharmacy
Issuing Officer
Name of the document Issuing Officer. This is the individual whose organizational authority covers the policy scope and who is primarily responsible for the policy.
Next Review
Date on which the next document review is due.
05/01/2027 12:00 AM
Last Review
Date on which the most recent document review was completed.
07/01/2026 12:00 AM
Last Revised
Date on which the most recent changes to this document were approved.
07/01/2024 12:00 AM
Effective Date
If the date on which this document became/becomes enforceable differs from the Origination or Last Revision, this attribute reflects the date on which it is/was enforcable.
07/01/2024 12:00 AM
Flesch-Kincaid Reading Level
10.4