Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

A transaction’s sale date, its processor settlement date, and the date a balance platform or bank records the funds can all differ. Reconcile by matching stable processor references and amounts first, then tracing the batch to its individual transactions—not by assuming that identical calendar dates mean identical activity.

Why one payment can have several dates

Payment records often describe different events, not competing versions of the same date. A transaction timestamp records when an event occurred; a sales-day or booking date groups it according to the processor’s configured business-day rules; a settlement date reflects when funds are allocated or paid; and a bank value date reflects the receiving institution’s treatment of the transfer.

Time zones and configured cutoffs can move activity across calendar boundaries. A transaction shortly after midnight UTC may still fall on the prior local business date, for example. Settlement can occur later because of the processor’s delay settings, weekends, holidays, scheme timing, or adjustments. A date field is useful only when its timezone and business meaning are known.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A reliable reconciliation workflow

  1. Preserve the source records

    Keep original processor exports or API events, report-generation parameters, transaction IDs, settlement batch references, amounts, currencies, and timestamps with their offsets when provided. Store derived local dates separately; do not overwrite the original timestamp.

  2. Document the account clock and cutoff

    For each processor account, record the timezone used by each report, the timezone that defines the sales day, and the configured sales-day closing time. Treat a report date as a defined business label, not as an interchangeable UTC timestamp.

  3. Choose a date range that covers the provider’s date basis

    Use the report’s documented date field and timezone to select the period. If one report uses a different timezone from the sales-day definition, include all dates that may contain records for that sales day. Do not filter only by the date shown in an order system.

    Rank #2
    Free Fling File Transfer Software for Windows [PC Download]
    • Intuitive interface of a conventional FTP client
    • Easy and Reliable FTP Site Maintenance.
    • FTP Automation and Synchronization
  4. Match the batch to the transfer

    Start with the settlement batch reference in the balance or payout record. Find the corresponding processor batch or payout entry, then compare the reference, net amount, description, and the provider-specified date field. A date-only match is weak evidence when business-day boundaries differ.

    Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  5. Reconcile the batch’s individual lines

    Use the settlement detail report or equivalent to enumerate the transactions assigned to the batch. Account for gross captures, fees, refunds, chargebacks, reversals, and other adjustments as separate lines. Do not assume a batch’s net amount equals sales captured on one calendar day.

    Rank #3
    Express Schedule Free Employee Scheduling Software [PC/Mac Download]
    • Simple shift planning via an easy drag & drop interface
    • Add time-off, sick leave, break entries and holidays
    • Email schedules directly to your employees
  6. Classify and investigate residuals

    Separate timing differences from amount differences. Check cutoff crossings, delayed settlement, weekends or bank holidays, late-arriving scheme funds, and adjustments assigned to a later batch. Escalate unmatched references or unexplained net amounts instead of forcing a date-based match.

  7. Make the process repeatable

    Store each account’s timezone, closing time, report timezone and date basis, identifier mappings, and matching rules as configuration. Monitor unmatched lines and date-boundary exceptions so recurring issues are visible and reviewable.

    Rank #4
    POS Software iOS Point of Sale System Cash Register Inventory Management Receipt Printing Order Delivery Cloud Printing for Small Businesses Retail Grocery Restaurant Coffee Shop Uber eats Door dash
    • 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

Adyen example: match its reports using their documented date fields

Adyen’s Reconcile balances documentation describes a processor-specific workflow, not a universal rule for other payment service providers. It uses a Settlement Details Report (SDR) for payment-processing batch details and a Balance Platform Statement Report (BPSR) for internal transfers.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Start from the BPSR transfer: identify the settlementBatch reference on the InternalTransfer entry and retrieve the corresponding SDR.
  • Compare the payout and transfer: match MerchantPayout to InternalTransfer using the amount, description, and BPSR Value Date against the applicable SDR date field.
  • Use the right SDR date: Adyen says the SDR date basis is the transaction booking date in the merchant-account timezone. For merchant accounts outside CET, add the Booking Date (AMS) column and use it to compare with balance-platform report dates instead of Creation Date.
  • Allow for the BPSR clock: Adyen documents that the BPSR is generated in CET. A sales day defined in another timezone can therefore span two CET calendar dates. For its worked example for July 17, 2026, Adyen instructs merchants to retrieve SDRs for July 16 and July 17.

Adyen documents 1–24 payable batches per day for merchant accounts, with each batch’s funds moving in a single internal transfer; accordingly, its documentation describes 1–24 internal transfers per day. These are Adyen operational details, not industry-wide statistics. 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.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Why daily totals can be misleading

In Adyen’s sales-day settlement model, captured funds within a local-time sales day are assigned to settlement batches associated with that sales day. Adyen describes the default sales day as midnight to midnight in the balance account’s local timezone, with the closing time configurable; settlement follows after a configured delay. A batch’s net funds can also include transaction costs, refunds, chargebacks, settlement reversals, and other adjustments, some of which may relate to a different sales day. Adyen further documents a processor-specific case in which funds not received within 30 days after capture are subtracted from the current settlement batch; that rule should not be generalized to other providers.

Settlement configuration matters. Adyen’s pass-through settlement documentation says that this model assigns sales to a batch as schemes or payment methods send funds, so one sales day’s funds may settle across several business days. It states that day totals cannot be used for reconciliation in this model; payments must instead be tracked in accounting reports. The page describes pass-through settlement as deprecated and unavailable for new integrations except for specified methods, so check the current account configuration before applying that distinction.

What to configure in a reconciliation process

For an in-house process or a tool evaluation, check whether the workflow can:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Apply per-account timezones, daylight-saving transitions, and configurable business-day cutoffs.
  • Retain transaction IDs, settlement batch references, and the original report or API payload for auditability.
  • Distinguish transaction time, booking date, sales day, settlement date, and bank value date.
  • Represent fees, refunds, chargebacks, reversals, and other adjustments explicitly.
  • Match batch payouts to transfers and then trace them to transaction lines, with reviewable exceptions.
  • Show why an item crossed a reporting date and let a reviewer reproduce the match from its source records.

These are process requirements derived from the date fields and failure modes described above, not claims about any specific software product.

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.