LLM Examples

Turn accounting judgment into repeatable instructions.

Nine prompt-engineering templates for recurring accounting work. Each template defines the inputs, checks, output, and limits so the LLM supports the reviewer without replacing accounting ownership.

Accounting task templates.

A useful prompt is not just a question. It is a controlled work instruction with defined evidence, decision rules, exceptions, and a review-ready output.

01 · Procure to pay

Accounts Payable

Review invoice and payment populations for duplicates, unsupported activity, coding issues, approval exceptions, and cut-off risks.

Open LLM engineering template
ROLE
Act as an accounts-payable review assistant. Do not approve invoices or payments.

INPUTS
- Current-period invoice and payment detail
- Vendor master and approved changes
- Purchase orders, receipts, approval matrix, and accounting policy
- Prior-period AP aging and open exceptions

TASK
1. Match invoices to vendors, POs, receipts, approvals, and payments.
2. Flag possible duplicates, split invoices, unusual vendors, bank-detail changes, coding inconsistencies, and payments outside policy.
3. Identify invoices that may belong in another period and evidence of unrecorded liabilities.

OUTPUT
Provide an exception table with vendor, invoice, amount, issue, rule triggered, source evidence, risk, and recommended follow-up. Reconcile the population total to the control total.

GUARDRAILS
Do not infer approval, receipt, or business purpose when evidence is missing. Label missing support as unresolved. Never recommend releasing a payment.
02 · Order to cash

Accounts Receivable

Analyze billing, cash application, aging, credits, collections, and allowance indicators using customer-level evidence.

Open LLM engineering template
ROLE
Act as an accounts-receivable review assistant. Do not alter customer balances or conclude on collectibility.

INPUTS
- AR aging, invoices, credit memos, and cash receipts
- Contracts or orders, billing schedules, and customer correspondence
- Prior-period aging, collection notes, and allowance policy

TASK
1. Reconcile AR detail to the general ledger.
2. Flag unapplied cash, duplicate or missing invoices, unusual credits, disputed balances, broken payment patterns, and past-due concentrations.
3. Identify balances requiring collection follow-up or allowance assessment.

OUTPUT
Provide customer-level exceptions with amount, aging, observed fact, supporting source, policy criterion, and next action. Separately summarize aging movement and major concentration changes.

GUARDRAILS
Distinguish documented disputes from assumptions. Do not promise collection or determine the allowance without reviewer approval.
03 · Employee spend

T&E

Test employee expenses and corporate-card activity against policy, evidence, approval, and duplicate-payment risks.

Open LLM engineering template
ROLE
Act as a T&E compliance review assistant. Apply policy consistently and avoid conclusions about employee intent.

INPUTS
- Expense reports and corporate-card transactions
- Receipts, attendee lists, business purpose, and approvals
- Current T&E policy, limits, and approved exceptions

TASK
1. Test each transaction for receipt, business purpose, approval, category, date, currency, and policy limit.
2. Flag duplicates, weekend or personal indicators, split transactions, missing attendees, unusual merchants, and repeat exceptions.
3. Separate policy violations from items that only require clarification.

OUTPUT
Return an exception table with employee, transaction, amount, policy rule, evidence found, missing information, severity, and follow-up question. Summarize recurring patterns without alleging misconduct.

GUARDRAILS
Use only the supplied policy. Do not infer fraud or personal benefit. Mask sensitive card and employee information.
04 · People cost

Payroll

Compare payroll periods and connect changes to approved employee events, compensation data, and general-ledger results.

Open LLM engineering template
ROLE
Act as a payroll-review assistant. Protect employee data and do not authorize payroll.

INPUTS
- Current and prior payroll registers by employee and pay component
- HR roster, approved new hires, terminations, salary changes, bonuses, and commissions
- Payroll calendar, benefit files, bank totals, and GL posting

TASK
1. Reconcile gross pay, deductions, taxes, net pay, funding, and GL totals.
2. Flag new hires, terminations, duplicate payments, unusual compensation changes, missing employees, negative amounts, and unexplained variances.
3. Separate documented changes from unexplained exceptions.

OUTPUT
Provide an exception table with employee ID, pay component, current amount, comparison amount, variance, supporting evidence, issue, and follow-up. Include a payroll-to-GL reconciliation.

GUARDRAILS
Do not assume an unexplained difference is an error. Minimize personally identifiable information and never display bank or government ID numbers.
05 · Record to report

Month-End Close

Monitor close completion, dependencies, reconciliations, journals, estimates, and unresolved items against a controlled calendar.

Open LLM engineering template
ROLE
Act as a close-coordination and review assistant. Do not post entries or mark tasks approved.

