Who this applies to: Read this if you are a state or local government finance professional and want to use generative AI more effectively while maintaining appropriate review, documentation, and data safeguards.
Government finance professionals are increasingly exploring generative AI to save time, organize information, and improve efficiency. However, the usefulness of an AI-generated response depends largely on the instructions provided. A vague prompt can produce incomplete, irrelevant, or misleading results, while a well-structured prompt can help organize complex accounting information, surface important questions, and identify areas requiring further analysis and professional judgement. To help government accountants get better AI results, this article outlines five elements for effective accounting prompts and shares practical guidance for using AI responsibly.
Important considerations before using AI
Organizations should establish an approved AI-use policy before employees use AI for government finance work. Before entering organizational, confidential, personal, or third-party information into an AI tool, coordinate with IT, information security, legal counsel, and other appropriate stakeholders. It’s important to remember that AI-generated output may be incomplete, inaccurate, or unsupported, and should supplement rather than replace professional judgement, independent verification, established internal controls, or required approvals.
Recognizing when to use AI and what questions to ask are two important considerations. Imagine it is the middle of the year-end close process. You have a bank reconciliation with several old reconciling items, a list of prior-year audit adjustments, and a meeting with the finance director later that afternoon. An organization-approved AI tool may help you organize the issues and prepare questions, but only if it receives useful instructions. “Review this reconciliation” leaves too much undefined. Ask yourself key questions to help determine what is needed to create an effective prompt:
- Which balances should agree?
- Which reporting period is involved?
- How old must an outstanding item be before it receives attention?
- Does the user want possible errors, follow-up questions, or proposed entries?
Writing a useful prompt is like assigning work to someone who is new to your finance department. You need to:
- Explain the background
- Define the task
- Identify the available evidence
- Describe the expected deliverable
- Set boundaries around the analysis
Five elements of an effective accounting prompt
A practical prompt generally includes:
- Context: The government, fund, reporting period, accounting basis, and purpose of the work
- Task: The specific review, comparison, summary, or analysis requested
- Evidence: The records and authoritative sources the AI should use
- Output: The format and level of detail expected
- Guardrails: The assumptions the AI should avoid and the matters that require professional review
The amount of direction should reflect the complexity and risk of the assignment. Rewriting a routine email requires less context than reviewing a year-end reconciliation or federal grant expenditure.
Context: Explain the governmental accounting environment
Context is particularly important in governmental accounting because the same transaction may be treated differently depending on the financial statement being prepared. For example, governmental fund statements are prepared using the current financial resources measurement focus and modified accrual basis of accounting. Government-wide statements use the economic resources measurement focus and accrual basis. A capital purchase recorded as an expenditure in a governmental fund may need to be reported as a capital asset addition at the government-wide level.
A prompt asking AI to review a government-wide conversion entry should therefore identify:
- The applicable governmental fund or activity
- Whether the analysis relates to fund-level or government-wide reporting
- The accounting basis and measurement focus
- The reporting period
- The purpose of the entry
- The supporting schedules provided
Without this context, AI may apply a generally correct accounting concept to the wrong reporting level.
Task: Be specific about the work requested
Broad instructions such as “review,” “analyze,” or “summarize” do not explain what a successful result should contain.
Weak prompt: Review this bank reconciliation and tell me whether anything is wrong.
Stronger prompt: Review the attached June 30 bank reconciliation for the pooled cash operating account. Compare the bank balance, general ledger balance, and listed reconciling items. Identify mathematical inconsistencies, unexplained differences, duplicate items, deposits or checks outstanding for more than 90 days, and items without adequate descriptions. Present the results in a table showing the issue, amount, source reference, and recommended follow-up question. Do not propose a journal entry or conclude that an item is an error without sufficient support.
The stronger prompt defines the scope and focuses the review on specific risk areas. The 90-day threshold is an example for the exercise, not a recommended standard. Each government should use criteria appropriate for its policies and circumstances.
Even with well-crafted prompts, AI tools can still make calculation errors, overlook spreadsheet formulas, and produce inaccurate page, tab, or cell references. Always recalculate totals independently and trace every significant observation back to the original record.
Capabilities also vary by tool and configuration: some tools cannot reliably read attachments, complex spreadsheets, or scanned PDFs, and the same prompt may produce different responses across multiple runs. Long-outstanding checks may also raise unclaimed property or escheatment considerations, which should be evaluated under applicable policies.
Evidence: Identify the records and authorities to use
Government finance conclusions should be traceable to reliable evidence. Tell the AI which files it may use and request a reference for each significant observation. This can be especially useful when developing an inventory of agreements that may require additional accounting analysis.
Agreement-review prompt: Review the attached agreement and extract the commencement date, end date, renewal and termination provisions, payment terms, underlying assets, rights to use or operate an asset, software or hosting components, implementation services, and other provisions that may be relevant to an accountant’s evaluation under GASB Statements 87 or 96. Cite the page and section supporting each item. Identify missing or unclear information as a question. Do not determine whether the agreement meets the definition of a lease or SBITA; the government’s accounting team will make that determination after reviewing the agreement and applicable authoritative guidance.
This separates document review from the accounting conclusion. AI can help locate and organize relevant terms, but the accountant remains responsible for determining the applicable standard and treatment. The same approach applies to technical research. Instruct the AI to use specified authoritative sources, such as GASB pronouncements or federal award documents, and then verify quotations, citations, and paragraph references directly.
Output: Describe the deliverable
A useful analysis can become difficult to use if it arrives in the wrong format. Tell the AI whether you need a table, checklist, memorandum, list of questions, or plain-language summary.
For audit preparation, a government might use an organization-approved tool, consistent with any confidentiality terms in the audit engagement, to review prior-year adjustments and prepared-by-client (PBC) lists:
Prompt: Using the attached prior-year audit adjustment summary and PBC list, prepare a current-year planning table with the following columns: financial statement area, prior-year issue, support previously requested, current-year owner, current-year support needed, due date, and follow-up question. Consolidate duplicate requests. Do not assume that a prior-year adjustment is required again this year.
In my own work, I have found that asking for an approved AI tool to organize prior-year adjustments and open requests into a structured current-year tracker produces a far more useful starting point than asking for a general summary. The structure makes recurring issues easier to spot, reduces duplicate requests, and helps focus follow-up where it matters most.
Other helpful output instructions include:
- Separate confirmed observations from open questions.
- Rank items by urgency or potential financial reporting impact.
- Limit the executive summary to five bullets.
- Identify the source supporting each observation.
- Place unresolved matters in a separate follow-up section.
Guardrails: Explain how uncertainty should be handled
Generative AI may respond confidently even when information is incomplete. A prompt should address uncertainty directly.
Consider including instructions such as:
- Use only the records and authoritative sources provided.
- Do not invent missing balances, transaction details, policies, or citations.
- Separate facts shown in the records from interpretations.
- Label unsupported items “Requires additional support.”
- Draft a question when the cause of a difference cannot be determined.
- Do not make final decisions about standard applicability, allowability, materiality, accounting treatment, or journal-entry approval.
- Identify conclusions that require higher-level review.
These guardrails improve the reviewability of the response, but they do not guarantee accuracy. A finance professional should validate the source references, calculations, and conclusions before using the work.
Break complex assignments into stages
Large assignments are often more manageable when divided into sequential steps. Consider the review of expenditures charged to a federal award:
- Ask AI to summarize the award’s purpose, period of performance, allowable-cost provisions, and any specific or special conditions.
- Review and correct that summary.
- Ask AI to compare selected expenditure descriptions with the summarized criteria.
- Have it identify items requiring invoices, payroll records, procurement support, or program clarification.
- Evaluate the flagged items against the award terms and the Uniform Guidance.
AI can help organize the review, but it should not make the final allowability determination. That decision depends on the complete transaction record, award terms, applicable federal requirements, government policies, and professional judgment. A staged approach is also helpful when reconciling governmental fund statements to government-wide statements. Begin with identifying conversion categories, then review the supporting schedules, and finally develop questions about unresolved differences. Do not ask AI to solve the entire reporting conversion in a single step.
Protect sensitive government information
Use only organization-approved AI tools and follow applicable policies governing confidential information, acceptable use, and records retention.
Before entering information, consider whether it contains:
- Employee or payroll data
- Banking or payment information
- Taxpayer or utility-customer information
- Protected health or personally identifiable information
- Confidential legal matters
- Procurement-sensitive information
- System configurations or cybersecurity information
- Information belonging to auditors, consultants, or other third parties
Remove, mask, aggregate, or replace sensitive information with representative data when appropriate. Approval to access information does not automatically mean approval to enter it into an AI system. Governments should also consider their public records and retention obligations. Depending on applicable state law and how the material is created, used, or retained, prompts and AI-generated outputs related to public business may be subject to disclosure and retention requirements.
Examples of AI prompts
|
Reuseable prompt template
|
|
Context
|
I am reviewing [accounting area] for [government, fund or activity, reporting period, and accounting basis]. The purpose is to [objective].
|
|
Task
|
Using the records identified below, please [specific review, comparison, or analysis].
|
|
Evidence
|
Use [files and authoritative sources]. Reference the page, tab, section, or transaction supporting each significant observation.
|
|
Output
|
Present the result as [table, checklist, memorandum, or questions] and include [required fields or sections].
|
|
Guardrails
|
Separate confirmed facts from interpretations. Identify missing information and matters requiring professional review. Do not make unsupported accounting, compliance, materiality, or standard-applicability conclusions.
|
Examples of strong vs. weak prompts
|
Budget-to-Actual Analysis
|
|
Weak Prompt
|
Analyze these budget variances.
|
|
Stronger Prompt
|
Compare fiscal-year-to-date expenditures with the amended budget and the same period in the prior year. Identify departments with unfavorable variances greater than $100,000 or 10%. For each item, describe the transactions contributing to the variance and draft a follow-up question when the cause cannot be determined. Do not infer a cause that is not supported by the records. Present the results in a table followed by a five-bullet summary for the finance director.
|
|
Accounts Receivable (AR)
|
|
Weak Prompt
|
Review this AR aging report.
|
|
Stronger Prompt
|
Review the attached June 30 AR aging report. Identify credit balances, accounts outstanding for more than 90 and 180 days, balances without recent activity, and amounts that do not agree with the general ledger control account. If subsequent receipt information is provided, identify which balances appear to have been collected after year-end. Present questions and recommended follow-up procedures, but do not conclude that an amount is uncollectible or recommend a write-off.
|
|
Capital assets and construction in progress
|
|
Weak Prompt
|
Find the capital assets in this general ledger detail.
|
|
Stronger Prompt
|
Compare the attached expenditure detail with the government’s capitalization policy. Identify transactions that exceed the capitalization threshold or contain descriptions suggesting equipment purchases, construction, improvements, land acquisition, or project-related professional services. Separately identify repairs, maintenance, and other items that may require further analysis. Do not make the final capitalization determination. Present each flagged transaction with its date, vendor, amount, account, description, source reference, and reason for follow-up.
|
|
Subsequent disbursements and expenditure accruals
|
|
Weak Prompt
|
Find any expenses we need to accrue.
|
|
Stronger Prompt
|
Review the attached disbursements recorded during the first 60 days after fiscal year-end. Identify transactions whose invoice dates, service periods, receiving dates, or descriptions indicate that the goods or services may relate to the prior fiscal year. Present the results by fund and department, identify the supporting documentation needed, and distinguish confirmed dates from assumptions. Do not determine the final accounting period or prepare an entry without sufficient support.
|
Keep professional responsibility with the finance team
AI can identify an unusual balance, extract terms from an agreement, or organize questions from prior-year audit files. It cannot accept responsibility for an accounting conclusion. Management remains responsible for the government’s records, internal controls, financial statements, and compliance decisions. An AI-generated observation should therefore be treated as a starting point for review, not by itself as support for an accounting entry, authorization, or approval. A strong prompt will not turn AI into an accountant. It can produce a more focused first review that helps the finance team spend less time organizing information and more time investigating issues and applying judgment.
Optimizing AI as a support tool
Effective prompting can help government finance professionals use AI as a practical support tool while keeping judgment and accountability with people. By providing clear context, reliable source material, specific instructions, and appropriate guardrails, finance teams can obtain more useful results without compromising verification, security, or internal controls. AI may accelerate the work, but the accountant remains responsible for the conclusion.
Key takeaways
- Structure prompts with clear context, a specific task, supporting evidence, the desired output, and appropriate guardrails.
- Define the government, fund, reporting period, accounting basis, and purpose to help AI apply accounting concepts correctly.
- Verify AI-generated calculations, citations, source references, and conclusions against original records and authoritative guidance.
- Protect sensitive information by using approved AI tools and following organizational policies for confidentiality, security, and records retention.
- Keep accounting decisions, approvals, and professional judgment with the finance team rather than relying on AI-generated conclusions.
About BerryDunn
BerryDunn’s governmental accounting team approaches each new engagement with an open mind, assessing client needs objectively to inform clear, powerful, and actionable recommendations. We partner with clients to establish compliance practices, optimize processes, and enhance the overall financial reporting process. Learn more about our team and services.