P-card payments: How purchasing cards work

This guide explains how p-cards work, how they compare with corporate credit and prepaid cards, and when they are the right fit for your finance team.

Key takeaways

• P-cards centralise low-value business spending and simplify settlement.

• Controls include card limits, merchant restrictions, and receipt capture.

• Corporate cards suit travel, while p-cards suit everyday purchasing.

• Prepaid cards use company funds upfront, with no credit line.

• The right option depends on supplier acceptance, VAT evidence, and data quality.

Benefits of purchase cards for finance teams

Purchase card payments let an employee buy low-value goods and services directly from a supplier using a card that the company settles centrally.

Finance therefore skips:

• The requisition.

• The supplier invoice.

• The reimbursement that would otherwise queue up before month-end.

An issuer provides a purchasing card, or p-card, to the business rather than to the person holding it.

The Institute of Commercial Payments, the industry body that succeeded the NAPCP, gives this concise definition:

“In the simplest terms, a P-Card is a charge card, similar to a consumer credit card. However, the card-using organisation must pay the card issuer in full each month, at a minimum.”

Companies typically use p-cards for indirect spend, including:

• Office supplies.

• Subscriptions.

• Temporary labour.

• Maintenance.

• Repairs.

These purchases are often too small to justify a purchase order and too frequent to run through expense reports.

That is why finance teams adopt p-cards for corporate purchasing rather than primarily for travel. Travel cards are a different instrument, covered below.

For a treasurer, the appeal is one settlement to the issuer each cycle instead of hundreds of small supplier payments to schedule.

For a finance operations manager, the benefits include:

• Fewer invoices to enter.

• Fewer claims to chase.

• More centralised payment data.

• Less manual reconciliation.

This is general guidance for UK finance teams, not tax advice. VAT treatment depends on your specific circumstances, so consult a qualified tax adviser before making decisions based on the rules covered here.

How do p-card payments work?

The issuer authorises a p-card payment like any other card payment at the point of sale.

For finance, two differences matter:

1. The issuer charges the transaction to a company account.

2. The issuer sends the organisation one consolidated invoice at least monthly.

That invoice lists every cardholder’s transactions and a grand total.

The cardholder does not owe the issuer and does not make payments personally.

The five-step payment cycle

1. Issue and configure the card

A programme administrator assigns a card to a named employee with:

• Spending limits for each purchase.

• Monthly spending limits.

• Merchant category code, or MCC, restrictions that block entire supplier categories.

2. Pay the supplier directly

The employee pays at checkout or online.

The administrator sets amount and merchant rules at network level, and the issuer applies them to each authorisation request.

The issuer declines a purchase outside those rules before the money moves.

3. Receive the transaction data

The supplier’s acquirer passes the transaction to the issuer.

The level of detail received depends on the supplier’s own systems:

• Some suppliers send only the amount and merchant.

• Others send summary tax information, often called Level 2 data.

• Some send line-item detail, often called Level 3 data.

4. Load and code the statement

You load the issuer’s transaction file into the accounting system or online portal.

Finance then assigns each line:

• A general ledger, or GL, code.

• A cost centre.

• A receipt.

• Any relevant tax information.

5. Review and settle

Someone independent of the cardholder reviews the activity.

The company then pays the issuer’s consolidated balance in full at the end of the cycle.

VAT evidence and p-card payments

In step four, finance also tests the VAT evidence.

HMRC’s VAT Notice 701/48 states:

“Ordinary purchasing, charge and credit cards do not have this capability, and statements or reports from such cards are not acceptable for VAT purposes.”

VAT Notice 701/48 explains that a card report can support input tax recovery only where:

• The card has an associated VAT invoicing capability.

• The report meets HMRC’s conditions.

• The relevant transaction details are included.

Whether your card or its reports qualify depends on how the issuer has configured the programme.

On an ordinary card:

• The statement line evidences the payment.

