What's a year end close checklist and which one can you use today?
This year end close checklist is a free Excel template with 40 tasks, owners and business-day due dates. It shows what's done, open and overdue, so nothing slips between your auditors and the ERP lock. A filled-in example and a short how-to come with it.
Enter your work email in the form and the Excel workbook arrives in your inbox, with 40 year-end tasks, a status for each, a progress summary and a worked example.
Excel workbook · 40 tasks · works in Excel and Google Sheets
Not there in a few minutes? Check spam, or .
Six steps, about 20 minutes. Do them the week before fiscal year end, not the week after.
Type the date once. Every due date in the workbook is counted in business days from it, weekends excluded, from four weeks before year end to five weeks after. The template counts weekends only, so add your own holiday adjustments by hand.
Every one of the 40 tasks needs one person, not a team. 'AP' is not an owner. 'Dana, AP lead' is. Unowned tasks are the ones that go overdue.
No inventory? Remove the physical count and cut-off rows. No foreign currency? Drop the revaluation row. A checklist you trust beats a long one you ignore.
Each task has a status dropdown. Done rows turn green. Rows past their due date and not done turn red. Update status daily during the close, in the same ten minutes as your stand-up.
The summary counts done, open and overdue tasks and gives a percent complete. Send that one line to your CFO. It replaces the 'where are we?' emails.
The example workbook is filled in for a fictional company at business day 5. Compare your own sheet with it to see what a healthy close looks like at the same point.

