Neither authorization date nor capture date is the right universal date for accounting. Keep authorization, capture, processor settlement, bank posting, and the underlying sale or expense date as separate fields. For accrual accounting, recognize revenue or expense when it is earned or incurred under the applicable accounting framework; use capture and settlement records to clear processor activity, and the actual bank posting to reconcile cash.
The right treatment depends on your role, jurisdiction, accounting framework, and transaction type. The workflow below is a practical way to keep the records traceable—not a rule that one card date governs every ledger.
As an Amazon Associate I earn from qualifying purchases.
What each date records
A card payment passes through distinct events. They can occur on different calendar or business days, and they answer different accounting questions.
- Authorization date and time: The payment request is sent for issuer approval. An approval may reserve the approved amount against the cardholder’s available credit or funds. It does not mean the merchant has collected the payment or that the goods or services have been delivered. The U.S. Treasury’s Card Acquiring Service overview describes authorization and settlement as separate stages.
- Capture date and time: The merchant submits an authorized transaction for collection. Capture queues the transaction for settlement, and the captured amount may differ from the original authorization. See Authorize.net’s Payment Transactions documentation.
- Settlement or batch date: The processor or acquirer clears captured transactions, often in batches. Cutoff times and time zones can put a capture into a later business-day batch.
- Funding or bank posting date: Funds become available to the merchant or appear in the bank account. This is a cash event that can follow settlement.
- Underlying recognition date: The date the sale, service, expense, asset, or liability qualifies for recognition under the applicable accounting framework and policy. That analysis concerns what was earned, incurred, delivered, or otherwise recognized—not merely when a card was authorized.
Which date belongs in which workflow?
| Workflow purpose | Primary date or evidence | Keep as supporting fields |
|---|---|---|
| Recognize accrual-basis revenue or expense | Underlying earned, incurred, or other recognition date under the applicable framework | Authorization, capture, settlement, and funding dates |
| Track an open card approval | Authorization date and time, plus current status | Capture, void, or expiry event; processor reference; amount |
| Clear an authorized charge through the processor | Capture date and amount linked to the authorization | Batch or settlement date, fees, and adjustments |
| Reconcile a processor payout to bank cash | Processor settlement or payout report and actual bank posting | Order, authorization, and capture references |
| Reconcile a cardholder statement | Date and amount shown for the posted item on that statement | Purchase or order date and any pending authorization details |
This distinction also helps with searches such as “authorization date vs posted date” or “transaction date vs posting date”: the labels can refer to different events, so identify what the record actually represents before deciding how to use it.
A practical reconciliation workflow
- Keep separate event fields. Retain the order or transaction date, authorization timestamp, capture timestamp, processor batch or settlement date, bank funding or posting date, amount, currency, processor reference, and status. Do not overwrite one event date with another to make reports line up.
- Recognize the underlying transaction under your accounting basis. On accrual books, apply the relevant earned/incurred rules to the goods, service, expense, inventory, or advance consideration. A card authorization alone is not a substitute for that determination. The IRS explains the general tax-accounting principle for U.S. accrual-method taxpayers in Publication 538; financial reporting may be governed by different standards.
- Track authorization-only items as pending. Treat an approval as an operational hold, not settled cash or conclusive proof that a sale is complete. Monitor whether it is captured, voided, or expires. Authorize.net states that its authorization-only transactions expire after 30 days if uncaptured; that is a provider-specific limit, not an industry-wide authorization lifetime. See its support article.
- Match capture to authorization. Link the captured amount and transaction reference to the original approval. Record partial captures, amount changes, reversals, voids, refunds, and duplicates as separate events rather than obscuring them with a changed date or amount.
- Reconcile processor clearing before bank cash. Match captured transactions to the processor’s batch or settlement report, accounting for fees and timing differences. Then match the payout to the deposit actually shown by the bank. For example, the U.S. Treasury says its Card Acquiring Service offers next-day funds availability and that prior-day transactions settle to Treasury’s Federal Reserve account before 2:00 p.m. ET. Those are details of that service, not a general processor timetable; see Treasury’s service description.
- Review period-end differences. Investigate transactions where delivery or performance, capture, settlement, and funding fall in different reporting periods. Record accruals where required by your policy and framework, and retain the supporting evidence. Do not shift dates just to make the bank statement and ledger share a period.
Why authorization is not usually the recognition date
Authorization indicates an approval and may create a temporary hold. It does not establish that a merchant captured the charge, received funds, or completed the underlying sale. Conversely, a delay in capture or funding does not necessarily mean that an earned revenue item or incurred expense belongs in a later period.
For U.S. federal tax accounting, IRS Publication 538 says accrual-method taxpayers generally report income in the year earned and deduct or capitalize expenses in the year incurred, subject to the all-events test and other applicable rules. That is tax guidance, not a universal financial-reporting rule. The Federal Reserve’s Financial Accounting Manual for Federal Reserve Banks similarly describes accrual recognition as occurring when revenues are earned or expenses incurred, but its scope is Reserve Bank accounting rather than every private business.
Rank #2
Cases where specialized rules matter
- U.S. tax reporting: Apply the tax accounting method and relevant rules for the taxpayer and transaction. Publication 538 is a U.S. federal tax source; it does not decide financial-statement treatment in every jurisdiction.
- Financial asset trades: AASB 9 Appendix B distinguishes trade-date accounting, based on commitment to buy or sell, from settlement-date accounting, based on delivery of the asset. This concerns financial assets and should not be generalized to routine card purchases or operating expenses. See the AASB 9 instrument.
- Consumer credit statements: U.S. Regulation Z commentary addresses statement-date disclosure, with different treatment for in-person transactions and mail, internet, and telephone orders. Those disclosure rules are not a general-ledger recognition policy. See 12 CFR 1026.10 and its commentary.
- Processor timing: Capture cutoffs, settlement delays, authorization expiry, and funding schedules vary by provider, account configuration, and contract. Confirm the current terms and time zone for the specific service before relying on an operational timing.
What to compare when dates disagree
When two reports show different dates, first establish which event each date represents. Then check the purpose of the record, the transaction type, your accounting basis and jurisdiction, the processor cutoff and time zone, and whether capture changed the authorized amount. A statement posting date may be the right evidence for a cardholder’s statement reconciliation while being irrelevant to when a merchant recognizes revenue.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteQuick Recap
Best Value
Rank #3
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
