What is a card program? How do you define it? You could measure the number of card holders and the number of issued cards or you could track the number of transactions and the total amount of spend over an arbitrary period of time. The policy, often the focal point of card program, could be the definition itself. What is the policy though other than a list of guidelines and rules that your card holders must adhere.
How do you manage your p-card policy? How do you notify your users of updates? How do you know that your policy is being actively enforced? How do you manage exceptions? What do you do when a card holder violates policy? How do you review transactions to find those not-so-obvious violations? How do you know that your policy is effective?
How do you communicate with your card holders about program or policy itmes? Email? Phone? Walk-up? How do they communicate with you? What happens when a card is lost or a limit needs to be increased? Is your assistance and approval required by your card holders for various card related tasks? What information is required to properly document a policy violation?
All of these questions and many others only start to scratch the surface of what it takes to successfully manage a card program. Over the next several weeks we plan to explore in detail what components makes up a typical card program and how a program admnistrator can make doing so as painless and rewarding as possible by utilizing Solerent’s flagship product ProcuREview.
If you enjoyed this article, please consider sharing it!
Datasheets
