Cross-check a dividend watchlist against current yield data

Why use this

1. An investor maintaining an ETF watchlist may compare yield figures that were collected on different dates or calculated on different bases. A daily-looking summary can conceal that the underlying numbers are stale or not directly comparable.

2. This job could make the yield cross-check transparent by recording definitions, dates and disagreements. The intended value is a reviewable data-quality check, leaving investment decisions and assumptions about future income with the investor and qualified advisers.

Why an agent / simpler alternative

Useful judgment

Distinguish yield definitions, match funds/share classes and explain discrepancies without treating a high yield as a recommendation.

Simpler alternative

Use the issuer's published data directly for a small watchlist.

Unsuitable when

The workflow would trade, rank investments for personal suitability or transmit private holdings without approval.

Proposed inputs

1. Name

   Watchlist extract

   Owner

   Authorized owner

   Minimum scope

   Required fund identifiers and existing yield/date fields

   Quality check

   Remove account balances and unnecessary personal holdings detail

2. Name

   Yield evidence

   Owner

   Permitted published sources

   Minimum scope

   Relevant values, definitions, currency and as-of dates

   Quality check

   Verify fund/share class and source identity

Access and setup — proposed or unknown

Proposed minimum

1. Use a redacted sheet and synthetic yield snippets first; no broker access, live posting or financial transactions.

Compatibility unknowns

1. Current source freshness, data access, scheduled messaging and runtime compatibility are unknown.

External actions requiring approval

1. Sharing customer financial information, changing the sheet or posting recurring summaries requires explicit bounded authorization.

Expected deliverable and review checks

Proposed artifact

Yield comparison table with matching identifiers, definition/date differences and unresolved discrepancies.

Critical checks

1. Do not combine unlike yield measures; retain source dates; distinguish reported values from forecasts and comparisons.

Missing output evidence

This overlay adds no new output inspection, execution or validation; consult the referenced canonical source outcome limits.

Failure signals and proposed responses

1. Signal

   A trailing yield is compared with another definition

   Why it matters

   The apparent change may be methodological

   Proposed response

   Separate measures and explain why comparison is unresolved.

2. Signal

   A ticker matches a different share class

   Why it matters

   The watchlist inherits the wrong figure

   Proposed response

   Verify full fund identity before updating the comparison.

Effort and cost — unknown

Setup work

1. Define identifiers and acceptable yield measures.

Ongoing review

1. Review discrepancies and source dates before use.

Unknowns

1. Publication lag, licensing, reporting reliability and service costs are unknown.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

Invent three fund records with mixed yield definitions, one stale date and one share-class mismatch; prepare a discrepancy table.

Acceptance checks

1. Flag all noncomparability; make no return forecast, trade suggestion or external post.

Stop conditions

1. Stop if current evidence is unavailable or private financial details need unauthorized disclosure.

Limits

1. A yield cross-check cannot establish expected returns, distribution sustainability or suitability for an investor.