How to manage vendor payments with single-use cards

A single-use card is a virtual card number created for a single transaction. Once that transaction is complete, the card automatically expires. This prevents vendors from charging the card again, blocks unauthorized use, and ensures every payment has a clean audit trail.

You can set exact amounts, link payments to specific invoices, and avoid the risk of duplicate or recurring charges.

What are single-use virtual cards for vendor payments

Single-use virtual cards are unique 16-digit card numbers generated for a specific vendor transaction. Once the payment processes, the card expires automatically. They replace checks, wires, and manual processes with a faster, more controlled payment method.

Unlike a physical corporate card that carries the same number for years, a single-use card lives and dies with a single payment. That distinction changes how you manage risk, reconciliation, and vendor relationships.

How single-use cards differ from physical corporate cards

Common use cases for vendor virtual payments

• One-time vendor purchases: Software licenses, equipment, and professional services where you need a clean, one-to-one payment record
• Subscription payments: SaaS tools where you want spend controls and the ability to cut off charges instantly
• New vendor trials: Test a vendor before committing to a recurring relationship, with zero risk of ongoing charges
• Project-based spend: Marketing campaigns, contractor payments, or any engagement with a defined budget and end date

Why finance teams use single-use cards for vendors

Single-use cards give you control, visibility, and security that checks and traditional cards can't match.

Automate payment tracking and reconciliation

Each card ties directly to a vendor, invoice, or purchase order, so transactions automatically categorize themselves. No more chasing receipts or matching payments manually. Month-end close involves fewer mismatches and less manual research.

Reduce fraud with one-time card numbers

Because the card number expires after use, vendors can't overcharge you and hackers can't reuse stolen card data. Expiring card numbers cut off the risk of repeat charges or account information leaks, which is a significant improvement over static card numbers.

Gain real-time visibility into vendor spending

You see transactions the moment they happen, not days later on a statement. This helps you catch issues early, close books faster, and maintain a direct link between the vendor, the invoice, and the transaction.

How to pay a vendor with a single-use virtual card

Paying a vendor with a single-use card takes minutes.

1. Create a new virtual card for the vendor

Generate a card through your platform by specifying the vendor name and payment purpose. Card creation takes seconds and doesn't require any physical materials or shipping.

2. Set the payment amount and expiration

Define the exact spend limit to match the invoice amount, and set when the card expires. This prevents overcharges and ensures the card can't be used after the transaction window closes.

3. Share card details with the vendor

Send the 16-digit card number, expiration date, and CVV to the vendor through a secure method. Many platforms let you email card details directly from the dashboard, so you don't need to relay numbers manually.

4. Track the transaction in real time

Once the vendor charges the card, you see the transaction immediately. The card deactivates after use, and the payment auto-matches to your records. There's nothing left to reconcile manually.

How to pay a vendor via card if they only accept ACH

Some vendors accept only ACH for payments, which can be limiting if you prefer using cards for control or tracking. In these cases, card-to-ACH conversion tools bridge the gap. This approach lets you use the visibility and controls of card payments while still meeting the vendor's ACH requirement.

How card-to-ACH conversion works

Card-to-ACH conversion enables you to pay vendors using your business card, while they receive funds in ACH format. It bridges two payment systems without adding manual work for either side.

Here's how the process works in practice:

1. You initiate payment with your card: You start by entering a payment with your business card. The payment goes through card networks as it normally would. This gives you the ability to use card controls and reporting from the start.
2. The provider intercepts the card payment: A payment processor or integrated payables platform captures your card payment and prepares to convert it. You see the charge appear on your card statement, while the vendor doesn't interact with card rails at all.
3. Conversion into ACH instructions: The processor creates an ACH instruction using the vendor's banking details that you or your ERP system already stores. The dollar amount matches your card authorization. This step ensures the vendor only ever sees an ACH transfer into their account.
4. Funds settle into the vendor account: The ACH transaction moves through the banking system and arrives as a deposit in the vendor's bank account, typically within 1 to 2 business days. From the vendor's perspective, the payment looks like any other ACH settlement.
5. Your records and controls stay intact: On your side, the payment remains logged as a card charge with all the usual benefits, including transaction-level data, category tagging, and spend controls. For accounting, the payment can be matched against the vendor invoice while still meeting the vendor's ACH requirement.

