# Overlapping Statement Periods in a Batch

- Author: AutoBankConvert (https://www.autobankconvert.com)
- Published: 2024-10-31
- Updated: 2024-10-31
- Category: Batch conversion
- Canonical: https://www.autobankconvert.com/blog/overlapping-statement-periods-in-a-batch

> How to handle overlapping statement periods in a batch, such as a monthly statement and a custom date range, so no transaction is posted to the books twice.
Overlapping statement periods in a batch happen when two files cover some of the same days for one account, such as a monthly statement and a custom date range download. Find the shared dates, pick one file as the source for each day, and drop the other file's lines for those days, so no transaction reaches the books twice.

## Where do overlapping statement periods come from?

Overlapping statement periods come from files that were produced in different ways for the same account. The bank's monthly statement covers a fixed cycle. Anything else a client downloads, such as a "last 90 days" activity report or a custom range, follows the dates the client typed. Put both in one batch and some days appear twice.

The common sources, in rough order of how often they turn up:

- **A custom date range plus monthly statements.** A client exports "January 1 to March 15" to answer a question, then later sends the January, February and March statements.
- **Cycles that do not match calendar months.** A statement that runs from the 16th to the 15th sits across two calendar months, and a client may also send a month-to-date download.
- **A changed statement cycle.** When a bank moves an account's cycle date, one statement may be short or long, and its dates can overlap the next one.
- **Catch-up bundles.** New clients often send everything they can find. A prospect who found you through [LinkedIn outreach for bookkeepers](/blog/linkedin-for-bookkeepers) and signed for a cleanup may hand over two years of mixed downloads in one go.

## How do you spot an overlapping statement period in a batch?

You spot an overlapping statement period by listing every file's start and end date per account and sorting them. If any file starts before the previous one ends, the two overlap. The printed opening and closing balances confirm it: a file whose opening balance does not equal the previous file's closing balance has a gap or an overlap.

A short list per account is enough. For each file, note:

1. The account ending.
2. The start and end date printed on the file.
3. The opening and closing balance.
4. Whether the file is a bank statement or a download of another kind.

Duplicate transactions are the other sign, but they are a later and noisier one. Two identical card charges on the same day can be real. Two identical periods cannot.

## Trimming overlapping statement periods to one source per day

Trimming overlapping statement periods means choosing which file is the source for each date, then keeping only that file's lines for those dates. Prefer the bank's monthly statement wherever it exists, because it has a printed opening and closing balance you can check against. Use the custom range only for days no statement covers yet.

Here is a worked example for one checking account. The dates and balances are made up.

| File | Type | Period | Opening | Closing | Keep for |
| --- | --- | --- | --- | --- | --- |
| A | Custom range download | Jan 1 to Mar 15 | 8,200.00 | 6,940.10 | Nothing once the statements arrive |
| B | Monthly statement | Jan 1 to Jan 31 | 8,200.00 | 7,615.44 | Jan 1 to Jan 31 |
| C | Monthly statement | Feb 1 to Feb 28 | 7,615.44 | 7,102.90 | Feb 1 to Feb 28 |
| D | Monthly statement | Mar 1 to Mar 31 | 7,102.90 | 6,488.25 | Mar 1 to Mar 31 |

File A overlaps all three statements. Before March's statement arrived, File A was the only source for March 1 to 15. Once File D is in hand, File A adds nothing, and every line in it would be a duplicate. The balance chain B to C to D links up with no break, which shows the statements alone cover the quarter.

If File D had not arrived yet, the right move is to keep File A's lines for March 1 to 15 only, mark them as provisional, and replace them when the statement comes in. Posting the provisional lines and then the statement on top is how the same week ends up in the books twice.

## Card statement periods that overlap a calendar month

Card statement periods overlap a calendar month because card cycles close on a fixed day that is rarely the last day of the month. A card closing on the 20th has a statement from February 21 to March 20. For a March month-end close, that statement holds eight days of February and twenty of March.

This is not double counting as long as each statement is used once. The risk comes when someone tries to "fix" the overlap by adding a custom download for March 21 to 31 and later posts April's statement over the same days. The guide to [bulk converting credit card statements](/blog/bulk-convert-credit-card-statements) covers how card cycles behave across a batch. For the month-end run as a whole, the post on [month-end batch conversion for all clients](/blog/month-end-batch-conversion-for-all-clients) shows where card cut-offs fit.

## Overlapping periods that are not double counting

Some overlaps are harmless, and removing lines from them would lose real transactions. Two files that share dates only cause double counting when they describe the same account. Files for different accounts can share every day of a month and be correct.

Leave these alone:

- **Two accounts at the same bank** on separate statements for the same month.
- **A combined statement and a separate statement** for different products, such as a checking statement and a separate card statement, both for March.
- **An old and a new account during a bank move.** A client who switches banks mid-month and keeps the old account open for a few weeks has two statements covering the same days. Each one is its own account.

The check is always the same: match the account first, then compare dates. When statements come from several institutions, the guide to [bank statements from multiple banks](/blog/bank-statements-from-multiple-banks) explains how to tell accounts apart when each bank labels them differently. AutoBankConvert checks each statement's opening balance plus transactions against its closing balance, which confirms each file is whole. Deciding which file covers which days is still a step you take before export, and [Get started](/get-started) is the place to request a spot when you want to try it on a real batch.