DAY 6
FP WEALTH SOLUTIONS SA | TRAINING
SOLVING WORK
TASKS WITH
CLAUDE CODE
Part 2 — a real end-to-end case: an accounting agent
Claude CodeSkillsGmail / TelegramPDF parsingGoogle DriveAutomation
MARCH 27, 2026 | ZHEMAL KHAMIDUN
01

Goal of the Day

From a case — to a working agent

What we do today

We take a real FPWS team task and build a complete working agent for it — no theory, straight to practice. The case: automating the monthly accounting routine.

Idea: documents arrive monthly (statements, invoices, calculations) — the agent collects, reconciles, reports and archives them itself.
02

Case: Accounting Agent

The task

What the agent must do

  • Accept documents via Email/Telegram throughout the month
  • On the 10th of the next month — analyze bank statements
  • Reconcile them against available primary documents
  • Produce a report: what's missing and from whom to request it
  • Collect everything and archive to Google Drive
Complexity: account and card statements in different PDF formats; working language English; heterogeneous documents. The agent parses all of it itself.
03

Task 1

Reconcile statements with source docs

Input

  • PDF statements for accounts and cards (various formats)
  • Accountant's base of primary documents
  • Employee contacts for requests

Output

  • Recognized amounts and transactions
  • Report: which documents exist, which don't
  • Recommendations: what to request and from whom
  • What's already there and need not be requested
04

Task 2

Invoice check and preparation

Invoice processing flow

  • Marina sends invoices (Word) by email
  • Check: date validity after the quarter, no duplicate amounts
  • Reconcile amounts with the table; on errors — query Marina and get feedback
  • Apply facsimile and convert to PDF
  • Ready PDFs — to the director for signature and sending to banks
05

Task 3

Reconcile incoming amounts

What we reconcile

Sasha sends a large end-of-quarter calculation. We reconcile it against actual incoming payments from the statements.

Result

  • Final table: amounts and dates of actual receipts
  • Discrepancies highlighted
  • Ready for management reporting
06

Solution Architecture

How we assemble the agent

Build principle

  • Project = a set of skills + a step-by-step plan
  • 14 steps: from configuration to a finished agent
  • Each step — its own prompt from its SKILL.md
  • After each step — tests and verification

Components

  • config.py, db.py — settings and database
  • gmail_client.py — receiving email
  • classifier.py — document parsing
  • agent.py, run.py — logic and run
07

Deploy Prompt

One prompt launches the build

Prompt (Day 6, verbatim)Unpack accounting-automation.zip into the current directory. Read all files: README.md, DEPLOY_PROMPT.md and every SKILL.md in skills/. This is an email-based accounting agent. Follow DEPLOY_PROMPT.md — a step-by-step plan (14 steps): first architecture analysis, then prerequisites, then implementation step by step. Start with step 1 (BOOTSTRAP.md) — create config.py, db.py, gmail_client.py, classifier.py, agent.py, run.py. After each step write tests and verify. Don't skip steps.
Takeaway: complex automation is described in plain language. The agent writes the code, tests it and assembles a working system step by step.
DAY 6 — SUMMARY
FROM A TASK —
TO A WORKING AGENT
A real case built end-to-end. The routine runs on autopilot.
3
Tasks:
statements · invoices · receipts
14
Build
steps
1
Launch
prompt
10x
Time
saved
HAMIDUN CONSULTING | CLAUDE CODE — PART 2
Zhemal Khamidun | @JHamidun | [email protected]
1 / 10