Generate Invoices from Project Conversations
You'll end up with: A professional invoice generated from your project chat or email thread
Letting the AI invent rates, hours, or discounts that never appeared in the thread — always tag unclear lines as "needs confirmation" and fix against the chat before sending.
- Have the full conversation copied or exported
- Know your legal business name and how you get paid (bank, Stripe, PayPal, etc.)
- Have client billing name and email
- Open Claude and Google Docs.
Capture the thread and billing identities
Paste or upload the conversation and pin who is invoicing whom before you build line items.
1. Go to https://claude.ai and start a **new chat**. 2. Paste your **full** project conversation — Slack export, email thread (oldest → newest), or meeting chat. Include enough context that rates and deliverables make sense. 3. Paste this prompt: "From the conversation above **only**, extract and label: (a) **Provider** — legal or trade name for who is **sending** this invoice (write UNKNOWN if not stated). (b) **Client** — billing name for who **pays** — company or person (write UNKNOWN if unclear). (c) **Currency** — only if explicitly stated or clearly implied; otherwise UNKNOWN. (d) **Tax IDs** — VAT, GST, EIN, etc. **only** if explicitly mentioned; otherwise write NONE STATED. Do not invent facts. Output a short block titled **Billing identities**." 4. If any line says UNKNOWN, add **one** bullet list under the block: what you must confirm with the client or your records **before** sending the invoice.
Extract billable line items from the chat
Turn messy chat into a table of services, quantities, rates, and short evidence quotes.
1. In the **same** Claude chat, paste: "Build a markdown **table** from the conversation with columns: **Description | Qty | Unit | Rate | Line total | Evidence (short quote)** Rules: - Every **rate** or **scope** must tie to a quoted phrase or number from the thread, or mark Rate as **NEEDS CONFIRMATION**. - Do **not** guess hours or prices. - If there are multiple phases (deposit, milestone, final), group them and add a **Subtotal** row per phase. - End with **Pre-tax subtotal** (sum of line totals only if math is certain; otherwise write NEEDS CONFIRMATION)." 2. Read each row: if **NEEDS CONFIRMATION** appears, decide whether you can fix it from the thread or must message the client **before** invoicing. 3. Delete or merge **duplicate** rows for the same deliverable.
Assemble invoice sections (totals, tax placeholder, terms)
Add invoice scaffolding: numbers, dates, payment terms, pay-to instructions, and a tax disclaimer — not legal advice.
1. Still in the same chat, paste: "Using my Billing identities block and the line-item table, draft **invoice sections** in this order: - Title: INVOICE - Invoice # — use my pattern: [PREFIX]-[YYYYMM]-[###] (I will replace PREFIX) - Issue date — today’s date in my locale - Due date — Net 15 / Due on receipt / specific date — **only** if the thread or my policy supports it; otherwise ask me to pick ONE term - Bill From / Bill To — copy from Billing identities - Line items table (same columns as before) - **Tax** — if tax rate is **not** explicit in the thread, print: "Sales tax / VAT: as applicable — verify locally" with **no** calculated amount - **Grand total** — subtotal plus tax **only** if tax amount is explicit in the thread; otherwise grand total = subtotal with a note that tax may apply - **Payment methods** — list only what I actually accept (bank transfer, Stripe, PayPal, etc.) - **Late fee** — include **only** if my policy or the thread states it" 2. Replace PREFIX in the invoice # with something you use (e.g. your initials or business acronym). 3. Scan for **contradictory** terms (e.g. Net 15 **and** due on receipt). If both appear, edit so **one** due rule wins.
Export to a professional layout and send
Move the draft into Google Docs, export PDF, and email it — invoice lives outside the chat.
1. Open https://docs.google.com → **Blank** document. 2. Title the file: **Invoice [Client name] — [YYYY-MM]** (use your client billing name). 3. Paste Claude’s invoice sections. Select all → pick **one** readable font (e.g. Arial or Georgia) → use **Insert → Table** for the line items if pasting broke columns; keep borders simple. 4. **File → Download → PDF** (.pdf). 5. Email your client: attach the PDF. Subject: **Invoice #[number] — [client]**. 6. Body: one short paragraph — what the invoice is for, due date, and how to pay (match your Payment methods). 7. Optional: if you use Stripe or another processor for card payments, add **one** payment link sentence — do not skip the PDF attachment unless your workflow is explicitly link-only.
All done!
You now have: A professional invoice generated from your project chat or email thread
Explore more guidesWant this workflow built for your business?
Book a free audit