Month end close file with 6 evidence categories

Key takeaways

• Verify books balance equality: In the Frappe Accounting Reports example, the report totals show $395,762 of debits and $395,762 of credits, confirming the snapshot is balanced according to Frappe.
• Retain employment tax records: The Internal Revenue Service instructs to keep all records of employment taxes for at least four years after filing the 4th quarter for the year, according to the specific retention rule in Employment tax recordkeeping.
• Distinguish recommendation from requirement: The balanced books totals are a suggested check for your close file, while the four-year retention period is a specific requirement for employment tax records.
• Scope your retention notes: Apply the four-year rule specifically to employment tax records as stated by the IRS, rather than assuming it covers every business document in the close file.
• Document the source: Note which figures come from your specific accounting tool’s reports and which retention periods come from government guidance to keep the evidence index clear.

Month end close documentation: the evidence to assemble

Your monthly close handoff file should contain six distinct evidence categories. First, include general books control totals that verify debits equal credits. Second, save receivables and payables aging snapshots that identify their specific periods and balances. Third, preserve bank reconciliation support, including the explanation for any differences between statement and book balances. Fourth, retain invoice maturity detail that shows how payment terms calculate due dates. Fifth, keep employment tax record copies, such as filed returns and confirmation numbers. Sixth, document the source, period, and balance for each item in your evidence index.

Before handoff: check books dates and aging snapshots

Verify that your general books control totals and aging snapshots clearly identify their reporting periods and balances before you hand off the file. In the Frappe Accounting Reports documentation, the example books cover the period from 13 July to 13 August 2026, containing Sales Invoice, stock, tax, and bank entries according to Frappe. Confirm that your own books report specifies a similar date range so the reviewer knows exactly which transactions are included in the close.

Check that your debit and credit totals match within the report. While equal totals indicate that the journal entries balance, they do not prove that every individual transaction is correct. Use this check to confirm the mechanical integrity of the books before moving to detailed review.

For receivables, ensure the aging snapshot identifies the specific balance and customer count. The Frappe example displays $249,212 outstanding from four customers as of 13 August 2026 according to Frappe. Verify that your report lists the total outstanding amount and the number of customers involved. This level of detail helps the reviewer understand the composition of the receivable balance without needing to open individual customer accounts.

Examine the aging buckets to see where the receivable amounts fall. In the Frappe example, the entire visible amount falls in the 0 to 30 day ageing bucket according to Frappe. If your receivables are spread across multiple buckets, confirm that the report clearly distinguishes them. This prevents confusion about which invoices are current and which are overdue.

For payables, check the aging snapshot for outstanding balances and specific vendor details. The Frappe example shows $184,293 outstanding to Summit Traders Ltd., Zuckerman Security Ltd., and MA Inc. in the 121 days and above bucket according to Frappe. Ensure your report names the specific vendors and the aging category they fall into. This allows the reviewer to immediately identify long-outstanding liabilities that may require attention.

Save these reports as part of your close file with the period dates clearly visible in the file names. This ensures that the evidence is easily retrievable and matches the specific month being closed.

During assembly: preserve bank balances and reconciliation explanations

When documenting the bank reconciliation portion of your close file, preserve both the starting balances and the final adjusted figures. In the example provided by Sage, the bank statement shows a closing balance of $14,200, while the company’s internal books show $12,850 ( Sage Advice US). Record these initial figures to establish the scope of the reconciliation. The difference between these two amounts is $1,350. According to Sage, this original $1,350 difference was fully explained by timing differences and transactions that had not yet been recorded internally.

Do not discard the explanation for this difference. The documentation should show how the discrepancy was resolved. In the same example, both adjusted balances now match at $13,800, confirming that the reconciliation is complete ( Sage Advice US). This matching figure serves as the evidence that the reconciliation process was finished. Keep the narrative explanation alongside the numerical result.

Your close file should contain a clear record of the starting statement balance, the starting book balance, and the final adjusted balance. You must also document the specific reasons for any differences found during the reconciliation process. If the difference is due to timing or unrecorded items, state that explicitly in the file. This allows a reviewer to understand how the balances were reconciled without needing to re-perform the work.

Ensure the file clearly distinguishes between the initial discrepancy and the final resolved state. Save the documentation that shows this match. If you are using other tools for this process, see Bank reconciliation for 4 bookkeeping apps for additional context on how different platforms handle these balances.

During assembly: check invoice maturity detail against payment terms

Verify that invoice maturity detail captures the specific split of receivable journal items and the calculated due dates before finalizing the file. Do not assume that one invoice creates a single receivable entry. The documentation notes that the $1000 debited to the account receivable is split into two distinct journal items, according to Odoo. This structural detail matters when matching payments to specific invoice components.

