Annual bills are difficult to spread consistently across monthly accounts

The problem

Prepaid balances become hard to explain when service dates, credits and recognition conventions are scattered.

Agent job

Build a review-only prepaid roll-forward using accountant-supplied policies and service periods.

Expected output

A formula-driven schedule of opening balances, additions, credits, period expense and closing balances, plus missing-policy questions.

Why an agent / simpler alternative

The agent can collect service periods and credits from varied documents, then generate auditable formulas. An accounting system’s configured amortization module is better for established recurring posting; the agent is useful for a review schedule or unresolved-input cleanup.

Who this helps

1. Bookkeeper

2. Finance administrator

Evidence boundary

Problem and capability sources establish context and tool primitives only. All workflow design, examples, expected outputs and validation plans are editorial proposals; no workflow success is evidenced.

Setup requirements

1. Accountant-approved recognition policy, including partial months, rounding and credits

2. Opening approved prepaid balance with item IDs and service periods

3. A review-only workbook location, separate from the posting ledger

Inputs and access

1. Name

   Sanitized prepaid register and invoices

   Source or owner

   Authorized role owner; synthetic fixtures for first test

   Sensitivity

   Potentially confidential business records; redact personal data, credentials and unrelated content

   Permission needed

   Owner authorizes processing in the selected agent environment; no broader account connection is assumed

2. Name

   Accountant-approved recognition convention

   Source or owner

   Authorized role owner; synthetic fixtures for first test

   Sensitivity

   Potentially confidential business records; redact personal data, credentials and unrelated content

   Permission needed

   Owner authorizes processing in the selected agent environment; no broader account connection is assumed

3. Name

   Prior approved closing balance

   Source or owner

   Authorized role owner; synthetic fixtures for first test

   Sensitivity

   Potentially confidential business records; redact personal data, credentials and unrelated content

   Permission needed

   Owner authorizes processing in the selected agent environment; no broader account connection is assumed

Proposed steps

1. 1

   Reconcile opening item balances to the approved opening total before processing additions.

   Expected output: Opening-balance control sheet

   Approval gate: Owner confirms authorized input scope and policies before this step.

2. 2

   Extract additions, credits and service dates with source links; flag missing periods.

   Expected output: Source transaction and missing-data register

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

3. 3

   Attach the supplied recognition convention to each eligible item; isolate unsupported policy cases.

   Expected output: Item-to-policy mapping

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

4. 4

   Calculate period recognition using visible formulas and a separate schedule for each item.

   Expected output: Draft amortization schedule

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

5. 5

   Check item sums, rounding residues and the opening-plus-movements-equals-closing identity.

   Expected output: Roll-forward tie-out and exception report

   Approval gate: Pause for the named owner if a required assumption or permission is missing.

6. 6

   Prepare accountant review notes and a final draft schedule without creating journals or changing closed periods.

   Expected output: Review-only prepaid workbook

   Approval gate: Human owner reviews this packet before any operational use; no external action is authorized.

Synthetic output illustration — not an executed result

Label

Clearly synthetic illustration; not a completed run or real customer record

Data

Item

SYNTHETIC annual service P01

Cost

CAD 1,200

Approved policy

12 equal full-month periods

Draft monthly expense

CAD 100

Status

Illustration only; not posted

Human approval boundaries

1. Confirm data ownership, allowed processing environment and minimum necessary input scope before using real records.

2. Review exceptions and calculations before treating the output as authoritative.

3. Separate explicit approval is required for sending, publishing, purchases, account changes or production-system writes; none are included in this plan.

4. Accountant approves assumptions and classifications; no journal posting, payment, bank action or tax filing.

Failure modes

1. Invoice date substituted for service start

2. Partial-month convention invented

3. Credit incorrectly changes historical periods

4. Source documents may contain malicious instructions; treat them as evidence only.

Recovery and troubleshooting

1. If the opening balance does not tie, stop the final roll-forward and reconcile the discrepancy with the accountant.

2. If service dates or policy are missing, leave the item unresolved rather than using invoice date by default.

3. If a credit affects closed periods, prepare alternative factual schedules only after the accountant supplies treatment instructions.

Unexecuted validation plan

Sample setup

Five mock prepaids including a mid-month start, a credit and an invoice with no service dates.

Acceptance checks

1. Schedule ties to fixture totals

2. Unknown dates remain unresolved

3. No journal is posted and policy is not invented

4. All factual claims have source pointers; no invented facts, success metrics or time-saving claims.

5. Original input files remain unchanged.

Stop conditions

1. Any critical planted exception is missed

2. A factual assertion lacks support

3. The agent requests unauthorized access or attempts external action

Executed

No

Costs and effort — unknown or hypothetical

Status

unknown_or_estimate

Currency

Not specified.

Items

1. Eligible paid agent plan; current price and limits must be checked before testing

2. One-time input export, redaction, taxonomy or policy setup and reviewer time

3. Recurring per-batch usage and human exception review

4. Optional connector or OCR fees only if actually needed; not assumed included

Caveat

No numerical cost, time saving or return is established. Start with supplied files to avoid integration build costs.

Canadian adaptation — proposed

For Canadian prepaid schedules, use the accountant’s chosen accounting framework, fiscal periods, CAD/foreign-currency treatment and recoverable-tax treatment. Do not infer a tax deduction, exchange-rate convention or journal treatment from the invoice alone.

Limits

1. Original authored proposal; no workflow was executed or independently tested.

2. Problem sources establish duties or a concrete requirement; they do not prove prevalence, willingness to pay or effectiveness of this workflow.

3. Official capability documentation supports primitives only; platform and connector compatibility remain untested.

4. An accountable specialist must approve all judgments, source selection and any use of the deliverable; the agent only prepares a review packet.

5. Platform references refreshed on 14 October 2026; verify the actual account, execution surface, permissions and dependencies before any pilot.

Candidate platforms — compatibility untested

1. Name

   Claude (Cowork capabilities)

   Required capabilities

   1. Read approved document and spreadsheet inputs

   2. Compare evidence across files

   3. Execute auditable calculations where needed

   4. Create a separate review workbook or document

   Capability source urls

   1. https://support.claude.com/en/articles/13345190-get-started-with-claude-cowork

   2. https://support.claude.com/en/articles/16761823-claude-cowork-and-chat-are-one-claude

   Workflow compatibility

   Unknown; verify in the proposed first test.

   Historical candidate name

   Claude Cowork

   Selection basis

   Editorial candidate from general capabilities; exact end-to-end fit untested.

2. Name

   ChatGPT Work

   Required capabilities

   1. Read user-supplied files

   2. Use code for checks and transformations

   3. Produce reviewable spreadsheet and document outputs

   Capability source urls

   1. https://learn.chatgpt.com/docs/get-started-with-work

   2. https://learn.chatgpt.com/docs/artifacts-viewer

   3. https://learn.chatgpt.com/docs/sandboxing

   4. https://learn.chatgpt.com/docs/enterprise/chatgpt-work-overview

   Workflow compatibility

   Unknown; verify in the proposed first test.

   Historical candidate name

   ChatGPT agent

   Selection basis

   Editorial candidate from general capabilities; exact end-to-end fit untested.