Kundli Matching: Inputs and Report Checks
Before using a Kundli matching calculator, verify both birth records, chart settings, component scores and missing-data limits. No score is promised here.
Editorially reviewed: Sep 8, 2026 · Reviewed by Tyean · Editorial Methodology
Before using a Kundli matching calculator, verify both birth records, chart settings, component scores and missing-data limits. No score is promised here.
Overview
Kundli matching tools compare two birth records under a named method. A useful report exposes the inputs, settings and score components; this page explains how to check one rather than pretending to calculate an unsupported score.
At a glance
Check the two birth records independently
Obtain each person’s permission and preserve the source of their date, time and birthplace. Do not copy one profile’s time zone into the other. A provider’s location picker may select a similarly named city, so confirm the resolved country and coordinates. The AstroSage form inspected for this guide requests separate birth profiles and offers advanced coordinate/time-zone fields. That visible workflow supports the input checklist; it does not validate promotional accuracy claims or establish that another product has the same features.
A twelve-hour input mistake is not a matching insight
Imagine a source record saying 7:20 p.m. but a report showing 07:20 in a 24-hour field. The intended entry is 19:20, so the discrepancy is twelve hours. Correcting the record comes before explaining any changed lagna, Moon category or score. After correction, compare the exported settings and individual rows, not only the new total. Save the old report as a superseded version rather than claiming that the relationship itself improved when a data-entry error was fixed.
What to expect from a transparent calculator
Look for the rule system, source or version, component maxima and handling of uncertain time. If the tool returns only a verdict, the calculation cannot be independently audited from that verdict. Name-only matching must not be passed off as a verified birth-chart comparison. This article does not submit birth data, generate a Guna score or promise that Tyean supports every matching algorithm. Check the current product’s documented capabilities separately, and keep the couple’s consent and actual circumstances outside a chart-based verdict.
Related definitions
Vedic Compatibility Methods: A Reading Guide
Choose a Vedic compatibility topic: birth-input checks, Ashtakoota, Manglik variants, Navamsa, dasha overlap and the limits of matching reports.
The Eight Kootas: Names, Maximum Points and Checks
Identify Varna, Vashya, Tara, Yoni, Graha Maitri, Gana, Bhakoota and Nadi, with their 36-point maxima and a report validation example.
Kundli Matching Accuracy, Consent and Uncertain Data
Distinguish repeatable chart calculations from predictive accuracy, handle unknown birth times honestly and protect consent in compatibility discussions.
What Birth Data Does a Vedic Chart Need?
Prepare birth date, local clock time and birthplace for a Vedic chart. Handle date ambiguity, missing time and time-zone conversion explicitly.
Historical Time Zones and DST in Birth Charts
Understand repeated or missing local times, historical offsets and IANA time-zone limits when converting a birth record for a Vedic chart.
Use with Tyean
Kundli Matching
Compare two sidereal charts through Ashtakoota Guna Milan, Moon nakshatras, and dasha timing without treating a guna score as a marriage verdict.
Vedic Birth Chart
Calculate a Vedic chart and inspect the displayed positions and settings.
Vedic Astrology Reading
Explore a traditional interpretation grounded in the calculated chart; outcomes are not guaranteed.
Sources and editorial basis
Read the guide alongside an Tyean result
Start with the concepts on this page, then check how the related product actually uses them. The links below keep its method, verification record, report example and purchase or use instructions together.
Vedic compatibility
For marriage, read the eight Ashtakoota components with their context and the stated Mangal Dosha convention. A 36-point framework is traditional matching, not a calibrated chance of a successful marriage. Other scenarios must not inherit marriage thresholds automatically. Identify whose chart is being described and whether the product uses one person or two. Treat a relationship label as a conversation prompt. Consent, safety, practical agreements and actual conduct matter more than a favorable symbolic pattern. A traditional source explains where a rule comes from. A calculation check tests the stated case. A generated report shows the writing for its recorded input, language and date. None of these alone proves future outcomes, independent expert endorsement or reader satisfaction. Check the sample page for its origin, completeness and any unavailable parts.
同体系词条
本页内容由太乙数衍整理汇编,结合传统经典与 AI 深度解析。以上内容仅作学习参考。