skip navigation

Credit Card Use Policies

This page provides detailed guidance to help local governments in Washington State develop, adopt, and update their policies for the use of credit cards by agency employees and officials, including key questions to consider and sample policies.

It is part of MRSC’s Financial Policies Tool Kit, created in partnership with the State Auditor’s Office Center for Government Innovation.

For examples of policies and code provisions authorizing local governments to accept credit card payments from customers, see our page on Credit Card Acceptance.


Many local governments allow designated staff members and officials to use credit cards for certain authorized expenses. Credit cards are most commonly used for small and incidental purchases, but they can also be used for other purchases such as travel expenses, payment of claims, or emergencies.

Many financial institutions offer a credit (or procurement) card program to local governments. This service can be bundled with the jurisdiction’s contract for other banking services, or it can be offered as a stand-alone service.

In addition, the Washington State Department of Enterprise Services maintains a purchasing agreement for Purchase Card programs which is available to any local governments that have signed a one-time contract usage agreement.

Statutory Authority

Local governments are authorized to use and contract for the issuance of credit cards for “official government purchases and acquisitions” (RCW 43.09.2855). The statute defines “credit card” as “a card or device issued under an arrangement pursuant to which the issuer gives to a card holder the privilege of obtaining credit from the issuer.”

Local government staff and officials are not authorized to use an official government credit card for personal (non-official) expenses under any circumstances, even if the individual were to immediately reimburse the agency. See the BARS Manual section on Purchase Cards (Cash Basis and GAAP manuals), as well as a 2011 informal opinion letter from the state Attorney General’s Office.

Types of Cards

When formulating your credit card policy, it is important to understand different types of credit cards that may be available to your jurisdiction:

  • Bank cards are issued by financial institutions and are accepted by a wide range of vendors for a wide variety of goods and services. Bank cards are often a Visa, Mastercard, or American Express card, issued and underwritten by the financial institution.
  • Merchant cards are issued by (or on behalf of) specific vendors such as office supply stores or vehicle fuel companies and are only accepted at those vendors. Merchant cards have much more limited uses than bank cards, but if your jurisdiction has an underlying contract for a particular type of commodity, merchant cards can be a very convenient procurement tool.
  • Fuel cards are a specific type of merchant card issued by petroleum companies and commonly used by local governments. The fuel card only works at one specific brand of gas station and is typically the result of a bid process. The card can be kept inside government vehicles and utilized by staff using that vehicle, or alternatively it can be maintained in a central office and signed out as needed. Fuel cards can also have other potential benefits such as tools to track fuel consumption.
  • Prepaid cards are purchased for their face value (such as $25 or $50), plus a possible small fee. These cards effectively serve as cash to whoever possesses the card, but they can be used effectively and provide enhanced controls in certain circumstances. Prepaid cards are slightly different than credit cards but are typically covered by the same policy.
  • Debit cards are different than credit cards. Instead of issuing credit for a purchase, a debit card typically removes money from your jurisdiction’s bank account immediately. It is our opinion that local governments in Washington are not authorized to use debit cards because the immediate withdrawal of public funds would be inconsistent with the state’s requirements for voucher review payment procedures. Having said that, some jurisdictions do use debit cards in lieu of checks for imprest/petty cash accounts. In this instance, the account being “debited” is a petty cash account established specifically for this purpose, rather than for general procurement.

These card types are not mutually exclusive – for instance, you might find that your jurisdiction needs a merchant card for certain purchases and a bank card for others. If using a bank card, keep in mind what types of cards your preferred vendors accept. For instance, Costco used to accept only American Express but then changed its policy to accept only Visa.

Key Components of a Credit Card Use Policy

The legislative body is ultimately responsible for establishing the credit card program and adequate internal controls, although oversight of the program’s daily operations and procedures is typically delegated to an administrative officer. RCW 43.09.2855 requires that the legislative body adopt a system for:

  • Distribution of the credit cards;
  • Authorization and control of the use of credit card funds;
  • Credit limits for the cards;
  • Payment of bills; and
  • Any other rule necessary to implement or administer the credit card system.

For the purposes of our guidance, we have divided credit card policies into the following three major policy areas, discussed in more detail below along with key questions to consider for each one:

  • Authorized expenses
  • Authorized users
  • Documentation, payment, and internal controls

Authorized Expenses

Your credit card policy should clearly establish what types of expenses are authorized and what expenses are prohibited. Common local government uses include:

Small and incidental purchases. The most common use of local government credit cards is for small and incidental purchases, as an alternative to petty cash funds or “open accounts” (also known as open or “blanket” purchase orders). The use of petty cash or open accounts can make it more difficult to track down the nature of an incurred expense or who incurred it – such as when petty cash was taken but not properly signed out, or when an open account was used with an unreadable signature – while using credit cards provides stronger internal controls and a clearer audit trail.

