This page is an English translation of the Japanese Data Quality page, provided for convenience. In the event of any discrepancy between this translation and the Japanese original, the Japanese version shall prevail.

About This Data Quality Verification

Before launching the beta, SWTQ Earnings Filter reviewed TDnet retrieval, XBRL parsing, report generation, email delivery, and the companies extracted as HITs.

This page lists, for each verification date, the number of filings processed, differences from the expected count, the company-name retrieval rate, and the status of HIT-company verification.

Please note: The "data quality verification" described on this page refers to internal checks of retrieved data and aggregated results performed within the service. It is not an assurance engagement performed by a third party.

1. Verification Overview

ItemDetails
Verification periodMay 11, 2026 – June 12, 2026
What was verifiedEarnings releases and XBRL data disclosed on TDnet
Comparison basisExpected number of earnings announcements
Main items checkedTDnet retrieval, XBRL parsing, company-name retrieval, KPI extraction, HIT-company verification, HTML/CSV generation, email delivery
Types of days verifiedHeavy earnings days, medium-volume days, ordinary days, light-volume days, zero-filing days
NoteSWTQ does not process from a schedule of expected earnings announcements — it processes based on the disclosures actually made on TDnet

2. Definition of Verification Status

StatusMeaning
Basic check completeBasic daily-processing items — such as the number of filings processed, company-name retrieval, HTML/CSV generation, and email delivery — have been checked. This does not mean every KPI for every individual company was manually cross-checked.
Detailed check completeFor heavy earnings days or other important verification dates, in addition to the basic check, HIT companies, special cases, displayed content, and classification reasons were checked in detail. This does not guarantee complete accuracy for every company and every field.
Ongoing reviewEven during beta operation, review and improvement continue in response to user feedback, new disclosure formats, unusual XBRL structures, and industry-specific presentation.
Not applicableNo companies were covered, or there were no HIT companies, so there was nothing to individually verify.

3. Daily Verification Results

DateExpected AnnouncementsSWTQ ProcessedDifferenceCompany-Name RetrievalHIT VerificationEmail DeliveryNotes
2026/5/11176177+1~100%Detailed check completeNo-send checkHeavy day
2026/5/12322324+2~100%Detailed check completeNo-send checkHeavy day
2026/5/13500504+4~100%Detailed check completeLive-send checkHeavy day
2026/5/14724724±0~100%Detailed check completeLive-send checkHeavy day
2026/5/15726729+3~100%Detailed check completeNo-send checkHeavy day
2026/5/1844±0~100%Basic check completeLive-send checkLight day
2026/5/1944±0~100%Basic check completeLive-send checkLight day
2026/5/201314+1~100%Basic check completeLive-send checkLight day
2026/5/2111±0~100%Basic check completeLive-send checkLight day
2026/5/2200±0~100%Not applicableLive-send checkZero-filing day
2026/5/2511±0~100%Basic check completeLive-send checkLight day
2026/5/2622±0~100%Basic check completeLive-send checkLight day
2026/5/2711±0~100%Basic check completeLive-send checkLight day
2026/5/2800±0~100%Not applicableLive-send checkZero-filing day
2026/5/2978+1~100%Basic check completeLive-send checkLight day
2026/6/122±0~100%Basic check completeLive-send checkLight day
2026/6/211±0~100%Basic check completeLive-send checkLight day
2026/6/311±0~100%Basic check completeLive-send checkLight day
2026/6/455±0~100%Basic check completeLive-send checkLight day
2026/6/51212±0~100%Basic check completeLive-send checkOrdinary day
2026/6/866±0~100%Basic check completeLive-send checkLight day
2026/6/91010±0~100%Basic check completeLive-send checkOrdinary day
2026/6/102020±0~100%Basic check completeLive-send checkOrdinary day
2026/6/113737±0~100%Basic check completeLive-send checkOrdinary day
2026/6/129998-1~100%Basic check completeLive-send checkMedium-volume day

4. HIT-Company Verification

For companies that met the criteria as a HIT, SWTQ cross-checks the results against the original disclosure documents.

In pre-launch beta verification, the checks cover: company name, security code, whether the disclosure was correctly identified as an earnings release, the key KPIs, the year-over-year figures, the reason for the HIT, and consistency across the HTML, CSV, and email displays.

However, complete accuracy across every company and every field is not guaranteed. When issues are reported by users, we review them and, where necessary, improve the extraction logic, display method, or methodology/classification criteria.

Check ItemWhat Is CheckedScopeStatus
Company nameWhether the notified company name is correctHIT companiesOngoing review
Security codeWhether the notified security code is correctHIT companiesOngoing review
Earnings-release determinationWhether the covered disclosure is properly an earnings releaseHIT companiesOngoing review
RevenueWhether the extracted revenue figure diverges significantly from the disclosureHIT companiesOngoing review
Operating profitWhether the extracted operating profit diverges significantly from the disclosureHIT companiesOngoing review
Ordinary profit / profit before taxWhether the extracted figure diverges significantly from the disclosureHIT companiesOngoing review
Net incomeWhether the extracted net income diverges significantly from the disclosureHIT companiesOngoing review
Year-over-year changeWhether the direction of the rate of change is reasonableHIT companiesOngoing review
HIT reasonWhether the Q/T/W/S classification reason matches what is displayedHIT companiesOngoing review
Report displayWhether the result is confirmable in the email, HTML, and CSVHIT companiesOngoing review

5. Basic Data Quality

MetricWhat Is CheckedResult
Company-name retrieval rateProportion of security codes for which a company name was obtained~100%
Blank security-code rateProportion of records with a blank security code~0.0%
Zero-filing-day handlingWhether processing completes normally on a day with zero covered companiesConfirmed
HTML generationWhether the HTML report is generatedConfirmed
CSV generationWhether the CSV report is generatedConfirmed
Email deliveryWhether delivery reaches registered email addressesConfirmed
Unsubscribe handlingWhether unsubscribed addresses are excluded from deliveryConfirmed

6. Notes on Processing Time

ItemDetails
Initial retrievalCovers TDnet retrieval, XBRL download, parsing, report generation, and email delivery
Re-runsMay reuse existing data and complete faster than the initial run
Daily processing timeVaries with run conditions; treated as a reference figure only
Scheduled runsAt scheduled run times, processing from startup through email delivery happens automatically

7. About Differences in Filing Counts

SWTQ is not a schedule of expected earnings announcements published by a securities firm — it processes based on disclosures actually made on TDnet.

For this reason, the expected number of earnings announcements and the number SWTQ actually processes may not fully match.

Main Cause of DifferenceDetails
Schedule vs. actual disclosureA scheduled disclosure is changed or postponed
Based on actual TDnet disclosuresA disclosure not on the expected schedule appears on TDnet
XBRL availabilityDisclosures without an attached XBRL may be excluded from processing
Disclosure typeDisclosures other than earnings releases may be excluded
Aggregation windowThe disclosure time can shift which day's aggregation a filing falls into

8. Notes

ItemDetails
Data sourceProcessing is based on information actually disclosed on TDnet
Count comparisonCompared against the expected number of announcements; an exact match is not guaranteed
Investment decisionsThis service does not recommend the purchase or sale of any specific financial instrument
Final confirmationAlways confirm each company's official disclosure materials before making an investment decision
Beta positioningDuring the beta, we continuously improve the service based on user feedback