Creator · JoelLewis
Last updated · Sep 4, 2026
Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building a daily position, cash, or transaction reconciliation process, investigating discrepancies between internal records and custodian records, diagnosing recurr
Creator · JoelLewis
Last updated · Sep 4, 2026
Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building a daily position, cash, or transaction reconciliation process, investigating discrepancies between internal records and custodian records, diagnosing recurr
Creator · JoelLewis
Last updated · Sep 4, 2026
Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building a daily position, cash, or transaction reconciliation process, investigating discrepancies between internal records and custodian records, diagnosing recurr
Creator · JoelLewis
Last updated · Sep 4, 2026
Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building a daily position, cash, or transaction reconciliation process, investigating discrepancies between internal records and custodian records, diagnosing recurr
Sandbox only
Install targets
Codex install prompt
Install the "reconciliation" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/client-operations/skills/reconciliation. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building a daily position, cash, or transaction reconciliation process, investigating discrepancies between internal records and custodian records, diagnosing recurring break patterns from corporate actions or pricing differences, setting tolerance thresholds for position, cash, or market value matching, implementing three-way reconciliation, designing break investigation workflows with aging and escalation, normalizing multi-custodian feeds from Schwab, Fidelity, or Pershing, reconciling cost basis or accrued income, or preparing for examinations on books and records accuracy. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"joellewis-reconciliation","task":"Install reconciliation","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Design assets, images, video, audio, multimodal media, presentation, and creative production skills.
Scenario
Design and creative
I need my agent to produce design assets, UI directions, presentations, or creative media workflows.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add JoelLewis/finance_skills --skill reconciliation
Maintenance
active
2mo since push
Risk
Risky
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
178
63/100 Quality · 80/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision · Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
RiskyA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
178 GitHub stars
Repo activity
178 stars, 34 forks
Maintenance
2mo since push
License
MIT
Install
npx skills add JoelLewis/finance_skills --skill reconciliation
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add JoelLewis/finance_skills --skill reconciliationDo not use when
Alternative
174.2K Stars
npx skills add anthropics/skills --skill frontend-design
Alternative
84.4K Stars
npx skills add Leonxlnx/taste-skill --skill design-taste-frontend
Alternative
174.2K Stars
npx skills add anthropics/skills --skill canvas-design
Alternative
174.2K Stars
npx skills add anthropics/skills --skill brand-guidelines
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20reconciliation%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20reconciliation%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/joellewis-reconciliation/install
Agent should check
Copy prompt
Task: Use reconciliation in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20reconciliation%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/joellewis-reconciliation/install
Install command: npx skills add JoelLewis/finance_skills --skill reconciliation
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/joellewis-reconciliation/install
LLM text format
/api/skills/joellewis-reconciliation/install?format=text
Find alternatives
/api/skills/search?q=reconciliation&limit=3
Agent prompt
Use reconciliation for this task. Review https://www.openagentskill.com/api/skills/joellewis-reconciliation/install, then install with: npx skills add JoelLewis/finance_skills --skill reconciliationRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/joellewis-reconciliation
LLM text
/api/registry/manifest/joellewis-reconciliation?format=text
Install alias
/api/registry/install/joellewis-reconciliation
Recommend
/api/registry/recommend?task=Use%20reconciliation%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Research agents
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO178 GitHub stars
Stars/forks activity
CHECK178 stars, 34 forks; issue activity unavailable in current metadata
Recent maintenance
PASS2mo since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Analyze markets
I need my agent to analyze markets, financial data, filings, portfolios, and quant strategies.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Alternative shortlist
Similar skills that may fit this task.
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
Apply Anthropic official brand colors, typography, and visual standards to appropriate Anthropic-related artifacts.
--- name: reconciliation description: "Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building a daily position, cash, or transaction reconciliation process, investigating discrepancies between internal records and custodian records, diagnosing recurring break patterns from corporate actions or pricing differences, setting tolerance thresholds for position, cash, or market value matching, implementing three-way reconciliation, designing break investigation workflows with aging and escalation, normalizing multi-custodian feeds from Schwab, Fidelity, or Pershing, reconciling cost basis or accrued income, or preparing for examinations on books and records accuracy." ---
# Reconciliation
## Core Concepts
### 1. Reconciliation Types and Hierarchy
Reconciliation is the systematic comparison of records across two or more systems to identify and resolve discrepancies. In securities operations, reconciliation ensures that the firm's internal records (the investment book of record, or IBOR) match the custodian's official records (the official book of record, or OBOR) and, where applicable, the clearing firm's records. The reconciliation hierarchy proceeds from the most fundamental data element (positions) through increasingly derived data elements.
**Position Reconciliation.** The foundational reconciliation. Compares the number of shares or units held for each security in each account between the firm's portfolio management system (PMS) and the custodian. Position reconciliation is typically zero-tolerance: any share count difference, no matter how small, constitutes a break. Fractional share differences (common with dividend reinvestment plans) must also be identified and resolved. Position reconciliation is performed daily, using end-of-day files from the custodian compared against the PMS position ledger.
**Cash Reconciliation.** Compares cash balances between the PMS and the custodian, accounting for settled cash, pending settlements, accrued income, and pending fee debits. Cash reconciliation is more nuanced than position reconciliation because timing differences are inherent — a trade executed on day T settles on T+1, and the PMS and custodian may record the cash impact on different dates. Cash tolerance thresholds are common, typically a small dollar amount (e.g., $0.50 to $5.00) to accommodate rounding differences across systems. Balances outside the tolerance require investigation.
**Transaction Reconciliation.** Compares individual transactions (trades, dividends, interest payments, transfers, fees) recorded in the PMS against the custodian's transaction ledger. Transaction reconciliation operates at the trade level, matching on security, quantity, price, trade date, and settlement date. Unmatched transactions on either side constitute breaks. Transaction reconciliation is typically performed on a T+1 basis — comparing yesterday's activity after the custodian's end-of-day file is received.
**Market Value Reconciliation.** Compares the total market value of each position and each account between systems. Market value breaks often result from pricing differences — the PMS and custodian may source prices from different vendors or apply different pricing hierarchies for thinly traded or illiquid securities. Market value tolerance is typically expressed in basis points (e.g., 5-10 bps of account value) rather than absolute dollars, because a $100 difference on a $50,000 account is more significant than a $100 difference on a $5,000,000 account.
**Accrued Income Reconciliation.** Compares accrued interest on fixed-income holdings and declared-but-unpaid dividends. Accrued income differences frequently arise from day-count convention differences (actual/actual vs. 30/360), ex-date vs. record-date timing, or different treatment of defaulted bonds. This reconciliation is particularly important for fixed-income-heavy portfolios where accrued income is a material component of total value.
**Cost Basis Reconciliation.** Compares the tax lot-level cost basis for each position between the PMS and the custodian. Cost basis discrepancies are among the most difficult to resolve because they may originate from historical corporate actions (splits, mergers, spin-offs, return of capital adjustments) that were processed differently in each system. Since the custodian reports cost basis to the IRS on Form 1099-B, cost basis discrepancies can result in incorrect tax reporting if not resolved. Cost basis reconciliation is typically performed less frequently than position reconciliation — monthly or quarterly — but with zero tolerance for discrepancies.
### 2. Three-Way Reconciliation
For advisory firms that use a portfolio management system separate from both the custodian and any clearing firm, three-way reconciliation is the standard of practice. The three records being compared are:
**Advisor System (PMS / Portfolio Accounting).** The firm's investment book of record (IBOR), maintained in the portfolio management system (Orion, Black Diamond, Tamarac, Addepar, or similar). This is the record the firm uses for performance reporting, billing, rebalancing, and client-facing communications. The advisor system reflects the firm's understanding of what each client owns.
**Custodian Records.** The official book of record (OBOR), maintained by the custodian (Schwab, Fidelity, Pershing, or similar). This is the legally authoritative record of client assets. The custodian is responsible for safekeeping assets, settling transactions, and reporting to the IRS. When the advisor system and custodian disagree, the custodian record is presumed correct unless the firm can demonstrate otherwise.
**Clearing Firm Records.** For firms that clear through a separate entity (introducing broker-dealers that clear through a correspondent clearing firm), the clearing firm maintains its own record of positions and transactions. The clearing firm processes settlements, maintains margin calculations, and generates customer statements. In a fully disclosed arrangement, the clearing firm's records should match the custodian's, but discrepancies can arise from timing, corporate action processing, or data feed errors.
**Authoritative Source by Data Element.** Different systems serve as the authoritative source for different data elements:
| Data Element | Authoritative Source | Reason | |---|---|---| | Share/unit count | Custodian | Custodian holds the securities in legal custody | | Settled cash balance | Custodian | Custodian controls the cash account | | Trade execution details | Executing broker / custodian | Trade occurred on their platform | | Cost basis (for tax reporting) | Custodian | Custodian reports 1099-B to IRS | | Performance returns | Advisor system (PMS) | PMS maintains the calculation methodology | | Model assignment and drift | Advisor system (PMS) | PMS manages the investment process | | Fee schedule and billing | Advisor system (PMS) | PMS calculates fees per advisory agreement | | Corporate action elections | Custodian | Custodian processes the action |
**Reconciliation Frequency.** The standard frequencies are: - Position reconciliation: daily (end of each business day) - Cash reconciliation: daily - Transaction reconciliation: T+1 (one business day after the trade or event) - Market value reconciliation: daily - Accrued income reconciliation: daily or weekly, depending on portfolio composition - Cost basis reconciliation: monthly or quarterly
### 3. Break Identification
A break is any discrepancy identified during reconciliation between two or more records. Break identification is the process of detecting, classifying, and prioritizing breaks for investigation and resolution.
**Tolerance Thresholds.** Not all discrepancies warrant investigation. Tolerance thresholds define the minimum discrepancy that constitutes a reportable break:
| Reconciliation Type | Typical Tolerance | Rationale | |---|---|---| | Position (shares/units) | Zero (exact match required) | Any share difference indicates a missing or erroneous transaction | | Cash balance | $0.50 - $5.00 | Small rounding differences across systems are expected | | Market value | 5-10 bps of account value | Pricing source differences create small value discrepancies | | Accrued income | $0.01 - $1.00 | Day-count and rounding conventions vary across systems | | Cost basis | Zero (exact match required) | Any basis difference affects tax reporting accuracy | | Transaction matching | Exact match on key fields | Unmatched transactions require investigation |
**Break Categorization.** Breaks are classified by root cause to enable pattern analysis and systemic remediation:
- **Timing differences.** The most common category. Arise when the PMS and custodian record the same event on different dates. Examples: a trade executed late in the day may appear in the PMS on trade date but in the custodian file the following day; a dividend may post in the custodian on the pay date but in the PMS on the record date. Timing breaks typically self-resolve within one to two business days. - **Pricing differences.** Occur when the PMS and custodian use different pricing sources or apply different pricing hierarchies. Most common for fixed-income securities, international equities (with exchange rate differences), and illiquid or thinly traded securities. - **Corporate action differences.** Arise when a corporate action (stock split, merger, spin-off, dividend reinvestment) is processed in one system but not the other, or processed with different terms (different exchange ratio, different effective date). Corporate actions are the single largest cause of position breaks that do not self-resolve. - **Missing transactions.** A transaction appears in one system but not the other. Common causes: a trade placed directly at the custodian without going through the PMS, a manual journal entry in one system, or a data feed failure that dropped a transaction. - **Duplicate transactions.** The same transaction is recorded twice in one system. Can result from data feed reprocessing, manual entry combined with automated feed, or system errors during corporate action processing. - **Data quality issues.** Security identifiers do not match across systems (CUSIP changes, ticker symbol changes), account numbers are mapped incorrectly, or data feed parsing errors corrupt field values.
**Break Severity Levels.** Breaks are prioritized based on their operational impact:
- **Critical (must resolve same day).** Position breaks affecting client-facing reporting or imminent billing, cash breaks exceeding a material threshold (e.g., $10,000), and any break that would affect a trade if left unresolved. - **High (must resolve within two business days).** Position breaks on any actively traded security, market value breaks exceeding the tolerance, and unmatched transactions from the prior day. - **Medium (must resolve within five business days).** Accrued income differences, cost basis discrepancies identified in periodic reconciliation, and pricing breaks on less liquid securities. - **Low (resolve within the current monthly cycle).** Minor rounding differences within tolerance, known timing differences expected to self-resolve, and informational discrepancies that do not affect reporting or billing.
### 4. Break Resolution Workflows
Once a break is identified and categorized, it enters a structured resolution workflow. Effective break resolution combines investigative rigor with operational efficiency.
**Investigation Procedures.** The standard investigation sequence for a position break is:
1. Verify the break is not a known timing difference by checking pending transactions and unsettled activity in both systems. 2. Review the transaction history for the affected security in both the PMS and custodian to identify the divergence point — the first date on which the records disagree. 3. Check for unproc
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for reconciliation, ready for a manual X post.
A practical pick for market research: reconciliation: Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building... 178 stars https://www.openagentskill.com/skills/joellewis-reconciliation?ref=x
Listing + install path for reconciliation: https://www.openagentskill.com/skills/joellewis-reconciliation?ref=x Install: npx skills add JoelLewis/finance_skills --skill reconciliation
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to JoelLewis but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/joellewis-reconciliation?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/joellewis-reconciliation?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/joellewis-reconciliation/audit)
[](https://www.openagentskill.com/skills/joellewis-reconciliation?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)JoelLewis
@joellewis
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Frontend Design
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
174.2K StarsTaste Skill: Anti-Slop Frontend
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
84.4K StarsCanvas Design
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
174.2K StarsAnthropic Brand Guidelines
Apply Anthropic official brand colors, typography, and visual standards to appropriate Anthropic-related artifacts.
174.2K StarsSandbox only
Install targets
Codex install prompt
Install the "reconciliation" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/client-operations/skills/reconciliation. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building a daily position, cash, or transaction reconciliation process, investigating discrepancies between internal records and custodian records, diagnosing recurring break patterns from corporate actions or pricing differences, setting tolerance thresholds for position, cash, or market value matching, implementing three-way reconciliation, designing break investigation workflows with aging and escalation, normalizing multi-custodian feeds from Schwab, Fidelity, or Pershing, reconciling cost basis or accrued income, or preparing for examinations on books and records accuracy. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"joellewis-reconciliation","task":"Install reconciliation","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Design assets, images, video, audio, multimodal media, presentation, and creative production skills.
Scenario
Design and creative
I need my agent to produce design assets, UI directions, presentations, or creative media workflows.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add JoelLewis/finance_skills --skill reconciliation
Maintenance
active
2mo since push
Risk
Risky
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
178
63/100 Quality · 80/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision · Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
RiskyA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
178 GitHub stars
Repo activity
178 stars, 34 forks
Maintenance
2mo since push
License
MIT
Install
npx skills add JoelLewis/finance_skills --skill reconciliation
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add JoelLewis/finance_skills --skill reconciliationDo not use when
Alternative
174.2K Stars
npx skills add anthropics/skills --skill frontend-design
Alternative
84.4K Stars
npx skills add Leonxlnx/taste-skill --skill design-taste-frontend
Alternative
174.2K Stars
npx skills add anthropics/skills --skill canvas-design
Alternative
174.2K Stars
npx skills add anthropics/skills --skill brand-guidelines
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20reconciliation%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20reconciliation%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/joellewis-reconciliation/install
Agent should check
Copy prompt
Task: Use reconciliation in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20reconciliation%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/joellewis-reconciliation/install
Install command: npx skills add JoelLewis/finance_skills --skill reconciliation
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/joellewis-reconciliation/install
LLM text format
/api/skills/joellewis-reconciliation/install?format=text
Find alternatives
/api/skills/search?q=reconciliation&limit=3
Agent prompt
Use reconciliation for this task. Review https://www.openagentskill.com/api/skills/joellewis-reconciliation/install, then install with: npx skills add JoelLewis/finance_skills --skill reconciliationRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/joellewis-reconciliation
LLM text
/api/registry/manifest/joellewis-reconciliation?format=text
Install alias
/api/registry/install/joellewis-reconciliation
Recommend
/api/registry/recommend?task=Use%20reconciliation%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Research agents
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO178 GitHub stars
Stars/forks activity
CHECK178 stars, 34 forks; issue activity unavailable in current metadata
Recent maintenance
PASS2mo since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Analyze markets
I need my agent to analyze markets, financial data, filings, portfolios, and quant strategies.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Alternative shortlist
Similar skills that may fit this task.
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
Apply Anthropic official brand colors, typography, and visual standards to appropriate Anthropic-related artifacts.
--- name: reconciliation description: "Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building a daily position, cash, or transaction reconciliation process, investigating discrepancies between internal records and custodian records, diagnosing recurring break patterns from corporate actions or pricing differences, setting tolerance thresholds for position, cash, or market value matching, implementing three-way reconciliation, designing break investigation workflows with aging and escalation, normalizing multi-custodian feeds from Schwab, Fidelity, or Pershing, reconciling cost basis or accrued income, or preparing for examinations on books and records accuracy." ---
# Reconciliation
## Core Concepts
### 1. Reconciliation Types and Hierarchy
Reconciliation is the systematic comparison of records across two or more systems to identify and resolve discrepancies. In securities operations, reconciliation ensures that the firm's internal records (the investment book of record, or IBOR) match the custodian's official records (the official book of record, or OBOR) and, where applicable, the clearing firm's records. The reconciliation hierarchy proceeds from the most fundamental data element (positions) through increasingly derived data elements.
**Position Reconciliation.** The foundational reconciliation. Compares the number of shares or units held for each security in each account between the firm's portfolio management system (PMS) and the custodian. Position reconciliation is typically zero-tolerance: any share count difference, no matter how small, constitutes a break. Fractional share differences (common with dividend reinvestment plans) must also be identified and resolved. Position reconciliation is performed daily, using end-of-day files from the custodian compared against the PMS position ledger.
**Cash Reconciliation.** Compares cash balances between the PMS and the custodian, accounting for settled cash, pending settlements, accrued income, and pending fee debits. Cash reconciliation is more nuanced than position reconciliation because timing differences are inherent — a trade executed on day T settles on T+1, and the PMS and custodian may record the cash impact on different dates. Cash tolerance thresholds are common, typically a small dollar amount (e.g., $0.50 to $5.00) to accommodate rounding differences across systems. Balances outside the tolerance require investigation.
**Transaction Reconciliation.** Compares individual transactions (trades, dividends, interest payments, transfers, fees) recorded in the PMS against the custodian's transaction ledger. Transaction reconciliation operates at the trade level, matching on security, quantity, price, trade date, and settlement date. Unmatched transactions on either side constitute breaks. Transaction reconciliation is typically performed on a T+1 basis — comparing yesterday's activity after the custodian's end-of-day file is received.
**Market Value Reconciliation.** Compares the total market value of each position and each account between systems. Market value breaks often result from pricing differences — the PMS and custodian may source prices from different vendors or apply different pricing hierarchies for thinly traded or illiquid securities. Market value tolerance is typically expressed in basis points (e.g., 5-10 bps of account value) rather than absolute dollars, because a $100 difference on a $50,000 account is more significant than a $100 difference on a $5,000,000 account.
**Accrued Income Reconciliation.** Compares accrued interest on fixed-income holdings and declared-but-unpaid dividends. Accrued income differences frequently arise from day-count convention differences (actual/actual vs. 30/360), ex-date vs. record-date timing, or different treatment of defaulted bonds. This reconciliation is particularly important for fixed-income-heavy portfolios where accrued income is a material component of total value.
**Cost Basis Reconciliation.** Compares the tax lot-level cost basis for each position between the PMS and the custodian. Cost basis discrepancies are among the most difficult to resolve because they may originate from historical corporate actions (splits, mergers, spin-offs, return of capital adjustments) that were processed differently in each system. Since the custodian reports cost basis to the IRS on Form 1099-B, cost basis discrepancies can result in incorrect tax reporting if not resolved. Cost basis reconciliation is typically performed less frequently than position reconciliation — monthly or quarterly — but with zero tolerance for discrepancies.
### 2. Three-Way Reconciliation
For advisory firms that use a portfolio management system separate from both the custodian and any clearing firm, three-way reconciliation is the standard of practice. The three records being compared are:
**Advisor System (PMS / Portfolio Accounting).** The firm's investment book of record (IBOR), maintained in the portfolio management system (Orion, Black Diamond, Tamarac, Addepar, or similar). This is the record the firm uses for performance reporting, billing, rebalancing, and client-facing communications. The advisor system reflects the firm's understanding of what each client owns.
**Custodian Records.** The official book of record (OBOR), maintained by the custodian (Schwab, Fidelity, Pershing, or similar). This is the legally authoritative record of client assets. The custodian is responsible for safekeeping assets, settling transactions, and reporting to the IRS. When the advisor system and custodian disagree, the custodian record is presumed correct unless the firm can demonstrate otherwise.
**Clearing Firm Records.** For firms that clear through a separate entity (introducing broker-dealers that clear through a correspondent clearing firm), the clearing firm maintains its own record of positions and transactions. The clearing firm processes settlements, maintains margin calculations, and generates customer statements. In a fully disclosed arrangement, the clearing firm's records should match the custodian's, but discrepancies can arise from timing, corporate action processing, or data feed errors.
**Authoritative Source by Data Element.** Different systems serve as the authoritative source for different data elements:
| Data Element | Authoritative Source | Reason | |---|---|---| | Share/unit count | Custodian | Custodian holds the securities in legal custody | | Settled cash balance | Custodian | Custodian controls the cash account | | Trade execution details | Executing broker / custodian | Trade occurred on their platform | | Cost basis (for tax reporting) | Custodian | Custodian reports 1099-B to IRS | | Performance returns | Advisor system (PMS) | PMS maintains the calculation methodology | | Model assignment and drift | Advisor system (PMS) | PMS manages the investment process | | Fee schedule and billing | Advisor system (PMS) | PMS calculates fees per advisory agreement | | Corporate action elections | Custodian | Custodian processes the action |
**Reconciliation Frequency.** The standard frequencies are: - Position reconciliation: daily (end of each business day) - Cash reconciliation: daily - Transaction reconciliation: T+1 (one business day after the trade or event) - Market value reconciliation: daily - Accrued income reconciliation: daily or weekly, depending on portfolio composition - Cost basis reconciliation: monthly or quarterly
### 3. Break Identification
A break is any discrepancy identified during reconciliation between two or more records. Break identification is the process of detecting, classifying, and prioritizing breaks for investigation and resolution.
**Tolerance Thresholds.** Not all discrepancies warrant investigation. Tolerance thresholds define the minimum discrepancy that constitutes a reportable break:
| Reconciliation Type | Typical Tolerance | Rationale | |---|---|---| | Position (shares/units) | Zero (exact match required) | Any share difference indicates a missing or erroneous transaction | | Cash balance | $0.50 - $5.00 | Small rounding differences across systems are expected | | Market value | 5-10 bps of account value | Pricing source differences create small value discrepancies | | Accrued income | $0.01 - $1.00 | Day-count and rounding conventions vary across systems | | Cost basis | Zero (exact match required) | Any basis difference affects tax reporting accuracy | | Transaction matching | Exact match on key fields | Unmatched transactions require investigation |
**Break Categorization.** Breaks are classified by root cause to enable pattern analysis and systemic remediation:
- **Timing differences.** The most common category. Arise when the PMS and custodian record the same event on different dates. Examples: a trade executed late in the day may appear in the PMS on trade date but in the custodian file the following day; a dividend may post in the custodian on the pay date but in the PMS on the record date. Timing breaks typically self-resolve within one to two business days. - **Pricing differences.** Occur when the PMS and custodian use different pricing sources or apply different pricing hierarchies. Most common for fixed-income securities, international equities (with exchange rate differences), and illiquid or thinly traded securities. - **Corporate action differences.** Arise when a corporate action (stock split, merger, spin-off, dividend reinvestment) is processed in one system but not the other, or processed with different terms (different exchange ratio, different effective date). Corporate actions are the single largest cause of position breaks that do not self-resolve. - **Missing transactions.** A transaction appears in one system but not the other. Common causes: a trade placed directly at the custodian without going through the PMS, a manual journal entry in one system, or a data feed failure that dropped a transaction. - **Duplicate transactions.** The same transaction is recorded twice in one system. Can result from data feed reprocessing, manual entry combined with automated feed, or system errors during corporate action processing. - **Data quality issues.** Security identifiers do not match across systems (CUSIP changes, ticker symbol changes), account numbers are mapped incorrectly, or data feed parsing errors corrupt field values.
**Break Severity Levels.** Breaks are prioritized based on their operational impact:
- **Critical (must resolve same day).** Position breaks affecting client-facing reporting or imminent billing, cash breaks exceeding a material threshold (e.g., $10,000), and any break that would affect a trade if left unresolved. - **High (must resolve within two business days).** Position breaks on any actively traded security, market value breaks exceeding the tolerance, and unmatched transactions from the prior day. - **Medium (must resolve within five business days).** Accrued income differences, cost basis discrepancies identified in periodic reconciliation, and pricing breaks on less liquid securities. - **Low (resolve within the current monthly cycle).** Minor rounding differences within tolerance, known timing differences expected to self-resolve, and informational discrepancies that do not affect reporting or billing.
### 4. Break Resolution Workflows
Once a break is identified and categorized, it enters a structured resolution workflow. Effective break resolution combines investigative rigor with operational efficiency.
**Investigation Procedures.** The standard investigation sequence for a position break is:
1. Verify the break is not a known timing difference by checking pending transactions and unsettled activity in both systems. 2. Review the transaction history for the affected security in both the PMS and custodian to identify the divergence point — the first date on which the records disagree. 3. Check for unproc
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for reconciliation, ready for a manual X post.
A practical pick for market research: reconciliation: Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building... 178 stars https://www.openagentskill.com/skills/joellewis-reconciliation?ref=x
Listing + install path for reconciliation: https://www.openagentskill.com/skills/joellewis-reconciliation?ref=x Install: npx skills add JoelLewis/finance_skills --skill reconciliation
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to JoelLewis but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/joellewis-reconciliation?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/joellewis-reconciliation?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/joellewis-reconciliation/audit)
[](https://www.openagentskill.com/skills/joellewis-reconciliation?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)JoelLewis
@joellewis
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Frontend Design
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
174.2K StarsTaste Skill: Anti-Slop Frontend
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
84.4K StarsCanvas Design
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
174.2K StarsAnthropic Brand Guidelines
Apply Anthropic official brand colors, typography, and visual standards to appropriate Anthropic-related artifacts.
174.2K StarsSandbox only
Install targets
Codex install prompt
Install the "reconciliation" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/client-operations/skills/reconciliation. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building a daily position, cash, or transaction reconciliation process, investigating discrepancies between internal records and custodian records, diagnosing recurring break patterns from corporate actions or pricing differences, setting tolerance thresholds for position, cash, or market value matching, implementing three-way reconciliation, designing break investigation workflows with aging and escalation, normalizing multi-custodian feeds from Schwab, Fidelity, or Pershing, reconciling cost basis or accrued income, or preparing for examinations on books and records accuracy. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"joellewis-reconciliation","task":"Install reconciliation","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Design assets, images, video, audio, multimodal media, presentation, and creative production skills.
Scenario
Design and creative
I need my agent to produce design assets, UI directions, presentations, or creative media workflows.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add JoelLewis/finance_skills --skill reconciliation
Maintenance
active
2mo since push
Risk
Risky
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
178
63/100 Quality · 80/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision · Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
RiskyA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
178 GitHub stars
Repo activity
178 stars, 34 forks
Maintenance
2mo since push
License
MIT
Install
npx skills add JoelLewis/finance_skills --skill reconciliation
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add JoelLewis/finance_skills --skill reconciliationDo not use when
Alternative
174.2K Stars
npx skills add anthropics/skills --skill frontend-design
Alternative
84.4K Stars
npx skills add Leonxlnx/taste-skill --skill design-taste-frontend
Alternative
174.2K Stars
npx skills add anthropics/skills --skill canvas-design
Alternative
174.2K Stars
npx skills add anthropics/skills --skill brand-guidelines
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20reconciliation%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20reconciliation%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/joellewis-reconciliation/install
Agent should check
Copy prompt
Task: Use reconciliation in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20reconciliation%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/joellewis-reconciliation/install
Install command: npx skills add JoelLewis/finance_skills --skill reconciliation
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/joellewis-reconciliation/install
LLM text format
/api/skills/joellewis-reconciliation/install?format=text
Find alternatives
/api/skills/search?q=reconciliation&limit=3
Agent prompt
Use reconciliation for this task. Review https://www.openagentskill.com/api/skills/joellewis-reconciliation/install, then install with: npx skills add JoelLewis/finance_skills --skill reconciliationRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/joellewis-reconciliation
LLM text
/api/registry/manifest/joellewis-reconciliation?format=text
Install alias
/api/registry/install/joellewis-reconciliation
Recommend
/api/registry/recommend?task=Use%20reconciliation%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Research agents
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO178 GitHub stars
Stars/forks activity
CHECK178 stars, 34 forks; issue activity unavailable in current metadata
Recent maintenance
PASS2mo since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Analyze markets
I need my agent to analyze markets, financial data, filings, portfolios, and quant strategies.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Alternative shortlist
Similar skills that may fit this task.
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
Apply Anthropic official brand colors, typography, and visual standards to appropriate Anthropic-related artifacts.
--- name: reconciliation description: "Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building a daily position, cash, or transaction reconciliation process, investigating discrepancies between internal records and custodian records, diagnosing recurring break patterns from corporate actions or pricing differences, setting tolerance thresholds for position, cash, or market value matching, implementing three-way reconciliation, designing break investigation workflows with aging and escalation, normalizing multi-custodian feeds from Schwab, Fidelity, or Pershing, reconciling cost basis or accrued income, or preparing for examinations on books and records accuracy." ---
# Reconciliation
## Core Concepts
### 1. Reconciliation Types and Hierarchy
Reconciliation is the systematic comparison of records across two or more systems to identify and resolve discrepancies. In securities operations, reconciliation ensures that the firm's internal records (the investment book of record, or IBOR) match the custodian's official records (the official book of record, or OBOR) and, where applicable, the clearing firm's records. The reconciliation hierarchy proceeds from the most fundamental data element (positions) through increasingly derived data elements.
**Position Reconciliation.** The foundational reconciliation. Compares the number of shares or units held for each security in each account between the firm's portfolio management system (PMS) and the custodian. Position reconciliation is typically zero-tolerance: any share count difference, no matter how small, constitutes a break. Fractional share differences (common with dividend reinvestment plans) must also be identified and resolved. Position reconciliation is performed daily, using end-of-day files from the custodian compared against the PMS position ledger.
**Cash Reconciliation.** Compares cash balances between the PMS and the custodian, accounting for settled cash, pending settlements, accrued income, and pending fee debits. Cash reconciliation is more nuanced than position reconciliation because timing differences are inherent — a trade executed on day T settles on T+1, and the PMS and custodian may record the cash impact on different dates. Cash tolerance thresholds are common, typically a small dollar amount (e.g., $0.50 to $5.00) to accommodate rounding differences across systems. Balances outside the tolerance require investigation.
**Transaction Reconciliation.** Compares individual transactions (trades, dividends, interest payments, transfers, fees) recorded in the PMS against the custodian's transaction ledger. Transaction reconciliation operates at the trade level, matching on security, quantity, price, trade date, and settlement date. Unmatched transactions on either side constitute breaks. Transaction reconciliation is typically performed on a T+1 basis — comparing yesterday's activity after the custodian's end-of-day file is received.
**Market Value Reconciliation.** Compares the total market value of each position and each account between systems. Market value breaks often result from pricing differences — the PMS and custodian may source prices from different vendors or apply different pricing hierarchies for thinly traded or illiquid securities. Market value tolerance is typically expressed in basis points (e.g., 5-10 bps of account value) rather than absolute dollars, because a $100 difference on a $50,000 account is more significant than a $100 difference on a $5,000,000 account.
**Accrued Income Reconciliation.** Compares accrued interest on fixed-income holdings and declared-but-unpaid dividends. Accrued income differences frequently arise from day-count convention differences (actual/actual vs. 30/360), ex-date vs. record-date timing, or different treatment of defaulted bonds. This reconciliation is particularly important for fixed-income-heavy portfolios where accrued income is a material component of total value.
**Cost Basis Reconciliation.** Compares the tax lot-level cost basis for each position between the PMS and the custodian. Cost basis discrepancies are among the most difficult to resolve because they may originate from historical corporate actions (splits, mergers, spin-offs, return of capital adjustments) that were processed differently in each system. Since the custodian reports cost basis to the IRS on Form 1099-B, cost basis discrepancies can result in incorrect tax reporting if not resolved. Cost basis reconciliation is typically performed less frequently than position reconciliation — monthly or quarterly — but with zero tolerance for discrepancies.
### 2. Three-Way Reconciliation
For advisory firms that use a portfolio management system separate from both the custodian and any clearing firm, three-way reconciliation is the standard of practice. The three records being compared are:
**Advisor System (PMS / Portfolio Accounting).** The firm's investment book of record (IBOR), maintained in the portfolio management system (Orion, Black Diamond, Tamarac, Addepar, or similar). This is the record the firm uses for performance reporting, billing, rebalancing, and client-facing communications. The advisor system reflects the firm's understanding of what each client owns.
**Custodian Records.** The official book of record (OBOR), maintained by the custodian (Schwab, Fidelity, Pershing, or similar). This is the legally authoritative record of client assets. The custodian is responsible for safekeeping assets, settling transactions, and reporting to the IRS. When the advisor system and custodian disagree, the custodian record is presumed correct unless the firm can demonstrate otherwise.
**Clearing Firm Records.** For firms that clear through a separate entity (introducing broker-dealers that clear through a correspondent clearing firm), the clearing firm maintains its own record of positions and transactions. The clearing firm processes settlements, maintains margin calculations, and generates customer statements. In a fully disclosed arrangement, the clearing firm's records should match the custodian's, but discrepancies can arise from timing, corporate action processing, or data feed errors.
**Authoritative Source by Data Element.** Different systems serve as the authoritative source for different data elements:
| Data Element | Authoritative Source | Reason | |---|---|---| | Share/unit count | Custodian | Custodian holds the securities in legal custody | | Settled cash balance | Custodian | Custodian controls the cash account | | Trade execution details | Executing broker / custodian | Trade occurred on their platform | | Cost basis (for tax reporting) | Custodian | Custodian reports 1099-B to IRS | | Performance returns | Advisor system (PMS) | PMS maintains the calculation methodology | | Model assignment and drift | Advisor system (PMS) | PMS manages the investment process | | Fee schedule and billing | Advisor system (PMS) | PMS calculates fees per advisory agreement | | Corporate action elections | Custodian | Custodian processes the action |
**Reconciliation Frequency.** The standard frequencies are: - Position reconciliation: daily (end of each business day) - Cash reconciliation: daily - Transaction reconciliation: T+1 (one business day after the trade or event) - Market value reconciliation: daily - Accrued income reconciliation: daily or weekly, depending on portfolio composition - Cost basis reconciliation: monthly or quarterly
### 3. Break Identification
A break is any discrepancy identified during reconciliation between two or more records. Break identification is the process of detecting, classifying, and prioritizing breaks for investigation and resolution.
**Tolerance Thresholds.** Not all discrepancies warrant investigation. Tolerance thresholds define the minimum discrepancy that constitutes a reportable break:
| Reconciliation Type | Typical Tolerance | Rationale | |---|---|---| | Position (shares/units) | Zero (exact match required) | Any share difference indicates a missing or erroneous transaction | | Cash balance | $0.50 - $5.00 | Small rounding differences across systems are expected | | Market value | 5-10 bps of account value | Pricing source differences create small value discrepancies | | Accrued income | $0.01 - $1.00 | Day-count and rounding conventions vary across systems | | Cost basis | Zero (exact match required) | Any basis difference affects tax reporting accuracy | | Transaction matching | Exact match on key fields | Unmatched transactions require investigation |
**Break Categorization.** Breaks are classified by root cause to enable pattern analysis and systemic remediation:
- **Timing differences.** The most common category. Arise when the PMS and custodian record the same event on different dates. Examples: a trade executed late in the day may appear in the PMS on trade date but in the custodian file the following day; a dividend may post in the custodian on the pay date but in the PMS on the record date. Timing breaks typically self-resolve within one to two business days. - **Pricing differences.** Occur when the PMS and custodian use different pricing sources or apply different pricing hierarchies. Most common for fixed-income securities, international equities (with exchange rate differences), and illiquid or thinly traded securities. - **Corporate action differences.** Arise when a corporate action (stock split, merger, spin-off, dividend reinvestment) is processed in one system but not the other, or processed with different terms (different exchange ratio, different effective date). Corporate actions are the single largest cause of position breaks that do not self-resolve. - **Missing transactions.** A transaction appears in one system but not the other. Common causes: a trade placed directly at the custodian without going through the PMS, a manual journal entry in one system, or a data feed failure that dropped a transaction. - **Duplicate transactions.** The same transaction is recorded twice in one system. Can result from data feed reprocessing, manual entry combined with automated feed, or system errors during corporate action processing. - **Data quality issues.** Security identifiers do not match across systems (CUSIP changes, ticker symbol changes), account numbers are mapped incorrectly, or data feed parsing errors corrupt field values.
**Break Severity Levels.** Breaks are prioritized based on their operational impact:
- **Critical (must resolve same day).** Position breaks affecting client-facing reporting or imminent billing, cash breaks exceeding a material threshold (e.g., $10,000), and any break that would affect a trade if left unresolved. - **High (must resolve within two business days).** Position breaks on any actively traded security, market value breaks exceeding the tolerance, and unmatched transactions from the prior day. - **Medium (must resolve within five business days).** Accrued income differences, cost basis discrepancies identified in periodic reconciliation, and pricing breaks on less liquid securities. - **Low (resolve within the current monthly cycle).** Minor rounding differences within tolerance, known timing differences expected to self-resolve, and informational discrepancies that do not affect reporting or billing.
### 4. Break Resolution Workflows
Once a break is identified and categorized, it enters a structured resolution workflow. Effective break resolution combines investigative rigor with operational efficiency.
**Investigation Procedures.** The standard investigation sequence for a position break is:
1. Verify the break is not a known timing difference by checking pending transactions and unsettled activity in both systems. 2. Review the transaction history for the affected security in both the PMS and custodian to identify the divergence point — the first date on which the records disagree. 3. Check for unproc
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for reconciliation, ready for a manual X post.
A practical pick for market research: reconciliation: Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building... 178 stars https://www.openagentskill.com/skills/joellewis-reconciliation?ref=x
Listing + install path for reconciliation: https://www.openagentskill.com/skills/joellewis-reconciliation?ref=x Install: npx skills add JoelLewis/finance_skills --skill reconciliation
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to JoelLewis but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/joellewis-reconciliation?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/joellewis-reconciliation?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/joellewis-reconciliation/audit)
[](https://www.openagentskill.com/skills/joellewis-reconciliation?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)JoelLewis
@joellewis
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Frontend Design
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
174.2K StarsTaste Skill: Anti-Slop Frontend
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
84.4K StarsCanvas Design
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
174.2K StarsAnthropic Brand Guidelines
Apply Anthropic official brand colors, typography, and visual standards to appropriate Anthropic-related artifacts.
174.2K StarsSandbox only
Install targets
Codex install prompt
Install the "reconciliation" agent skill from https://github.com/JoelLewis/finance_skills/tree/main/plugins/client-operations/skills/reconciliation. Read its SKILL.md or equivalent instructions first, install only the files needed for this workspace, and summarize any required setup before using it. Skill purpose: Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building a daily position, cash, or transaction reconciliation process, investigating discrepancies between internal records and custodian records, diagnosing recurring break patterns from corporate actions or pricing differences, setting tolerance thresholds for position, cash, or market value matching, implementing three-way reconciliation, designing break investigation workflows with aging and escalation, normalizing multi-custodian feeds from Schwab, Fidelity, or Pershing, reconciling cost basis or accrued income, or preparing for examinations on books and records accuracy. After the install attempt, report the result to https://www.openagentskill.com/api/agent/outcome with POST JSON {"event_id":"install_<unique-id>","skill_slug":"joellewis-reconciliation","task":"Install reconciliation","agent":"codex","outcome":"success","install_used":true}. Replace event_id with a unique value and outcome with success or failed. Report success only after the skill is installed and a minimal verification passes.Supply asset profile
Design assets, images, video, audio, multimodal media, presentation, and creative production skills.
Scenario
Design and creative
I need my agent to produce design assets, UI directions, presentations, or creative media workflows.
Agent fit
Claude Code + CLI + Codex
Codex, Claude Code, Cursor, CLI, or custom agents.
Install
Ready
npx skills add JoelLewis/finance_skills --skill reconciliation
Maintenance
active
2mo since push
Risk
Risky
Financial research output is not financial advice; require human review before any live investment decision
GitHub quality
178
63/100 Quality · 80/100 Trust
Coverage tags
Review notes
Financial research output is not financial advice; require human review before any live investment decision · Potential broker, wallet, exchange, or real-money execution surface; sandbox and explicit approval are required
Agent adoption scorecard
These scores combine public repository metadata, OpenAgentSkill review signals, maintenance freshness, and install readiness. They are a shortlist signal, not a replacement for human review.
Quality
PromisingUseful candidate, but compare it with alternatives before adopting.
Trust
Sandbox onlyUseful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
Audit
RiskyA machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
OpenAgentSkill Trust Score v5
Run only in a sandbox and compare close alternatives before using it for real work.
Stars
178 GitHub stars
Repo activity
178 stars, 34 forks
Maintenance
2mo since push
License
MIT
Install
npx skills add JoelLewis/finance_skills --skill reconciliation
Install safety
Agent-readable metadata
Use this block or the embedded JSON to decide whether an agent should install this skill, choose an alternative, or ask for human review first.
Suited tasks
Suited agents
Install decision
Trust and risk
Outcome loop
Install command
npx skills add JoelLewis/finance_skills --skill reconciliationDo not use when
Alternative
174.2K Stars
npx skills add anthropics/skills --skill frontend-design
Alternative
84.4K Stars
npx skills add Leonxlnx/taste-skill --skill design-taste-frontend
Alternative
174.2K Stars
npx skills add anthropics/skills --skill canvas-design
Alternative
174.2K Stars
npx skills add anthropics/skills --skill brand-guidelines
Agent safety v2
This skill should not be selected by an agent without explicit human security review.
Do not auto-install. Inspect the source, dependencies, and permission surface first.
medium
Skill may drive a browser or interact with web pages.
medium
Skill likely fetches remote pages, APIs, repositories, or external services.
medium
Skill may read or write project files, documents, generated artifacts, or local workspace state.
Agent resolve plan
The Resolve API returns the selected skill, alternatives, safety policy, audit notes, install target, and copy-paste prompt an agent can follow without scraping this page.
Open JSON
/api/agent/resolve?task=Use%20reconciliation%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Resolve text
/api/agent/resolve?task=Use%20reconciliation%20for%20an%20agent%20workflow&agent=codex&max_risk=medium&format=text
Install handoff
/api/skills/joellewis-reconciliation/install
Agent should check
Copy prompt
Task: Use reconciliation in this workspace.
Resolve first: https://www.openagentskill.com/api/agent/resolve?task=Use%20reconciliation%20for%20an%20agent%20workflow&agent=codex&max_risk=medium
Review install handoff: https://www.openagentskill.com/api/skills/joellewis-reconciliation/install
Install command: npx skills add JoelLewis/finance_skills --skill reconciliation
Before running it, summarize audit warnings, required permissions, and the fallback skill if install is risky.Agent handoff
Use the public install endpoint to fetch the command, safety checklist, target prompts, and canonical links for this skill.
Install handoff
/api/skills/joellewis-reconciliation/install
LLM text format
/api/skills/joellewis-reconciliation/install?format=text
Find alternatives
/api/skills/search?q=reconciliation&limit=3
Agent prompt
Use reconciliation for this task. Review https://www.openagentskill.com/api/skills/joellewis-reconciliation/install, then install with: npx skills add JoelLewis/finance_skills --skill reconciliationRegistry metadata
This page exposes the same decision, trust, audit, use-case, and install signals through the Registry API, so agents can rank this skill without scraping the UI.
Manifest
/api/registry/manifest/joellewis-reconciliation
LLM text
/api/registry/manifest/joellewis-reconciliation?format=text
Install alias
/api/registry/install/joellewis-reconciliation
Recommend
/api/registry/recommend?task=Use%20reconciliation%20in%20an%20agent%20workflow&limit=3
Agent fit
Research agents
Use-case tags
Platforms
Claude Code
Audit report
A machine-readable review of install readiness, security metadata, maintenance, and adoption risk.
Agent decision cockpit
Prototype with this skill first; keep a fallback candidate ready.
Role in stack
Fallback candidate
Primary fit
Research agents
Trust label
Prototype first
Install path
Command ready
Use when
Evidence
review first
Implementation path
Trust profile
Useful candidate with missing or mixed trust signals. Keep it in an isolated workspace until the outcome loop proves task fit.
GitHub adoption
INFO178 GitHub stars
Stars/forks activity
CHECK178 stars, 34 forks; issue activity unavailable in current metadata
Recent maintenance
PASS2mo since push
License clarity
PASSMIT
Good signals
Review before install
Recommended action
Run only in a sandbox and compare close alternatives before using it for real work.
Quality profile
Useful candidate, but compare it with alternatives before adopting.
Workflow fit
Investigate faster
I need my agent to research a topic, compare sources, and produce a concise report.
Analyze markets
I need my agent to analyze markets, financial data, filings, portfolios, and quant strategies.
Manage repositories
I need my agent to triage GitHub issues, review pull requests, and summarize repository changes.
Workflow fit
Find, compare, and synthesize
A workflow for agents that gather sources, compare claims, summarize long material, and draft useful research briefs.
Turn skills into distribution
A workflow for turning newly indexed skills into SEO briefs, social drafts, comparison pages, and reusable publishing workflows.
Operate and verify web apps
A workflow for agents that navigate products, fill forms, take screenshots, and verify real user flows across web applications.
Alternative shortlist
Similar skills that may fit this task.
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
Apply Anthropic official brand colors, typography, and visual standards to appropriate Anthropic-related artifacts.
--- name: reconciliation description: "Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building a daily position, cash, or transaction reconciliation process, investigating discrepancies between internal records and custodian records, diagnosing recurring break patterns from corporate actions or pricing differences, setting tolerance thresholds for position, cash, or market value matching, implementing three-way reconciliation, designing break investigation workflows with aging and escalation, normalizing multi-custodian feeds from Schwab, Fidelity, or Pershing, reconciling cost basis or accrued income, or preparing for examinations on books and records accuracy." ---
# Reconciliation
## Core Concepts
### 1. Reconciliation Types and Hierarchy
Reconciliation is the systematic comparison of records across two or more systems to identify and resolve discrepancies. In securities operations, reconciliation ensures that the firm's internal records (the investment book of record, or IBOR) match the custodian's official records (the official book of record, or OBOR) and, where applicable, the clearing firm's records. The reconciliation hierarchy proceeds from the most fundamental data element (positions) through increasingly derived data elements.
**Position Reconciliation.** The foundational reconciliation. Compares the number of shares or units held for each security in each account between the firm's portfolio management system (PMS) and the custodian. Position reconciliation is typically zero-tolerance: any share count difference, no matter how small, constitutes a break. Fractional share differences (common with dividend reinvestment plans) must also be identified and resolved. Position reconciliation is performed daily, using end-of-day files from the custodian compared against the PMS position ledger.
**Cash Reconciliation.** Compares cash balances between the PMS and the custodian, accounting for settled cash, pending settlements, accrued income, and pending fee debits. Cash reconciliation is more nuanced than position reconciliation because timing differences are inherent — a trade executed on day T settles on T+1, and the PMS and custodian may record the cash impact on different dates. Cash tolerance thresholds are common, typically a small dollar amount (e.g., $0.50 to $5.00) to accommodate rounding differences across systems. Balances outside the tolerance require investigation.
**Transaction Reconciliation.** Compares individual transactions (trades, dividends, interest payments, transfers, fees) recorded in the PMS against the custodian's transaction ledger. Transaction reconciliation operates at the trade level, matching on security, quantity, price, trade date, and settlement date. Unmatched transactions on either side constitute breaks. Transaction reconciliation is typically performed on a T+1 basis — comparing yesterday's activity after the custodian's end-of-day file is received.
**Market Value Reconciliation.** Compares the total market value of each position and each account between systems. Market value breaks often result from pricing differences — the PMS and custodian may source prices from different vendors or apply different pricing hierarchies for thinly traded or illiquid securities. Market value tolerance is typically expressed in basis points (e.g., 5-10 bps of account value) rather than absolute dollars, because a $100 difference on a $50,000 account is more significant than a $100 difference on a $5,000,000 account.
**Accrued Income Reconciliation.** Compares accrued interest on fixed-income holdings and declared-but-unpaid dividends. Accrued income differences frequently arise from day-count convention differences (actual/actual vs. 30/360), ex-date vs. record-date timing, or different treatment of defaulted bonds. This reconciliation is particularly important for fixed-income-heavy portfolios where accrued income is a material component of total value.
**Cost Basis Reconciliation.** Compares the tax lot-level cost basis for each position between the PMS and the custodian. Cost basis discrepancies are among the most difficult to resolve because they may originate from historical corporate actions (splits, mergers, spin-offs, return of capital adjustments) that were processed differently in each system. Since the custodian reports cost basis to the IRS on Form 1099-B, cost basis discrepancies can result in incorrect tax reporting if not resolved. Cost basis reconciliation is typically performed less frequently than position reconciliation — monthly or quarterly — but with zero tolerance for discrepancies.
### 2. Three-Way Reconciliation
For advisory firms that use a portfolio management system separate from both the custodian and any clearing firm, three-way reconciliation is the standard of practice. The three records being compared are:
**Advisor System (PMS / Portfolio Accounting).** The firm's investment book of record (IBOR), maintained in the portfolio management system (Orion, Black Diamond, Tamarac, Addepar, or similar). This is the record the firm uses for performance reporting, billing, rebalancing, and client-facing communications. The advisor system reflects the firm's understanding of what each client owns.
**Custodian Records.** The official book of record (OBOR), maintained by the custodian (Schwab, Fidelity, Pershing, or similar). This is the legally authoritative record of client assets. The custodian is responsible for safekeeping assets, settling transactions, and reporting to the IRS. When the advisor system and custodian disagree, the custodian record is presumed correct unless the firm can demonstrate otherwise.
**Clearing Firm Records.** For firms that clear through a separate entity (introducing broker-dealers that clear through a correspondent clearing firm), the clearing firm maintains its own record of positions and transactions. The clearing firm processes settlements, maintains margin calculations, and generates customer statements. In a fully disclosed arrangement, the clearing firm's records should match the custodian's, but discrepancies can arise from timing, corporate action processing, or data feed errors.
**Authoritative Source by Data Element.** Different systems serve as the authoritative source for different data elements:
| Data Element | Authoritative Source | Reason | |---|---|---| | Share/unit count | Custodian | Custodian holds the securities in legal custody | | Settled cash balance | Custodian | Custodian controls the cash account | | Trade execution details | Executing broker / custodian | Trade occurred on their platform | | Cost basis (for tax reporting) | Custodian | Custodian reports 1099-B to IRS | | Performance returns | Advisor system (PMS) | PMS maintains the calculation methodology | | Model assignment and drift | Advisor system (PMS) | PMS manages the investment process | | Fee schedule and billing | Advisor system (PMS) | PMS calculates fees per advisory agreement | | Corporate action elections | Custodian | Custodian processes the action |
**Reconciliation Frequency.** The standard frequencies are: - Position reconciliation: daily (end of each business day) - Cash reconciliation: daily - Transaction reconciliation: T+1 (one business day after the trade or event) - Market value reconciliation: daily - Accrued income reconciliation: daily or weekly, depending on portfolio composition - Cost basis reconciliation: monthly or quarterly
### 3. Break Identification
A break is any discrepancy identified during reconciliation between two or more records. Break identification is the process of detecting, classifying, and prioritizing breaks for investigation and resolution.
**Tolerance Thresholds.** Not all discrepancies warrant investigation. Tolerance thresholds define the minimum discrepancy that constitutes a reportable break:
| Reconciliation Type | Typical Tolerance | Rationale | |---|---|---| | Position (shares/units) | Zero (exact match required) | Any share difference indicates a missing or erroneous transaction | | Cash balance | $0.50 - $5.00 | Small rounding differences across systems are expected | | Market value | 5-10 bps of account value | Pricing source differences create small value discrepancies | | Accrued income | $0.01 - $1.00 | Day-count and rounding conventions vary across systems | | Cost basis | Zero (exact match required) | Any basis difference affects tax reporting accuracy | | Transaction matching | Exact match on key fields | Unmatched transactions require investigation |
**Break Categorization.** Breaks are classified by root cause to enable pattern analysis and systemic remediation:
- **Timing differences.** The most common category. Arise when the PMS and custodian record the same event on different dates. Examples: a trade executed late in the day may appear in the PMS on trade date but in the custodian file the following day; a dividend may post in the custodian on the pay date but in the PMS on the record date. Timing breaks typically self-resolve within one to two business days. - **Pricing differences.** Occur when the PMS and custodian use different pricing sources or apply different pricing hierarchies. Most common for fixed-income securities, international equities (with exchange rate differences), and illiquid or thinly traded securities. - **Corporate action differences.** Arise when a corporate action (stock split, merger, spin-off, dividend reinvestment) is processed in one system but not the other, or processed with different terms (different exchange ratio, different effective date). Corporate actions are the single largest cause of position breaks that do not self-resolve. - **Missing transactions.** A transaction appears in one system but not the other. Common causes: a trade placed directly at the custodian without going through the PMS, a manual journal entry in one system, or a data feed failure that dropped a transaction. - **Duplicate transactions.** The same transaction is recorded twice in one system. Can result from data feed reprocessing, manual entry combined with automated feed, or system errors during corporate action processing. - **Data quality issues.** Security identifiers do not match across systems (CUSIP changes, ticker symbol changes), account numbers are mapped incorrectly, or data feed parsing errors corrupt field values.
**Break Severity Levels.** Breaks are prioritized based on their operational impact:
- **Critical (must resolve same day).** Position breaks affecting client-facing reporting or imminent billing, cash breaks exceeding a material threshold (e.g., $10,000), and any break that would affect a trade if left unresolved. - **High (must resolve within two business days).** Position breaks on any actively traded security, market value breaks exceeding the tolerance, and unmatched transactions from the prior day. - **Medium (must resolve within five business days).** Accrued income differences, cost basis discrepancies identified in periodic reconciliation, and pricing breaks on less liquid securities. - **Low (resolve within the current monthly cycle).** Minor rounding differences within tolerance, known timing differences expected to self-resolve, and informational discrepancies that do not affect reporting or billing.
### 4. Break Resolution Workflows
Once a break is identified and categorized, it enters a structured resolution workflow. Effective break resolution combines investigative rigor with operational efficiency.
**Investigation Procedures.** The standard investigation sequence for a position break is:
1. Verify the break is not a known timing difference by checking pending transactions and unsettled activity in both systems. 2. Review the transaction history for the affected security in both the PMS and custodian to identify the divergence point — the first date on which the records disagree. 3. Check for unproc
Source provenance
Decision snapshot
recent repository activity
Audit
Install and adoption review
Agent-proven evidence
Outcome reports after resolve, review, install, and one narrow run.
No agent outcome data yet. The first agent run can report success, setup needs, risk blocks, failure, or not-relevant through /api/agent/outcome.
Install
Free and open source. Review the report before installing into production agents.
Growth loop
Scenario-led draft for reconciliation, ready for a manual X post.
A practical pick for market research: reconciliation: Design and operate reconciliation processes across portfolio management, custodian, and clearing systems. Use when building... 178 stars https://www.openagentskill.com/skills/joellewis-reconciliation?ref=x
Listing + install path for reconciliation: https://www.openagentskill.com/skills/joellewis-reconciliation?ref=x Install: npx skills add JoelLewis/finance_skills --skill reconciliation
Listing source
This listing was indexed from public sources and is not marked official until a maintainer claim is approved.
Attribution links to the public repository or creator profile. Creators can claim the listing to update ownership signals.
Claim this skillOwner claim
This Registry indexed listing is attributed to JoelLewis but is not marked official yet. Claim it to add a verified owner signal and make future launch, install, and audit updates easier to trust.
Creator backlink kit
Show the canonical listing, current trust and audit signals, and real Agent-Proven evidence where developers evaluate the repository.
[](https://www.openagentskill.com/skills/joellewis-reconciliation?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/joellewis-reconciliation?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)
[](https://www.openagentskill.com/skills/joellewis-reconciliation/audit)
[](https://www.openagentskill.com/skills/joellewis-reconciliation?ref=github&utm_source=github&utm_medium=referral&utm_campaign=creator_badge)JoelLewis
@joellewis
Share whether this skill looks useful for your agent workflow. Aggregated feedback improves rankings over time.
Sandbox only
Frontend Design
Guidance for distinctive, intentional UI design, typography, visual direction, and non-template-like product interfaces.
174.2K StarsTaste Skill: Anti-Slop Frontend
Design and implementation guidance for distinctive landing pages, portfolios, product demos, and purposeful redesigns.
84.4K StarsCanvas Design
Create original visual art, posters, PNG assets, and PDF documents through a clear design philosophy.
174.2K StarsAnthropic Brand Guidelines
Apply Anthropic official brand colors, typography, and visual standards to appropriate Anthropic-related artifacts.
174.2K StarsPermission surface
filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness
Permission surface
filesystem or document access
Agent outcomes
No agent outcome data yet
Docs
Strong README/SKILL.md context
Risk summary
Install readiness