A transaction’s sales date, its processor settlement-batch date, and the date funds appear in a balance platform or bank can all differ. Reconcile them by following stable processor references from batch to transfer and then to transaction lines—not by matching calendar dates or daily totals alone. Timezone and cutoff rules vary by provider; Adyen’s documented reports offer a concrete example, not a universal payment-industry standard.
Why the dates do not line up
Each date may describe a different event. A transaction timestamp records when activity occurred; a processor’s business or sales date may assign it to a local accounting day; a settlement date reflects when the processor groups or releases funds; and a balance-platform or bank date may reflect a transfer or value date. These dates are related, but they are not interchangeable.
As an Amazon Associate I earn from qualifying purchases.
A processor may define its sales day using an account timezone and a configured closing time. A transaction near midnight UTC can therefore fall on a different local business date. Settlement may follow later because of the configured delay, weekends, holidays, scheme timing, or adjustments. A bank posting date can differ again.
Adyen defines a sales day as “a 24-hour period in which Adyen processes your payments.” In its sales-day settlement model, the default runs midnight to midnight in the balance account’s local timezone, but the closing time can be configured. Funds are settled after the sales day according to a configured delay. Those are Adyen-specific definitions and behaviors, not assumptions to apply to another processor without checking its documentation.
#1 Best Overall
A repeatable reconciliation workflow
- Preserve the original evidence. Keep the processor’s original report exports or API events, transaction identifiers, batch references, timestamps and offsets where supplied, amounts, currencies, and report-generation parameters. Store any derived local date separately; do not overwrite the source timestamp.
- Document the clock for each account. Record the report timezone, the timezone used to define the sales day, and the configured closing time. Treat provider date fields as labels with documented meanings, not as substitute UTC timestamps. Account for daylight-saving changes where relevant.
- Choose the period using the report’s date basis. If the report timezone differs from the account’s sales-day timezone, retrieve every report date that could contain events from the target sales day. Use the provider’s instructions for translating between the two date bases.
- Match the batch to its transfer first. Locate the settlement batch reference in the balance or payout report and identify its corresponding processor batch or payout entry. Compare the reference, net amount, description, and applicable value or booking date.
- Reconcile the batch’s transaction lines. Use settlement details to enumerate the transactions assigned to the batch. Account separately for captures, fees, refunds, chargebacks, reversals, and other adjustments; do not assume the batch is simply the total of sales made on one calendar day.
- Classify any residual. Separate timing differences from amount differences. Check cutoff crossings, delayed settlement, weekends or bank holidays, late-arriving scheme funds, and adjustments posted in a later batch. Escalate unmatched references or unexplained net amounts rather than forcing a date-only match.
- Make the rules reproducible. Store per-account timezone and closing time, report date basis, identifier mapping, and matching rules. Track unmatched lines and date-boundary exceptions so reviewers can reproduce each match from the original evidence.
Adyen example: matching BPSR transfers to SDR batches
Adyen’s Reconcile balances documentation describes a daily workflow using a Settlement Details Report (SDR) for payment-processing batch details and a Balance Platform Statement Report (BPSR) for internal transfers.
- Find the
settlementBatchreference on the BPSRInternalTransferentry. - Retrieve the corresponding SDR. If there are multiple batches in a day, Adyen says to generate an SDR per batch or use a date report that includes all batches.
- Match the SDR
MerchantPayoutto the BPSRInternalTransferusing amount and description, and compare the BPSR Value Date with the SDR Creation Date or, when applicable, Booking Date (AMS). - For an account outside CET, add the SDR’s Booking Date (AMS) column and use it to compare against balance-platform report dates rather than relying on Creation Date.
- When the BPSR sales-day dates cross CET calendar days, retrieve SDRs for both corresponding dates.
The reason for the final step is that Adyen generates the BPSR in CET, while an account’s sales day may use another timezone. Adyen’s documentation gives July 17, 2026 as a worked example requiring SDRs for July 16 and July 17. One sales day in the merchant’s timezone can thus be represented across two CET dates in the BPSR. The SDR’s date basis is the transaction booking date in the merchant account timezone; the Booking Date (AMS) field is the documented comparison field for merchants outside CET.
Rank #2
![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL160_.jpg)
- Intuitive interface of a conventional FTP client
- Easy and Reliable FTP Site Maintenance.
- FTP Automation and Synchronization
Adyen also documents 1–24 payable batches per day for merchant accounts, with the funds from each batch moving in a single internal transfer, resulting in between 1 and 24 internal transfers per day. This is an Adyen operational detail, not an industry-wide range.
Why daily totals are not enough
Even with the correct timezone, summing sales by date may not reproduce a settlement amount. Under Adyen’s sales-day model, captured funds assigned to a local-time sales day are associated with batches for that sales day, but the net batch can also reflect transaction costs, refunds, chargebacks, settlement reversals, and other adjustments. Some adjustments in a current batch can relate to another sales day. Adyen further states that if it does not receive funds within 30 days after capture, it subtracts those funds from the current settlement batch; this is an Adyen-specific rule.
Rank #3
![Express Schedule Free Employee Scheduling Software [PC/Mac Download]](https://m.media-amazon.com/images/I/41yvuCFIVfS._SL160_.jpg)
- Simple shift planning via an easy drag & drop interface
- Add time-off, sick leave, break entries and holidays
- Email schedules directly to your employees
Adyen’s separate pass-through settlement model assigns sales to a batch as schemes or payment methods send funds, so one sales day’s funds may settle over several business days. Adyen says this model does not allow reconciliation based on day totals and requires tracking payments in accounting reports. The page describes the model as deprecated and unavailable for new integrations except for specified methods. Check the current configuration and provider documentation before applying either Adyen model.
What to verify with another processor
Do not assume another PSP uses Adyen’s reports, fields, sales-day rules, or settlement timing. For each account, establish:
Rank #4
- SERVICES: This iOS POS software doesn't need any installation. As long as you have an idle pad, you can use it.It supports iOS Mac Pad. We offer professional customer service and free software updates
- SOFTWARE: Once purchased, you can enjoy 1 months of remote support and iCloud. No contracts or mandatory fees
- MULTIFUNCTION: This POS software offers a wide range of features, including ordering, customizable receipts, calculation of different tax rates, integration with multiple food delivery platforms, QR code ordering and more. It meets all your needs
- Mobile APP: With the mobile app, you can enjoy cloud backup and mobile reporting services. Check on your store anytime, anywhere—it’s simple, convenient, and easy to get started with
- EASY to USE: This POS software is compatible with various point-of-sale devices, such as cash drawers, barcode scanners, and printers. It supports cloud printing, no distance limits, you can print store receipts from anywhere. There’s no need to purchase an expensive POS cash register—saving both money and space
- Which timezone applies to each report and which one defines the provider’s business day.
- Whether the sales-day cutoff is configurable and how date fields handle daylight-saving transitions.
- Whether a report date represents transaction time, booking date, sales day, settlement date, or transfer value date.
- Which stable references connect transaction lines, settlement batches, payouts, balance transfers, and bank deposits.
- How fees, refunds, chargebacks, reversals, and late-arriving funds appear in reports.
- Whether the provider’s settlement model permits daily-total reconciliation or requires payment-level matching.
Designing a multi-processor reconciliation process
When handling multiple PSPs, keep provider-specific clock and field definitions in configuration instead of forcing every report into one generic “date” column. Preserve each original identifier and record any mapping used to connect it to an order, batch, transfer, or bank entry. A sound process distinguishes transaction time, booking date, sales day, settlement date, and bank value date, and leaves a reviewable trail for exceptions.
For a reconciliation tool or internal process, useful evaluation criteria are timezone and cutoff support per account; retention of source reports and identifiers; explicit handling of adjustments; batch-to-transfer matching followed by transaction-level tracing; and an audit trail that explains why an item crossed a reporting date. These are process requirements derived from the documented date and matching issues, not claims about any particular product.
Quick Recap
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.
