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.
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
- Two input sets
- Birth date, time and place
- Conversion fields
- Time zone and location coordinates
- Report requirement
- Named method and component details
- This page
- Informational checklist, not a matching calculator
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 OpenFate 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.
Sources and editorial basis
- P. V. R. Narasimha Rao: Vedic Astrology — An Integrated ApproachRao, §1.3, printed pp.5–14: longitude, house and chart vocabulary only. The two-profile input form is evidenced by the separate AstroSage source. Rao is not presented as the provider of a full matching algorithm or the source of any product-capability claim. Traditional definitions are not scientific validation of personal outcomes.A named practitioner’s introduction to Jyotish. Used for terminology and a stated method, not universal school agreement or scientific validation. The added March 18, 2010 note describes changed views; it does not establish a fully revised 2010 edition.
- OpenFate Editorial MethodologyOpenFate Editorial Methodology, stable sections #editorial-principles, #editorial-workflow, #editorial-ai, and #editorial-context. Used for the calculation/interpretation and evidence-boundary policy.OpenFate separates deterministic chart calculation, traditional interpretation, and modern editorial explanation.
- AstroSage: Kundli Matching Input FormAstroSage “Kundli Matching”, two-profile form and advanced settings: birth date/time/place, longitude, latitude and time-zone fields, inspected2026-09-08. Read-only form inspection; no birth data submitted and no score generated. Promotional accuracy claims are not adopted.Provider-owned form documenting separate birth date, time, place and advanced coordinate/time-zone inputs. Supports an input-review workflow, not advertised accuracy or OpenFate feature parity.