Reconciliation | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Reconciliation and proposed adjusting items.

Start with: GL/subledger/bank statement exports for the same period.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

Match the scope, period, currency and opening balances of the records being reconciled.
Compare transactions using stable identifiers and supporting attributes. Do not force a match on amount alone.
Classify differences as timing, missing record, duplicate, misclassification or unresolved, with evidence and an accountable role.
Return the reconciliation and proposed corrective items. Verify the reconciled balance mathematically and keep unexplained differences separate from approved adjustments.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve cash visibility and accounting preparation.

Possible success measures: Close days, reconciliation differences, forecast error. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions

---
name: reconciliation
description: "Prepare reconciliation and proposed adjusting items. Use for this workflow with supplied business information."
---

# Reconciliation

## Inputs and purpose

Use this workflow to prepare: Reconciliation and proposed adjusting items.

Start with: GL/subledger/bank statement exports for the same period.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Match the scope, period, currency and opening balances of the records being reconciled.

2. Compare transactions using stable identifiers and supporting attributes. Do not force a match on amount alone.

3. Classify differences as timing, missing record, duplicate, misclassification or unresolved, with evidence and an accountable role.

4. Return the reconciliation and proposed corrective items. Verify the reconciled balance mathematically and keep unexplained differences separate from approved adjustments.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve cash visibility and accounting preparation.

Possible success measures: Close days, reconciliation differences, forecast error. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).