How Bank Reconciliation Cutoff Works: The Alignment Mechanism

The bank reconciliation cutoff works by defining the boundary between two statement periods. The lender uses 4 variants: statement period end (most common), posting date

Most US banks use statement period end as the default, which is the last day of the monthly statement cycle.

This page covers how the bank reconciliation cutoff works: the 4 variants, the difference between posting date and transaction date, the bank holiday and weekend problem, the multi-currency complication, how the cutoff interacts with month-end close for bookkeepers, and the 3 common mistakes that lead to cutoff errors. For the broader reconciliation process, see the bank reconciliation cutoff guide and the bank statement glossary.

TL;DR. The reconciliation cutoff works by anchoring each transaction to a specific date. The 4 variants: statement period end (default, the last day of the cycle), posting date (when the bank processes the transaction), value date (when funds are available), and bank-defined cutoff (varies by institution). The cutoff matters because bookkeepers, accountants, and tax preparers all need to know which month a transaction belongs to. The cutoff is set by the bank, not the customer, which is why reconciliations typically follow the bank’s statement cycle rather than the calendar month. The 3 common mistakes: assuming posting date equals transaction date, ignoring bank holidays and weekends, and not specifying the cutoff variant in the reconciliation policy.

How the Reconciliation Cutoff Works: The 4 Variants

The reconciliation cutoff has 4 variants in the US banking system, and the right one depends on the bank’s policy and the customer’s needs. Understanding all 4 is critical because the choice affects which month each transaction counts in for accounting purposes.

Variant 1: Statement period end. The last day of the monthly statement cycle. Most US banks use this as the default. The statement period runs from the day after the previous period end to the period end date. Transactions posting during that window belong to the statement. The statement period end is typically the same day each month (e.g., the 4th, the 15th, the last day), depending on when the customer opened the account and what cycle the bank assigned.

Variant 2: Posting date. The date the bank processes the transaction, which can differ from the transaction date by 1-3 days for checks and ACH. A check written on the 28th of the month but not deposited until the 2nd of the next month posts on the 2nd (or later). For cutoff purposes, the posting date is the relevant date for “which month does this transaction count in.” This is the variant most bookkeepers use for their reconciliation work, because it matches the date the transaction actually hit the bank account.

Variant 3: Value date. The date the funds become available, which can differ from the posting date for holds, pending transactions, and check deposits. For most bank reconciliation purposes, the value date is less relevant than the posting date, but for cash flow forecasting, the value date matters because it determines when the cash actually becomes available to use. The difference is most visible with check deposits: the check posts on day 1 (when the bank processes it), but the value date is day 3-5 (when the hold clears and the funds are available).

Variant 4: Bank-defined cutoff. Some banks define a specific cutoff time (e.g., 5 PM Pacific on the last business day of the month) for certain transaction types (e.g., wire transfers). Transactions initiated after the cutoff time are processed on the next business day, which can push them into the next statement period. This is a common source of reconciliation errors for businesses that initiate wires at the end of the month. The fix: initiate month-end wires and ACH transfers at least 2 business days before the cutoff.

Posting Date vs Transaction Date: The 1-3 Day Gap

For checks and ACH transfers, the posting date is typically 1-3 days after the transaction date. The gap exists because the bank needs time to process the transaction: read the MICR line, verify the signature, confirm the funds, and update the account balance. For a check deposited at an ATM, the posting date can be the next business day. For an ACH transfer initiated on Friday, the posting date can be Monday (or later, if Monday is a holiday).

The gap matters for reconciliation because a check written on March 30 but not deposited until April 2 has a transaction date in March but a posting date in April. The bookkeeper who reconciles against the transaction date (March) will be off by 3 days from the bookkeeper who reconciles against the posting date (April). For bank reconciliation, the posting date is the right choice because it reflects when the bank actually moved the money.

For month-end close, the gap creates a specific problem: transactions initiated in the last 3 days of the month may not post until the first 3 days of the next month, which means they belong to next month for accounting purposes. The bookkeeper must either accrue these transactions (record them in the current month even though they have not posted) or accept the timing difference. Most accounting software handles the timing difference automatically by using the posting date as the transaction date in the bank feed.

The Bank Holiday and Weekend Problem

Bank holidays and weekends create a specific cutoff problem: transactions initiated on a non-business day do not post until the next business day, which can push them across the cutoff boundary. A wire transfer initiated at 4 PM on Friday the 28th (the last business day of the month) does not post until Monday the 31st, which is a different statement period if the cycle ends on the 28th.

