Make AI-prepared journals prove the schedule before they reach the ledger

The product announcement changes the control question

On August 20, Xero said a forthcoming JAX agent will handle monthly practice work from reviewing document reconciliation status through manual journals for prepayments and amortization, then provide a complete account of its actions for customers to review and accept. That is a concrete product direction, not evidence that the accounting is correct by default.

The announcement moves AI from explaining a ledger toward preparing a posting artifact. The human gate therefore needs more than a summary and an Accept button. A reviewer must know which source population was included, which policy was applied, how each service period was determined, how the schedule was calculated, which exceptions were excluded, and whether the exact approved proposal became the posted journal.

Xero's current JAX beta documentation provides useful boundaries. JAX works within existing practice permissions, processes data after a user sends a message, and says it will not act on the user's behalf in the documented beta experience. Product availability and behavior can change by region, plan, and rollout. The new month-end agent is described as forthcoming, so this guide treats it as a trigger for control design rather than claiming it is already available to every customer.

Practitioner evidence shows why the boundary matters. A current r/Accounting thread asks what staff should do when a CFO wants the team to “use AI,” while a July r/xero discussion reports a user demonstrating that JAX failed to answer several questions. Neither thread establishes product quality. Together they show a common operational gap: leadership wants adoption, but the accounting team still needs a task-specific acceptance standard.

Freeze the eligible population before calculating anything

A recurring schedule is only as complete as the source population. Begin with the prior approved schedule and the ledger opening balance. Add current invoices, contracts, purchase orders, approvals, credits, cancellations, refunds, transfers, and modifications through a documented cutoff. Reconcile that inventory to an independent system report or control total.

Document reconciliation status is relevant but not sufficient. A captured invoice may still be a duplicate, assigned to the wrong entity, missing an approval, outside policy, or linked to a service period that differs from the invoice date. A missing document can also remain invisible if the source system population was never reconciled. The AI should receive explicit evidence IDs and completeness status rather than an unbounded folder.

Do not let the model fill gaps with plausible dates. A twelve-month software invoice may cover a contractual period that begins before or after the invoice date. An annual insurance policy can include endorsements and cancellations. A deferred implementation cost may require a different policy from a prepaid subscription. The workflow routes classification to a qualified accountant instead of treating every “annual” payment as straight-line prepayment.

The schedule is a deterministic accounting data product

Build the schedule outside model prose. Each row should carry original cost, opening accumulated release, current additions or reductions, approved recognition rule, current-period release, closing accumulated release, remaining balance, remaining periods, currency, account mapping, and status. A controlled spreadsheet, accounting module, or deterministic script should reproduce the arithmetic.

closing_balance = opening_balance
                + approved_additions
                - approved_credits_and_transfers
                - current_period_release
                - other_approved_reductions

assert accumulated_release <= approved_cost_basis
assert current_period_release >= 0
assert schedule_closing == ledger_opening + journal_movement
assert total_debits == total_credits

The model can propose the formula inputs and explain anomalies. It should not be the only calculation engine. Independent reperformance matters because the schedule can be internally polished while using the wrong start date, number of periods, day-count convention, currency rate, or sign. Recalculate every material item and a risk-based sample of the rest, then compare results within an approved tolerance.

PCAOB AS 1105 is written for auditors, not management's complete close process, but its evidence principles are useful: information produced by the company needs accuracy, completeness, precision, and relevance. AS 2501 similarly emphasizes process, assumptions, evidence that supports or contradicts an estimate, and professional skepticism. When a schedule includes estimates or judgment, the control packet should show those elements rather than hiding them inside an AI explanation.

Bind every schedule export to a digest and cutoff. If a late credit arrives after the schedule was approved, create a new version and rerun the gate. Do not edit the file while keeping the same proposal ID. Version discipline is what lets the reviewer prove that the journal posted was the journal reviewed.

Worked example: annual insurance with a midterm credit

Assume a company pays $120,000 on July 1 for a twelve-month insurance policy running July 1 through June 30. Company policy permits straight-line monthly release when coverage is even and the contract supports the period. The July and August releases are $10,000 each. At August 31, before other changes, accumulated expense is $20,000 and the remaining prepaid balance is $100,000.

On August 15, the insurer issues a $12,000 credit for removing one location, effective September 1. The wrong shortcut is to divide the net $108,000 by twelve and retroactively change July and August. The schedule should preserve the original approved releases, link the credit to the policy modification, and apply the approved treatment from the supported effective date. The qualified accountant decides that treatment; the model only lays out the evidence and arithmetic.

The review packet should show at least two separate proposals if policy interpretation is unresolved: one applying the credit to remaining coverage and another holding it as an exception. It should not choose the lower expense or force the ending balance to a target. The named policy owner resolves the question and the schedule is recalculated from that decision.

After approval, the recurring August journal may debit insurance expense and credit prepaid insurance for $10,000. The credit-related entry, if any, is a separate controlled line with its own evidence IDs. Separating the lines makes the change reviewable and prevents a net amount from hiding opposing movements.

The journal proposal needs a release contract

A journal proposal should identify entity, book, period, posting date, currency, debit and credit accounts, dimensions, description, amount, reversal behavior, source IDs, schedule version, policy version, preparer, and required approvers. “Post the amortization” is not a sufficient instruction.

proposal_id: PREPAID-2026-08-0042
status: proposed_not_posted
schedule_digest: sha256:4f8...
entity: US01
book: corporate
period: 2026-08
posting_date: 2026-08-31
currency: USD
lines:
  - {account: 610200, debit: 10000.00, credit: 0, cost_center: CORP}
  - {account: 142100, debit: 0, credit: 10000.00, cost_center: CORP}
