Authorization Date vs Capture Date in Accounting

Updated 5 November 2026 · Standard formula, shown below

For accounting, use the capture date—the date a card payment is completed or submitted for settlement—as the primary date for recording the transaction, while retaining the authorization date for reconciliation and audit history. An authorization is a temporary approval to charge; it is not proof that the money was captured or that the transaction will settle.

What authorization and capture dates mean

When a customer pays by card, the payment often passes through at least two distinct stages. First, the issuer checks the card and available funds or credit and approves or declines the request. An approved authorization generally places a hold on the account; it does not itself transfer the funds to the merchant. Later, the merchant or payment processor captures the authorized amount, requesting that the payment proceed through settlement.

The authorization date records when the approval was obtained. The capture date records when the merchant completed the charge request. The settlement or deposit date is another date: it reflects when funds are processed and may appear in the merchant’s bank account. These dates can differ, and systems may label them differently, so check the definitions used by your processor and accounting software.

Which date belongs in the accounting workflow?

For a normal completed sale, use the capture date as the transaction date in the payment record and in the reconciliation workflow. At capture, there is a completed charge to account for, subject to the processor’s settlement and any later refund, reversal, or dispute. The authorization date is valuable supporting information, but it usually should not be treated as the date of a completed payment.

This is a practical workflow rule, not a universal accounting policy. The appropriate recognition date for revenue, sales tax, or other obligations depends on the nature of the transaction and the accounting framework and policies that apply. A payment processor’s capture date does not, by itself, determine when revenue is earned. For example, a prepaid order for goods that have not yet shipped may require different revenue treatment from a completed service. Keep the payment event date distinct from the date you recognize revenue.

Authorization: record as a pending payment event or operational status, not as captured cash.
Capture: use as the primary payment transaction date for the card charge and its reconciliation.
Settlement or deposit: use to match processor payouts to the bank statement and record related timing differences or fees.

How the dates work in a real transaction

Suppose a customer places an order late on Monday. The card is authorized that evening, but the order ships and is captured on Wednesday. The processor includes the charge in a payout that reaches the merchant’s bank on Thursday. The authorization, capture, and deposit therefore fall on three different dates.

For the card-payment record, Wednesday is generally the useful transaction date because that is when the charge was captured. Monday explains when the issuer approved the request; Thursday helps explain when the cash reached the bank. If a monthly report shows a captured charge on Wednesday and a deposit on Thursday, that difference is a timing gap, not necessarily an error. Processor payout reports can bridge the captured transactions, fees, refunds, and bank deposit.

Some merchants capture immediately after authorization, making the authorization and capture dates identical or nearly so. Others capture when goods ship, when a service is completed, or in multiple partial captures. In those cases, retaining both timestamps prevents the authorization from being mistaken for a completed charge.

Choosing a date for reporting and reconciliation

Choose dates according to the question the report is meant to answer, and document the rule so reports remain consistent across periods.

Completed card sales by transaction date: group captured charges by capture date.
Bank cash received: reconcile payouts by the date funds post to the bank, using the processor’s payout detail.
Pending orders or payment activity: show authorization date and status, clearly separated from captured transactions.
Revenue and period-end reporting: follow the organization’s revenue-recognition policy rather than assuming either card date alone settles the question.

Use a consistent time zone as well. A processor may store timestamps in one zone and display them in another; a late-night transaction can consequently appear on a different calendar date in an export. Preserve the source timestamp and time-zone context where possible, and apply a defined reporting time zone rather than changing dates manually.

Common problems and misconceptions

An approval is not a completed payment. An authorization can expire, be reversed, or fail to result in capture. Treating every approval as collected cash can overstate completed sales or create reconciliation differences. Keep uncaptured approvals in a pending state and clear them according to the system’s process.

Capture does not mean the bank deposit has arrived. Settlement and payout timing can cross weekends, holidays, or month-end. A captured charge can belong in one reporting period while its payout appears in the next. Reconcile the processor’s batch or payout report to the bank instead of shifting the transaction date simply to force a match.

One authorization may lead to a different final amount. A merchant may capture less than the authorized amount, capture in parts, or make an adjustment where the payment arrangement and processor support it. Record actual captures as they occur, not the original authorized amount as if it were final. A later refund or chargeback is a separate event and should remain traceable to the original payment.

Do not confuse date fields with accounting recognition. The capture date answers when a card charge was completed through the payment flow. It does not answer every question about when goods were delivered, a service was performed, or revenue should be recognized. Keep those concepts and records separate.

Frequently Asked Questions

Should I use the authorization date or capture date for a card sale?
Use the capture date as the primary date for a completed card-payment record. Keep authorization date as supporting information for tracking the approval and investigating timing issues.

Is the authorization date the same as the transaction date?
Not necessarily. It is the date the issuer approved the request. If capture happens later, the capture date is the more relevant date for the completed charge.

Is capture date the same as settlement date?
No. Capture is the merchant’s request to complete the charge; settlement and payout occur through subsequent processing. The bank deposit may post later still.

What if authorization and capture happen on different days?
Store both dates and use the capture date for the captured-payment record. Use the authorization date to explain the earlier approval, and check time zones if the date difference seems unexpected.

Should I recognize revenue on the capture date?
Not automatically. Revenue recognition depends on the transaction and the applicable accounting policy. Capture date records a payment-processing event; it does not necessarily show when the business earned the revenue.

How should I handle an authorization that is never captured?
Do not record it as a completed card charge. Keep it identified as pending or authorized, then mark it expired, voided, or otherwise resolved using the processor’s status and your bookkeeping workflow.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.