PC
Period-Close Agent

Closes your books while you sleep.

Runs your month-end checklist daily, not just on close week. Flags blockers, re-sequences dependent tasks, drafts the Controller sign-off memo, files the audit packet.

No credit card Live in 60 seconds Off-switch per agent
Saves
5 days / close
Touches
Period closeRecurring JEsAudit trail
01What it actually does

No demo magic. Real actions, real audit trail.

Each action runs through the same engine your humans use: same posting rules, same approval routing, same audit log. The agent's name is on every transaction it touches.

01
Runs the close checklist every morning
Picks up the standard close template (subledger cutoffs, bank recs, accruals, depreciation, allocations, tax accrual, payroll, intercompany, consolidation, sign-off). Walks dependencies; advances anything ready, holds anything blocked.
02
Reverses recurring JEs on day-1 of the new period
Reads the recurring JE schedule. Posts each reversal at 00:00 local entity time. Logs every reversal with the original JE id so the audit trail walks both directions.
03
Drafts the close memo for the Controller
On HardClose readiness, generates the memo: which entities closed, which are blocked, why, suggested resolution, comparative period commentary. Controller signs off; agent files the packet.
04
Files the audit packet
Bundles the trial balance, period-close checklist evidence, recurring JE reversals, intercompany match report, FX rate trail, sign-off log. Drops it in the audit storage with a signed manifest.
02How it decides

The logic behind every action.

Not a black box. The decision rules are explicit, configurable, and surfaced on every action so the auditor (and you) can trace the why.

01
Sequence by dependency, not by schedule
Tasks have explicit predecessors. Bank rec waits for the bank feed; accruals wait for bank rec; tax accrual waits for accruals. Agent never advances out of order.
02
Flag, don't force
When a task can't proceed, the agent opens a Blocker with the missing input named (e.g. 'Bank feed for Entity-04 missing for 31-Mar') and routes it to the responsible owner.
03
Compare to last 3 closes
Each task carries a forecast-finish based on the last three closes for that entity. Anything trending +1 day above forecast pages the Controller before it becomes a problem.
03What you control

Off-switch per agent. Always.

Every agent runs on a leash you set. Approval thresholds, dry-run mode, per-entity disable, audit trail, your call.

01
Off-switch per entity
Disable the agent on a single entity without affecting the others. Useful during a contentious month or an audit lock-down.
02
Approval thresholds
Set which tasks the agent can advance unattended (e.g. recurring reversals, depreciation runs) vs which require Controller sign-off (e.g. accruals over $X, period state changes).
03
Read-only mode
Run the agent in dry-run: it walks the checklist, posts nothing, writes a 'what it would have done' log. Use during evaluation or after policy changes.
04
Audit trail
Every action signed with the agent identity, timestamp, source policy version, and the human who configured it. Append-only, exportable.
04This morning

A real activity log.

Excerpted from a production tenant. Every line is signed, timestamped, and traceable to the action it represents.

Period-Close Agent · activity log · today
06:00
Picked up close checklist for period 2026-03 across 8 entities.
06:01
Posted 47 recurring JE reversals for day-1 of period 2026-04.
06:14
Bank reconciliation completed for 7 of 8 entities. Entity-04 missing 31-Mar bank feed. Blocker opened, routed to Treasury.
07:02
Depreciation run posted for 4 entities (3 entities pending QC of new asset additions).
07:33
Forecast: HardClose readiness 4 Apr (vs. last-3 average 7 Apr). Two entities trending early, six on schedule.
07:34
Controller email drafted: 'Close progress 2026-03, ready for HardClose Apr-04 forecast.' Awaiting send approval.
05Built on

The skills this agent calls.

Every agent is composed from the underlying ERP skills, the same ones your humans use. No private data path, no shadow ledger.

06FAQ

Common questions.

Asked by the people whose name goes on the audit packet.

What happens if the agent is wrong?

Every action is reversible. The agent posts through the same JE engine your humans use, with the same audit trail and approval routing. If a recurring reversal posts in error, the original JE id is on the reversal: one-click roll-back. The Controller sign-off step is the human gate before HardClose.

Can the agent close the period itself?

Only if you let it. By default, period state changes (Open SoftClose HardClose) require Controller sign-off. You can grant the agent SoftClose autonomy per entity if you want; HardClose typically stays human-only for audit reasons.

How does it handle our custom close steps?

Add custom tasks to the close template with their dependencies, owners, and approval rules. The agent treats them like any standard step: runs what it can, flags what it can't.

What does 'saves 5 days / close' mean?

Average across mid-market multi-entity customers running this agent for 3+ closes. Close-week effort drops because the recurring work happens daily and Blockers are surfaced 5–7 days earlier than a manual checklist would catch them.

07The other 7 agents

Run them together.

Agents share the same ledger and the same audit trail. Period-Close hands off to Consolidation; AP Intake hands off to Approvals.

Run the Period-Close Agent on your own data.

Free to sign up. Live in 60 seconds. Walk every screen, post a test JE, invite the team. No credit card, no sales call.

Start free