One Purchase Can Create Several Dates<\/h2>\n
A single purchase can generate multiple timestamps, including:<\/p>\n
- \n
- order or checkout time,<\/li>\n
- card authorisation,<\/li>\n
- merchant capture,<\/li>\n
- invoice creation,<\/li>\n
- card posting, and<\/li>\n
- settlement.<\/li>\n<\/ul>\n
These events do not all happen at the same moment.<\/p>\n
For example, an order may be placed at 23:58<\/strong>, authorised immediately, and captured after midnight. The order and final card transaction can therefore appear on different days even though they belong to the same purchase.<\/p>\n
The key question is not simply:<\/p>\n
\u201cWhich date is correct?\u201d<\/strong><\/p>\n
It is:<\/p>\n
\u201cWhat event does this date represent?\u201d<\/strong><\/p>\n
![\"\"](\"https:\/\/wordpress.buvei.com\/wp-content\/uploads\/2026\/09\/Card-Transaction-Dates-Explained3-1024x576.png\")
<\/h2>\nOrder, Authorisation<\/a>, and Posting Dates Explained<\/h2>\n
These three dates are often confused.<\/p>\n
The order date<\/strong> usually reflects when the customer submitted the purchase.<\/p>\n
The authorisation date<\/strong> reflects when the merchant first requested approval from the card system.<\/p>\n
The posting date<\/strong> reflects when the transaction becomes a completed card-side ledger entry.<\/p>\n
These dates can differ because merchants do not always capture payments immediately.<\/p>\n
For example:<\/p>\n
Friday:<\/strong> Order placed and card authorised
Monday:<\/strong> Merchant completes capture and the transaction posts<\/p>\nA Friday authorisation appearing as a Monday posted transaction can therefore be part of a normal payment flow.<\/p>\n
How Time Zones Affect Transaction Dates<\/a><\/h2>\n
The merchant's system may not use the buyer's local time zone.<\/p>\n
A global service may record transactions according to its:<\/p>\n
- \n
- headquarters,<\/li>\n
- billing entity,<\/li>\n
- account region,<\/li>\n
- system settings, or<\/li>\n
- UTC.<\/li>\n<\/ul>\n
That means the same event can appear on different calendar dates depending on where it is viewed.<\/p>\n
For example, a buyer in Europe may see a payment dated one day differently from a US-based merchant portal.<\/p>\n
Before treating two dates as inconsistent, check the time zone used by each system.<\/p>\n
Why Invoice Dates Can Be Different<\/h2>\n
An invoice date follows the merchant's commercial or accounting process.<\/p>\n
It may be created when:<\/p>\n
- \n
- an order is accepted,<\/li>\n
- a service period begins,<\/li>\n
- goods are shipped, or<\/li>\n
- a billing cycle closes.<\/li>\n<\/ul>\n
Because of this, the invoice date does not have to match the card posting date.<\/p>\n
For example, a subscription invoice may be dated on the final day of the billing period while the card charge is processed the following morning.<\/p>\n
Both records can be correct because they describe different events.<\/p>\n
![\"Anthropic](\"https:\/\/wordpress.buvei.com\/wp-content\/uploads\/2026\/09\/BUVEI\u5e7f\u544a\u56fe-4.webp\")
<\/a><\/h2>\nWeekends, Holidays, and Processing Delays<\/h2>\n
Digital services can activate immediately even when the final card posting happens later.<\/p>\n
For example:<\/p>\n
Saturday:<\/strong> Subscription authorised and service activated
Monday:<\/strong> Transaction appears as completed<\/p>\nWeekends, holidays, merchant capture schedules, and processing cycles can all affect when a card transaction posts.<\/p>\n
Daylight-saving changes can also shift the displayed local time even when the underlying UTC timestamp stays the same.<\/p>\n
So a difference of several hours \u2014 or sometimes one or two days \u2014 does not automatically mean something went wrong.<\/p>\n
Why Dates Matter for Month-End Reporting<\/h2>\n
Date differences become especially important around month-end.<\/p>\n
A transaction authorised in one month may post in the next.<\/p>\n
For example:<\/p>\n
December 31:<\/strong> Authorisation
January 2:<\/strong> Posting<\/p>\nIf one report uses authorisation date and another uses posting date, the same payment can appear in different reporting periods.<\/p>\n
Teams should therefore define which date is used for:<\/p>\n
- \n
- budgeting,<\/li>\n
- accounting,<\/li>\n
- expense reporting,<\/li>\n
- and card reconciliation.<\/li>\n<\/ul>\n
The important thing is consistency.<\/p>\n
Dashboard and Export Dates May Also Differ<\/h2>\n
A dashboard and CSV export can show different-looking timestamps even when they refer to the same event.<\/p>\n
For example:<\/p>\n
Dashboard:<\/strong> 10:05 CET
CSV:<\/strong> 09:05Z<\/p>\nThese can represent exactly the same moment.<\/p>\n
Before comparing timestamps, check whether:<\/p>\n
![\"\"](\"https:\/\/wordpress.buvei.com\/wp-content\/uploads\/2026\/09\/Card-Transaction-Dates-Explained1-1024x576.png\"){kind=spacer}
<\/h2>\n