Accounting Close — Daily Progress Report During Close Week

When close week starts, most owners stop seeing the details. They get a calendar reminder that says "close by Friday" and nothing until the books are either done or late. By then, the only question left is who to blame.

Definition: Accounting close

The period at the end of a month, quarter, or year when the finance team finalizes all transactions, reconciles accounts, and prepares financial statements.

Definition: Daily progress report

A short, written status note sent at the end of each workday during close week that covers completed tasks, open items, and blockers.

Definition: Controller

The senior finance lead responsible for the accuracy of the books, the close timeline, and sign-off before statements go to the owner or external stakeholders.

What to include in a daily close-week report

A daily progress report during close week should answer three questions: what was closed today, what is still open, and what is blocking the team. Keep it to one screen.

Daily section

• Date and close day (for example, Day 3 of 5)
• Completed reconciliations and journal entries
• Accounts still open (AP, AR, payroll, accruals, prepaids)
• Items waiting on other departments or external parties
• Blockers with owner and needed resolution time
• Plan for tomorrow

Example good vs bad

Bad: "Working on accruals. Almost done."

Good: "Accruals: 4 of 6 departments submitted. Waiting on marketing for Q3 event spend. Plan: post accruals tomorrow morning if marketing replies by 4 PM."

Bad: "No updates today."

Good: "Bank rec complete. Payroll posted. AR aging review in progress — 12 invoices over 60 days need controller sign-off."

How the owner reads this report

The owner does not need to know every journal entry. They need to know whether close will happen on time and what could stop it. A daily progress report gives them that signal early enough to act.

If the report shows the same blocker two days in a row, the owner knows to intervene before Friday. If the report is missing, the owner knows the team is underwater before the deadline passes.

Tool tip (AiAdvisoryBoard.me): During close week, run the same Plan → Fact → Gap rhythm you use for operations. Plan what should close today, record the fact of what actually closed, and surface the gap before it becomes a missed deadline. See how the 7-day diagnostic surfaces this visibility across the company: https://aiadvisoryboard.me/?lang=en

Copy/paste template

# Accounting Close — Daily Progress Report
Date: YYYY-MM-DD | Close day: X of Y

## Completed today
- [Task] — [Account/area] — [Status]
- [Task] — [Account/area] — [Status]

## In progress
- [Task] — Owner: [Name] — Expected completion: [Time/date]
- [Task] — Owner: [Name] — Expected completion: [Time/date]

## Blocked
- [Item] — Blocked by: [Person/team] — Needed by: [Time]
- [Item] — Blocked by: [Person/team] — Needed by: [Time]

## Waiting on others
- [Department] — [Item] — Last follow-up: [Date]

## Plan for tomorrow
- [Task]
- [Task]

## Owner attention needed
- [Yes/No] — [What and why]

Cadence and timing

Send the report at the same time every day — ideally at the end of the finance team's workday, before the owner starts their evening review. During a five-day close, that means five short reports. The consistency matters more than the length.

If close week includes a weekend or holiday, adjust the cadence but do not skip a day without telling the owner why. Silence during close week reads as a problem.

Common close-week blockers

• Waiting on department heads for expense submissions
• Bank statements not yet available
• Payroll data pending from HR
• Accruals missing from operations
• Intercompany transactions not reconciled
• External auditor questions outstanding

Each blocker should name the person who can unblock it and the time by which the finance team needs an answer. A blocker without an owner is just a complaint.

Micro-case (what changes after 7–14 days)

A 90-person professional services firm used to discover close delays on the last day of the month. The controller started sending the daily progress report above at 5 PM each close day. On day two, the report showed payroll data was still missing from HR. The owner saw it that evening, sent a reminder, and payroll posted the next morning. Close finished on time for the first time in two quarters. The owner did not micromanage the accounting team; they simply saw the gap early enough to remove it.

Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

FAQ

Who should send the daily progress report during close week?

The controller or the senior accountant running the close. If the finance team is small, the person responsible for the close timeline should own it.

How long should the report be?

Short enough to read in under two minutes. One screen, bullet points, no narrative paragraphs.

What if nothing changed today?

Say so explicitly, and list what is still in progress. "No new completions" is a valid status if the open items and blockers are clear.

Should the report go to the whole company?

No. Send it to the owner, the controller, and any department heads whose input is needed. Close-week status is finance operations, not all-hands content.

Can this replace the month-end close checklist?

No. The daily progress report tracks status during close week; the checklist tracks the actual accounting work. Use both.

Close week is not the time to discover that the books will not close. A daily progress report makes the status visible while there is still time to fix it. Start tomorrow with the template above, send it at the same time each day, and watch how quickly the owner stops asking for updates.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works: https://aiadvisoryboard.me/?lang=en