Finance Workflow Examples · GL and close · Tier 1 · first governed workflows
AR sub-ledger reconciliation with aging buckets
The receivables twin of the AP rec, with aging buckets, credit memos and unapplied cash as negative open amounts, and receipts posted after the as-of date backed out.
Current effort: Monthly, three to six hours · ERP shops, professional services, telecom.
On the one-page 1113 Workflow Card
The 1113 Workflow Card is a structured way to examine one recurring task before deciding where AI belongs: seven fields, one page. It is not, by itself, a production specification, execution log, evidence that a review occurred, or control certification.
- 01 · Purpose and triggerWhy the task exists, when it starts, and what business outcome it supports.
Confirm that open receivables agree to the GL by account and show the aging honestly, so the reviewer can approve the balance and the CFO gets a reliable aging story. Starts at month end when the AR extract is cut.
- 02 · Inputs and permissionsWhat comes in, where it comes from, its sensitivity, and whether it may be used in the approved AI environment.
The AR open-item extract as of month end with document types, the trial balance, and the list of receipts posted after the as-of date. Contains customer names and balances; treat as confidential. Whether the extract may enter the approved AI environment depends on the organization's policy; practice or sanitized files are used until that is confirmed.
- 03 · Current stepsWhat the person does today, in order.
Per account: bucket open items (current, 31 to 60, 61 to 90, 91 to 120, over 120). Treat credit memos and unapplied cash as negative open amounts. Back out receipts posted after the as-of date. Compare to the trial balance by account. Explain each difference. Write the aging narrative.
- 04 · Rules, judgment, and AI’s roleWhat must remain deterministic, where judgment is required, and exactly what AI prepares.
Deterministic (computed in code, the same answer every time): Open-amount logic, the receipts cut-off, the aging buckets, and the comparison to the trial balance. Code.
Needs judgment: Whether a residual difference is a posting error or a cut-off item, and what the aging movement means for collections.
AI prepares: Draft the explanation for each difference, draft the aging narrative from the bucket totals, and answer 'show me the items behind this difference' from the extract. It does not set the cut-off or the buckets.
- 05 · Output and downstream useWhat is produced, who uses it, and whether it informs a decision or changes another system.
AR-versus-TB by account with the difference, the aging by bucket, an as-of stamp, and a short aging narrative. Used in the same approval loop as AP and in the month-end pack; nothing posts.
- 06 · Checks, exceptions, and responsibilityWhat a person reviews, how errors are identified, what happens when something is wrong, and who remains accountable.
The reviewer approves by email, checking the credit-memo and unapplied-cash handling and any receipt near the cut-off. A difference that cannot be explained goes back to the AR clerk. The reviewer remains accountable for the balance and the narrative.
- 07 · Evidence and next decisionCurrent effort, expected benefit, quality measure, test result, and the decision to continue, revise, decompose, or stop.
Current effort: three to six hours by hand each month. Expected benefit: the explanation and narrative drafting stop being typed from scratch; a hypothesis until measured. Quality measure: accounts tie or carry an explained difference, and the aging narrative matches the bucket totals. Test result: illustrative example, not yet tested in your environment. Next decision, continue, revise, decompose, or stop: to be established during evaluation.
Control in this example. Nothing posts to the sub-ledger or the GL. Write-offs and adjustments follow the existing approval.
AI handles defined preparation. A person reviews. Your controls remain in place.
Where it goes wrong
Forgetting the cut-off. Receipts after the as-of date are the most common false difference.
Why it lands in a room
Same recognizable shape as AP; adds the aging story every controller has told a CFO.
This example illustrates the method. It is not a production-ready workflow, a software specification, or a substitute for your organization’s policies, controls, and approved technology environment.