Customs and Trade Compliance
affaan-m/ECC
Covers customs work: HS and HTS tariff classification, entry documents, Incoterms, FTA duty savings, denied-party screening and responses to audits and penalty notices.
Design, generate, and deliver client performance reports across all channels, covering quarterly reports, tax reporting, portal integration, and compliance review.
$ npx skills add JoelLewis/finance_skills --skill client-reporting-delivery -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JoelLewis/finance_skills client-reporting-delivery --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/advisory-practice/skills/client-reporting-delivery .claude/skills/client-reporting-delivery && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "client-reporting-delivery" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-reporting-delivery into .claude/skills/client-reporting-delivery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-reporting-delivery", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-reporting-deliveryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JoelLewis/finance_skills --skill client-reporting-delivery -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JoelLewis/finance_skills client-reporting-delivery --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/advisory-practice/skills/client-reporting-delivery .agents/skills/client-reporting-delivery && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "client-reporting-delivery" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-reporting-delivery into .agents/skills/client-reporting-delivery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-reporting-delivery", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JoelLewis/finance_skills --skill client-reporting-delivery -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JoelLewis/finance_skills client-reporting-delivery --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/advisory-practice/skills/client-reporting-delivery .cursor/skills/client-reporting-delivery && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "client-reporting-delivery" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-reporting-delivery into .cursor/skills/client-reporting-delivery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-reporting-delivery", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JoelLewis/finance_skills.git --path plugins/advisory-practice/skills/client-reporting-delivery--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JoelLewis/finance_skills --skill client-reporting-delivery -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JoelLewis/finance_skills client-reporting-delivery --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/advisory-practice/skills/client-reporting-delivery .gemini/skills/client-reporting-delivery && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "client-reporting-delivery" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-reporting-delivery into .gemini/skills/client-reporting-delivery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-reporting-delivery", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JoelLewis/finance_skills client-reporting-deliveryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JoelLewis/finance_skills --skill client-reporting-delivery -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/advisory-practice/skills/client-reporting-delivery .github/skills/client-reporting-delivery && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "client-reporting-delivery" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-reporting-delivery into .github/skills/client-reporting-delivery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-reporting-delivery", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JoelLewis/finance_skills --skill client-reporting-delivery -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JoelLewis/finance_skills client-reporting-delivery --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JoelLewis/finance_skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/advisory-practice/skills/client-reporting-delivery .opencode/skills/client-reporting-delivery && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "client-reporting-delivery" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/advisory-practice/skills/client-reporting-delivery into .opencode/skills/client-reporting-delivery/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "client-reporting-delivery", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
client-reporting-deliveryDesign, generate, and deliver client performance reports across all channels, covering quarterly reports, tax reporting, portal integration, and compliance review.
Client Reporting Delivery is an agent skill from JoelLewis/finance_skills. Design, generate, and deliver client performance reports across all channels, covering quarterly reports, tax reporting, portal integration, and compliance review. Use when the user asks about building or redesigning report templates, choosing what to include in quarterly or annual client reports, transitioning from print to digital delivery, integrating a client portal, presenting net-of-fee performance with benchmarks, managing report production timelines, or handling e-delivery consent. Also trigger when users…
Its SKILL.md is about 9.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/examples.md`).
It sits in Legal & Compliance, covering Regulatory compliance. The repository describes itself as: Claude Code skill plugins for financial services — 81 skills across 7 domain plugins covering investment management, compliance, advisory practice, trading, and operations. The licence is MIT.
9 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 5c498ea. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Client Reporting Delivery loads about 9.9k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 182 tokens; SKILL.md has 5,064 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from JoelLewis/finance_skills at commit 5c498ea, republished under its MIT licence (© JoelLewis). 5,064 words, ~9,868 tokens.
.claude/skills/client-reporting-delivery/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.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:
Reporting platforms fall into several categories. PMS-embedded reporting tools (Orion Portfolio Solutions, Black Diamond, Tamarac Reporting) generate reports directly from the portfolio management database, ensuring data consistency. Standalone reporting platforms (e.g., Addepar) aggregate data from multiple sources and offer advanced customization, often favored by firms serving UHNW clients and family offices. (Backstop Solutions, sometimes miscategorized here, is an institutional research-management/CRM platform rather than a client reporting tool.) Client portal integration layers the reporting function into a broader digital client experience.
Custodian statements and advisor-produced reports serve complementary but distinct purposes. Custodian statements are the official record of account activity and positions, produced by the custodian (Schwab, Fidelity, Pershing). Advisor-produced reports add value through consolidated household views, custom benchmarks, goal-based framing, blended performance across custodians, and advisor commentary. Clients receive both, and firms should help clients understand the relationship between the two, particularly when minor data differences arise from timing or methodology.
A well-designed quarterly performance report follows a logical structure that guides the client from high-level summary to supporting detail:
Cover page — Firm branding, client or household name, reporting period, key headline metrics (total portfolio value, period return, net change in value). The cover page sets the tone and provides the most critical data points at a glance.
Executive summary and market commentary — A brief narrative (typically one page) covering market conditions during the period, key events that affected portfolios, and a forward-looking perspective. This section can be firm-level (same for all clients) or personalized by the advisor.
Portfolio summary — Asset allocation (current vs target, shown as pie chart or bar chart and table), total holdings count, cash position, and net deposits/withdrawals during the period. Household-level view aggregating all accounts.
Performance summary — Period returns (MTD, QTD, YTD, 1-year, 3-year, 5-year, 10-year, since inception) with benchmark comparison. Displayed as both table and chart. Net-of-fee returns as the primary presentation with gross-of-fee available.
Account detail — Individual account summaries within the household, each showing account type, custodian, value, allocation, and performance. Important for clients with multiple accounts across different registration types.
Holdings detail — Complete listing of positions by account or by asset class, showing security name, ticker, shares/units, market value, percentage of portfolio, unrealized gain/loss, and yield.
Transaction summary — Purchases, sales, income received, contributions, withdrawals, and fee debits during the period. Level of detail varies by client preference.
Fee summary — Advisory fees charged during the period, showing calculation methodology (AUM, billing rate, proration if applicable). Increasingly important given regulatory emphasis on fee transparency.
Disclosures and disclaimers — Required legal language including past performance disclaimers, benchmark descriptions, fee impact disclosure, and firm registration information.
Content customization by client segment is essential. Mass affluent clients typically prefer simplified reports emphasizing total value, return, and allocation with minimal holdings detail. High-net-worth (HNW) clients generally want comprehensive reports including full holdings, transaction detail, and benchmark comparisons. Ultra-high-net-worth (UHNW) and family office clients often require institutional-grade reporting with performance attribution, alternative investment detail, multi-entity consolidation, and custom analytics. The challenge is balancing comprehensiveness with readability — a 40-page report that goes unread serves no one.
Performance is the most scrutinized section of any client report. Presenting returns accurately and clearly requires attention to methodology, time periods, benchmarks, and context.
Return methodologies: For TWR vs. MWR definitions and calculation, see the wealth-management performance-metrics and performance-reporting skills. In client reports: TWR is the standard for strategy evaluation; MWR answers "how did my money do?" and is increasingly presented alongside TWR. Presenting both can be powerful when accompanied by a brief explanation of the difference — when the two diverge significantly, it signals that cash flow timing had a material impact and opens a productive conversation.
Return periods:
Standard periods displayed in quarterly reports include MTD (month-to-date), QTD (quarter-to-date), YTD (year-to-date), trailing 1-year, trailing 3-year, trailing 5-year, trailing 10-year, and since-inception. Annualization conventions are critical: returns for periods exceeding one year should be annualized (geometric annualization), while returns for periods of one year or less should be presented as cumulative (non-annualized). Mixing conventions without clear labeling is a common source of confusion and potential compliance issues.
Benchmark selection and display:
Every portfolio should have a clearly defined benchmark. The primary benchmark should reflect the portfolio's strategic asset allocation and investment universe. For diversified portfolios, a blended benchmark (e.g., 60% MSCI ACWI / 40% Bloomberg US Aggregate) is more appropriate than a single index. Reports should include the benchmark description, component indices and weights, and a note that the benchmark is not investable and does not reflect fees. Some firms also display peer group comparisons or risk-adjusted metrics (Sharpe ratio, Sortino ratio) for sophisticated clients.
Net-of-fee vs gross-of-fee returns:
Net-of-fee returns are the preferred presentation for client reports because they represent the client's actual experience after paying advisory fees. Gross-of-fee returns may be shown alongside net for transparency or for GIPS-compliant presentations. The fee impact over long periods is substantial and should not be obscured.
GIPS compliance considerations:
Firms that claim compliance with the Global Investment Performance Standards must adhere to specific presentation requirements in composite reports, including required disclosures, composite construction rules, and prescribed return calculation methodologies. Individual client reports are not composites, but firms claiming GIPS compliance should ensure client-level reporting does not contradict or undermine their composite presentations.
Performance disclaimers:
Every report displaying performance data must include disclaimers stating that past performance is not indicative of future results, describing the benchmark and its limitations, disclosing whether returns are net or gross of fees, and noting any material factors affecting comparability across periods (e.g., strategy change, benchmark change).
Report customization operates at multiple levels, from firm-wide template design to individual client preferences.
Level of detail: Some clients want a two-page summary; others want 30 pages of detail. The reporting system should support configurable section inclusion, allowing advisors to toggle sections on or off per client. Common toggleable sections include holdings detail, transaction detail, individual account breakdowns, and performance attribution.
Grouping and organization: Reports can organize portfolio data in several ways depending on client preference and portfolio structure:
Household vs account-level reporting: Most clients prefer a consolidated household view as the primary presentation, with account-level detail as a secondary section. The household view enables total portfolio allocation, consolidated performance, and a single net worth perspective. Account-level detail remains important for tax planning, beneficiary considerations, and account-specific objectives.
Custom benchmarks: Clients with unique portfolio constraints (ESG exclusions, concentrated stock positions, alternative allocations) may require custom benchmarks that reflect their investable universe. The reporting system should support advisor-defined blended benchmarks with custom weights and component indices, updated as the target allocation evolves.
Personalized commentary: The highest-value customization is advisor-written commentary specific to the client's situation. This might address recent portfolio changes, progress toward financial plan goals, upcoming planning actions, or responses to client questions. Some firms provide a firm-level market commentary as a default with an editable field for advisor personalization. Advisors who consistently add personalized commentary report stronger client engagement and retention.
White-labeling: Multi-advisor firms, RIA aggregators, and sub-advisory relationships often require white-labeled reports carrying the presenting firm's branding rather than the platform or TAMP provider's branding. The reporting system should support configurable logos, firm names, disclosures, and contact information.
Language and terminology: Reports should use language appropriate to the client's financial sophistication. A retired schoolteacher needs different terminology than a former CFO. Avoid unnecessary jargon where plain language suffices, but do not oversimplify for sophisticated clients who expect precision.
Report delivery has evolved from exclusively print-and-mail to a multi-channel environment. Firms must manage several delivery methods simultaneously.
Client portal (primary digital channel):
The client portal is the hub of digital delivery. Reports are published to the portal where clients can view them online, download as PDF, and access historical reports in an archive. Portal-based delivery offers several advantages: immediate availability (no mail delay), persistent access (clients can revisit reports anytime), reduced cost (no printing or postage), environmental sustainability, and integration with other portal features (real-time portfolio view, document vault, secure messaging). The portal should provide notification (email or push) when new reports are available.
Email delivery:
Email delivery remains common, typically as an encrypted PDF attachment or a link to the client portal. Email is familiar and requires no portal login, making it accessible for less tech-savvy clients. However, email delivery raises security concerns (sensitive financial data in transit or in inboxes), so best practices include PDF encryption with a client-specific password, secure email platforms, or portal links rather than attachments. Firms should document email delivery preferences and security measures.
Print and mail:
Physical printed reports delivered via postal mail are declining but not extinct. Some clients, particularly older individuals or those in jurisdictions with specific requirements, prefer or require printed reports. Print delivery involves additional cost (printing, paper, postage), longer delivery time (days vs instant), and environmental impact. Firms transitioning to digital-first delivery should maintain a print capability for clients who opt in and for any regulatory requirements that mandate physical delivery.
In-person review:
Many advisors present reports during client meetings rather than simply delivering them. The meeting context allows the advisor to walk through results, provide context, answer questions in real time, and connect performance to financial plan progress. In-person presentation may use the same PDF report, a slide-deck derivative, or an interactive portal screen share. The report serves as both a leave-behind document and a meeting framework.
Multi-channel strategy:
The recommended approach is digital-first with print opt-in. Default delivery is portal publication with email notification. Clients who prefer print explicitly opt in and receive mailed copies in addition to (not instead of) digital access. This ensures every client has portal access to current and historical reports while accommodating print preferences.
E-delivery consent:
SEC rules on electronic delivery (primarily from SEC guidance releases and interpretive letters) require that firms provide notice that documents are available electronically, ensure the client has access to the electronic format, and obtain evidence of delivery (or evidence of notice with access). Firms should document client consent to electronic delivery, provide clear instructions for portal access, and maintain systems that confirm report availability and client access. Under FINRA rules, broker-dealers have additional requirements for implied consent and opt-out rights.
Delivery confirmation and tracking:
Firms should track report delivery status: portal published, email sent, email opened (if tracked), portal accessed, print mailed, print delivered (via tracking number if warranted). Delivery tracking supports compliance (evidence of delivery), operations (identifying delivery failures), and client service (confirming clients received their reports).
The quarterly reporting cycle is a firm's most operationally intensive recurring process, typically spanning T+5 to T+15 after quarter-end (5 to 15 business days after the quarter closes).
Workflow stages:
Data finalization (T+1 to T+5): Custodian data feeds settle, reconciliation between PMS and custodian records completes, corporate actions process, and pricing finalizes. Reports cannot be generated until data is clean. The most common delay is waiting for custodian reconciliation to complete, particularly for accounts holding alternative investments, private placements, or international securities with delayed settlement.
Report generation (T+5 to T+7): Batch report generation runs for all client accounts and households. The PMS or reporting platform compiles data into report templates, calculates performance for all required periods, generates charts and tables, and produces PDF output. Batch runs may take several hours for large firms (thousands of accounts). Exception reports flag accounts with data issues that prevent clean report generation.
Quality assurance (T+7 to T+9): QA is the critical gate between generation and delivery. The QA process includes automated validation (returns within expected ranges, AUM totals match PMS, fee calculations correct, no missing data fields) and manual spot-checking (visual inspection of formatting, chart rendering, correct client names and account numbers, cross-referencing with custodian statements). QA should cover a statistical sample at minimum; many firms review all reports for households above a materiality threshold.
Compliance review (T+9 to T+10): Compliance reviews a sample of reports to verify disclaimers are present and current, performance presentation is accurate and not misleading, benchmark descriptions are complete, and fee disclosures are appropriate. Any reports used for marketing purposes (e.g., shared with prospects) trigger additional review under the SEC Marketing Rule.
Advisor review and commentary (T+8 to T+11): Advisors review reports for their client relationships, add personalized commentary where applicable, and flag any issues (data they know to be incorrect, clients with special circumstances requiring modified reports). This stage often runs in parallel with compliance review.
Approval and release (T+11 to T+12): Final approval, either by a designated operations manager, the Chief Compliance Officer, or through an automated workflow, clears reports for delivery. Once approved, reports are locked against further editing.
Delivery (T+12 to T+15): Reports are published to the client portal, email notifications are sent, and print reports are dispatched. Delivery may be staggered (largest clients first, or by advisor team) to manage volume and catch any last-minute issues before the full batch goes out.
Handling exceptions:
Timeline management:
The reporting cycle compresses many dependencies into a tight window. Bottleneck identification is essential: late custodian data, slow reconciliation, advisor commentary delays, and compliance review capacity are the most common constraints. Firms should establish clear deadlines for each stage with escalation procedures when deadlines slip.
The client portal has become central to the reporting strategy, serving as both a delivery channel and an interactive extension of the static report.
Report access models:
The most effective portal strategy combines all three: periodic batch reports for the formal record, on-demand capability for ad-hoc needs, and interactive dashboards for day-to-day engagement.
Portal features that complement reports:
Driving portal adoption:
Many firms struggle with portal adoption rates, which typically range from 40% to 70% of clients actively using the portal. Strategies to improve adoption include making the portal the default delivery channel, demonstrating the portal during client meetings, simplifying the registration process (single sign-on, mobile-friendly), providing portal training materials, and emphasizing features beyond report access (document vault, secure messaging, goal tracking). Younger clients and those with larger portfolios tend to have higher adoption rates.
Portal vendors:
Leading platforms include Orion Connect (integrated with Orion PMS, strong reporting and planning integration), Black Diamond Client Experience (known for visual report quality and client experience), Tamarac Reporting (integrated with Envestnet ecosystem), Addepar Client Portal (favored by UHNW and family office firms for advanced analytics), and custom-built portals (used by larger firms wanting full control over the client experience). Selection criteria include integration with the firm's PMS, report customization capability, mobile experience, security features, and total cost of ownership.
Tax reporting is a distinct reporting function with its own timeline, data requirements, and audience (the client's CPA or tax preparer in addition to the client).
Tax-related reports:
Year-end deliverables beyond tax reports:
Timing and coordination:
Tax reporting follows a distinct timeline from performance reporting. Preliminary tax reports are typically available in January, based on the best available data. However, custodians issue corrected 1099s through February and sometimes into March (particularly for accounts holding partnerships, REITs, or international securities). Final tax reports should be issued only after the custodian's 1099 correction period closes. Firms should communicate the timeline clearly to clients and their CPAs to avoid filing with preliminary data that later changes.
Coordination with client CPAs is a value-added service. Proactive firms send tax reports directly to the client's CPA (with client authorization), provide a cover letter explaining the reports and any notable items, and make themselves available to answer CPA questions during tax season. This reduces friction for the client and positions the advisor as a hub of the client's financial team.
Client reports are communications to clients and therefore subject to regulatory scrutiny. Compliance requirements vary based on the firm's registration type (RIA, broker-dealer, dual registrant) and how the reports are used.
Regulatory framework:
Required disclaimers:
Supervisory review:
Firms must establish supervisory procedures for client report review. The scope of supervisory review typically includes verifying performance accuracy (sampling), confirming disclaimers are present and current, reviewing advisor-written commentary for compliance (no guarantees, no promissory language, fair and balanced), and checking that reports are consistent with the client's actual account and investment strategy. Compliance should document the review process, the reviewer, the date, and any issues identified and resolved.
Record retention:
Under the SEC's books-and-records rules (Rule 204-2 for RIAs, Rule 17a-4 for broker-dealers), firms must retain copies of all communications delivered to clients, including client reports. Retention periods are typically five years (RIAs) or six years (broker-dealers) from the date of delivery. The retained copy must be the exact version delivered to the client. Digital archiving of PDFs published to portals satisfies this requirement when properly indexed and backed up.
GIPS requirements:
Firms claiming GIPS compliance must present composite-level performance in GIPS-compliant reports to prospective clients. Individual client reports are not composites, but the firm should ensure that client-level performance data does not contradict composite presentations and that GIPS-required disclosures appear on any report used to market the firm's investment capabilities.
Quality assurance is the safeguard between report generation and client delivery. Errors in client reports damage credibility, create compliance risk, and generate costly re-issuance work.
Automated validation checks:
Visual and manual inspection:
Common errors and root causes:
Error tracking and resolution:
Firms should maintain an error log tracking each identified issue: date discovered, report affected, error type, root cause, resolution, and corrective action to prevent recurrence. Error rate metrics (errors per 1,000 reports generated) should be tracked over time and reported to management. A rising error rate signals a systemic issue (data quality, template instability, staffing) requiring intervention.
Client-reported errors:
When a client identifies an error, the resolution workflow includes acknowledgment (prompt response to the client), investigation (verify the error and identify the cause), correction (generate a corrected report), re-issuance (deliver the corrected report with a brief explanation), and root cause analysis (determine whether the error is isolated or systemic). The tone of client communication should be transparent and professional, treating the error seriously while reassuring the client that their actual account and investments are unaffected if the error is limited to the report.
See references/examples.md for three end-to-end worked examples — redesigning a quarterly reporting package with tiered templates, transitioning from print to digital-first delivery, and remediating performance calculation errors in delivered reports. Load it when the user needs a full scenario walkthrough.
Generating reports before data is final. Rushing to meet a delivery deadline with preliminary data — particularly for alternative investments, international securities, or accounts with pending corporate actions — leads to inaccurate reports and costly re-issuance. Establish a data readiness gate that must pass before report generation begins.
One-size-fits-all report design. Delivering the same 25-page report to every client regardless of portfolio size, complexity, or sophistication wastes the client's time and the firm's resources. Tier-based customization ensures each client receives an appropriately scoped report.
Neglecting the performance disclaimer. Omitting or using outdated performance disclaimers creates compliance risk. Disclaimers must be reviewed and updated at least annually by compliance, covering past performance language, benchmark descriptions, fee impact, and calculation methodology.
Ignoring delivery preferences. Forcing all clients to digital delivery or continuing to print for clients who prefer digital wastes resources and frustrates clients. Maintain an accurate delivery preference database and honor stated preferences.
Presenting annualized returns for periods under one year. Annualizing a three-month return inflates the apparent performance and is misleading. Only annualize returns for periods exceeding one year, and clearly label all return periods.
Failing to reconcile advisor reports to custodian statements. When clients notice discrepancies between the advisor's report and the custodian statement, they lose confidence in the advisor's data. Proactively explain common differences (timing, methodology, household consolidation) and ensure the report includes a note about the relationship between the two.
Treating the report as a standalone document rather than a conversation tool. Reports are most valuable when reviewed with the client, not simply mailed. Advisors who use reports as a framework for client meetings extract significantly more relationship value from the reporting investment.
Underinvesting in quality assurance. Skipping or minimizing QA to speed delivery is a false economy. A single cross-client error (delivering Client A's data to Client B) creates a privacy breach, compliance violation, and severe reputational damage that far exceeds the cost of thorough QA.
Not tracking portal adoption metrics. Launching a client portal without measuring adoption leads to low usage and wasted technology investment. Set specific adoption targets and actively manage the onboarding funnel.
Delaying tax report delivery without client communication. Clients and their CPAs expect tax reports by a certain date. When corrected 1099s delay final tax reporting, proactive communication about the timeline prevents frustration and demonstrates professionalism.
© JoelLewis, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file (references) in plugins/advisory-practice/skills/client-reporting-delivery of JoelLewis/finance_skills.
Open the folder on GitHubat commit 5c498ea
Client Reporting Delivery next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Client Reporting Delivery this skillJoelLewis/finance_skills | 205 | — | ~9.9k | Automated safety check: Pass | MIT | |
| Customs and Trade Complianceaffaan-m/ECC | 276k | 5 repos | ~7.2k | Automated safety check: Pass | Apache-2.0 | |
| Quality Manager Qmralirezarezvani/claude-skills | 28k | — | ~4.7k | Automated safety check: Pass | MIT | |
| Gc Reviewalirezarezvani/claude-skills | 28k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Vendor Due Diligenceborghei/Claude-Skills | 886 | — | ~3.2k | Automated safety check: Pass | MIT | |
| Sec Analyst MasterOctagonAI/skills | 127 | — | ~2.2k | Automated safety check: Pass | MIT |
affaan-m/ECC
Covers customs work: HS and HTS tariff classification, entry documents, Incoterms, FTA duty savings, denied-party screening and responses to audits and penalty notices.
alirezarezvani/claude-skills
Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies.
alirezarezvani/claude-skills
/cs:gc-review <plan — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface.
borghei/Claude-Skills
Assess IT vendors and third-party partners with multi-factor risk scoring and regulatory compliance checklists.
OctagonAI/skills
Comprehensive SEC filing analyst skill that orchestrates all Octagon SEC analysis skills.
maziyarpanahi/openmed
Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.
JoelLewis/finance_skills
Determine how to distribute capital across asset classes using strategic and tactical allocation frameworks.
JoelLewis/finance_skills
Determine how much capital to allocate to individual positions within a portfolio.
JoelLewis/finance_skills
Analyze commodity markets including futures curve dynamics, roll yield, and supply/demand fundamentals.
JoelLewis/finance_skills
Analyze currency markets, exchange rate mechanics, and FX risk management for international portfolios.
JoelLewis/finance_skills
Provide frameworks for managing and paying off personal debt effectively.
JoelLewis/finance_skills
Build diversified portfolios using correlation analysis, efficient frontier construction, and factor-based diversification.
Categories
Design, generate, and deliver client performance reports across all channels, covering quarterly reports, tax reporting, portal integration, and compliance review. Client Reporting Delivery is an agent skill from JoelLewis/finance_skills. Design, generate, and deliver client performance reports across all channels, covering quarterly reports, tax reporting, portal integration, and compliance review.
Client Reporting Delivery fits situations like: the user asks about building; redesigning report templates; choosing what to include in quarterly; annual client reports.
Run `npx skills add JoelLewis/finance_skills --skill client-reporting-delivery -a claude-code`. Or copy the skill folder (plugins/advisory-practice/skills/client-reporting-delivery in JoelLewis/finance_skills) into .claude/skills/client-reporting-delivery in your project. Claude Code loads it when a task matches its description.
Run `npx skills add JoelLewis/finance_skills --skill client-reporting-delivery -a codex`. Or copy the skill folder (plugins/advisory-practice/skills/client-reporting-delivery in JoelLewis/finance_skills) into .agents/skills/client-reporting-delivery in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JoelLewis/finance_skills --skill client-reporting-delivery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/client-reporting-delivery, .gemini/skills/client-reporting-delivery, .github/skills/client-reporting-delivery and .opencode/skills/client-reporting-delivery in your project.
SKILL.md names no scripts, command-line tools or credentials: Client Reporting Delivery is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Client Reporting Delivery is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 9.9k tokens (SKILL.md is roughly 39k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.3k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Client Reporting Delivery: Customs and Trade Compliance (affaan-m/ECC, 276k stars), Quality Manager Qmr (alirezarezvani/claude-skills, 28k stars), Gc Review (alirezarezvani/claude-skills, 28k stars) and Vendor Due Diligence (borghei/Claude-Skills, 886 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
JoelLewis (a GitHub user) maintains it in JoelLewis/finance_skills, which has 205 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on July 18, 2026.
Source: JoelLewis/finance_skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.