Audit Trail & Execution Feed

Kraal keeps review history close to the work. Use the execution feed when you are following a specific run, use the client Audit Center when you need a broader client timeline, and use the firm-wide audit view when you need to review activity across the clients you are allowed to access.

The goal is traceability: who acted, what changed, when it happened, which client it belonged to, and where to go next for review. Kraal does not expose hidden system credentials, authentication tokens, or unrelated client data in these views.

Which view to use

View	Use it for
Execution Feed	Following one automated run, dispatch sweep, Kraven activity, or task execution as it progresses
Task Detail	Reviewing the full context for one task, including conversation, artifacts, approvals, and result history
Client Audit Center	Reviewing a client-wide timeline across tasks, approvals, workflow actions, and connected accounting activity
Firm-wide Audit	Reviewing recent audit events across the clients and entities within your access scope

Start with the narrowest view that answers your question. If you are debugging one run, start with the Execution Feed or Task Detail. If you are doing a handoff or close review for one client, start with the Client Audit Center. If you are looking for patterns across a portfolio, use the firm-wide audit view.

Execution Feed

The Execution Feed shows operational progress for automation work. It is designed for live review while Kraal is running, retrying, skipping, or completing work.

Typical entries include:

• work accepted into a queue
• step started, completed, skipped, or failed
• safe execution completed
• human review requested
• retry or repair path surfaced
• completion receipt recorded

Use the Execution Feed to answer:

• Is this run still active?
• Which step failed or needs review?
• Did Kraal skip anything because it was not safe to run automatically?
• What should I inspect next?

The feed is not a replacement for accounting review. It is an operational timeline that helps you understand execution state and navigate to the right review surface.

Client Audit Center

The Client Audit Center is the client-wide audit trail. It combines meaningful events across Kraal tasks, approvals, workflow actions, and connected accounting activity into one timeline.

Use it during:

• daily review handoffs
• month-end close review
• client support investigation
• approval follow-up
• reconciliation of Kraal actions against connected accounting activity

The timeline includes automated journal entries posted during the close workflow — every tax provision, bad debt allowance, prepaid amortization, deferred revenue, payroll accrual, depreciation, FX revaluation, accrual, and intercompany elimination journal entry that Kraal posts is captured with the close period, the close item it belongs to, the posting date, and the resulting journal entry name. Use these entries to trace any specific GL movement back to the close-item run that produced it.

For a full walkthrough, see Audit Center.

Firm-wide Audit

The firm-wide audit view helps authorized firm users review recent events across a portfolio without opening each client one by one. It is useful when you need to confirm whether activity happened across multiple clients, identify recent review actions, or spot operational patterns.

The firm-wide view only shows activity within your access scope. Users with client-limited access should expect to see only the clients and entities assigned to them.

Use the filters to narrow the feed by:

• client
• event family
• source system
• date range
• search terms

Event detail and permalinks

Some audit events can be opened as a dedicated detail page. Use this when you need to share a review pointer with another authorized teammate or return to a specific event later.

Event detail pages may include:

• event summary
• timestamp
• actor or system source
• client and related record context
• related task or document link when available
• structured before/after context when relevant

Permalinks do not grant extra access. A user still needs the right Kraal permissions and client scope to view the event.

Integrity checks

Where available, Kraal can verify whether a client audit sequence is internally consistent. Use this as a review aid when you need extra confidence that the visible audit history is coherent.

An integrity result may report:

• the audit window reviewed
• whether the sequence appears consistent
• any gaps or anomalies Kraal can safely surface
• suggested next steps if review is needed

An integrity check is not a substitute for professional judgment, source-document review, or required firm controls. Treat it as a signal that helps prioritize review.

Safe review practices

• Share audit permalinks only with teammates who already have a business need to access that client.
• Do not paste screenshots containing client names, amounts, or event detail into public channels.
• Use the related task or document links instead of copying raw event details into external systems.
• If an event looks unexpected, review the related task, approval, and connected-system activity before taking corrective action.
• If you suspect unauthorized access or incorrect client scope, stop using the event for operational decisions and escalate through your firm's security process.

What these views do not show

For security and privacy, Kraal audit views are designed not to expose:

• authentication tokens or session details
• integration secrets
• internal infrastructure identifiers
• unrelated client activity outside your access scope
• low-level diagnostic logs that are only useful to Kraal support

Support may ask for a timestamp, client name, event label, or screenshot of a non-sensitive summary when investigating an issue. Do not send credentials, tokens, or private connection details.