The 11 federal bank holidays create 11 potential cutoff disruptions per year: New Year’s Day, MLK Day, Presidents Day, Memorial Day, Juneteenth, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving, and Christmas. Some holidays are widely observed (Thanksgiving, Christmas) and create 3-4 day weekends. Others are less disruptive (Columbus Day) and create 3-day weekends. The bookkeeper must account for the holiday calendar when planning the month-end close, which is why the close calendar is typically published 6-12 months in advance.

The fix: initiate month-end wires and ACH transfers at least 2 business days before the cutoff. For businesses with month-end deadlines, this means planning the wire schedule in advance rather than waiting until the last day. For bookkeepers reconciling, this means flagging any transaction that initiated before the cutoff but posted after as a “cutoff edge” and noting it in the reconciliation log. For multi-currency businesses, the holiday calendar of the destination country matters too, which is why the cutoff is more complex internationally than domestically.

Cutoff and the Bookkeeper’s Month-End Close

For bookkeepers doing month-end close, the reconciliation cutoff is the deadline for the close. The standard month-end close process is: (1) collect all transactions for the period through the cutoff date, (2) reconcile the bank statement against the books, (3) identify and resolve discrepancies, (4) post adjusting journal entries, (5) close the period in the accounting software. The cutoff is the end of step 1, but it affects all subsequent steps because any transaction that posts after the cutoff but belongs to the period is a “subsequent event” that may need to be accrued or noted.

For businesses with high transaction volume, the cutoff is typically the last business day of the month, not the last calendar day. This gives the bookkeeper a clean cut and avoids the weekend/holiday problem. For the full month-end close workflow, see the month-end close workflow page and the bookkeeper workflow page.

For multi-entity businesses, the cutoff is typically aligned across all entities so the consolidated financial statements cover the same period. If one subsidiary closes on the 30th and another on the 31st, the consolidation has a one-day gap that must be either bridged with an adjusting entry or accepted as a known difference. For the multi-e

ntity workflow, see the multi-entity reconciliation page.

Multi-Currency Cutoff

For multi-currency businesses, the cutoff determines which exchange rate to use. A transaction in euros that posts on March 31 uses the March 31 exchange rate for the financial statements, even if the customer paid in February. The cutoff is the date that matters for the rate, which means the cutoff policy must specify both the date AND the rate source (e.g., the daily rate from the Federal Reserve, the closing rate from the European Central Bank, the rate from the bank’s FX desk).

The exchange rate source matters because different sources can give different rates on the same day. The Federal Reserve rate is typically the most conservative (mid-market), the ECB rate is similar, and the bank’s FX desk rate includes a margin (typically 1-3% on top of mid-market). For financial reporting, the mid-market rate is standard. For cash flow planning, the bank’s rate is more accurate (it reflects what the business actually paid or received).

For businesses with frequent multi-currency transactions, the cutoff policy should specify the rate source explicitly and update the rate daily. Most accounting software can pull the rate automatically, which removes the manual lookup step. For the broader reconciliation process beyond the cutoff, see the bank statement reconciliation page.

The 3 Common Cutoff Mistakes

3 mistakes that consistently cause cutoff-related reconciliation errors:

1. Assuming posting date equals transaction date. For checks and ACH, the posting date can be 1-3 days after the transaction date. For wire transfers initiated at the close of business, the posting date can be the next business day. The fix: always reconcile against the posting date, not the transaction date, and flag any transactions where the difference is more than 1 day as a cutoff edge case.

2. Ignoring bank holidays and weekends. Transactions initiated on a Friday or before a bank holiday do not post until the next business day. The fix: build a 2-3 business day buffer into the close calendar, and document any transactions that post in the next period as cutoff edges.

3. Not specifying the cutoff variant in the reconciliation policy. If the reconciliation policy does not specify whether the cutoff is the statement period end, posting date, or bank-defined cutoff, different bookkeepers will use different dates, which leads to inconsistent reconciliations. The fix: write the cutoff policy into the close procedure document, and reference the same cutoff in the reconciliation workpapers.

Start with the Workflow

The fastest path is to start with the conversion step, which produces the data that every other step needs. The bank statement converter handles the PDF-to-Excel step in 2-5 minutes, with no upload to a server.

For a complete reference of the terms used throughout this article, see the bank statement glossary.

For deeper understanding, see: How Bank Reconciliation Mechanism.