01
Set the expected package
You define what should exist for the reporting period before judging what was received.
Made for CPAs
Check a Business Year-End Package for Gaps
Also useful for: people in Finance
35 min
Intermediate
Financial Organization
Improve Operations
You compare received year-end records with the documents needed to close the books, then sort open items by status, urgency, and effect on the work.
We'll use them to write your prompt.
Completed ✓
Make Your Play
Give us the situation. We’ll build the prompt.
Year-end packages often look complete until preparation starts.
Your answers save as you type.
What you'll do
This is the plan inside your prompt. Add your details first. Then follow these steps with ChatGPT or Claude.
02
Map every received file
You connect each upload to the request it may satisfy and expose files that can't be identified.
03
Grade completeness by category
You compare expected evidence with received evidence using consistent status rules.
04
Run category-specific gap checks
You test the package for common year-end omissions that a simple file count can miss.
05
Prioritize unresolved items
You separate items that stop the work from questions that can wait or be documented internally.
06
Prepare the follow-up package
You turn the review into a concise request list and preserve the reasoning for your file.
Make Your Play
Check a Business Year-End Package for Gaps
Tell us what the prompt needs to know
Start with the questions below. Each answer personalizes the playbook and builds the prompt you’ll use at the end.
Your situation
Enter the exact fiscal or calendar period covered by the review.
Describe the business activities and the accounts, payroll, debt, inventory, receivables, or payables you expect it to have.
0/10000
List the documents requested under the engagement, including required dates or periods.
0/10000
List or upload the received file inventory with file names, document types, accounts, and covered dates. Remove sensitive identifiers first.
0/10000
List confirmed closed accounts, waived requests, unavailable records, and categories that don't apply.
0/10000
This playbook was updated. Review your inputs before copying.
What you'll do
Check a step when you finish it.
01
Set the expected package
You define what should exist for the reporting period before judging what was received.
02
Map every received file
You connect each upload to the request it may satisfy and expose files that can't be identified.
03
Grade completeness by category
You compare expected evidence with received evidence using consistent status rules.
04
Run category-specific gap checks
You test the package for common year-end omissions that a simple file count can miss.
05
Prioritize unresolved items
You separate items that stop the work from questions that can wait or be documented internally.
06
Prepare the follow-up package
You turn the review into a concise request list and preserve the reasoning for your file.
Fill in the fields above to generate your prompt preview.
Assembled prompt
Beginner instructions
Start with a file inventory instead of opening every transaction-level document. List each file, the account or report it appears to cover, and its date range. Remove full account numbers, Social Security numbers, and payroll identifiers before sharing information with an AI assistant. Review every item marked Complete before relying on the result.
Advanced instructions
Match the review to your engagement request list and internal year-end procedures. Add client-specific accounts from the trial balance or prior-year file, but don’t use prior-year presence as proof that an account is still active. You can apply your own priority rules after the completeness check, but don’t mark absent evidence complete based only on expected materiality.
Use this when
Use this after the main year-end upload arrives and before detailed preparation begins. It also works when inherited files are disorganized or several team members collected the documents.
You'll need
- Reporting period
- Business overview
- Expected documents
- Received document inventory
- Known exceptions
You'll get
- All eight evidence areas checked
- A supported status to each applicable item assigned
- The reporting periods covered confirmed
- Work-stopping gaps from lower-priority questions separated
- Duplicate or already-satisfied requests from the follow-up list removed
By the end of this playbook
You will have:
- All eight evidence areas checked
- A supported status to each applicable item assigned
- The reporting periods covered confirmed
- Work-stopping gaps from lower-priority questions separated
- Duplicate or already-satisfied requests from the follow-up list removed
Examples
Progress 1 of 6