• The receipt or invoice is still needed to evidence the VAT.

Check the notice’s current wording against your own card setup before relying on it.

Capturing the receipt at the point of spend rather than at the end of the cycle is one of the tasks a spend management platform can support.

Spendesk’s play-by-the-rules setting can block further card spending until the required receipt is submitted. This moves the reminder into the workflow rather than into finance’s inbox.

Classic purchasing card programmes

In a classic programme, a bank extends credit and delivers transaction data through statements.

A bank or other financial institution issues the card on a Visa or Mastercard network. It sets the company’s overall credit limit based on a credit assessment of the company’s circumstances and account history.

The administrator can then divide that limit among cardholders.

Issuers may pay a rebate to the buying organisation under negotiated terms. The level depends on factors such as:

• Annual charge volume.

• How quickly the company settles.

• Average transaction size.

• Credit losses.

• The terms of the individual programme.

There is no universal published rate.

In a classic statement-driven setup, the financial controller sees a purchase when the statement file arrives rather than when the employee commits to it.

Without purchase orders in front of the card, nothing records the obligation before the supplier is paid.

That is the gap a treasurer feels when trying to separate committed spend from settled spend.

When a programme delivers data at cycle end, coding also happens in a block after the cycle closes. This creates the reconciliation crunch finance teams hate.

A transaction dated the 30th that posts on the 2nd lands in a different period, and the card report may not balance to the general ledger until someone moves it manually.

P-cards vs corporate credit cards

P-cards and corporate credit cards differ mainly in liability and intended spend.

A p-card is a central-liability card for goods and services, settled in full by the company.

A corporate credit card is usually issued for travel and entertainment. On many programmes, the employee is liable for the balance and claims the money back.

Liability and billing separate commercial card types more than the network or physical card does.

For a finance operations manager, the table describes two different workflows.

A p-card transaction arrives as a line in a statement file that accounts payable can code and match before independent review.

A corporate card transaction arrives as an expense claim with a receipt attached, often weeks after the spending occurred.

For a treasurer, the liability row is the one to read.

Central liability means cash leaves at settlement in one payment on the issuer’s date.

With individual liability, the outflow is a reimbursement run whose timing depends on when employees file their claims.

Commercial card acceptance costs

Both are commercial cards, and that classification can carry a higher acceptance cost for suppliers.

In the EU, the Interchange Fee Regulation caps consumer-card interchange while commercial cards fall outside those caps. The UK sets its own rules, so check the position there separately.

Interchange income is part of the economics behind rebates that issuers negotiate with buying organisations.

Higher acceptance costs are one reason some suppliers refuse or surcharge cards, where local surcharging rules allow it.

Because the rules may change, check the current position and the issuer’s terms before pricing a programme.

Classic corporate cards

A classic corporate card is a travel and entertainment card:

• It is issued to a travelling employee.

• It often has individual liability.

• It is typically reconciled through an expense claim after the trip.

Companies settle the balance weeks after the spending occurs, which lets them extend their working capital.

The employee has a card in hand in a foreign city, while the cost lands on finance later.

The receipt may be in a coat pocket, the claim may be filed after the trip, and the spending may be coded when the claim is approved.

A control tightened today may not take effect until next month if limit changes wait for the billing period.

Single-use virtual cards

Single-use virtual cards close part of this gap on either card type.

A card number generated for one purchase, with a fixed amount, reduces exposure compared with standing card details.

An administrator can attach the receipt requirement when issuing the card, and the platform can prompt the cardholder afterwards.

Procurement cards

Procurement card is another name for a purchasing card.

The IOCP lists ProCards, payment cards, and purchase cards as synonyms. CIPS defines a procurement card as a company-owned card for low-value purchases made without formal requisitions.

In UK usage, the term often signals a programme connected to purchasing policy.

UK central government, for example, treats procurement cards as a method of prompt payment rather than credit.

Its pan-government policy builds in separation of duties between:

