Build a month-end evidence pack by collecting approved invoice and reconciliation references into a controlled register, separating unresolved exceptions and freezing a named version for handover. Every signed-off item should lead back to the evidence and approval that support it. Automation can assemble the pack; a finance reviewer decides whether it is ready.
The useful output is a handover your accountant or finance manager can retrace: what was included, which documents were used, what was approved and what still needs attention. This is a focused starting point for accounting automation.
Define what this month's pack must cover
Agree the entity, reporting period, cut-off and document categories before collecting files. State whether the pack covers supplier invoices, bank reconciliations, supplier statement reconciliations or a defined combination. A folder labelled “month-end” leaves too much interpretation to the next person.
Ask the finance reviewer to identify the expected source registers and reconciliation schedule. Use these to check coverage. Searching a folder only tells you what was found; it does not identify an expected reconciliation that nobody uploaded.
Record the inclusion rule for each category. For example, the reviewer might require a supplier invoice reference, supporting document and approval record before that item enters the signed-off section. These are proposed operating rules for your team to agree, rather than universal accounting requirements.
Separate document status from evidence approval
An invoice's system status and its suitability for this pack answer different questions. Keep the source status alongside the pack review status. Do not translate “authorised” into “all month-end evidence checked” without a recorded human decision.
Xero's official Accounting API definition includes examples containing invoice identifiers, payment references, reconciliation flags and update timestamps. Those fields can help anchor references, but they do not establish that your whole evidence pack is complete. Source: Xero Accounting API definition
Define who can approve each evidence category and where that approval is recorded. An approval should identify its scope: the invoice document, the reconciliation or the whole pack. A preparer's note saying “looks fine” should remain a note until the designated reviewer accepts it.
Build a register that survives a handover
Give each pack item a stable reference. Alongside it, record the source record identifier, document location, exact document version, reporting period, approval reference and review status. For reconciliations, include the account or supplier covered and the supporting statement reference.
Capture when the source was collected. Where a document can change, preserve the approved snapshot or record a version reference that remains retrievable. A link to a continually overwritten spreadsheet cannot show what the reviewer saw at sign-off.
Keep the relationship between records explicit. One payment may support several invoices; one invoice may have several supporting documents. Record those links without counting the same invoice repeatedly. If the relationship is unclear, create an exception rather than forcing a convenient match.
Use a plain spreadsheet initially if it meets the handover need. The register's structure matters more than whether an AI agent assembled it.
Use automation for collection and grounded summaries
A proposed workflow can collect approved references, check required fields, compare the register against the expected schedule and assemble a draft handover. Keep arithmetic and duplicate checks in defined rules. Use AI where document wording needs summarising, with references attached to each summary.
OpenAI file search retrieves information from uploaded files using semantic and keyword search and can return file citations. This supports a proposed way to locate supporting passages; it does not decide which documents your finance team has approved. Source: OpenAI file search
Likewise, Structured Outputs can constrain responses to a supplied schema. A consistent structure does not establish that an extracted amount, reference or approval is correct. Check those values against the source before accepting them into the register. Source: OpenAI Structured Outputs
If retrieval fails, show “source unavailable” rather than generating a plausible summary. Before deployment, check current account, plan and region eligibility for the selected products. Agree which finance documents may be processed and who may access the resulting pack.
The distinction between AI agents and automation helps here: fixed collection rules may be sufficient, while interpreting varied documents may justify a narrowly scoped agent.
Copy this month-end handover checklist
Use this checklist as the pack's cover sheet. Complete the fields and retain it with the evidence register and exception list.
Month-end evidence pack handover
- Entity: [name]
- Reporting period: [start–end]
- Evidence cut-off: [date, time and time zone]
- Pack ID and version: [identifier]
- Prepared by: [name]
- Finance reviewer: [name]
- Included categories and expected source registers: [list]
Evidence register , one row per pack item
| Field | What to enter |
|---|---|
| Pack item reference | Stable reference used throughout the pack |
| Source record | System name and record identifier |
| Document reference | Accessible location and exact version or retained snapshot |
| Period and scope | Period covered; account, supplier or invoice concerned |
| Reconciliation reference | Supporting reconciliation and statement reference, or reason not applicable |
| Approval evidence | Approver, approval date, scope and recorded approval location |
| Pack review status | Signed off or unresolved |
| Exception reference | Linked exception, or none |
Exception list , one row per unresolved issue
| Field | What to enter |
|---|---|
| Exception reference | Stable identifier linked to affected pack items |
| Issue | Missing evidence, ambiguous match, suspected duplicate or other stated problem |
| Evidence available | References already checked |
| Required next action | Specific evidence or decision needed |
| Owner and target date | Named person and agreed follow-up date |
| Resolution | Pending, or decision with supporting reference and reviewer |
Release checks
- Compare included items with the agreed source registers and reconciliation schedule.
- Confirm signed-off items have retrievable evidence and scoped approvals.
- Keep unresolved items outside signed-off counts and totals.
- Record counts and any totals with their scope and currency.
- Open source links using the recipient's intended access.
- Record the reviewer's release decision, including accepted open exceptions.
- Freeze this version and identify its storage location.
- For a replacement, retain the previous version and list changed items, reasons and approvals.
Work through ordinary and difficult cases
The following identifiers, amounts and outcomes are hypothetical.
Ordinary case: Invoice INV-A for R4,600 has an approved document snapshot, an approval reference and a link to the reviewed supplier reconciliation. The preparer records these references. The finance reviewer checks the relationship and marks the pack item signed off. Its summary names the supporting evidence without suggesting that pack sign-off authorises payment.
Missing evidence: Invoice INV-B for R2,300 appears in the agreed source register, but its supporting document cannot be opened. Keep it visible in the exception list. Assign the missing document request to the accounts clerk. Do not omit it silently or describe it as signed off because the system record exists.
Ambiguous match: A R6,900 payment could relate to several invoices, and the remittance advice is missing. Record the candidate references and ask the finance reviewer to confirm the allocation using additional evidence. Leave the relationship unresolved until that decision is recorded.
Possible duplicate: Two differently named PDFs refer to INV-C. Compare their invoice identifiers and contents. If they are copies of the same approved document, the reviewer can retain one canonical reference and record the duplicate handling. If they differ, preserve both and request a decision on the authoritative version. Do not delete or overwrite either during investigation.
Freeze the pack and control late changes
Issue each handover with a pack identifier, version, cut-off and release decision. Keep the signed-off register and exception list together so recipients see both the completed work and remaining questions.
A late reconciliation correction should trigger a replacement version. Record the affected items, what changed, why it changed and who reviewed the replacement. Do not quietly update an already issued pack.
For the first repeat cycle, ask the recipient to trace a signed-off invoice, a reconciliation and an exception. Fix broken references or unclear ownership before expanding the workflow. Custom AI agent workflows can provide a broader design starting point once these handover rules are settled.
FAQ: Month-end evidence pack decisions
Can we issue the pack with unresolved exceptions?
Yes, if the designated finance reviewer accepts that handover scope and records the decision. Label the exceptions clearly, with owners and next actions. Issuing the pack must not imply that every reconciliation or underlying accounting question is resolved.
What if an approved document changes after collection?
Compare the changed document with the version referenced in the pack. Ask the reviewer whether the change affects approval or reconciliation evidence. Keep the issued version intact and release a replacement when needed, with a clear change log.
Do we need a custom AI agent to assemble the pack?
Start with the register and collection rules. Consider a custom AI agent when varied documents require interpretation that fixed rules cannot handle adequately. Keep its summaries traceable and its authority limited to preparing evidence.
If your business needs help turning approved finance documents into a repeatable handover, explore AI automation and get in touch with a sample register and your current month-end checklist.