Nothing here is financial advice, and none of it replaces your own checks.
Use these prompts to turn close documents into one evidence record that can be reviewed in a status meeting. They are for financial controllers and audit teams handling period-end close. Nothing here is financial advice, and none of it replaces your own checks or the decisions of the qualified people responsible for the close.
Start with the master tracker. Then use the narrower prompts only where the meeting needs an answer: ownership, overdue work, exceptions or sign-off blockers. This order matters. A blocker list built from unstructured reconciliations is harder to trace back to source evidence.
Key point
Start with source references
Every tracker row needs a document name, worksheet, task ID, request ID or other source reference. Without it, the tracker is a to-do list, not audit evidence.
1. Prepare the three input documents
Before pasting anything, export or copy the latest version of each document:
- The close timetable, including task IDs, dates, owners and review steps.
- The reconciliation register and any individual reconciliations with open breaks.
- The auditor request log, including request references and requested support.
Keep the period end visible in each input. If your group has several entities, retain the entity name on every row. Do not paste a redacted summary if the original register contains the owner, reviewer or due date needed to test completion.
If you are providing files rather than pasted text, check the handling available in your workspace. File and input support can differ by version, so consult the xAI documentation overview before relying on a file workflow for a close-critical task.
Watch out
Do not merge unlike items too early
A balance sheet reconciliation, a control review and an auditor request may relate to the same account, but they can require different evidence and different reviewers.
2. Build the tracker before chasing people
Run Build the master evidence tracker against the three source documents. It gives every evidence item a row and distinguishes the evidence itself from its owner, reviewer and sign-off effect.
Read the rows marked Missing or Conflict first. They often reveal a basic problem: the timetable says a task is complete, but the reconciliation register has no reviewer, or the auditor request identifies support that has not been logged.
Do not overwrite the source documents to make them fit the tracker. Instead, retain the disagreement in the Exception or open point field. This gives the controller or reviewer a clear item to resolve and preserves the audit trail.
Check
A usable tracker has a route back to evidence
Pick five rows at random. You should be able to find the named source, identify the owner and reviewer, and see what evidence would move the item forward.
3. Use the right follow-up prompt
The prompts after the master tracker have different jobs. Run only the one that answers the immediate meeting question.
| If you need to know | Use this prompt | Take to the meeting |
|---|---|---|
| Who must supply or review missing evidence | Find missing ownership and support | The unassigned evidence table and questions list |
| What needs action today | Triage overdue close evidence | P1 actions and escalation routes |
| Whether reconciliation breaks are properly documented | Test unresolved exceptions | The exceptions register and follow-up list |
| What prevents a documented sign-off discussion | Prepare the sign-off blocker list | The decision record and agenda |
Use a stated current date for overdue triage. Otherwise, an item can look late simply because the input is from a prior close cycle. If the date is unclear, keep it unclear. Do not make up a deadline to make the table look complete.
4. Check the output against the source
The most convincing-looking row can still be wrong. Check the output in three passes.
- Identity check: Confirm entity, account, reporting period and task or request reference against the original document.
- Evidence check: Open the cited support. Verify that it is the requested reconciliation, review record, schedule or response, rather than a similarly named prior-period file.
- Status check: Compare
CompleteorResolvedwith the preparer evidence and the reviewer conclusion. Completion without review evidence is not the same as a completed review.
Pay particular attention to grouped rows. The master prompt may link documents concerning the same account or process. Confirm that they genuinely describe the same obligation. If one request covers a control and another covers a balance, split them into separate tracker rows in your working file.
Check
Test the claimed blockers
For each item marked Blocks sign-off, ask: what exact evidence is absent, who can provide it, and which source says it is required? If any answer is missing, the blocker needs further investigation.
5. Record decisions outside the generated text
Use the sign-off decision record as meeting support, not as the signed record itself. After the meeting, update the controlled tracker or close checklist with the decision, decision maker, date, evidence received and remaining conditions. Retain the source files and the meeting record according to your organisation's retention process.
Do not ask the model to determine whether an exception is immaterial, whether an accounting treatment is appropriate, or whether sign-off should proceed. The prompts deliberately leave those decisions to the responsible controller, reviewer, auditor or other qualified person.
When it does not work
If the tracker produces too many Missing fields, paste the underlying register rather than a summary, and include column headings. If it creates duplicate rows, provide the timetable task ID, account, entity and auditor request reference so related items can be matched. If status or ownership is wrong, correct the controlled source record first, then rerun the relevant prompt with the updated extract.
If the output cannot be traced to a document, do not use it as evidence. Mark the item for investigation, keep the source reference blank rather than guessed, and take it to the close meeting for assignment.