Platform  /  SkyConnect  · module 05 of 06 · delivery layer
05  ·  SkyConnect  ·  Integrate

Your books
don’t move.
SkyConnect comes to them.

SkyConnect is the integration layer of the TraCarta platform. It pushes reconciled vouchers, structured invoices, and audit-ready records into your existing accounting and ERP systems, and pulls the data TraCarta needs back. Both directions. Scheduled. Audited.

Tally SAP S/4 Oracle Fusion Zoho Books Microsoft Dynamics NetSuite GSTN ICEGATE + custom
The other delivery problem

Reconciled data is worthless
until it’s in your books.

Most finance platforms hand you a report and call it done. The last mile, getting that report into the system where your team actually works, is where the work quietly piles up. SkyConnect exists so that work disappears.

01, The CSV trap

Export, format, import, fix, repeat

The default delivery model is a CSV. Someone downloads it, opens it in Excel, fixes the column order, uploads it to the ERP, fixes what the ERP rejected, posts what’s left. Every cycle. Every entity. Every month-end.

02, Every system speaks differently

Your ERP’s native language is not CSV

Tally wants XML. SAP wants IDocs or BAPI. Oracle wants FBDI. Zoho wants its own JSON shape. A generic export forces your team to do the translation work that should have already been done.

03, The audit hole

CSV breaks the audit chain

Once a CSV leaves TraCarta and enters Excel, the link between the airline invoice, the reconciliation, the journal, and the posted voucher is broken. Auditors ask “how do you know this entry maps to this invoice?”, and the honest answer is “a spreadsheet someone edited.”

What SkyConnect delivers

Data lands where your team works.
Both directions. No CSV in sight.

SkyConnect speaks your stack’s native dialects, on schedules that match your filing cycle, with a complete audit chain from source invoice to posted voucher.

Native push

Your ERP’s own format

Tally XML, SAP IDoc/BAPI, Oracle FBDI, Zoho native API, each ERP gets the voucher format it expects, with the field structure your accountant would have typed by hand.

Native pull

2B, masters, configs

GSTR-2B entries pulled from the GSTN portal on every filing cycle. Vendor masters synced from your ERP. Cost-centre and project codes refreshed as they change. The platform stays current without anyone uploading anything.

Round-trip audit

Every byte, traceable

Each pushed voucher and each pulled record carries a full provenance chain: source, transformation, destination, timestamp, approver. Auditors get a single export with the chain intact.

Supported systems

The stacks we already speak.

Two categories: the accounting and ERP systems where your books live, and the regulatory portals where your tax data flows. Custom systems on request, usually two weeks from sign-off to first sync.

Accounting & ERP
Tally Prime & ERP 9 Direct API
SAP S/4 HANA & ECC IDoc / BAPI
Oracle Fusion Cloud & EBS REST / FBDI
Zoho Books Native API
Microsoft Dynamics 365 F&O OData
NetSuite SuiteTalk
Custom ERP On request
Tax & regulatory
GSTR-2B GSTN portal Auto-pull
GSTR-1 & 3B Filing helpers Auto-pull
e-Way Bill Bi-directional
e-Invoice IRP / NIC Bi-directional
ICEGATE Customs Beta
DGFT On request
Custom regulator On request
Sync rhythms

The pace you need.
For the system that needs it.

Not every connection should move at the same speed. SkyConnect supports three rhythms. Pick what fits each system, change it any time.

Rhythm 01 Real-time

Event-driven push the moment a journal is approved. Latency in seconds. Best for tightly-coupled accounting workflows where the books need to reflect TraCarta’s state continuously.

e.g. SAP S/4 · Tally Prime · Zoho Books
Rhythm 02 Scheduled

Cycle-aligned sweeps, daily, weekly, or aligned to filing dates. Best for systems where batch posting suits your workflow, or where the destination has its own approval cadence.

e.g. Oracle EBS · Custom ERP · ICEGATE
Rhythm 03 On-demand

Manual trigger from SkyBoard or via webhook. Best for sensitive postings your team wants to gate explicitly, or for one-time backfills and migrations.

e.g. month-end runs · year-end true-ups · one-off backfills
Security posture

Least-privilege. End-to-end.

The principle: SkyConnect should have the minimum access needed to do its job, on encrypted paths, with a complete record of what crossed each boundary.

Scopes

Read-only where possible

SkyConnect requests the narrowest scope each system supports. Master pulls run on read-only credentials. Voucher push uses dedicated service accounts your IT team can disable at any moment.

Transit

Encrypted at every hop

Every connection, to your ERP, to GSTN, between modules, uses encryption your security team would expect. No data moves over unsecured channels.

Audit

Every sync logged with full provenance

Each push and pull records source, destination, byte count, timestamp, and the operator or system that triggered it. Exportable for audit, queryable by your team, immutable once written.

Integration questions

What your IT team will ask.

Does this require us to open inbound firewall holes?

No. SkyConnect initiates every connection outbound from our infrastructure to your systems, or from your systems to ours, when you prefer. You don’t open inbound ports or expose your ERP to the internet.

What about on-premise SAP or Tally?

Fully supported. SkyConnect runs a small relay agent inside your network for on-prem systems. It opens outbound TLS connections only, no inbound rules required, and your IT team controls the credentials.

Our ERP is custom. Can SkyConnect still integrate?

Almost always. If your system has any way to accept structured data, an API, an inbox, a watched folder, a database table, we can integrate. Custom integrations typically take two weeks from sign-off to first live sync.

What happens if a destination is down?

SkyConnect queues. Vouchers wait in our buffer, your inbound pulls hold position, and we retry with exponential backoff. When the destination recovers, the queue drains in order. Nothing is lost; nothing is double-posted.

Can we disable a connection without affecting others?

Yes. Every connection is independent. Disable Tally for a maintenance window, keep SAP and GSTR-2B flowing. Resume Tally when you’re ready. The queue catches up automatically.

How does SkyConnect handle our chart of accounts changes?

SkyConnect pulls your COA from the ERP on a configurable cadence. When you add a new GL or cost-centre, SkyIQ’s mapping picks it up automatically. No re-configuration on our side, no re-deployment.

Connect one system

Pick one system. See what flows.

We’ll connect SkyConnect to one of your systems, usually Tally, SAP, or your GSTN portal, in two weeks. You’ll see what data moves, on what schedule, with what audit trail. If it doesn’t fit, walk away.

Start a SkyConnect pilot