irmion
HelpLog in Find a tool

Evidence-first money workflow · Finance & Business

Dividend Payment Calendar Reconciler

Match expected and actual dividend payments by security, amount tolerance, and date window to find missing, shifted, or unplanned income.

  1. 1Prepare
  2. 2Analyze
  3. 3Review and export

Prepare the evidence

Paste the documented CSV schema or choose a local CSV file. Nothing is sent to Nirmion.

Choose one label for this run. Values are not converted between currencies.

Differences no larger than this value may match. Keep the tolerance narrow and review fallback matches.

Expected and actual dividend rows can match only within this many calendar days.

Required headers: date,security,amount. Use the expected payment date, security label, and gross amount.

CSV drop zone readyUTF-8 CSV up to 1 MiB and 5,000 data rows.

Drag and drop your CSV here

Drop a UTF-8 CSV in this area or choose a local file. You can review and edit its text below before analysis.

Required headers: date,security,amount. Use the posted date and amount from the account record.

CSV drop zone readyUTF-8 CSV up to 1 MiB and 5,000 data rows.

Drag and drop your CSV here

Drop a UTF-8 CSV in this area or choose a local file. You can review and edit its text below before analysis.

Review the analysis

Summary metrics lead back to the rows that support them.

Method and interpretation

How to use Dividend Payment Calendar Reconciler

Use this dividend tracker after payments post or when reconciling an income calendar to a brokerage export. It matches expected rows with actual evidence and identifies missing payments, date shifts, amount differences, and unplanned receipts. The result is an audit queue, useful for checking records before updating income forecasts or tax workpapers.

  1. Prepare the input

    Prepare one CSV with expected payment date, security label, and gross amount, plus a second CSV with actual posted date, security label, and amount. Keep security names consistent. Choose a small money tolerance for rounding and a calendar-day window that reflects settlement or posting delay. Separate cash dividends from reinvested share purchases and use one currency per run.

  2. Check the worked example

    The example expects two March payments and one June payment. Fund A posts one day late in March, Fund B differs by USD 0.25 but remains within tolerance, and the June Fund A payment posts five days late. An unplanned Fund C receipt remains visible rather than being forced into the nearest expectation.

  3. Read the evidence

    A matched row can still require review when the date or amount differs. Missing expected rows are action items; unplanned actual rows may be a special distribution, a renamed security, an omitted expectation, or a duplicate import. Return to the broker statement or issuer notice before changing tax or income records. The expected gross total is context, not a guarantee of future income.

Calculation method

For each expected row, candidates must have the same normalized security label, an amount difference no greater than tolerance, and a date difference inside the selected window. The nearest unmatched date wins. Exact date and amount matches are reconciled; tolerance or date shifts require review. Actual rows can match only once.

Review Investor.gov’s explanation of mutual fund dividend payments and distributions

Questions this workflow helps answer

Use these questions to confirm that this tool matches the task you need to complete.

  • Which expected dividend payments are missing from my brokerage CSV?
  • How can I reconcile dividend dates and amounts with an income calendar?
  • Which dividend payments were late, changed, or not in my forecast?

Limits and decision boundary

The tool does not fetch declaration, ex-dividend, record, or payment dates. It cannot explain withholding tax, foreign exchange, return of capital, special dividends, corporate actions, or reinvestment. A gross expectation may not equal a net cash posting. Verify source records and jurisdiction-specific reporting separately.

Common mistake

Do not match on ticker alone after a merger, share-class change, or account transfer. Confirm that the security and payment event are the same, and avoid widening tolerance until unrelated payments begin to match.

Your pasted values and selected CSV files are processed in this browser tab. This workflow does not connect to a bank, save a budget, or provide financial, tax, legal, or investment advice.

Questions about this workflow

Should I enter the ex-dividend date?

Use the expected payment date because the actual file contains posted cash. Track ex-dividend dates in a separate eligibility calendar.

Why is a matched row marked for review?

The amount or date changed within the allowed tolerance. Confirm the reason before accepting it.

Can reinvested dividends be included?

Use the dividend cash amount as actual evidence, then track the separate unit purchase in an investment ledger.