Avoid EOFY Reconciliation Delays: A Bookkeeper's June Survival Guide (2026)

The four most common EOFY reconciliation delays are: missing bank statements, balance discrepancies caught too late, unrecognised June transactions, and BAS deadline pressure. Convert PDF statements as they arrive through June rather than batching them all in July. Use ReckonFlow’s balance verification to catch issues before import.

The Four Causes of EOFY Reconciliation Delays

1. Late statement collection

The problem: Clients send statements in drips throughout June. You process each one as it arrives instead of batching them. By June 28, you realise three clients haven't sent anything. You chase them. They send garbled screenshots from their phone. You spend June 29 trying to OCR a photo of a laptop screen.

The fix: Set a firm collection deadline of June 20 for all clients. Send the request on June 1 with a clear message: "I need every bank statement by June 20 to guarantee your BAS is lodged on time." For repeat offenders, set up an auto-reminder schedule:

|------|--------|

This sounds aggressive, but EOFY is the one time of year where firm deadlines are expected. Clients know June is crunch time.

2. Balance discrepancies during verification

The problem: You convert a statement to CSV, import it into Xero, and the closing balance doesn't match. Now you're cross-referencing 50 transactions against the PDF trying to find the error. That's 45 minutes you don't have.

The fix: Run balance verification before conversion, not after. Every bank statement should pass this check:

```

Opening balance + total credits - total debits = closing balance

```

If it doesn't balance, stop and investigate before converting. Common causes:

- Multi-line descriptions: ANZ and CBA statements sometimes split a single transaction across two lines. If the parser only reads the first line, you'll miss half the description and potentially the amount.

- Opening balance captured as a transaction: Some parsers (and manual transcribers) accidentally include the opening balance row as a transaction. This adds a phantom debit or credit.

- Missing closing balance line: Some PDFs position the closing balance below the transaction table but outside the normal row structure. If you're scanning manually, check the statement footer.

- Pending transactions: Only import posted transactions for EOFY. Pending transactions may not appear on the statement at all, or may appear differently.

Why balance verification before import matters: A discrepancy found after import means rolling back a reconciled account. A discrepancy found before import means fixing one PDF. The second is 20x faster.

3. Wrong date format in the CSV

The problem: You export transactions from your PDF converter (or transcribe them manually) in a date format that Xero doesn't accept. Xero's CSV importer expects DD/MM/YYYY. Your CSV has MM/DD/YYYY because Excel auto-converted it based on your system locale. Every row fails validation.

The fix: Three strategies, from most reliable to least reliable:

1. Use YYYY-MM-DD (ISO 8601) in your CSV: This format is unambiguous. No matter what locale Excel or Xero uses, 2026-06-30 cannot be misinterpreted as June 30 or June 30. It's June 30. If your conversion tool supports it, use ISO dates for everything.

2. Use DD/MM/YYYY consistently: Xero AU accepts this. The trick is preventing Excel from "helpfully" converting it to MM/DD/YYYY. Open your CSV in a text editor, not Excel, before importing. If you must use Excel, import the CSV using Data → From Text/CSV and specify DD/MM/YYYY as the column format.

3. Use a tool that handles date normalisation: ReckonFlow outputs all dates as YYYY-MM-DD by default (or DD/MM/YYYY if you prefer), so the format is always Xero-safe regardless of your system locale.

EOFY-specific date trap: June 30 transactions that post on July 1 (weekend or public holiday processing) should use June 30 as the transaction date, not July 1 as the post date. Check every statement for this: it's the most common single-day date error at EOFY.

4. Forgetting to account for all bank accounts

The problem: A client has three accounts: everyday, savings, and business. They send statements for two of them. The third account has $50 in it and hasn't been used all year, so nobody thinks to include it. But Xero needs every account reconciled for the EOFY balance sheet to tie out.

The fix: At the start of June, ask each client for a complete list of their bank accounts. Not "the ones with transactions": every account. Then:

- Tick off each statement as it arrives against your account list

- Flag missing accounts after June 20

- For zero-activity accounts, request a one-page statement showing opening and closing balance (most banks provide this)

- Reconcile even dormant accounts: a $0 balance still needs a reconciliation entry

The 6-Week EOFY Reconciliation Timeline

Here's a timeline that avoids delays entirely:

Week 1 (June 1-7): Prepare

- Send statement collection email to all clients with clear format requirements

- Compile a full account list per client (including dormant accounts)

- Check your conversion tools work for all bank types you handle

- If using ReckonFlow, verify your account is set up and the correct bank parsers are active

Week 2-3 (June 8-21): Collect and convert

