📁 Finance

Auditor Prompt: Walkthrough Notes to Test Steps and Memo

Paste anonymized walkthrough notes: get risk and control rows, test steps, a sample plan from your own method, a PBC list and a draft audit observation.

4.0
1Reviews
P
November 10, 2026

Prompt

Act as an internal audit senior who turns walkthrough notes into fieldwork papers that a manager can review the same day. You write in plain audit language, you keep inquiry, inspection and reperformance separate, and you leave every judgment about control effectiveness to the engagement team.

Inputs:
- Audit type (internal audit, external financial statement, SOX): [AuditType]
- Process area and period: [ProcessArea]
- Anonymized walkthrough notes: [WalkthroughNotes]
- Controls as the process owner described them: [ControlsDescribed]
- Risks and assertions in scope: [RiskAssertions]
- Population and its source report: [PopulationDetails]
- Sample sizes from your firm or department methodology: [SampleSizes]
- Exceptions found so far, if any: [ExceptionsFound]
- Policy, framework or standard you test against: [Criteria]
- Who reads the report: [ReportAudience]

Generate:
1. Process narrative: the walkthrough notes rewritten as a short, numbered step flow with who does what, in which system, and where each control sits.
2. Risk and control matrix rows: for each risk in RiskAssertions, the matching control from ControlsDescribed, its type (preventive or detective, manual or automated), frequency and owner. Mark any risk with no control as a design gap.
3. Design questions: what the walkthrough did not answer, written as questions for the process owner.
4. Test steps per control: numbered steps split into inquiry, inspection and reperformance, each with the evidence to keep.
5. Sample plan: apply only the SampleSizes given, state how to pick items from the population (random selection with the seed recorded), and what makes an item an exception.
6. PBC request list: each document or report to request, the period, and the control it supports.
7. Draft observation for each item in ExceptionsFound, in condition, criteria, cause, effect and recommendation order. Write the cause as a question to confirm if the notes do not state it.
8. Open items: everything that must be confirmed before the workpaper can be signed off.

Rules: use only the facts in the Inputs and never invent counts, amounts, dates or standard paragraph numbers. Do not state an audit opinion or call a control effective or ineffective; write "for engagement team conclusion" instead. Remove client names, account numbers and personal data before pasting.

Instructions

Strip client names, bank details and personal data from your notes first, and paste only what your firm allows into an approved workspace. Put your own sample sizes in SampleSizes; the prompt will not pick them for you. Variation: set AuditType to external financial statement and list assertions per account. Tip: paste your firm's observation template into Criteria to match house style. Harbor Lane Supply is an invented example. This prompt drafts working papers; audit conclusions stay with the engagement team. Not audit, legal or tax advice. PromptDig has no tie to OpenAI or any standard setter.

Generated Output

This image was generated using the prompt above.

Auditor Prompt: Walkthrough Notes to Test Steps and Memo - Result

Examples

Example Input

AuditType: internal audit, operational and financial controls
ProcessArea: accounts payable, vendor master bank detail changes, January 1 to June 30
WalkthroughNotes: Harbor Lane Supply (fictional). Vendors email a bank change request to the AP inbox. An AP clerk fills in a vendor change form, calls the vendor back, and updates the bank fields in the ERP. The AP manager prints a weekly vendor master change report every Monday and signs it after review. The clerk said callbacks are sometimes made from a mobile phone and not written on the form. Notes were taken on a yellow legal pad.
ControlsDescribed: C1 callback to the phone number already on file before any bank change, recorded on the change form; C2 weekly review and sign-off of the vendor master change report by the AP manager
RiskAssertions: R1 a fraudulent bank change diverts a vendor payment (occurrence, existence); R2 an unauthorized user edits vendor bank fields in the ERP (access)
PopulationDetails: 46 bank detail changes from the ERP change log; 26 weekly change reports
SampleSizes: C1 25 items; C2 5 weeks (from the department methodology table)
ExceptionsFound: 2 of 25 sampled change forms, VC-0112 and VC-0139, have no callback recorded. VC-0139 was paid 12,350 four days after the change; the vendor later confirmed the new account was genuine. The two forms are marked with red flags in the binder.
Criteria: AP Policy 4.2 (callback to the number on file before any bank change); COSO 2013 Internal Control framework
ReportAudience: CFO and audit committee

Example Output

1. PROCESS NARRATIVE
1) Vendor emails a bank change request to the AP inbox.
2) AP clerk completes a vendor change form. [C1] Clerk calls the vendor back on the number already on file and records the call on the form.
3) Clerk updates the bank fields in the ERP.
4) [C2] Every Monday the AP manager prints the weekly vendor master change report, reviews it and signs it.

2. RISK AND CONTROL MATRIX
R1 Fraudulent bank change diverts a payment (occurrence, existence) | C1 callback | preventive, manual | each change | AP clerk
R1 same risk | C2 weekly report review | detective, manual | weekly | AP manager
R2 Unauthorized ERP edits to bank fields (access) | no control described | DESIGN GAP: ask who has edit rights to vendor bank fields.

3. DESIGN QUESTIONS
- Who can edit vendor bank fields in the ERP, and is that list reviewed?
- Does C2 compare each change back to a change form, or only scan the report?
- What should the clerk do when a callback is made from a mobile phone?

4. TEST STEPS
C1: (inquiry) confirm the callback steps with the AP clerk; (inspection) for each sampled change, inspect the form for a callback record using the number on file; (reperformance) compare the number called with the vendor phone number held before the change.
C2: (inspection) for each sampled week, inspect the report for the AP manager's signature and date; (reperformance) trace every change on the report to a change form.
Evidence: copies of the forms, the signed reports and the ERP change log extract.

5. SAMPLE PLAN
C1: 25 of the 46 changes in the ERP change log, chosen by random number generator; record the seed. Exception: no callback recorded, or a callback to a number that is not the one on file.
C2: 5 of the 26 weekly reports, chosen at random. Exception: unsigned, signed by someone other than the AP manager, or a change with no matching form.

6. PBC REQUEST LIST
- ERP change log of vendor bank fields, January 1 to June 30 (C1 population)
- Vendor change forms for the 25 sampled items (C1)
- 5 sampled signed weekly change reports (C2)
- List of ERP users with edit rights to vendor bank fields (R2 design gap)
- AP Policy 4.2, current version

7. DRAFT OBSERVATION: Bank detail changes made without a recorded callback
Condition: 2 of 25 sampled bank detail changes (VC-0112 and VC-0139) had no callback recorded on the change form. VC-0139 was paid 12,350 four days after the change; the vendor later confirmed the new account was genuine.
Criteria: AP Policy 4.2 requires a callback to the number on file before any bank change.
Cause: to confirm with the AP manager. The clerk said some callbacks are made from a mobile phone and not written down.
Effect: without a recorded callback, a fraudulent bank change could go unnoticed and a payment could be sent to the wrong account.
Recommendation: require the callback date, time and number called on every form, and have the C2 reviewer check that field.
Conclusion on C1: for engagement team conclusion.

8. OPEN ITEMS
- Confirm the cause with the AP manager.
- Complete C2 testing on the 5 sampled weeks.
- Get the ERP access list for R2.
- Check whether any other sampled change was paid before its callback date.

Share this prompt

Reviews (0)

Please login to leave a review.
Loading reviews...