Kraven sweeps and Daily Board automation

Kraven 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.

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

How sweeps work

A Kraven sweep is a controlled review pass over Daily Board work. During a sweep, Kraven 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

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

Automatic and manual runs

By default, automatic Kraven 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 Kraven 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

Kraven 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 Kraven mode, evidence confidence, and approval policy

If Kraven 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.

What users should expect

Kraven should tell you whether an item was:

• safely handled
• prepared and waiting for approval
• blocked by setup, source access, or client input
• routed for human review
• acknowledged without source-condition proof

For accounting-sensitive work, Kraven 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.