reversal: none
source_ids: [POLICY-8841, INV-99210, SCHEDULE-2026-08-v4]
required_approvals: [accounting_manager]
posting_role: close_operator

Validate total debits and credits by entity and currency, not only for the complete batch. Confirm signs, account status, dimensions, posting period, duplicate journal detection, and reversal configuration. A technically balanced entry can still be wrong because it uses the wrong entity, expense account, department, period, or service date.

Use segregation of duties that fits the organization. The preparer assembles evidence and the schedule. An independent reviewer reperforms calculations and checks mappings. A policy owner resolves judgment. A final approver authorizes one digest. A controlled posting operator imports or enters that exact artifact. In a small team, one person may hold several roles, but self-review risk and compensating controls should be explicit.

Route exceptions instead of averaging them into the schedule

Recurring close automation creates value by separating routine items from exceptions. It creates risk when the exception lane becomes a place where unmatched amounts disappear. Every exception needs an amount at risk, consequence, owner, evidence request, deadline, provisional treatment, and status.

• Missing service period: hold the item until the contract, purchase order, acceptance, or policy owner supplies evidence.
• Credit or cancellation: link to the original item, confirm effective date, and recalculate remaining basis without retroactive netting unless approved.
• Duplicate source: quarantine both records until identity and ledger posting are reconciled.
• Foreign currency: separate transaction-date basis, release rule, remeasurement, and translation under approved policy.
• Impairment or abandoned benefit: route to accounting judgment; do not continue the prior schedule automatically.
• Prior-period error: do not bury the correction in the recurring journal; follow correction and reopening policy.
• Unapproved mapping: hold rather than selecting the closest account name.
• Material item: trigger the required additional reviewer, consultation, or evidence threshold.

Some exclusions allow the routine population to proceed. Others undermine completeness of the entire schedule. A missing low-value invoice may be isolated under policy; an unreconciled opening balance means the close population itself is unreliable. The human reviewer makes that distinction and records the basis.

Accept one exact version, then reconcile the posted consequence

The release gate should offer APPROVE TO POST, APPROVE WITH DOCUMENTED EXCLUSIONS, REWORK, HOLD, or REJECT. It must identify the exact proposal digest, schedule digest, source cutoff, unresolved exclusions, required approvers, posting role, and expiration. Approval should expire if the proposal, schedule, mapping, period, or source population changes.

After posting, capture the journal ID, timestamp, operator, batch or import result, rejected lines, manual changes, and attachments. Compare the posted lines with the approved proposal. Then reconcile the ledger's closing prepaid or deferred balance with the approved schedule. An approval receipt without a post-posting tie-out proves intent, not outcome.

PCAOB's journal-entry guidance highlights risks around population completeness, selection, documentation, and entries made near period end. Again, management's control design is not identical to an auditor's procedure. The lesson is still useful: journal evidence must support the complete population and the reason for the selected treatment, not merely show that someone reviewed a screen.

Keep the AI transcript only if policy permits and it adds value. The core retained evidence is the source register, calculation, independent reperformance, exception log, exact journal artifact, approvals, system receipt, and reconciliation. A verbose conversation is not a substitute for a concise, structured workpaper.

Failure modes that survive a quick Accept click

A 30-day pilot for one recurring journal lane

1. Select one low-complexity, recurring prepayment class with clear policy, stable mappings, and reversible posting.
2. Freeze the prior schedule, source-population report, control totals, policy, calculation convention, and approval roles.
3. Run the AI-assisted workflow in shadow mode for two closes without posting from the AI output.
4. Measure population coverage, unsupported dates, mapping errors, calculation differences, exceptions, reviewer time, rework, and close-cycle time.
5. Seed tests for a duplicate invoice, missing contract, mid-period credit, wrong entity, stale mapping, closed period, and changed proposal after approval.
6. Require independent recalculation of every material item and a rotating sample of routine rows.
7. Issue a mock approval receipt and prove that any schedule change invalidates it.
8. Post one controlled canary journal only after the established accounting gate, then reconcile journal, ledger, and schedule.
9. Review segregation of duties, evidence retention, access, model/tool changes, and rollback with accounting and system owners.
10. Decide SCALE, LIMIT, REDESIGN, HOLD, or STOP based on accepted journals and total review cost, not draft speed.

A successful pilot does not prove that the model “knows accounting.” It proves that one bounded workflow can reach an accepted journal with complete evidence, reproducible calculation, controlled exceptions, qualified judgment, and an exact ledger tie-out more efficiently than the prior process.

Frequently asked questions

Can AI post a prepayment or amortization journal automatically?

A product may support automated actions, but capability is not authority. This workflow keeps the output as a proposal until qualified humans verify the population, policy, schedule, accounts, dates, signs, dimensions, reversals, exceptions, and exact posting artifact.

Is an AI action log sufficient review evidence?

No. It can document system behavior, but it does not prove the source population was complete, the treatment was appropriate, calculations were correct, approvals were valid, or the ledger matches the approved schedule.

Should every schedule row be manually recalculated?

Reperform every material or high-risk item and use a risk-based sample for routine items under the organization's control policy. Also tie full-population control totals, because sampling cannot prove that missing items were included.

What if the service period is missing?

Return HOLD. Request the contract, purchase order, acceptance evidence, policy decision, or another approved source. Do not default to invoice date, payment date, or twelve months because the result looks reasonable.

Does this workflow determine the accounting treatment?

No. Qualified professionals must apply the relevant framework, company policy, facts, materiality, tax, legal, audit, and regulatory requirements. The pack organizes preparation and review evidence.

How should product roadmap claims be interpreted?

Verify current availability in the relevant tenant, geography, plan, and documentation. Xero's August announcement describes the month-end agent as forthcoming; this guide does not assume universal availability.