Collect missing evidence for the month-end close
Turn missing receipts, pending invoice approvals and unanswered close questions into an owner-specific request queue. Keep reminders and received evidence synchronized with the closing checklist.
How this works
Maintain a precise queue of what finance still needs from whom. Treat a missing document, an approval decision and an accounting question as different request types, each with its own completion evidence.
This workflow gathers inputs for the close. It does not review accounting treatment, approve an invoice, authorize payment or declare the books closed. Those decisions remain with the assigned finance owners.
Before you start
Period and checklist owner
Choose the accounting period, entity scope, closing checklist and person authorized to accept evidence. Define which missing items actually block close.
Verified responsibility map
Use accountable owners and their delegates from existing records. An email sender is not automatically the invoice approver or expense owner.
Reminder policy
Specify allowed channels, cadence, quiet periods, escalation thresholds and whether sending is already authorized. Draft-only mode is usable without a communication connector.
Prepare the inputs
- Close checklist
- Required
Rows with entity, period, item_id, type, status, owner and due_at.
Use a stable item ID and distinguish closing period from document date. Flag absent owners or impossible dates.
- Evidence inventory
- Required
Current receipt links, approval records and answers associated with checklist items.
Check the exact entity, transaction or invoice reference. A document arriving is not proof that finance accepted it.
- Prior request ledger
- Required
Requests already sent, recipient, channel, message ID and last outcome.
Include recent manual reminders where available to avoid duplicate or conflicting contact.
- Cadence and escalation rules
- Required
Approved timing, channel and owner-to-escalation mapping.
If rules or recipients are unknown, prepare drafts and questions without inventing a chase schedule.
Implementation, step by step
Scope and normalize the outstanding items
- Freeze the checklist snapshot for the chosen entities and period. Separate missing receipts, missing approvals and unresolved questions.
- Assign a stable request key from entity, period and item ID. Preserve reopened items and duplicates for owner review rather than dropping them from the totals.
Checkpoint: Every in-scope checklist item has a traceable state and request key.
Check whether the evidence already exists
- Search only approved folders, inboxes or exports for the requested material using the exact transaction and period references.
- Link plausible matches as evidence-received, then request finance acceptance where required. An unrelated invoice with the same amount or a vague “done” reply does not clear the item.
Checkpoint: The remaining queue reflects actual missing or unaccepted evidence, with uncertain matches flagged.
Prepare owner-specific requests
- Group outstanding items for the same verified owner into one clear request when the approved policy permits. Name exactly what is missing, its reference, due date and permitted submission route.
- Keep approvals as explicit decisions by the designated approver. Do not ask a colleague to approve their own item when the configured responsibility rules separate those roles.
Checkpoint: Each draft asks for a specific artifact, decision or answer without disclosing another team’s unrelated financial details.
Send authorized reminders without duplication
- Before any authorized send, refresh the item state and prior request ledger. Suppress resolved, paused or already-reminded items according to the approved cadence.
- Record the returned message identifier and actual send time. If delivery is uncertain, reconcile the destination before another attempt; a scheduling record alone is not proof of delivery.
Checkpoint: One current reminder state is recorded for each item and permitted recipient.
Match responses and escalate remaining blockers
- Attach incoming evidence and answers to their request keys, keeping the initial status and the reviewer’s acceptance separate. Reopen the request if finance rejects an incomplete document.
- Prepare an escalation queue when the agreed deadline or reminder threshold is reached. State the exact missing evidence and owner; do not increase pressure or add recipients beyond the approved policy.
Checkpoint: Received, accepted, rejected and still-missing items remain distinguishable.
Reconcile the daily close-evidence report
- Report opening blockers, newly added items, accepted resolutions, reopened items and ending blockers. Explain changes that affect the totals.
- List each remaining dependency, responsible owner and next action. Keep overall close completion with the closing owner rather than deriving it from an empty reminder queue.
Checkpoint: The report balances to the checklist and does not equate replies or uploads with approvals.
Decisions along the way
A receipt arrives after a reminder was prepared
Refresh the evidence state before sending; cancel or revise the pending request if the item is already accepted.
Someone replies “approved” but is not the designated approver
Preserve the reply as correspondence and route it for confirmation without changing approval status.
One document covers several checklist items
Link each relevant item explicitly and let finance verify allocation; do not mark unrelated records resolved.
Owner is absent or cannot be identified
Use the existing delegate rule if one exists; otherwise ask the close owner to assign responsibility and hold the send.
What you will produce
close-evidence-tracker.csv
CSVA period-bound queue with an evidence acceptance state.
Include: entity · period · item_id · request_type · owner · due_at · evidence_reference · acceptance_status · next_action
close-reminder-drafts.md
MarkdownSpecific requests grouped by approved recipient and cadence.
Include: request_keys · recipient · channel · missing_items · deadline · draft · authorization
close-chase-ledger.csv
CSVA recoverable log of authorized communications and resolutions.
Include: request_key · action · message_id · sent_at · delivery_state · response_reference · reviewer · resolution
Check the result
- Reconcile opening plus new plus reopened minus accepted resolutions to ending blockers.
- Check that every resolved item has the required evidence and acceptance record.
- Verify no reminder crosses entities, periods or unauthorized recipient groups.
- Test response-arrives-before-send and uncertain-delivery cases to prevent avoidable repeats.
When something goes wrong
Checklist statuses lag behind new uploads
Mark received evidence pending review and refresh the checklist before sending; do not hide the lag with a guessed resolution.
Reminder delivery is uncertain
Check the message destination or receipt and retain unknown delivery if confirmation is unavailable.
A submission contains the wrong period’s document
Keep the current request open and draft a precise clarification identifying the mismatch.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Synthetic: prepare today’s follow-ups for the September close.
Inputs
There are four opening blockers: two receipts, one invoice approval and one expense explanation. One receipt is accepted, the explanation is answered but awaits review, and a new missing receipt is added.
Expected result
Report four ending blockers: 4 opening + 1 new - 1 accepted. Mark the explanation received-pending-review, suppress the resolved receipt reminder, and draft requests only for items that still require the owner’s action. Do not report the invoice approved or the close complete.
Run a small pilot
Start small
Use one entity and one closing period in draft-only mode before authorizing any recurring sends.
Record the baseline
Record coordinator minutes, duplicate reminders and blockers misreported as resolved.
Agree success criteria
Agree a useful response turnaround target and require exact reconciliation and no unauthorized recipients during the pilot.
Stop or revise
Pause sends if responses are treated as approval or reminders continue after accepted resolution.
Keep the scope clear
- Do not approve expenses, change accounting entries, release payments or certify a completed close.
- Keep financial attachments in the approved finance location; share only the necessary reference with each owner.
- Apply reminder timing and escalation only within the user’s existing authorization.
Check before using
The closing owner accepts supporting evidence and approvals; the assistant never marks an accounting item approved merely because someone replied.
Business activities
- Manage finances and accounting
- Coordinate meetings and follow-ups
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Period-specific close checklist · Missing-document and approval records · Owner directory and reminder rules
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow