Discovery field guide / Department
How to find AI opportunities in Finance & Accounting
Where should discovery start?
Start with a recent close, not a catalog of finance tools. Trace one reconciliation from source transaction to approved journal and ask where accountants collect evidence, explain differences, or wait for sign-off. Repeated interpretation of messy documents may justify AI assistance; missing account mappings or inconsistent approval rules usually call for a process or system fix first.
The shared framework
Fourteen stages, from objective to portfolio.
Every guide uses this sequence to connect a business problem to an accountable investment. Revisit earlier stages when new evidence changes the assessment.
Stage 1: Business Objective
Name the outcome the organization is trying to move, so every later idea has something to be measured against.
Stage 2: Department
Locate the team that owns the objective and the work that feeds it.
Stage 3: Process
Describe how the work actually runs today: steps, handoffs, systems, and exceptions.
Stage 4: People
Capture who performs and depends on the work, and what they know that no document records.
Stage 5: Problem
State the friction in plain terms: delay, rework, error, cost, or risk, with evidence.
Stage 6: Opportunity
Frame a specific improvement that addresses the problem, not yet tied to any technology.
Stage 7: AI/Automation Fit
Compare AI, RPA, IDP, workflow automation, process redesign, and no technology change.
Stage 8: Value
Estimate benefit in the objective's own terms, with assumptions written down.
Stage 9: Feasibility
Check data, systems, skills, and change capacity needed to deliver.
Stage 10: Risk
Surface compliance, quality, security, and adoption risks and the controls they need.
Stage 11: Scoring
Rate each opportunity on the same dimensions so comparisons are consistent and explainable.
Stage 12: Prioritization
Sequence opportunities by score, dependencies, and capacity, with reasons people can challenge.
Stage 13: Investment
Match approved effort to the sequence; people with budget authority decide what gets funded.
Stage 14: Portfolio
Track opportunities over time as a living set: delivered, in flight, waiting, and retired.
Start with one observable journey
Choose one legal entity and one recurring reconciliation. Assemble a redacted source extract, the working paper, the exception log, and the review history. Follow both an ordinary item and a material exception before expanding to the whole close.
This guide covers controllership, transactional finance, and financial planning. Supplier selection belongs in Procurement; finance discovery follows the evidence and controls around payment, accounting, and reporting.
Where to look in the work
The working papers between systems
Look at spreadsheet bridges between the ledger, subledgers, bank feeds, and management reporting. Mark every copied balance, narrative explanation, and manual reconciliation. Distinguish work caused by inconsistent identifiers from work that requires reading and interpreting evidence. A connector or mapping table may remove more friction than a model.
Exceptions that survive each close
Sample unmatched receipts, disputed invoices, intercompany differences, and late accruals across normal and peak periods. Record how often an item returns to a preparer and why. The discovery unit is the exception path, including review and correction, not just the initial document or transaction.
Who to interview and what each person knows
Preparer, reviewer, and control owner
Interview a staff accountant while they reconstruct an actual working paper, then ask the controller what makes it acceptable. Include internal audit or the designated control owner before proposing a changed approval step. They often know why an apparently redundant check exists.
The source-data owner
Bring in accounts payable, treasury, or the finance-system administrator responsible for the underlying feed. Ask who can authorize access and correct source errors. A finance analyst's local export is not evidence that a repeatable, permissioned integration exists.
What to ask: follow the evidence
What makes this item hard to close?
Ask: Which missing fact caused the last escalation? Show the evidence used to resolve it. How did you decide the balance was supportable? Which entries must a second person approve? Capture thresholds, segregation of duties, and entity-specific rules instead of assuming every discrepancy is equivalent.
Where does the time really go?
Ask the preparer to separate evidence gathering, active investigation, reviewer effort, and waiting. Ask what happens after a bad classification or unsupported explanation. Check whether closing earlier changes a business decision, rather than treating every elapsed hour as a cash saving.
Signals of opportunity, and reasons to look elsewhere
Repeated interpretation with traceable support
A promising signal is recurring effort reading remittance advice or explaining known reconciliation patterns, with reliable source records and reviewer agreement. Preserve links to those records. A fluent explanation without a reproducible tie to the ledger is a risk signal, not a completed accounting task.
The same correction keeps returning
Repeated coding corrections can expose a bounded candidate for assistance, but first test whether supplier master data, chart-of-account design, or upstream validation explains the issue. Infrequent, material judgments with no stable review standard belong in a different risk category from routine evidence preparation.
How to evaluate what you find
Reconcile before judging the narrative
Use held-out examples that include reversals, missing evidence, and unusual period-end transactions. Assess completeness and supportability as well as classification accuracy. Require abstention on unsupported items and compare the combined preparer-plus-reviewer effort against the current method, including retained evidence.
Keep controls inside the cost estimate
Check access to financial records, retention requirements, change approval, and the audit trail with responsible owners. Do not let the same automation prepare and approve a journal. Price the ongoing testing and review work before calling the candidate feasible.
How to compare, prioritize, and invest
Start before posting authority
Prefer a bounded evidence-gathering or reconciliation-preparation trial with a named reviewer over autonomous journal posting. Sequence data-mapping repairs first when they are prerequisites. Separate one-time cleanup from recurring benefits so the portfolio does not fund the same correction twice.
Invest against a close objective
Compare candidates by demonstrable reduction in rework, more timely decision support, and control reliability, not invoice count alone. Set a stop condition if reviewer effort rises or traceability fails. The controller should own acceptance and decide whether evidence supports a wider rollout.
Turn observations into a comparable opportunity record
Describe the current process before naming a solution. Record the trigger, owner, input, steps, handoffs, systems, output, and exception path. Separate what you observed from what someone recalled and what you still need to verify. A vivid interview story is a useful lead, not proof that every case behaves the same way. Validate it against a sample of ordinary work and difficult exceptions, with the limits of that sample made explicit.
Measure active work separately from waiting. Note the observation period, case mix, frequency, and source of each estimate. Include the receiving team's effort, checking, correction, and escalation so a local improvement does not merely transfer work. Describe the outcome in operational terms before attaching a monetary value. Capacity released is not automatically a budget saving; explain what can actually change and which manager has authority to make that change.
Compare interventions before selecting a tool
If a rule is explicit and the input is structured, test ordinary workflow automation first. If the task repeats a stable interface action, examine RPA and an integration alternative. If the difficulty is reading documents, consider IDP with source checks. AI may help where language or variable evidence requires interpretation, but its output still needs a task-specific acceptance standard. Process redesign or no technology change may be the right answer when policy, ownership, or an unnecessary step causes the problem.
Write down why each alternative would or would not address the observed cause. Do not compare a carefully controlled AI proposal with an artificially weak version of the current process. Include data repair, access approval, integration, training, review, and upkeep in each feasible option. An unavailable prerequisite is a reason to sequence work or pause, not a detail to hide inside a feasibility score.
Agree on a decision, not just a demonstration
Before a trial, name the business owner, evaluator, permitted data, review boundary, and person who can stop it. Define acceptable outputs and failures that must trigger escalation. Use examples held out from development, including missing information and uncommon cases. Compare the complete task with the baseline, including human verification and downstream consequences. Preserve the evidence behind the result so another owner can challenge the conclusion.
Keep value, feasibility, risk, and evidence confidence visible separately. A candidate with an attractive benefit estimate is not ready if its owner cannot obtain the data or operate the controls. Record the decision to investigate, pilot, wait, reject, or retire, with a reason and a condition for revisiting it. After delivery, compare observed results with assumptions rather than leaving the original estimate in the portfolio as fact.
Use the evaluation guide for the evidence standard and the prioritization guide to compare qualified candidates. Your leaders make funding decisions; a score or a discovery tool supplies structured evidence, not investment authority.
Continue through the discovery framework
Browse all departments and industriesRelated practice notes
For focused interview techniques, examples, and scoring detail alongside this field guide:
Bring a reconciliation into IntakeOS
Start with the process owner, a redacted exception, the systems involved, and the approval boundary. Use a demo to see how IntakeOS captures that discovery evidence for qualification; finance leaders still decide whether the opportunity deserves investment.
IntakeOS supports structured interviews, qualification, and comparison; it does not make funding decisions or replace professional review. Learn about VARA, review the trust page, or explore the platform before sharing sensitive information.
Explore discovery in an IntakeOS demo