- Process statements as they arrive: don't batch them for later

- Run balance verification on every PDF immediately

- Convert to Xero CSV or QIF (for MYOB) format

- Name output files consistently: ClientName_Account_Period.csv

- By June 21, aim to have 80% of statements converted and ready

Week 4 (June 22-28): Import and reconcile

- Import all converted CSVs into Xero

- Reconcile each account against the bank feed (if active)

- Flag discrepancies immediately: don't defer them

- Contact clients about missing statements or balance issues

- Target: every statement imported by June 28

Week 5 (June 29 - July 3): Final check

- Run the Xero reconciliation report for each client

- Verify opening balances for the new financial year against June 30 closing balances

- Check that all accounts are reconciled (not just active ones)

- Lodge BAS for clients with June quarter deadlines

Week 6 (July 4-7): Buffer

- Handle late-arriving statements

- Process any transactions that posted after June 30 but belong to the previous financial year

- Final review before lodgement deadlines

What to Do If a Delay Happens Anyway

Even with perfect preparation, delays happen. A client goes on holiday and forgets to send statements. A bank's download portal goes down on June 28. A PDF arrives corrupted and can't be parsed.

When a delay happens, triage:

1. What's the actual deadline? Not every client needs BAS lodged by July 7. Some have quarterly BAS (July 28 deadline). Some have monthly. Check first before stressing.

2. Can you process partially? If one account's statement is missing but the other two are ready, import the three and leave the missing one for later. Don't wait for perfection.

3. Can you estimate safely? For a normal business account with predictable transactions, you can estimate the closing balance from the bank feed and reconcile with a note. Flag it for correction when the statement arrives.

4. When is the latest you can lodge? For most small businesses, a July 14 lodgement (one week late) has no penalty if the tax owed is paid by July 7. Know the rules so you can make informed decisions instead of panicking.

Tools That Prevent EOFY Reconciliation Delays

|-----------|-----------------|---------|

The most impactful combination for EOFY: use a bank feed where available (Xero syncs daily), and use a PDF converter with balance verification for statements that can't be fed automatically (historical periods, new accounts, client-provided PDFs).

Frequently Asked Questions

What causes EOFY reconciliation delays?

The four most common causes are: late client statements arriving after June 25, balance discrepancies discovered after import, wrong date formats in CSV files causing Xero import failures, and forgetting to reconcile all bank accounts (including dormant ones). Each is preventable with the right workflow.

How long does EOFY reconciliation take for a single client?

For a standard client with 2-3 bank accounts and normal transaction volume, expect 30-60 minutes total including statement collection, conversion, import, and reconciliation. Batch processing with a conversion tool reduces the mechanical work to about 2-3 minutes per account.

Can I reconcile June statements in July?

Yes: in fact, most bookkeepers process June statements during the first week of July. The key deadlines are July 7 (BAS lodgement for monthly lodgers) and July 28 (quarterly lodgers). As long as you import and reconcile before the lodgement date, you're fine. The risk is trying to do 30 clients in 3 days: which is why starting in June is smarter.

What if a client's PDF statement is unreadable?

If the PDF is a scanned image, run it through OCR first (Google Drive's built-in OCR is free and works well). If the PDF is corrupted, ask the client to download a fresh copy from their bank. If the client can only provide screenshots, you'll need to transcribe manually: and verify the balance twice.

Do I need to reconcile every single transaction at EOFY?

For EOFY lodgement, you need the opening and closing balances to match the bank statements. You don't need to categorise every transaction if the client handles their own bookkeeping. But you do need to verify that all transactions are present and no rows were missed during conversion. Balance verification handles this: if opening + credits - debits = closing, every transaction was accounted for.

Conclusion

EOFY reconciliation delays are almost never caused by a single catastrophic event. They're caused by small, predictable problems: a late statement, a wrong date format, a missed account: that compound when you're processing 20 clients in three days.

The fix isn't working faster. It's working earlier. Collect statements by June 20. Verify balances before conversion. Use tools that automate the mechanical steps so you can focus on the judgment calls. Build a 6-week timeline that gives you room to handle the unexpected.

Start now. Send that statement request email today. Every day you delay is a day you'll need in July.

Want to eliminate CSV date format issues and manual balance checks? Try ReckonFlow free: upload a June bank statement and see the balance-verified output in 30 seconds. Works with CBA, ANZ, Westpac, NAB, and Macquarie.

---

Skip the EOFY scramble next year

ReckonFlow converts and verifies bank statements automatically. Start using it before June and avoid the last-minute rush entirely.

Sign up free →