Costs and timing differences to consider

Paying a vendor through card-to-ACH conversion involves trade-offs in both cost and timing. While the method offers flexibility, it's important to understand the impact on your payment process.

• Transaction costs: ACH transfers are among the lowest-cost options, often under $1 per payment. Card-to-ACH routes can include processing fees ranging from 2% to 3% of the transaction value. For a $50,000 vendor payment, that difference can mean $1,500 in additional costs.
• Settlement speed: Standard ACH transfers settle within 1 to 2 business days. Same-day or instant ACH is available but requires cutoff times and added fees. Card-to-ACH settlements depend on the processor but often match standard ACH timing. Some platforms provide faster settlement to vendors while still charging your card immediately.
• Cash flow effects: Paying by card can extend your float by up to 30 days, depending on your billing cycle. This gives you more flexibility to manage working capital, even though the vendor sees funds through ACH on their usual timeline.
• Market scale: In 2025, the ACH network processed 35.19 billion payments, showing how deeply embedded ACH is in vendor transactions. The scale explains why most vendors continue to rely on it as their primary settlement method.

The choice between direct ACH and card-to-ACH depends on how much value you place on extended float, card-level controls, and vendor relationships compared to the higher fees.

How single-use cards improve payment security

Single-use cards are one of the strongest tools you have against vendor payment fraud. Every card is built to limit exposure from the moment it's created.

Built-in merchant restrictions and spend limits

You can lock cards to specific merchant category codes (MCCs) or vendor names. If someone tries to use the card at a different merchant, it declines automatically. Combined with exact dollar limits, this means a card can only be used for the precise payment you authorized.

Automatic card expiration after use

Once the vendor charges the card, it becomes unusable. There's no risk of duplicate charges, subscription creep, or unauthorized reuse. The card number is dead the moment the transaction settles.

Protection against vendor data breaches

If a vendor's payment systems get hacked, your exposed card number is already inactive. With traditional cards, a breach compromises ongoing access to your account. Single-use cards eliminate that risk entirely because there's nothing for an attacker to reuse.

How to map vendor payments to GL codes automatically

Vendor payments can be automatically mapped to general ledger codes when your accounting system uses rules tied to vendor information. Every time you pay a specific vendor, the expense is assigned to the correct account without manual coding.

For example, if you always pay a software subscription to a cloud provider, those charges can be routed directly to your software expense account. A logistics vendor can be linked to freight expense, and a legal partner can be mapped to professional services. By setting these rules, the system eliminates guesswork and keeps your chart of accounts consistent.

How vendor-level coding works

Vendor-level coding links each vendor in your system to a predefined general ledger account. This allows your accounting platform to classify payments automatically, creating consistency and reducing errors.

The process typically works like this:

1. The vendor is added to your system: When a new vendor is created, details such as name, category, and contract type are stored in your vendor master file
2. GL code is assigned to the vendor profile: Each vendor is linked to a default GL account. For example, a law firm may be assigned to professional services expenses, while a delivery partner is tied to transportation expenses.
3. Payment is processed: When you make a payment to that vendor, the system automatically pulls the default GL code from the vendor profile and applies it to the transaction
4. Transaction flows to the ledger: The payment is posted to the correct account without manual coding. This keeps expense classifications consistent across periods.
5. Review and adjust as needed: Finance teams periodically review vendor mappings to confirm they remain accurate. If a vendor relationship changes, the GL code is updated at the vendor level, and all future payments follow the new rule.

By linking payments to vendors in this way, you keep reporting aligned, reduce reconciliation issues, and maintain cleaner books.

Linking payments to contracts and purchase orders

Cards can tie to specific purchase orders (POs) or contracts, so spend tracks against approved budgets. When a recurring payment is tied to an approval workflow, each renewal reflects authorization from the right budget owner. This prevents outdated or duplicate subscriptions from flowing through unnoticed.

You maintain vendor compliance by keeping payments tied to valid agreements, and you improve visibility by confirming that recurring spend continues to have business value. This connection between contracts, approvals, and payments closes the loop between procurement and accounts payable.

How virtual cards integrate with your accounting system

Integration determines whether virtual cards save you time or create more work. The right setup means transactions flow into your books automatically, with no CSV exports or manual entry.