Check that the payment terms used on the invoice automatically generate the correct due dates. Defining terms automatically calculates the payments’ due date(s), according to Odoo. Confirm that the calculated dates match the terms agreed with the customer. If the terms involve multiple installments, verify the sequence of these dates. Terms are computed in the order of their due dates, according to Odoo. This ordering check ensures that the maturity schedule aligns with the contractual payment plan.

When reviewing the journal entries, look for the distinct items that make up the total receivable amount. The split into distinct journal items reflects how the system handles payment terms within a single invoice. Inspect the books to confirm that each journal item corresponds to a specific term or installment. This inspection verifies that the receivable balance is supported by detailed maturity data rather than a single aggregate figure.

If your workflow involves importing bank statements to match against these payments, review the Import bank statements: compare 4 bookkeeping tools guide to understand how different tools handle transaction matching. This context helps ensure that the imported data aligns with the calculated due dates and journal items.

Evidence reference table: examples, amounts and record requirements

The table below lists the specific evidence items, amounts, and record requirements for each publisher. Each row cites the exact figures or instructions found in the respective source.

The Frappe account-total row reflects Nova's books for 13 July to 13 August 2026, and the receivables row is as of 13 August 2026.

Use this table to verify that each category in your close file contains the specific data points listed.

After assembly: complete the close evidence checklist and retention note

Finalize the file by verifying that employment tax documentation meets specific retention standards. The Internal Revenue Service outlines distinct requirements for these records that differ from general bookkeeping files.

Filed returns and confirmations Retain copies of all filed returns along with their confirmation numbers. The IRS explicitly lists "Copies of returns filed and confirmation numbers" as part of the required employment tax recordkeeping Internal Revenue Service. Ensure these documents are indexed by tax period to match the close date.

Fringe benefits and reimbursements Include records of fringe benefits and expense reimbursements provided to employees. These records must include substantiation for each item. The IRS specifies "Records of fringe benefits and expenses reimbursements provided to your employees, including substantiation" as a necessary component of the file Internal Revenue Service. Verify that notes or logs supporting these payments are attached to the corresponding book entries.

Retention timeline Apply the specific retention rule for employment taxes. Mark the retention expiration date in your file management system based on the fourth-quarter filing date for the relevant year.

Checklist completion Review the assembled file against the six evidence categories. Confirm that the employment tax section contains the filed returns, confirmation numbers, and substantiated benefit records. Note the retention deadline for the current year's fourth quarter filing. If you are preparing for year-end payroll reconciliation, see December payroll close: 6 checks for reporting records for additional verification steps.

Final action Enter the source, period, balance, and file location for each employment tax document into the evidence index. Ensure the retention note clearly states the four-year period starting from the fourth-quarter filing date.

Illustrative example of six close-file lines

Picture a close file with round figures and no named company. Account totals show 1000 in debits and 1000 in credits. Aging shows 750 outstanding from 4 customers, all in the 0 to 30 day bucket. A bank statement balance of 1350 and a book balance of 1000 are both adjusted to 1000. One invoice of 1000 is split into 2 items with due dates in order. Employment tax copies stay for 4 years after the 4th quarter filing. The index lists the source, period, and balance for all 6 categories.

Next step

Create an evidence index for the current close and enter the source, period, balance and file location for each applicable document already available.

FAQ: supporting documentation for a monthly close file

What documentation belongs in a month end close file?

The file should include general books control totals, receivables and payables aging snapshots, bank reconciliation support, invoice maturity detail, employment tax record copies, and an evidence index of source, period, and balance. These six categories are what the close handoff should contain. Employment tax records specifically require filed-return copies and confirmation numbers, as detailed in the assembly sections above.

How does the Sage example explain the difference between bank and book balances?

The original $1,350 difference between the bank statement and the company’s books was fully explained by timing differences and transactions that had not yet been recorded internally, according to Sage.

Which reconciliation start date can I use in FreshBooks?

You can choose any date within the statement period and put this into FreshBooks’ Bank Rec as your Reconciliation Start Date, according to FreshBooks. The documentation cites July 28 as an example of such a date.

Does the four-year instruction apply to all business records or specifically employment tax records?

The instruction applies specifically to records of employment taxes, not all business records, according to Internal Revenue Service. Apply this retention period to employment tax documentation within the close file.

Can one invoice create more than one receivable journal item in Odoo?

Yes, the $1000 debited to the account receivable is split into two distinct journal items, according to Odoo. Check invoice maturity detail rather than assuming one invoice equals one receivable item.