AI Playbooks

Playbooks are guided work sessions run by Kraal's AI engine on real accounting workflows. Instead of a one-off chat answer, a playbook reads the live state of the work, narrates what it found, and drives the workflow forward step by step — with every consequential action proposed to you for approval first.

Playbooks are designed for accountant-in-the-loop work. Kraal assesses, batches, and proposes; you decide. Nothing is posted, sent, or finalized before a person approves it.

When to use playbooks

Use a playbook when you want a consistent, reviewable way to drive repeatable work across clients or periods. Good examples include:

• Working a client's unreconciled bank lines to cleared.
• Catching up open close periods, oldest month first.
• Chasing outstanding client documents before close.
• Sweeping the work queue's ready-to-post rows in one approval.
• Preparing an AP payment batch or an AR reminder pass for approval.

For one-off questions, ChatIQ or the Ask Kraal panel may be enough. For repeatable operational work, a playbook gives Kraal a tighter scope, a defined sequence, and approval gates at each consequential step.

Available playbooks

Playbook	What it does
AP Payment Run	Drives a client's AP payment batch through the standard review, preflight, and matching steps. Every payment action is proposed for approval, and items on hold are never paid.
AR Collections	Reviews overdue receivables against the client's reminder cadence and proposes the reminder pass as a single approval. No reminder is sent until you approve it.
Bank Reconciliation	Works a client's unreconciled bank lines using the standard reconciliation run and the prepared match packets, each applied only after your approval.
Client Document Chase	Reviews outstanding client document requests and close-driven document gaps, then proposes new requests, reminder batches, and delivery fixes for approval.
Close Catch-Up	Drives a client's open close periods to done, oldest month first, running each month's close checklist. Approval-required items wait for a person.
Inventory Flow	Drives order-to-cash and inventory document flow. Each document conversion or work order action is its own approval, and compliance blockers pause the run until resolved.
Queue Sweep	Packages the work queue's ready-to-post rows into batch approvals for a one-click sweep, leaving every judgment row with you.
Report Pack Delivery	Generates a client's monthly report pack and proposes sending and locking as two separate approvals, with recipients confirmed first.
Transaction Processor Review	Drives a Transaction Processor review session: batches similar low-risk fixes for approval, brings judgment items to you one at a time, and posts only after a final approval.

How to run a playbook

1. Open the workspace page where the work lives — for example Bank Reconciliation, a close period, Work List, Report Packs, or the Transaction Processor.
2. Use the Work with Kraal button on that page. On some pages it carries a workflow-specific label, such as Let Kraal drive this reconciliation or Run Kraal Sweep.
3. Review Kraal's assessment of the current state. If the playbook asks for input — exclusions, recipients, or a decision on a judgment item — answer before it continues.
4. Approve or reject each proposed action. Approved actions run on Kraal's standard workflow rails and report back what happened.
5. Review the completion summary: what ran, what was skipped, and what still needs a person.

If a session pauses waiting on you, it resumes once you answer or approve. You can exclude specific items from a single run without changing any standing policy.

Review expectations

Before relying on a playbook run, confirm:

• The selected client, entity, and period are correct.
• The assessment matches what you expect from the underlying workspace.
• Each proposed action is specific enough to approve with confidence.
• Anything skipped or held is either resolved or intentionally deferred.
• The completion summary matches what you see in the accounting records.

Guardrails

Playbooks are intentionally bounded:

• They are approved organization workflows, not open-ended background automation.
• Every consequential action — posting, sending, converting, locking — is a proposal that waits for human approval.
• Judgment calls are routed to you as questions, never decided silently.
• Exclusions and pauses apply to a single run; standing policies are only changed by a person on the normal settings surfaces.
• They do not bypass your firm's approval or review process, and high-risk items stay with a person regardless.

For sensitive or high-impact accounting changes, use the normal review and approval flow before making changes in your accounting system.

Tips for better results

• Start the playbook from the right client and workspace context.
• Answer input requests promptly so the session can continue.
• Use per-run exclusions when a specific item should sit this run out.
• Review the proposed batch contents before approving, especially amounts and counterparties.
• Re-run the playbook after resolving blockers; each run re-checks live state before acting.