Direct ERP and accounting software connections

Most modern platforms connect directly to ERPs and accounting tools like NetSuite, QuickBooks, and Sage Intacct. Transactions sync automatically, so your ledger stays current without anyone touching a spreadsheet.

These integrations pull vendor names, amounts, dates, and GL codes into your system in real time. If you've already set up vendor-level coding rules, every synced transaction arrives pre-categorized and ready for review.

Automatic transaction syncing and categorization

Each transaction flows into your system with vendor name, amount, date, and coding already attached. Month-end close becomes faster because the data is already organized before you start your review.

This eliminates the most tedious part of reconciliation: hunting down transactions, matching them to invoices, and manually entering codes. With automatic syncing, your team spends less time on data entry and more time on analysis.

How to handle duplicate charges and other edge cases

Even with strong controls, edge cases come up.

What happens if a vendor charges a one-time card twice?

A one-time use card is designed to stop duplicate charges. Once the card processes a transaction, it becomes inactive. If a vendor attempts to charge the same card again, the transaction is automatically declined by the payment network.

The decline also protects against unintentional errors. If a vendor splits an invoice into multiple charges by mistake, only the first attempt succeeds. The result is a clear match between your invoice and your payment, with no excess activity left to investigate.

With Ramp, refunds remain valid even if a one-time card has expired or is locked, preventing stranded credits and ensuring accurate reconciliations.

Impact on your reconciliation process

When a vendor attempts to charge a one-time card twice, the failed transaction never enters your books. This prevents duplicate entries that would otherwise slow down your close. You see only the original approved payment, which keeps the link between the invoice and the transaction intact.

This structure reduces manual intervention. Without duplicate charges, you avoid time spent matching extra entries or reversing incorrect payments. Around 50% of finance leaders cite reconciliation delays as one of their top challenges during the month-end close. One-time card controls remove a common source of those delays.

Reconciliation also becomes more accurate. Each one-time card is tied to a specific vendor and invoice, so the payment record is easy to trace. If a vendor mistakenly retries a charge, the decline keeps your system aligned without creating exceptions to investigate.

Vendor side outcomes

When a vendor tries to charge a one-time card a second time, the network blocks the payment instantly. The vendor sees a decline code and no funds move. This response signals that the card can't be reused, giving the vendor immediate clarity.

For vendors, the outcome matters because it shapes how their billing and collections teams handle the situation. Instead of dealing with pending transactions or lengthy reversals, they know right away that a new payment method is required.

Here's a breakdown of what vendors experience in different situations:

For vendors, the clear signals reduce confusion and help them maintain accurate records. They avoid holding funds that may later be reversed and gain faster visibility into failed payments.

What happens if a terminated employee's card is charged?

When an employee leaves, their card is deactivated in your system. Any attempt by a vendor to charge that card fails at the authorization stage. No funds are released, and the charge doesn't post to your books.

What the vendor sees after a failed charge

When a vendor tries to bill a terminated card, the payment request is immediately declined by the network. The vendor receives an error code that identifies the card as inactive or closed. No pending transaction is created, so there's no temporary hold on funds.

Most payment processors deliver specific decline codes, such as "lost or stolen card" or "account closed," which help vendors understand that the charge can't be retried. This allows them to contact you for an updated payment method rather than submitting repeated requests.

Decline events are common in vendor billing. About 18% to 20% of recurring transactions fail due to invalid or expired cards. In the case of a terminated employee's card, the decline prevents unauthorized spending and ensures the vendor is aware that a valid replacement is needed.

Impact on your accounting records

When a terminated card is charged, the transaction never posts to your ledger. Because the authorization fails, no expense is recorded, and your books stay aligned with actual spend. This prevents reconciliation errors that would otherwise occur from charges associated with inactive employees.

The benefit is clear in audit preparation. Each declined charge ensures that no unapproved vendor payments slip into your expense accounts. Blocking these transactions keeps your documentation clean and reduces the chance of audit adjustments.

Reassigning payments to active cards

When a vendor attempts to charge a terminated card, recurring payments need to be linked to an active account so services continue without interruption. Reassignment ensures that vendor relationships remain intact while spend is tracked under the right employee or department.

The process generally follows these steps:

