Manual checks sample a fraction of your travel and hope it is representative. The engine reconciles the full population instead, the same way every cycle, across both ledgers: airline invoices under SkyLedger and hotel documents under StayLedger. Output reaches you through Mythos, and on SkyLedger Max every exception it raises is pursued with the carrier rather than simply reported.
Reconciling travel GST properly is simple to describe and brutal to do by hand. Three reasons it had to be engineered.
Thousands of tickets a year, each needing its invoice matched to a specific line in a specific GSTR-2B, against a specific GSTIN. At any real scale, a spreadsheet-and-intern approach doesn't degrade gracefully, it silently misses things.
Every airline formats invoices differently; TMCs re-issue and consolidate; GST portal data has its own shape. Before any matching can happen, all of it has to be read, normalised and attributed correctly, every cycle.
No single missing invoice looks worth a system. A few hundred rupees here, a wrong GSTIN there. It's only in aggregate, found by checking everything, that the recoverable amount becomes what it actually is.
This is the atomic operation, performed once per invoice, thousands of times per cycle: your ticket on one side, the airline's filing on the other, checked field by field.
The same four stages, every period, in the same order. Here's an illustrative quarter moving through.
Invoices read and normalised from every airline, TMC and channel.
Confirmed against your GSTR-2B, line by line, to the right GSTIN.
Missing, mismatched or misreported, each one quantified.
Your position, gap register and audit trail, nothing sampled, nothing assumed.
The matching logic below is shared. What differs is which documents feed it and how far the engagement carries the result.
Chain, property and platform tax invoices for domestic room nights, extracted into the same register format so both streams reconcile through one process rather than two. StayLedger is priced separately but runs on this engine.
The same matching applied to periods you never reconciled, bounded by the returns still open to amendment. SkyAudit is one engagement rather than a cycle, and it ends when the sweep is complete.
Registers, reconciliation output, gap reports and follow-up logs land in your own OneDrive through Mythos. Nothing is retained on our servers once a cycle is delivered.
Every gap the engine flags falls into one of these families, each invisible to a sample, each recoverable once found.
You hold a valid GST invoice, but the airline never reported it in your 2B. Until it appears there, the credit doesn't exist for you, however real the charge was.
The filing exists, against the wrong entity. Common in multi-GSTIN organisations, where a booking maps to one company and the airline reports to another. The credit lands where it can't be used.
Filed, against the right GSTIN, but wrong. Tax amount short, invoice number off, values that don't tie. Small individually; a real number in aggregate.
Airline invoices, TMC statements, booking data and your GST portal records, in whatever formats they arrive, normalised into one working set, attributed to the right entity and GSTIN.
Each invoice reconciled against your GSTR-2B: invoice number, GSTIN, taxable value, tax, field by field, exactly as you saw above, for every record.
Missing filings, wrong entities, mismatched values, flagged, categorised into the three families, and quantified in rupees. Nothing extrapolated from a sample.
Your claimable credit, your gap register, and the working behind every number, auditable, comparable cycle to cycle, ready for your filing and your auditors.
A sample tells you about the tickets you happened to check. A full population tells you about all of them. When credit is lost one invoice at a time, the only reliable way to find it is to look at every invoice, which is exactly what the engine makes possible.
Book a free reconciliation review, we'll run a sample of your travel through the engine and show you what it finds.