However, it is important to note that credit cards, petty cash, and open accounts are not mutually exclusive. A credit card program can be created for staff members who routinely make small and incidental purchases, while petty cash accounts can be maintained for those staff members or departments where such purchases are less common and the overhead costs of a credit card program may not make sense. In addition, open accounts are often established with vendors after a competitive procurement process, and once the bids are awarded, the goods included within the scope of the bid can potentially be purchased with a credit card.

Travel expenses. Credit cards are a common and convenient way to pay for many travel-related expenses, such as plane tickets, hotel rooms, car rentals, and conference registrations. However, using a government credit card for travel also creates potential opportunities for misuse, since it is common for traveling employees to also incur non-business expenses on their trips. (Examples include paying for a spouse to travel with the employee, incurring personal charges on the hotel bill such as movie rentals, or staying a few extra days.)

The credit card policy should reference your jurisdiction’s travel policy and clearly state that the credit card should not be used for these non-reimbursable expenses, even if the employee intends to reimburse the entity.

The use of government credit cards for business travel must comply with RCW 42.24.115, which provides requirements for fully itemized travel expense vouchers and imposes a time limit to reconcile an employee’s travel expenses on the card. In addition, it enables a “prior lien against and a right to withhold any and all funds payable or to become payable to the official.” As mentioned earlier, this does not authorize an officer or employee to intentionally incur personal expenses on the card, even if the expenses are paid back prior to the card’s statement date. However, the required audit procedure may identify expenses on the card that are not allowed by the entity’s travel policies (or law), in which case timely repayment of the disallowed amounts must be made.

Travel can also involve multiple forms of payment in addition to credit cards, making it complicated to track the various payments and reimbursements for a single business trip. In many cases, a travel pre-approval process is helpful to clarify the form of payment and/or reimbursement. For example, the City of Redmond has separate guidelines on the use of credit cards for travel purposes to help clarify these issues for employees and for audit purposes (see the examples section near the end of this page).

For more guidance on travel expenses: See our page Travel and Expense Reimbursement Policies.

Payment of claims. Some local governments have found credit cards to be effective and efficient for accounts payable types of claims. There can be a few different reasons for this.

In many cases, the credit card sponsor offers a rebate of some amount based on timely payment of the credit card balance. By incurring charges on credit cards and promptly paying the card statement or invoice promptly, some governments have recovered significant amounts of money. This is especially true when the card is used to pay for invoices that have been presented to the agency for expenses already incurred and approved for payment (i.e. pre-audited), since using the card for this purpose typically results in much larger total transactions subject to the rebate.

Vendors also appreciate prompt payment, and using a credit card is often a faster, more efficient, and perhaps less costly means of payment than generating a check or electronic payment through the normal accounts payable process.

And in some vendor management or accounts payable systems, it can be difficult to “set up” a vendor so that a payment can be processed to them through the system. In those instances, credit cards can be useful for paying “one-time” vendors that you do not expect to use often enough to be worth the time required for the full setup process. However, if you use this approach you should be careful of any related obligations that otherwise could be missed. This includes auditing the invoices in a manner consistent with the rest of your payables system to ensure the bill is properly due and payable. You may also have an obligation to provide the vendor with a 1099 form depending on the size or nature of the transaction, which you should verify with the card issuer or an accounting professional.

Emergencies. Many local governments have developed plans for how to respond to an emergency situation when traditional business tools and methods may not be available. For example, some local governments require that a purchase start with a requisition to a procurement official, but an emergency situation duly declared by appropriate officials may require more immediate access to goods or services. Staff members also may find themselves in different organizational roles during an emergency. For example, when the Emergency Operations Center (EOC) is activated, administrative staff may find themselves assigned to procurement roles, and some agencies include credit cards as part of the EOC kits available to staff in these circumstances.

In these cases, staff should have detailed instructions included with the cards regarding the necessary documentation for the card’s use. In addition, emergency procurement procedures should be part of the routine training for staff likely to be assigned to these roles when the EOC is activated.

