Detect balance-sheet variances automatically with a reconciliation agent

Step 1: Define the reconciliation ruleExcel

Set an explicit materiality threshold — a flat dollar amount, a percentage of account balance, or whichever is larger (e.g. "over $500 or 1%, whichever is greater") — and write it down in the agent's instructions rather than leaving it implicit.

Without a stated number, the agent has no way to distinguish a $12 rounding difference worth ignoring from a $5,000 variance worth real attention.

Step 2: Connect the agent to your GL export and balance sheetCopilot Studio

Point a Copilot Studio agent at the general ledger detail and the balance sheet tab so it can compare them line by line each period.

Prompt idea:

Compare the GL detail export against the balance sheet by account. Flag any variance over $500 or 1% of the account balance, and draft a correcting journal entry with a one-line explanation for each flagged item.

Step 3: Review flagged items before posting anythingExcel

Treat every drafted correcting entry as a suggestion, not an instruction — the agent doesn't know about timing differences or in-flight approvals that explain a variance.

Step 4: Track recurring variancesExcel

If the same account flags every month, that's a process problem worth fixing upstream, not something to keep correcting downstream.

Check the work

• Trace each flagged variance back to its source transactions in the GL before accepting the correcting entry.
• Confirm the materiality threshold is actually being applied consistently across accounts.
• Watch for the same account recurring month after month — that signals a root-cause issue, not a one-off.

Source: Microsoft Copilot Scenario Library — Finance (2026)