Kraal sweeps and Daily Board automation

Kraal helps accounting teams keep the Daily Board moving by reviewing open work, grouping related items, running bounded safe actions, and preparing work that needs approval.

Kraal is designed to reduce manual review load without continuously scanning every connected system every few minutes.

How sweeps work

A Kraal sweep is a controlled review pass over Daily Board work. During a sweep, Kraal may:

• identify items that are safe to handle automatically
• group related review items, such as repeated source blockers or recurring exceptions
• prepare approval-ready accounting work for a controller or admin to approve
• recheck source conditions after a repair or approved action
• leave blocked items visible when source access, client input, or accounting judgment is still needed

Kraal separates lightweight Daily Board refresh from heavier accounting review. The board can refresh in the background, while full Kraal sweeps are budgeted and conservative.

Between-close detection

Sweeps also run two detection passes between closes, so problems surface as they emerge instead of waiting for the month-end checklist:

• Accrual discovery — scans the period a close would be working on for accruals it may be missing: vendors that bill on a cadence and went silent, prior accruals that stopped recurring, and bills that arrived after cutoff for in-period service. Candidates land in the accruals register with their reason and evidence.
• Error & risk detection — scans for duplicate journal entries and vendor payments, round-amount manual entries, weekend and backdated postings, suspense-account activity, and statistical outliers. Findings land in the risk findings register for disposition.

Both passes are detection only: nothing is proposed for posting and nothing posts. They surface the same candidates and findings you review during Accrual Identification and Errors & Risk Review in the close, just earlier. If a source could not be read during a pass, the run says so rather than presenting the period as clean.

Automatic and manual runs

By default, automatic Kraal sweeps are intended to run at a conservative cadence, such as morning and afternoon business review windows. This keeps work fresh without repeatedly reading source systems when nothing meaningful has changed.

Users with the right access can also start a manual sweep when they want Kraal to review the board immediately. Manual sweeps are useful after:

• new documents are uploaded
• bank or accounting data has synced
• a setup or permission issue was fixed
• an approval was completed
• a controller wants to clear the board before a review meeting

Kraal may also use targeted event-driven sweeps after meaningful changes. These should focus on the affected client, source, or work item rather than reprocessing the whole portfolio.

Resource guardrails

Kraal sweeps use guardrails so automation stays useful and predictable:

• each run has a bounded amount of work it can inspect
• safe actions are capped per run
• repeated work is grouped instead of handled as unrelated one-off items
• unavailable or unchanged sources should use backoff rather than repeated retries
• accounting mutations remain controlled by the client's autonomy mode, evidence confidence, and approval policy

If Kraal cannot prove that a source condition was fixed, it keeps that distinction visible. A wake can be acknowledged or dismissed, but that is different from proving the underlying source issue has cleared.

Certified packages

Some Kraal work is packaged so the backend can certify it before execution. That means Kraal is not guessing at the boundaries of the work. It can see:

• the exact work item it is handling
• which client, workspace, or entity scope applies
• whether the work is read-only, draft-only, or allowed to mutate data
• what receipt or audit record should come back after the run
• what follow-up check should happen after the run
• when to stop and leave the item visible if the source changes or the boundary no longer holds

This is what makes Kraal useful for accounting teams: it can do more work safely, while still leaving a clear review trail when human judgment is needed.

Policy-guided routing

When client policy context is available, Kraal can use it to tune how it selects work within the certified boundary. In practice, that means the sweep can stay focused on accountant-value work, respect review boundaries, and preserve the same audit trail and follow-up checks.

Policy-guided routing does not remove the review trail or bypass approval. It only helps Kraal choose and batch the work that is already eligible to run.

What users should expect

A sweep reads back exactly what happened to each item:

• completed — safely handled within the certified boundary
• skipped — not eligible or not needed this pass
• held for you — Kraal prepared the work but deliberately stopped for a person; it lands back in your approval or review lanes
• rejected — blocked by setup, source access, or policy, with the stop reason visible

For accounting-sensitive work, Kraal should show why the work is safe, why approval is needed, or why the item stayed visible. When in doubt, review the evidence and approval details before posting or submitting accounting records.