Key questions to consider:

  • What types of expenses are authorized? Small and incidental purchases? Travel? Billing and accounts payable? Emergencies? Some cards may be authorized for multiple purposes, while others might be restricted to a single purpose (such as travel). In addition, the policy should provide guidance on using the card to procure a good or service that is subject to a contract or bid award.
  • Are prepaid cards authorized? Prepaid cards can be an efficient way to distribute agency funds in the right context, such as providing stipends for participation in a civic function (such as or judging events), civic projects (such as a neighborhood entry beautification grant), or to distribute per diem to traveling employees. (For more information on per diem, see our Travel and Expense Reimbursement Policies page.) Your agency’s policy should clearly state whether prepaid cards are authorized and, if so, the permitted uses and procedures to secure the cards (since they are essentially the same as cash).
  • What are the appropriate credit limits? Credit card policies often establish a limit for both a single purchase (for instance, $500 per purchase) and for the total amount of purchases over a time period (for instance, $5,000 per month). This limits the consequences and risk of misuse of a card.
    • Local entities will often set different limits for different staff members based on the nature of their duties. For example, the purchase limits may be higher for procurement officials or inventory managers (such as the vehicle shop or public works materials yard) than for other staff members. These limits should be reviewed periodically and should be appropriate given the actual use of the cards.
    • Many commercially available card programs also allow your entity to temporarily adjust credit limits to accommodate unique situations. For example, a business trip may prove to be more expensive than the typical limits would provide for. As part of the trip authorization, the card program administrator could set a higher limit for the card during the travel period, reverting back to the standard limits upon return. These situations should be addressed in the policy and procedures.
  • What uses should be prohibited? Most policies identify numerous types of commodities or services for which the card cannot be used, and many card programs allow the program administrator to restrict card use by commodity type. Local governments should do their best to include a complete list of unallowable items – whether prohibited under state law or other local policies – within their credit card policy. Examples of expenses that might be restricted or prohibited include, but are not limited to:
    • Cash advances (prohibited by RCW 43.09.2855);
    • Items or services for personal use;
    • Expenses incurred by a spouse, family member, or other person not authorized under the agency’s policies;
    • Alcoholic beverages;
    • Celebrations, meals, refreshments, or employee events when not consistent with agency policy;
    • Gifts or flowers for another employee that would run afoul of state laws against gifts of public funds;
    • Capital equipment;
    • Fuel for privately owned vehicles;
    • Charges made outside an employee’s approval authority;
    • “Split transactions” in which a cardholder arranges for a vendor to split a large transaction into multiple smaller transactions (for instance, to get around the per-transaction credit limit);
    • Purchases that might violate your jurisdiction’s procurement policy or ethics policy (such as purchases from vendors who might pose a conflict of interest for the purchasing employee or official); and/or
    • Purchases restricted by any other laws, policies, or guidelines (such as technology purchases, which may require prior vetting by IT staff, or promotional hosting expenses, which are prohibited for all local governments except for a limited exception for port districts).

Authorized Users

When Washington local governments first started using credit cards, most opted for shared (departmental) cards because card sponsors required the Social Security numbers of all individually named users. However, most card sponsors no longer require the SSN for individual users.

The State of Washington Office of Financial Management recommends individually assigned cards, rather than shared cards, to provide better accountability and fraud protections. However, this may not be practical for every local government in every situation. Shared cards require additional controls, as described below.

Key questions to consider:

  • Which staff members or departments will be issued cards? Many entities issue cards to individual users, often with the user’s name and the jurisdiction’s name both embossed on the card. This is especially useful for individuals who frequently purchase small items or services. Alternatively, you can use shared (departmental) cards that can be signed out as needed. Many jurisdictions use both approaches.
  • What are the cardholder’s responsibilities? Your policy and procedures should establish each cardholder’s responsibilities, including proper use and reporting, card safekeeping, and consequences related to misuse of the card or noncompliance with your entity’s policies.
  • Will non-employees (such as volunteers) be allowed to use official credit cards? If so, your policy should specifically authorize this and establish the conditions for use.
  • What are the acknowledgment and training requirements? Jurisdictions generally require card users to sign a verification form indicating that they have read the policies and agree to abide by them. In addition, many jurisdictions require card users to participate in training prior to receiving the card. This training is often two-fold: (1) rules, laws, and policies related to the use of the card, such as permitted and prohibited uses as well as verification requirements and timelines, and (2) how to use the card sponsor’s web-based tools to document transactions and reconcile expenses. If your jurisdiction uses shared cards, you should consider which employees require training.
  • How will your entity retain physical control of the cards? Your policy should emphasize that all cardholders are responsible for safeguarding the card’s security at all times and provide guidance on minimum security standards, which might include restrictions on loaning the credit card to other individuals. If a cardholder does not take enough care to retain physical control of the card, the policy may provide for appropriate disciplinary action, including potentially revoking card privileges.
    • For shared cards, which entail more risk, your entity should establish a card “sign-out” program, in which whoever takes possession of the card should sign the card out and, upon its return, sign the card back in on a record maintained by the card custodian. When the credit card statement arrives, any purchase can be traced to a date and time and then to the individual in control of the card at that time.
  • How can your jurisdiction reduce the likelihood that cards are lost or accidentally misused? For example, an interesting and creative approach is to provide a unique and distinctive card design and/or provide the card in a protective sleeve with your agency’s name, logo/seal, and contact information printed on the outside. These methods can help differentiate the card from any personal credit cards the cardholder might have in their wallet, reducing the likelihood of accidental misuse, and can also provide a method to return lost or stolen cards.

Documentation, Payment, and Internal Controls