1. Identify recurring charges tied to the inactive card: Review past statements to spot subscriptions or vendor payments linked to the terminated employee's card
2. Select a valid replacement card: Assign the payment to a department card or to another employee who now manages the vendor relationship
3. Update payment details with the vendor: Provide the new card details to the vendor to ensure billing resumes smoothly on the correct account
4. Verify the reassignment in your system: Confirm that the payment method has been updated in both the vendor's billing portal and your accounting platform
5. Monitor the first billing cycle after reassignment: Check that the charge posts to the correct GL code and that no duplicate payments occur during the transition.

A structured reassignment process minimizes risk and ensures your financial records remain accurate.

How to reconcile prepaid vendor deposits

Prepaid vendor deposits are payments you make before receiving goods or services. They're common with vendors that require up-front commitments for materials, long-term contracts, or high-value services. Single-use cards create a clear audit trail for each deposit, making reconciliation more straightforward.

Reconciliation begins when the vendor issues an invoice. The deposit is applied against the invoice, reducing the outstanding balance.

How prepaid vendor deposits are recorded

When you make a deposit to a vendor before receiving goods or services, the payment is recorded as a prepaid asset rather than an expense. This reflects the fact that value hasn't yet been delivered. Prepaid deposits sit on your balance sheet as current assets until the vendor fulfills the order or provides the service.

For example, a $15,000 advance to a supplier for raw materials is classified as a prepaid expense. Once the materials arrive, the amount is moved from the asset account to the cost of goods sold. This shift ensures that your expenses align with the period when the benefit is received.

You benefit from tracking these deposits carefully. Each entry creates a clear link between the up-front payment and the future expense, making it easier to reconcile invoices and maintain a precise ledger.

Tracking deposits against vendor invoices

Once a vendor deposit is recorded as a prepaid asset, the next step is tracking how it offsets future invoices. Each time an invoice arrives, the deposit is applied until the balance is fully used. This creates a direct link between the initial payment and the expenses recognized over time.

For instance, if you place a $12,000 deposit for equipment, a $3,000 vendor invoice reduces the prepaid balance to $9,000. The expense portion is transferred from the asset account into the corresponding expense category. This cycle continues until the full deposit is cleared.

You also gain clearer visibility into vendor relationships. Tracking deposits against invoices reveals the amount of value you've already received and the amount that remains outstanding. This transparency supports both cash flow planning and audit readiness.

Accounting treatment during reconciliation

Reconciling prepaid vendor deposits requires moving amounts from assets to expenses as the vendor delivers goods or services. Until delivery, the deposit remains on your balance sheet as a prepaid asset. Once the obligation is met, the prepaid amount is released into the income statement as an expense.

Here's how different deposit scenarios flow through the books:

How to earn rebates on virtual card payments

Vendor payments that used to cost you money through check fees, wire fees, and processing charges can actually earn you money with virtual cards. Many platforms offer cashback rebates on card spend, turning your accounts payable workflow into an incremental revenue stream.

The math is simple. If you're moving a significant portion of vendor payments to virtual cards and earning even 1% to 1.5% back, the savings add up quickly across hundreds of monthly transactions. This is money you'd otherwise lose to wire transfer fees or check printing costs.

Automate vendor payments with Ramp virtual cards

Managing vendor payments requires ensuring that one-time cards block duplicate charges, prepaid deposits are shifted into expenses at the right time, and recurring subscriptions are mapped cleanly to the correct accounts. Each piece contributes to financial records that reflect reality, not just activity.

Strong reconciliation practices protect you from the gaps that often cause month-end delays. Closing gaps through clear rules and automated processes keeps vendor spend aligned with both contracts and budgets.

This is where automation makes the difference. By linking vendor payments to unique identifiers, mapping spend to the right GL codes, and syncing directly with your accounting system, you remove the manual work that creates errors.

Ramp's platform adds another layer of control with single-use cards, automated categorization, and real-time reconciliation. Features like these move reconciliation from a time-intensive review into a streamlined process that consistently produces clean records.

You also gain transparency that extends beyond accounting. Clean records provide a clearer view of vendor relationships, payment history, and unused deposits. That clarity reduces disputes, shortens audits, and builds trust across both internal teams and external partners.

Try an interactive demo to see how Ramp virtual cards work for vendor payments.