• Authorisers.

• Cardholders.

• Administrators.

• Independent transaction reviewers.

The finance team usually communicates how the programme is governed through the name, policy, and controls around it.

A card called a procurement card tends to come with:

• A spend policy.

• MCC blocks.

• A named reviewer.

• A transaction file.

A card called a corporate card tends to come with an expense claim form.

Prepaid or debit cards vs credit cards

A prepaid or debit-based company card spends money the company has already loaded onto the account.

A credit-based purchasing card spends against a line the issuer extends, which the company settles after the cycle.

The funding split changes:

• Cash timing.

• Limit behaviour.

• Liability.

• Protection.

• Repayment requirements.

Funding and float

A prepaid card has no grace period.

Under the EU Second E-Money Directive, an e-money issuer may not grant credit from funds customers have loaded. The loaded balance is therefore the limit.

A credit p-card gives you a settlement window. The issuer sets the overall company limit following a credit assessment and may revise it.

Cash timing

With prepaid cards, cash leaves the operating account when the card account is topped up, before any purchase occurs.

With credit cards, cash leaves at settlement.

A treasurer forecasting weekly outflows models the two differently:

• Prepaid funding is a scheduled transfer you control.

• Credit settlement is one large debit on the issuer’s date.

Limit behaviour

A configured prepaid-card system prevents spending above the loaded balance.

The administrator controls the limit through the amount allocated.

With a credit or charge model, the issuer decides the company limit and may reduce it or suspend cards under the terms of the agreement.

Read what happens if a settlement is late before building the programme around it.

Protection if the issuer fails

Fund-protection arrangements differ by:

• Provider.

• Legal entity.

• Jurisdiction.

• Product structure.

No general rule can be given.

Check the provider’s Financial Conduct Authority register entry and cardholder agreement, or ask a specialist, before relying on any protection claim.

Liability for unauthorised use

Both funding models start from statutory defaults for lost or stolen cards.

Business agreements can change those defaults, so the issuer agreement, rather than a general rule, determines where losses fall.

Check what your issuer agreement says and confirm the position with a specialist before relying on any liability cap.

Prepaid company cards

Prepaid company cards, sometimes sold as employee debit cards, use a loaded-balance model rather than an issuer’s credit decision.

Spendesk’s smart company cards are prepaid or debit-based.

Each physical or virtual card carries its own:

• Limit.

• Approval rules.

• Receipt reminders.

The money behind it is money the company has already allocated, so the budget owner’s decision caps the spend.

Are p-cards the right payment tool for you?

P-cards suit you when:

• Most low-value suppliers accept cards.

• The issuer can feed line-level data into your accounting system.

• One monthly settlement is easier to manage than hundreds of small supplier payments.

• You can capture and review receipts consistently.

• The funding model suits your treasury requirements.

They may be less suitable when:

• Key suppliers refuse or surcharge cards.

• The statement file arrives too late to help the close.

• Transaction data lacks the fields finance needs.

• Cardholders still submit receipts at cycle end.

• The programme creates more manual work than it removes.

Work through these checks before committing to a programme.

Supplier acceptance

EU rules do not cap commercial-card interchange.

In its May 2026 call for a cap, EuroCommerce, representing European merchants, put current rates between 1.3% and 2.4%.

It described those rates as up to six times consumer-card levels.

These fees are a common reason suppliers refuse or surcharge cards.

Ask your 50 most frequent low-value suppliers before assuming acceptance.

Data quality

Level 3 detail depends on the supplier’s systems. Missing or invalid fields can drop a transaction into a higher-priced, less detailed category.

Accounting automation only helps if the card data contains the fields your bookkeeping rules expect.

These may include:

• Supplier.

• Amount.

• Tax.

• Cost centre.

• General ledger code.

• Transaction date.

Ask the issuer which fields its transaction file carries.

Receipt capture

Expense claims waste time and effort when a card was supposed to remove them.

