Client Reporting Delivery

This handles the full lifecycle of client reporting for advisory firms, from template design through delivery confirmation. You'd reach for it when building quarterly performance reports, managing tax reporting workflows, transitioning to client portals, or setting up QA processes. It covers the practical stuff: what sections go in a report, how to structure data from your PMS and custodian feeds, customizing by client segment (mass affluent through UHNW), and navigating the compliance review process. The source material is thorough on report architecture and content structure, which matters since most firms are either stuck with clunky PMS templates or drowning in custom requests they can't scale.

skills.sh installs: 685
GitHub stars: 224
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add joellewis/finance_skills --skill client-reporting-delivery --agent claude-code

Installs into .claude/skills of the current project.

Files

Client Reporting and Delivery

Core Concepts

Client Reporting Architecture

The reporting pipeline in an advisory firm flows from data sources through a generation engine to client delivery. The primary data sources are the portfolio management system (PMS), custodian data feeds, financial planning tools, and the billing system. Each source contributes distinct data elements: the PMS provides portfolio holdings, performance calculations, and asset allocation; the custodian provides official transaction records, settled positions, and tax lot data; the financial planning tool provides goal progress and projection data; and the billing system provides fee calculations and payment history.

Report types span the full advisory relationship:

SKILL.md on GitHub