# Interbank Transfer Schedule for Year-End Cash

- Author: PreciseBankFlow (https://precisebankflow.com)
- Published: 2026-10-17
- Category: Bank statements in an audit
- Canonical: https://precisebankflow.com/blog/interbank-transfer-schedule

> How to build an interbank transfer schedule at year-end: dates out and in, books versus bank, and the patterns that point to kiting or a cutoff error.
An interbank transfer schedule lists every transfer between the client's bank accounts in the days around year-end, with four dates for each: when the paying account recorded it and when its bank cleared it, and when the receiving account recorded it and when its bank credited it. Mismatched dates reveal kiting or a cutoff error.

## What goes on an interbank transfer schedule?

An interbank transfer schedule holds one row per transfer between accounts the client controls, covering a window of roughly one to two weeks either side of the balance sheet date. Each row carries the amount, the paying and receiving accounts, and four dates. The point is to show, for every transfer, whether both sides landed in the same period.

### The columns

A standard layout has these columns:

- **Reference**, such as a check number or wire reference.
- **Amount.**
- **Paying account**, with the date the books recorded the disbursement and the date the bank paid it.
- **Receiving account**, with the date the books recorded the receipt and the date the bank credited it.
- **Conclusion**, a short note on whether the transfer was in the right period on both sides.

### Which transfers belong on it

Include every movement between accounts the entity owns or controls: operating to payroll, sweeps into a money market account, transfers to a subsidiary's account if the subsidiary is consolidated, and checks one account writes to another. The window should start a few business days before year end and run until every transfer written before year end has cleared, which is usually one to two weeks into the new year. Transfers well outside that window cannot affect the year-end balance and add only noise.

### Why the schedule exists

Transfers between accounts should net to zero in total cash. When the two halves of a transfer fall in different periods, they do not. A transfer recorded as received in December but not yet recorded as paid shows the same money in two accounts at once, and cash is overstated by the full amount. The schedule is how the auditor sees that.

## Building the interbank transfer schedule from both accounts' records

Build the interbank transfer schedule from four sources: the paying account's cash disbursements record, the receiving account's cash receipts record, and the bank statements for both accounts covering the window. Each source supplies one of the four dates. No single report from the client gives all four, which is exactly why the schedule catches what a reconciliation alone can miss.

Work in this order:

1. List every transfer in the window from the general ledger, using the transfer or intercompany cash accounts as a starting point.
2. Add any transfer that appears on a bank statement but not in the ledger. These are the rows that matter most.
3. For each row, take the book dates from the disbursements and receipts records.
4. Take the bank dates from each bank's statement, or from the statement for the period after year end that the bank sent to you.
5. Mark each date as before or after year end.
6. Write a conclusion for each row.

Every account in the schedule should also appear on the cash lead, the summary workpaper that lists each cash account and ties it to the trial balance. If a transfer runs to an account that is not on the lead, stop and find out why. The [layout and tie-outs of a cash lead schedule](/blog/cash-lead-schedule) are covered in their own guide.

### Getting the bank dates right

Use the date the bank actually posted the item, not the date printed on the check or wire request. For a check, that is the date it cleared the paying bank. For a wire or online transfer, both banks usually post on the same day, but not always across time zones or when the transfer was entered after the bank's cutoff time.

## Worked interbank transfer schedule for a December year-end

The schedule below is an example for a client with a December 31 year-end. The client name, references and amounts are illustrative, not from a real engagement.

| Ref | Amount | Paid per books | Paid per bank | Received per books | Received per bank | Conclusion |
| --- | --- | --- | --- | --- | --- | --- |
| W-501 | 40,000.00 | Dec 28 | Dec 28 | Dec 28 | Dec 28 | Same period both sides |
| Ck 3317 | 25,000.00 | Dec 30 | Jan 3 | Dec 30 | Dec 31 | Paying side outstanding; on reconciliation |
| Ck 3320 | 60,000.00 | Jan 2 | Jan 4 | Dec 31 | Dec 31 | Receipt in December, payment in January |
| W-508 | 15,000.00 | Dec 31 | Dec 31 | Jan 2 | Dec 31 | Receiving side late; cutoff error |
| Ck 3324 | 9,500.00 | Jan 3 | Jan 5 | Jan 3 | Jan 4 | Both sides January; no effect |

### Reading each row

- **W-501** is clean. All four dates fall in December.
- **Ck 3317** is a normal timing difference. Both books recorded it in December, and the check had not cleared the paying bank by December 31. It should appear on the paying account's outstanding check list, and the receiving account shows the deposit. Total cash is not overstated because the outstanding check reduces the paying account's adjusted bank balance.
- **Ck 3320** is the problem row. The receiving account recorded and deposited 60,000.00 in December, but the paying account did not record the check until January. At December 31 the same 60,000.00 sits in both accounts, and year-end cash is overstated by that amount. This is the classic kiting signature.
- **W-508** is the opposite error. The paying account recorded the wire in December, both banks posted it in December, but the receiving account's books did not record the receipt until January. Book cash is understated by 15,000.00 and the receiving account's reconciliation should carry it as a book-side item.
- **Ck 3324** falls wholly in January, so it does not affect the year-end balance.

Each of those conclusions links to a cash assertion. Ck 3320 is an existence and cutoff problem, W-508 is completeness, and the [assertions a bank reconciliation test covers](/blog/test-bank-reconciliation-assertions) explains which procedure supports each.

## Which interbank transfer patterns point to kiting?

Kiting uses the time a check takes to clear between banks to make the same money appear in two accounts. On an interbank transfer schedule it shows as a receipt recorded and deposited before year end while the matching disbursement is recorded after year end, or is missing from the paying account's books entirely.

### Signs that a pattern is deliberate

One late disbursement can be an error. These patterns make it more likely the timing was arranged:

- **Repeated round transfers** back and forth between the same two accounts in the last days of the year.
- **Checks rather than wires** for transfers that would normally move electronically. Checks create float; same-day wires do not.
- **Transfers just before year end that reverse just after**, with no business reason given.
- **Accounts at different banks**, which lengthens the clearing time compared with two accounts at the same bank.
- **A disbursement that is in the bank's records but not in the books** at year end.
- **Overdrafts covered by incoming transfers**, which suggest one account depends on the float from another.

### What to do next

Ask the client to explain each suspect transfer and show the authorization. Extend the schedule window, since a kite has to be kept going and will leave a trail of similar transfers. Get the statements directly from both banks for the extended period. Then check whether the reconciliations for both accounts list the transfer the way the schedule says they should.

Currency raises a similar double-counting risk. If the client moves cash between a till, a safe and a bank account, the [audit procedures for counting petty cash and tills](/blog/cash-count-audit-procedures) can be scheduled alongside the transfer work, so the same money cannot be counted twice in different places.

## Interbank transfer cutoff errors that are not fraud

Many mismatched rows on an interbank transfer schedule are innocent: a bookkeeper who records the receiving side when the bank notice arrives, a transfer keyed on December 31 after the bank's daily cutoff, or a month-end close that posts the second half of a transfer a day late. These still need correcting, because the year-end balance is wrong either way.

### Common honest causes

- **Posting on notification.** The receiving entity books the transfer when it sees the credit, which may be days after the paying entity booked it.
- **Bank cutoff times.** An online transfer entered late on the last business day can post the next business day, which may fall in the new year.
- **Holiday timing.** A year end on a weekend or holiday pushes bank posting into January while the books stay in December.
- **Separate bookkeepers.** When two entities keep separate ledgers, each may record the transfer on a different date.

### Correcting the error

The correction is usually an entry that moves one side of the transfer into the right period, plus a matching change to the reconciliation. For W-508 in the example, the receiving account needs an entry recording the 15,000.00 in December. If you want to practise the entries for timing items like these on a whole reconciliation, the [bank reconciliation practice problems with solutions](/blog/bank-reconciliation-practice-problems) work through them.

Record the error even when it is honest. A string of cutoff errors on transfers is a control finding about the close process, and it raises the chance that other cutoff errors exist elsewhere.

## Interbank transfers the schedule can miss

A schedule built only from the general ledger misses any transfer the books do not show. Automatic sweeps, wires initiated directly at the bank, and transfers to accounts owned by related parties outside the reporting entity can all move money without a matching ledger entry in the window. Build part of the schedule from the bank side to catch them.

### Sweeps and zero-balance accounts

A sweep arrangement moves balances automatically, often every night, between an operating account and an investment or concentration account. The books may record only a monthly summary. Read the sweep agreement, and ask the bank to confirm the year-end position of both accounts so the schedule can treat the sweep as one transfer with known dates.

### Transfers to entities outside the group

A transfer to an owner's personal account, a sister company that is not consolidated or a related lender is not an interbank transfer in the schedule's sense, because the money leaves the entity. It belongs in the disbursements testing and, often, in the related party work. Treat it as a reason to look harder, not as a row that nets to zero.

### Checking the statements line by line

The most reliable way to catch a transfer the ledger missed is to read every bank statement line in the window for each account. PreciseBankFlow extracts statement lines from digital and scanned PDFs and matches them to the ledger, so a transfer that appears at the bank but not in the books stands out as unmatched. The conclusion on whether that line is a kite, an honest late posting or something else is still the auditor's to draw.

To try those checks on your next set of year-end statements, [request early access to PreciseBankFlow](/get-started).