To safeguard public funds, your credit card policy should describe the auditing and reconciliation process, along with what documentation is required (and when) to support the purchases. Your jurisdiction’s auditing officer is responsible for reviewing credit card documentation under RCW 42.24.080.

Most credit card programs provide monthly statements itemizing all purchases made with government credit cards. While many local governments pay from the statements, careful attention should be given to reconciling the detailed account activity to the statement amounts. Often there will be differences that need to be identified and documented (such as the timing of credits for returns). Your jurisdiction should not pay the credit cards directly from the statement without having a sound reconciliation process and supporting documentation for the card activity.

Each cardholder should directly review the purchases made using their card and reconcile the charges; this responsibility should not be delegated to others. Original documentation should be provided by vendors for each purchase. For travel-related purchases, documentation must be provided upon billing or no later than 30 days of the billing date (RCW 42.24.115), but timely documentation is a good idea for all credit card purchases. Disorganized or lost documentation is a common problem.

The appropriate type of documentation may depend on the exact nature of the purchase, but the documentation should be clear “on its face” (that is, without any further explanation) as to the appropriate use of the card. The typical “credit card receipt” generated by a credit card terminal is not sufficient documentation to confirm an authorized expenditure. A traditional receipt itemizing the goods or services purchased is necessary for audit purposes.

As with other payments, it is important to code the credit card activity to the correct account. To avoid the potential for “mis-coding” transactions, modern day credit card systems permit integration to your general ledger by allowing the agency to “map” (or emulate) the card account coding to the agency’s general ledger codes. Creating a base code for each cardholder will ensure that the card’s activity is captured within the right organizational element of the agency’s general ledger and to the most likely actual account (object code) to be charged for the expense. The cardholder can then review the transactions online and adjust the account to be charged if it is different than the base account.

Your jurisdiction should avoid late fees or penalties by paying the amounts due, once reconciled. Keep track of the differences in amounts not paid, such as disputed charges, and work with the vendor to avoid incurring late fees for the disputed amounts. It is best to resolve such differences in a timely manner, as too many outstanding items which are overdue for too long can complicate a correct reconciliation, lead to problems with documentation or potential penalties and late fees from the credit card vendor, and increase the credit balances on your statements which can further complicate reconciliation.

Key questions to consider:

  • What documentation will be required to support each purchase? Original documentation should be provided for each purchase and should include such standard elements as the date and time of purchase, the specific item(s) or service(s) purchased, and related details such as taxes and gratuities (if applicable). If the receipt is not clear as to the item purchased, or if the purpose of the purchased item is not clear, additional information should be provided.
    • For hotel stays, the documentation should include the above items plus the number of people, and specific details for any additional charges (such as meals or amenities such as the use of an Internet connection). For meals, itemized receipts should be provided in addition to the receipt reflecting the credit card charge and tip paid.
  • How will your jurisdiction review credit card purchases? Most credit card programs provide a monthly statement itemizing all purchases made with credit cards issued to the government. These statements are often online and can easily be distributed to the individual cardholders. Individual cardholders should review and approve all purchases made with their cards. In addition, card activity should be reviewed by an additional employee – ideally the employee’s supervisor or someone else in position to question the employee’s charges. You should also consider who is in the best position to review and question charges incurred by senior officials.
    • Care should be taken to avoid duplicate payments, such as a payment made both with a credit card (often at the time of purchase from an established vendor) and through the accounts payable process. The review process should also monitor for split purchases and enforce the transaction limits. The auditing officer should review credit card activity, just as they would for accounts payable.
  • What happens if a credit card is misused? Most government-issued cardholders will also have at least one personal credit card, which can sometimes create confusion and lead to the accidental misuse of the card. Your policy or procedures should call for identification of the misuse as early as possible, preferably before the credit card statement arrives, and require the employee to repay the amount immediately. The employee should be reminded of the agency’s policy against personal use. A one-time misuse is probably an honest mistake, but subsequent offenses may lead your agency to a different conclusion and course of action, potentially including revocation of the card and other disciplinary proceedings.
  • Are there any other internal controls that are appropriate? Your policy and procedures should also speak to any other internal controls to prevent misuse of a card. For instance, for fuel cards there should be adequate controls in place to monitor fuel usage (such as average miles per gallon for the vehicle) to ensure that the card appears to only be used for that vehicle and not for any personal vehicles. For purchases, you might restrict shipments to any other addresses besides your government’s address. Some banks also have software that enables the jurisdiction to monitor card activity real-time.

Examples of Credit Card Use Policies

Below are selected examples of credit card use policies adopted by local governments in Washington.



Special Purpose Districts

Recommended Resources

Below are some useful resources from the State Auditor’s Office (SAO), Government Finance Officers’ Association (GFOA), and other organizations to help your entity develop and update its credit card policy.

Last Modified: February 23, 2024