Methodology

How we source and calculate data.

Every number on RetailBonds.in is traceable to a public source. This page explains the sources, update frequency, calculation conventions, and what we don't measure.

Last updated: August 2026

This page describes where our data comes from, how often we update it, how we calculate the figures we display, and what we do not measure. The goal is verifiability: every claim on RetailBonds.in should be traceable to a public source.

Data sources

We aggregate data from the following primary sources:

We do not source data from paid feeds (Bloomberg, Refinitiv, etc.) at this time. Our coverage therefore has gaps: instruments that are not listed on BSE/NSE or covered by CRISIL may be absent. Coverage expands as more scrapers come online (ICRA, CARE, India Ratings).

Update frequency

Data flows into our database via scheduled scrapers running on our infrastructure:

All scrapes run outside Indian market hours. Stale data is a real risk. If a fetch fails repeatedly, we display a warning on the affected page rather than show outdated figures silently.

Validation and quality

For every scraper, we run automated health checks on expected record counts, schema integrity, and range sanity on yields and dates. When a check fails, the source is flagged and reviewed before its output reaches our screener or detail pages.

We retain raw snapshots of every scraping run for debugging and audit purposes. These snapshots are compressed and stored on-server; they are not publicly accessible.

What we do not measure

Calculation conventions

Our calculations follow FIMMDA (Fixed Income Money Market and Derivatives Association of India) standards where applicable:

Where our calculations differ from a source’s published figure, the difference is usually a convention choice (day-count or settlement date). We aim to be explicit and consistent rather than match a specific source’s number exactly.

Issuer name normalization

The same issuer often appears with different names across sources ("Power Finance Corporation Limited", "PFC Ltd", "Power Finance Corp"). We use fuzzy name matching (rapidfuzz token-set ratio, threshold 85) to collapse these into a single issuer record, caching confirmed matches as aliases. Every match is logged for audit. False positives at the 85–90 score band are a known limitation; we correct them as discovered.

Handling missing data

When a field is unknown, we display “—” rather than guess. We do not impute coupon rates, maturity dates, or ratings.

Handling conflicting data

When two sources disagree, we display the SEBI filing as authoritative and log the discrepancy. We do not silently average or pick the more attractive number.

Reporting errors

If you find a data error, email [email protected] with the ISIN, the field in question, and the source supporting the correction. We acknowledge corrections within two business days.

Limitations and transparency

RetailBonds.in is a small independent operation, not a regulated data provider. Our coverage will have gaps. Our refresh frequencies will occasionally lag. Our calculations rest on convention choices that other providers may make differently. We will get things wrong, and when we do, we will fix them publicly rather than quietly.