SkySuite is the TraCarta platform. The engine retrieves, reconciles, and journalizes. The unglamorous work that makes the numbers true. The delivery layer lands it in the portal your team uses and the books your accountant trusts. The partner layer lets TMCs carry the whole thing under their own brand. Each module is its own page; the suite is the composition.
Every competitor sells one big “GST recovery platform” and quietly hopes nobody notices that the work has at least three different shapes underneath. We didn’t want to hide that. SkySuite is six modules because the work is genuinely six jobs, and pretending otherwise is what makes most platforms in this category feel hollow.
Pulling an invoice from an airline portal is portal-automation work. Triangulating it against GSTR-2B and your booking record is forensic-accounting work. Turning that into journal entries your ERP will accept is integration work. They look adjacent on a slide; they are completely different disciplines underneath. Different modules let each be excellent at the one thing it does.
A reconciled record sitting in a database is worth nothing. SkyBoard organizes the work for your finance team; SkyConnect pushes it into the systems where decisions actually happen. These aren’t features of the engine, they’re a separate layer with their own commitments to clarity and uptime.
A white-label that’s a feature flag inside a product can be revoked. A white-label that’s its own module is a contract: with non-compete clauses, with separate SLAs, with separate billing. TMCs deserve to know which one they’re buying. We made it obvious by giving it its own page, its own pricing footprint, and its own layer in the airspace.
Each layer answers a different question. The engine answers is the number right. Delivery answers can our team act on it. Partner answers can we sell it.
The engine is where the unglamorous work happens, the work that everything else rests on. Coverage and accuracy are the promises. If the engine is wrong, every downstream output is wrong, and no portal polish saves you. Three modules, in flow.
Crosses your firewall, logs into every Indian airline GST portal you book on, locates each ticket, pulls the invoice. On schedule, in bulk, every cycle, every airline. The only TraCarta module that touches the outside world.
Open SkyDoxThree records: airline invoice, GSTR-2B, your booking. One verdict per case, drawn from eight (Recover / Hold / Pursue / Reclaim / Adjust / Refile / Forfeit / Dispute). The intellectual heart of SkySuite.
Open SkyLedgerReconciled record in, journal entry out, debits, credits, GL codes, narrations your accounting system actually accepts. SkyIQ suggests; a human reviews and posts. The bridge from engine to your books.
Open SkyIQA correct number that nobody can act on is the same as a wrong number. Delivery is the layer that lands the engine’s work where decisions actually happen, on your team’s screens, in your accounting system, on your filing cadence. Clarity and integration are the promises.
Where finance ops, the tax associate, and the auditor each find exactly what they need on day one. Organized around what to do next, not what columns exist. Deliberately not live. This layer sells clarity, not motion.
Open SkyBoardYour books don’t move; SkyConnect comes to them. Pushes journal vouchers into Tally / SAP / Oracle / Zoho, pulls GSTR-2B and masters back. Both directions, scheduled, audited. No human re-keying.
Open SkyConnectListed in the engine too, because that’s where it computes, but it shows up in delivery as well, because that’s where you experience it: the human-readable draft journal entry, queued for review and posting in SkyBoard.
Open SkyIQThe partner layer is what most platforms hide behind a feature flag. We put it in its own layer because it changes the contract: non-compete, brand invisibility, separate billing. SkyLink is the one TraCarta product a TMC ever names, under their own brand, with the engine working invisibly behind it. Internally we call the platform SkySuite; externally, a TMC’s clients see only the TMC’s brand.
Four axes a serious buyer would evaluate. Three layers, each making a different promise on each axis. Anywhere a cell is honest about a limit, we wrote it that way, not the marketing version.
Six pages is a lot to read in one sitting. If you’re on this site for a specific reason, here’s the page that probably matters most to you.
Start with SkyLedger. It’s the intellectual heart of the engine, the verdict console, the three-record comparison, the eight-verdict catalog. If the audit-trail discipline doesn’t hold up there, nothing downstream matters.
Open SkyLedger first TMC leadership / MDStart with SkyLink. Brand-skin mockup, ownership matrix that answers the hard partnership questions, worked unit economics. The framing for the TMC audience lives on the solutions page; the mechanism lives here.
Open SkyLink first CTO / IT / integrationsStart with SkyConnect. The live topology, the bi-directional sync model, the supported-systems grid (Tally, SAP, Oracle, Zoho, GSTR-2B). That page tells you whether SkySuite fits your stack in three minutes.
Open SkyConnect firstModule-specific questions live on each module’s page. Below are the ones that come up about SkySuite as a whole: the composition, the commitments, and the boundaries.
No. The engine is the only block we treat as inseparable, SkyDox, SkyLedger, and SkyIQ run as one. Delivery and partner are à la carte. The most common starting shape is engine + SkyBoard (everything reconciled, nothing pushed yet); SkyConnect comes on later when ERP integration is scoped. SkyLink only applies if you’re a TMC.
Yes, that’s the recon audit. One filing cycle, your data, the full engine, no commitment past delivery. The audit doesn’t use SkyBoard or SkyConnect; you receive a report. If the math works, that’s the conversation about which delivery modules to turn on.
SkySuite ends at the journal-entry post and the GSTR filing. We don’t replace your ERP, we don’t replace your CA, we don’t file your returns. SkyIQ drafts entries; your team reviews and posts them; your CA reviews the books; your filing process continues as it does today. The handoff is deliberate.
Because it sits at the boundary. Computationally it’s an engine module, it derives the journal entry from the reconciled record, alongside SkyLedger. Experientially it’s a delivery module, the draft entry shows up in SkyBoard’s review queue, where your team approves and posts. Listing it in both layers is more honest than picking one.
Inside your tenant, yes, SkyLedger’s reconciliation thresholds and SkyIQ’s GL mappings improve with your historical patterns. Across tenants, no, we don’t pool data, don’t train shared models on your records, don’t use one customer’s history to inform another’s verdicts. The verdict logic is the same for everyone; the calibration is yours.
SkySuite at six is the airline-GST shape, fully covered. Adjacent categories, hotel GST, vendor-services GST, expense GST, are real adjacencies we’ve mapped but not committed to. Any new module would get its own page, its own pricing, and its own layer. The suite grows by adding doors, not by overloading existing ones.
The recon audit is the cheapest, fastest, most honest way to see whether SkySuite earns its place in your stack. One cycle of your airline invoices, your booking exports, and your GSTR-2B. The engine returns the eight-verdict report and the financial position. No SkyBoard, no SkyConnect, no integration, just the math, on your numbers. If the recoverable column doesn’t make the case, walk away.
Run one cycle →