Skip to main content
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

1

The job

Who has this problem and what it costs them.
2

What you'll build

The flow, end to end.
3

Ingredients

Tables, master data, integrations, model tier.
4

The starter SOP

A complete, copy-paste procedure. Change the field names to yours and it runs.
5

Walkthrough

Setup, first cases, and what good looks like in review — including one case the agent correctly refuses to auto-resolve.
6

Iterating and hardening

Editing the SOP by chat, running the improvement loop, then triggers, agentic approval, and thresholds.

​
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 to refine against your actual review feedback.
All sample data in these cookbooks is invented — companies, products, codes, and values. Replace it with your own.

​
Available 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.

Order processing: PO matching

Purchase orders arrive in every shape. Match buyer to customer master, line items to item master, resolve shipping, draft the confirmation.

Invoice automation: vendor invoice audit

Cross-reference vendor invoices against POs and receipts. Catch duplicates, price and quantity mismatches, and missed credits — continuously.

Inbox intake

Turn a shared mailbox into structured, worked cases — routing, attachments, special requests, and drafted replies.
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 for why that order matters.
More recipes are on the way: vendor statement reconciliation, master-data sync and dedup, the month-close pattern, and agent-generated reporting.

New to cloudsquid?

Start with the quickstart — it builds a miniature version of the PO matching recipe in about 15 minutes.