A year end close is a dated, owned sequence of cut-off, reconciliation, adjustment, review and lock steps. These are the groups in the template, in the order they run.
The template ships with an example for Northwind Distribution Inc. (illustrative). Fiscal year ended Thursday 31 Dec 2026. The status below is as of 7 Jan 2027, business day 5 as the template counts it (weekends only; 1 Jan is not excluded).
| Line in the example | What it shows |
|---|---|
| Overall status | 40 tasks: 13 done, 27 open, 1 overdue. 33% complete. |
| Planning (done) | Timetable with auditors on day -20. PBC list and count scheduling on day -15. Next-year periods and W-9s on day -10, with 3 vendors still missing a W-9. |
| Physical count (done) | Counted on 31 Dec. Variance was 0.4% of value, and two bins were recounted. |
| Bank, count adjustments, AR (done) | Bank reconciliations finished, count adjustments posted and AR posting complete. |
| Fixed assets and payroll (done) | Asset additions and depreciation posted, payroll accruals booked. |
| Overdue (red) | Accrue goods received not invoiced and reconcile AP, due business day 4. Two receipts are disputed with the vendor and credit notes are still awaited. |
| Tax provision | Due day 12. |
| Audit adjustments and statements | Due day 15. |
| Board review | Due day 18. |
| ERP year-end close | Due day 20. |
| Representation letter and archive | Due day 25. |
Everything above is in the workbook itself. Replace the example dates and owners with yours and the colors and percentages update.
Here are six entries a controller will recognise. The amounts are illustrative and are not in the template, which tracks tasks rather than postings. They show why each task exists.
Bank fees. Bank balance per statement is 425,900. Add deposits in transit of 2,650, deduct outstanding checks of 16,200 and you get 412,350. The ledger shows 412,500 because 150 of fees were never booked. Debit Bank charges 150, credit Cash 150. Cash goes from 412,500 to 412,350 and ties.
Accrued expense. The December utility bill of 6,200 arrives in January. Debit Utilities expense 6,200, credit Accrued expenses 6,200. Expenses rise and liabilities rise by the same amount.
Prepaid release. A 24,000 annual insurance policy was paid on 1 July. Six months are used. Debit Insurance expense 12,000, credit Prepaid insurance 12,000. The prepaid balance falls to 12,000.
Depreciation. A delivery truck costs 90,000 over 5 years with no salvage value, so straight-line depreciation is 18,000 a year. Debit Depreciation expense 18,000, credit Accumulated depreciation 18,000.
Bad debt allowance. Receivables are 1,200,000. Management sets the allowance at 1.5%, which is 18,000, against an existing 9,000. Debit Bad debt expense 9,000, credit Allowance for doubtful accounts 9,000. The percentage is a judgment, so keep the support with the entry.
FX revaluation. A EUR 50,000 payable was booked at 1.0800, which is 54,000. At year end the rate is 1.1000, so it's 55,000. Debit Unrealized FX loss 1,000, credit Accounts payable 1,000.
Net effect. Pre-tax income falls by 46,350 (150 + 6,200 + 12,000 + 18,000 + 9,000 + 1,000). The trial balance still balances, because each entry has equal debits and credits. If it doesn't, you have a one-sided entry.
Names and menus change by version, so confirm against the vendor pages in the sources below before you run anything that can't be reversed.
| ERP | How the year closes |
|---|---|
| Dynamics 365 Business Central | Post your adjustments first. On the Accounting Periods page, use Close Year; Microsoft's documentation states that a closed fiscal year can't be reopened. Then run the Close Income Statement batch job, which creates entries that cancel the balances of income statement accounts. You post that journal yourself, and the result moves to the balance sheet and retained earnings. Control who can post into old dates with Allow Posting From and Allow Posting To in General Ledger Setup (and user setup). |
| Dynamics GP | Close the subledgers first: Inventory, Receivables, Payables and Fixed Assets each have their own year-end procedure. Set up the next fiscal year in Fiscal Periods Setup. Then run Tools, Routines, Financial, Year-End Closing and name the retained earnings account. Microsoft's guidance is to back up first, because the routine changes balances. |
| NetSuite | Go to Setup, Accounting, Manage Accounting Periods and open the period close checklist. Work the tasks in order, lock AR, AP and payroll, then use Lock All. Closing the last period of the year moves the year's result to retained earnings. In OneWorld, locks can be set per subsidiary. Edit or Full permission on Manage Accounting Periods is required. |
| Dynamics NAV | The flow matches Business Central: close the accounting periods, then run the Close Income Statement batch job and post the journal. Older versions differ in screen names. |
None of these steps replaces a review. Each one should come after a named person has signed off the reconciliations.
Use three roles per task: a preparer who does the work, a reviewer who checks it, and an approver who accepts the result. The preparer never reviews their own work.
A workable split: staff accountants prepare reconciliations. The controller reviews them and approves the accruals, tax provision and audit adjustments. The CFO approves the final statements and signs the representation letter.
Set a materiality threshold for explaining differences, and write it down. For example, explain any reconciling difference above 500 or 1% of the balance, whichever is lower. That number is a company policy, not an external standard. Pick yours with your auditors.
Here's a simple before and after timeline. Before: Day -30 you agree dates with auditors, day -20 you send the timetable, day -15 you schedule the count, day -10 you set up next-year periods and chase W-9s. After: Day 0 the count runs, day 5 reconciliations are tied, day 12 the tax provision is due, day 15 audit adjustments and statements, day 18 board review, day 20 ERP year-end close, day 25 representation letter and archive.
A close that runs on a dated plan finishes in weeks, not months. If you'd like a benchmark for your own days to close, APQC publishes financial close measures for peers; use those rather than a rule of thumb. For the monthly version of this process, see our month end close process checklist and the month-end close automation page.
Most of these show up as red rows on day 4 or 5.
The agent works inside your ERP, does the matching and drafting, and a person approves every action. It doesn't post, lock or close anything by itself.
The agent reads task status and due dates, then flags a row that's heading for overdue before it turns red.
It matches subledger to ledger and lists unexplained differences with the transactions behind them, so the preparer starts at the exceptions.
It drafts journal entries from receipts, invoices and schedules and attaches the support. Nothing is posted yet.
The reviewer opens each draft, changes it if needed and approves it. The approval is logged with name and time.
The controller runs the lock and the year-end routine in the ERP. The agent never runs these.
We build and tune the agent for your Business Central, GP or NetSuite setup. See human-in-the-loop agents and ERP integration.
It's a dated, owned list of the steps that take your books from the last day of the fiscal year to a locked year: cut-off, reconciliations, adjustments, review and sign-off. The template here has 40 of them.
The monthly close is a routine you repeat. The year-end close adds the physical count, 1099s, tax provision, audit work and the ERP year-end routine that moves income statement balances to retained earnings.
It depends on your size, ERP and audit. The template plans it from four weeks before year end to five weeks after, with the ERP close on business day 20 in the example. Compare your own days with APQC's published financial close benchmarks.
In Business Central, no: Microsoft's documentation says a closed fiscal year can't be opened again. That's why the review and sign-off come first. Other ERPs differ, so check yours.
It's an Excel workbook and doesn't connect to anything. The tasks apply to Business Central, Dynamics GP, NAV, Epicor, SYSPRO, NetSuite and Sage, and you map each task to your own screens.
Enter your work email in the form on this page. The workbook arrives in your inbox.
If your close runs through Business Central, GP, NAV, Epicor, SYSPRO, NetSuite or Sage, we'll walk through your ERP year-end steps and show where an approval-first agent saves time. Thirty minutes, no slides.
Facts on this page checked on 19 November 2026.

Founder and CEO

Chief Sales Officer
Thanks, we’ve got your details. A named member of our team will reply within one business day.
Talk to a QServices solutions architect about your ERP. You'll leave with two or three automation ideas you can act on, even if you never work with us.