> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudsquid.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Cookbooks

> Complete recipes for real finance and operations processes — each with a copy-paste starter SOP, sample data, and a full walkthrough.

A cookbook is a complete recipe for one process: the architecture, a working starter `SOP.md` you can copy into your project today, sample data, and a walkthrough from setup to reviewed cases.

They exist because the hard part of a new process isn't clicking through the setup — it's knowing what a good procedure looks like. So every cookbook ships one.

## What's in each cookbook

<Steps>
  <Step title="The job">
    Who has this problem and what it costs them.
  </Step>

  <Step title="What you'll build">
    The flow, end to end.
  </Step>

  <Step title="Ingredients">
    Tables, master data, integrations, model tier.
  </Step>

  <Step title="The starter SOP">
    A complete, copy-paste procedure. Change the field names to yours and it runs.
  </Step>

  <Step title="Walkthrough">
    Setup, first cases, and what good looks like in review — including one case the agent correctly refuses to auto-resolve.
  </Step>

  <Step title="Iterating and hardening">
    Editing the SOP by chat, running the improvement loop, then triggers, agentic approval, and thresholds.
  </Step>
</Steps>

## The promise

Copy the SOP, adapt the field names, run your first cases today. The starter is a real procedure, not a stub — and it's a good starting point for [the improvement loop](/concepts/improvement-loop) to refine against your actual review feedback.

<Note>
  All sample data in these cookbooks is invented — companies, products, codes, and values. Replace it with your own.
</Note>

## Available cookbooks

<CardGroup cols={2}>
  <Card title="Run an audit" icon="magnifying-glass-dollar" href="/cookbooks/run-an-audit">
    **Start here.** Point an agent at 12–24 months of your own AP history, read-only, and get evidence-backed findings. Nothing connects to a production system.
  </Card>

  <Card title="Order processing: PO matching" icon="file-invoice" href="/cookbooks/po-matching">
    Purchase orders arrive in every shape. Match buyer to customer master, line items to item master, resolve shipping, draft the confirmation.
  </Card>

  <Card title="Invoice automation: vendor invoice audit" icon="receipt" href="/cookbooks/invoice-audit">
    Cross-reference vendor invoices against POs and receipts. Catch duplicates, price and quantity mismatches, and missed credits — continuously.
  </Card>

  <Card title="Inbox intake" icon="inbox" href="/cookbooks/inbox-intake">
    Turn a shared mailbox into structured, worked cases — routing, attachments, special requests, and drafted replies.
  </Card>
</CardGroup>

<Tip>
  **Run an audit** and **vendor invoice audit** are the same checks at two stages: one looks backward over history, the other runs on invoices as they arrive. See [from audit to prevention](/concepts/audit-to-prevention) for why that order matters.
</Tip>

More recipes are on the way: vendor statement reconciliation, master-data sync and dedup, the month-close pattern, and agent-generated reporting.

<Card title="New to cloudsquid?" icon="rocket" href="/quickstart">
  Start with the quickstart — it builds a miniature version of the PO matching recipe in about 15 minutes.
</Card>