If cardholders still email receipts at cycle end, the programme has moved the problem rather than solved it.

Look for receipt capture attached to the transaction at the point of spend.

Commitment visibility

A classic statement shows what has settled.

If treasury needs to distinguish spend before and after settlement, including approval and authorisation status across entities and currencies, the card platform must record more than the posting.

Funding model

Credit gives you:

• A settlement window.

• A single settlement.

• Potential working-capital flexibility.

Prepaid cards give you:

• A limit enforced by the loaded balance.

• Funding transfers you schedule yourself.

• No issuer credit line to manage.

Choose the model that matches how your treasury team wants outflows to behave.

How Spendesk supports p-card-style spend

If those checks point towards controls and data at the point of spend, a spend management platform is the layer to evaluate.

Spendesk is an all-in-one spend management platform consolidating:

• Company cards.

• Expense management.

• Accounts payable.

• Procurement.

• Budgeting.

For p-card-style spend, the purchasing cards carry their limits and receipt rules.

Approvals record the commitment before the card is used.

The coded transaction is then ready for the accounting export during the month rather than after the statement arrives.

Start by evaluating that capability against your:

• Controls.

• Data requirements.

• Receipt requirements.

• VAT evidence requirements.

• Accounting workflow.

If you want to explore how the workflow would run across your entities, get a free tour.

The steps a p-card removes at the front of the process, including the requisition, invoice, and reimbursement, come back at the end if the programme is only a card and statement.

Coding, receipt matching, and VAT evidence still have to happen.

The question is whether they happen:

• When the employee pays.

• In the days after the transaction.

• In a reconciliation backlog at the end of the cycle.

Treasury and finance operations want the same thing from card spend: to know what has been committed and settled, with proper evidence in place before the close begins.

A p-card programme, or a prepaid company card with similar controls, gets you there when the data and receipt travel with the transaction instead of arriving on a statement a month later.

Frequently asked questions about purchase card payments

These answers cover implementation, authentication, and VAT-reporting questions that may affect how you configure a purchasing card programme.

How long does it take to set up a purchasing card programme?

Typically, setup takes several weeks to a few months, depending on:

• ERP integration.

• Cardholder count.

• Issuer approval.

• File-transmission testing.

• Pilot requirements.

• Cardholder training.

Issuer implementation guides usually move through the following stages:

1. Research and business case.

2. Issuer selection.

3. Credit approval.

4. File-transmission testing.

5. Pilot.

6. Cardholder training.

7. Full rollout.

Connecting the transaction file to your accounting or ERP system is often the largest variable.

The IOCP recommends re-engineering the procure-to-pay process rather than bolting card processing onto existing procedures.

Ask the issuer for its file-testing timeline before fixing a launch date.

Does Strong Customer Authentication apply to purchase card payments?

A general article cannot determine whether authentication can be skipped for a particular purchase card payment.

EU and UK rules allow an exemption for some dedicated corporate payment processes, but whether your cards fall within it is for the issuer to decide.

Check the cardholder agreement or contact the issuer directly before assuming an exemption applies.

What information must a VAT-compatible purchasing card report contain?

A VAT-compatible report must contain the information HMRC requires for the relevant supply.

This includes:

• The value and description of the supply.

• The VAT amount and rate.

• The time of supply.

• Supplier details.

• The supplier’s VAT number.

• The customer’s name and address.

Confirm that your issuer’s report includes the required fields before using it as evidence for input tax recovery.

What happens when a purchase card transaction exceeds £5,000?

Under HMRC’s VAT Notice 701/48, a full VAT invoice is expected where a single purchasing-card transaction exceeds £5,000.

The card report should not be treated as sufficient evidence for those transactions. The workflow should therefore capture and retain the full invoice.

How the threshold applies depends on the card arrangement and your circumstances. Confirm the current notice wording with a qualified tax adviser before relying on it for input tax recovery.