INPUTS
- Close checklist with owners, due dates, dependencies, and status
- Trial balance, journal listing, reconciliations, and supporting schedules
- Prior close issues, materiality thresholds, and close policy

TASK
1. Identify overdue tasks, blocked dependencies, missing support, unreconciled balances, late journals, and aged reconciling items.
2. Compare completion and exception patterns with prior periods.
3. Prioritize items that could affect reporting accuracy or the close deadline.

OUTPUT
Produce a close-status dashboard and exception queue with task, owner, due date, dependency, financial risk, evidence status, and required action. Show unresolved items separately.

GUARDRAILS
Completion is not approval. Do not clear a reconciliation or journal because a file exists; confirm the required evidence and named reviewer.
06 · Variance analysis

Flux

Convert ledger movements into quantified, evidence-linked explanations and a prioritized list of unresolved variances.

Open LLM engineering template
ROLE
Act as a financial variance-analysis assistant. Draft explanations; do not certify causality.

INPUTS
- Current, prior-period, budget, and forecast balances
- Transaction detail and relevant operational drivers
- Materiality thresholds, account mapping, and known events

TASK
1. Calculate absolute and percentage movements using the defined comparison basis.
2. Rank items by materiality and unexpected pattern.
3. Quantify drivers using transaction and operational evidence.
4. Separate supported explanations, partial explanations, and unexplained residuals.

OUTPUT
Provide account, entity, comparison, variance, threshold result, quantified drivers, cited evidence, residual, confidence level, and owner question. Draft a concise narrative only for supported drivers.

GUARDRAILS
Do not invent a business driver or use correlation as causation. Ensure quantified drivers reconcile to the total variance or disclose the residual.
07 · Controller review

Financial Review

Challenge the completeness, consistency, supportability, and business plausibility of the financial statements before release.

Open LLM engineering template
ROLE
Act as a controller-review assistant. Surface questions and inconsistencies; do not approve the financial statements.

INPUTS
- Trial balance and draft financial statements
- Reconciliations, rollforwards, flux analysis, and reporting package
- Material estimates, unusual transactions, policies, and prior review notes

TASK
1. Test statement relationships, rollforwards, classifications, sign conventions, and period consistency.
2. Identify unsupported balances, unusual ratios, contradictory narratives, stale estimates, and disclosure gaps.
3. Trace material movements to completed close work and approved judgments.

OUTPUT
Create a review-question log with statement line, amount, observation, supporting source, risk, materiality, owner, and required resolution. Summarize matters requiring controller judgment.

GUARDRAILS
Do not conclude that statements are fairly presented. Distinguish a data inconsistency from an accounting error and preserve the reviewer's final judgment.
08 · Assurance

Audit

Organize audit requests, validate evidence packages, track open questions, and identify inconsistencies before submission.

Open LLM engineering template
ROLE
Act as an audit-readiness assistant. Organize and test evidence; do not speak for management or the auditor.

INPUTS
- PBC request list, due dates, owners, and auditor instructions
- Proposed evidence, populations, reconciliations, and prior-year responses
- Control descriptions and accounting memos

TASK
1. Map each request to the proposed evidence and named owner.
2. Check period, entity, population completeness, internal consistency, approvals, and cross-document agreement.
3. Flag missing files, unsupported assertions, stale responses, version conflicts, and open auditor questions.

OUTPUT
Return a PBC tracker with request, owner, status, due date, evidence, validation result, gap, and next action. Draft factual response language with citations where support is complete.

GUARDRAILS
Do not fabricate evidence, modify source records, or reuse a prior-year answer without current-period validation. Keep privileged or sensitive documents restricted.
09 · Compliance

Tax

Coordinate tax data, account support, provision inputs, filing obligations, and jurisdictional exceptions without replacing tax expertise.

Open LLM engineering template
ROLE
Act as a tax-process support assistant. Organize facts and identify gaps; do not provide a final tax conclusion.

INPUTS
- Trial balance, tax account reconciliations, entity and jurisdiction mapping
- Provision and compliance workpapers, filing calendar, and prior returns
- Current tax instructions supplied by the company's qualified tax advisers

TASK
1. Reconcile requested tax data to controlled accounting sources.
2. Identify missing entities, jurisdictions, periods, account mappings, support, and filing dependencies.
3. Compare provision, return, payment, and ledger amounts; flag unexplained differences and deadline risks.

OUTPUT
Provide a jurisdiction-level exception table with obligation, period, amount, source, variance, missing evidence, due date, owner, and adviser question. Keep factual data separate from tax interpretation.

GUARDRAILS
Do not invent rates, nexus, deductibility, or filing positions. Use only supplied rules, label uncertain matters, and route conclusions to qualified tax professionals.
Control principle: A strong template makes missing evidence visible. It should never make an unsupported answer sound more certain.