Posting is the slowest mile
A junior accountant booking 5,000 airline vouchers a quarter spends two to three full days on it. The work is mechanical, but it’s also high-risk. One wrong GL and the credit lands in the wrong place.
03 · SkyIQ · Journalize
Reconciled
isn’t booked.
SkyIQ takes the reconciled output from SkyLedger and drafts the journal entries your accounting system actually wants: debits, credits, GL codes, narrations, cost centers. Your controller reviews. Your team posts. The most painful part of the cycle finishes itself.
Tally
SAP
Oracle Fusion
Zoho Books
Microsoft Dynamics
NetSuite
+ custom
Recon doesn’t end the work.
Posting does.
A clean reconciliation report tells you what should be in your books. It doesn’t put it there. That last step, reading each line, deciding the GL, typing the voucher, is where finance teams quietly lose three days a month.
Manual entry is where audits find things
GL miscoding, swapped CGST/IGST, wrong cost center, missing narration. These are the entries auditors flag, not because the recon was wrong, but because the booking that followed introduced new errors.
Books close late because of this step
Most finance teams know they could close faster. The bottleneck is usually voucher entry, not reconciliation. Removing the typing step accelerates month-end by days, not hours.
Posting-ready journals.
Reviewed by your team. Posted by your team.
SkyIQ never writes to your books directly. It drafts the entries, attaches them to source invoices, and waits for your controller to approve. The work is done; the authority stays where it should.
Every entry, fully formed
Debit and credit lines, GL codes, cost centers, narrations, tax codes, reference numbers. The voucher your accountant would have typed — pre-typed.
Your chart of accounts, not ours
We learn your COA during onboarding. Your GL codes, your cost-center conventions, your narration style. The entries SkyIQ drafts look like the entries your team already books.
Every line traces home
Every drafted entry links to its source invoice, source PNR, and the SkyLedger recon that produced it. Reverse a posting, and the chain is intact. Ready for the auditor.
From recon field to GL code, by configuration.
SkyIQ’s mapping is per-client. The table below is a sample, your actual mapping uses your GL codes, your cost-center scheme, and your narration conventions. Configured during onboarding, adjustable on the fly.
Recon field
GL account
Notes
Travel expense (base fare)
→
5410.001
Split by cost-center
Input GST, CGST
→
1640.001
Recoverable
Input GST, SGST
→
1641.001
Recoverable
Input GST, IGST
→
1642.001
Inter-state & international
Airline payable
→
2110.<AIRLINE>
Per-airline sub-ledger
Credit note adjustment
→
5410.CN
Reverses original line
Cost center
→
TRV-<CITY>
From booking metadata
Narration
→
PNR / Doc no / Route
Templated, configurable
SkyIQ drafts. You review. You post.
We’ve built SkyIQ around a simple principle: no automated system should touch your books without a human signing off. The four-step flow keeps the work fast and the authority clear.
STEP 01
Draft
SkyIQ derives the journal entry from the reconciled invoice and your COA mapping. Linked to source.
SkyIQ
STEP 02
Review
Your controller sees the draft alongside the source invoice. Edit any line, override the GL, adjust the narration.
Your controller
STEP 03
Approve
Single click approval per entry, or batch-approve a filtered set. Approval is logged with user, timestamp, and any edits made.
Your controller
STEP 04
Post
Approved entries flow into your accounting system via SkyConnect, or export as a voucher file your team uploads.
SkyConnect
Wherever your books live, SkyIQ speaks the dialect.
Approved entries are formatted for your accounting system natively. No CSV gymnastics, no manual mapping, no “export and import” dance, just the voucher format your ERP expects, ready to consume.
Direct API
Tally
TallyPrime and Tally.ERP 9. XML push via SkyConnect.
Direct API
SAP
S/4 HANA and ECC. IDoc or BAPI, configurable per landscape.
Direct API
Oracle Fusion
Fusion Cloud GL and EBS. REST or FBDI loader.
Direct API
Zoho Books
Native journal API. Fastest setup, usually same-day.
Export
Custom ERP
Excel, CSV, or your ERP’s native voucher schema.
Trust & audit
Built for the people who hate surprises.
Controllers don’t trust automation that touches the journal. We built SkyIQ around that. Every entry is traceable, reviewable, and reversible.
Traceable
Every line links to its source
Each draft entry carries a reference to its source invoice (PDF), its reconciliation result (SkyLedger), and the COA rule that produced it. Click any GL line, see exactly why it was suggested.
Reviewable
Nothing posts without approval
SkyIQ doesn’t auto-post. Every entry waits for human review. Bulk-approve when confident; line-by-line when not. The choice is yours, every cycle.
Reversible
Full audit log, exportable
Every approval, edit, override, and post is logged with user and timestamp. Reverse a journal, the reversal links back to the original. Auditors get a single export with the whole chain intact.
What your finance team will ask.
Does SkyIQ post entries automatically?
No. SkyIQ always drafts. Your controller reviews and approves before anything flows to your ERP. We won’t touch your books without a human in the loop, even if you ask us to. The closest we get is batch-approve workflows, where the controller approves a filtered set with one click.
What if our chart of accounts is non-standard?
Every COA we’ve seen has been non-standard in some way. That’s the norm, not the exception. During onboarding we map your specific GLs, cost-center conventions, narration templates, and any organisation-specific dimensions. Your mapping is yours.
How do credit notes and debit notes work?
Each is handled as its own entry type with its own derivation rule. Credit notes reverse the original posting (with full trace), debit notes adjust upward. The reversal isn’t a manual offset, it’s a derived entry SkyIQ generates the moment the credit note arrives in SkyDox.
What about TDS, RCM, foreign-currency travel?
All handled. Reverse charge entries for unregistered foreign carriers, TDS where applicable, FX conversion at the invoice date rate, each as a configurable rule in your COA mapping. International travel is supported alongside domestic.
Does it handle ISD (input service distribution)?
Yes. ISD-registered organisations can route input credit through an ISD entity with proportional distribution to recipient units. The split is configured in your COA mapping, SkyIQ generates the distribution journal alongside the invoice posting.
Can we override a suggestion?
Always. Every drafted entry is editable before approval. Overrides are logged with user, timestamp, and reason, both for audit and to refine the COA rules over time. Patterns of override become improvements to your mapping.
See it on your books
Send us last quarter’s recon.
Send us last quarter’s recon.
We’ll send back the journals you would have booked.
One quarter of your reconciled airline data. SkyIQ drafts the journal entries against your chart of accounts. Your controller compares to what your team actually posted. The delta is what you’ll save every cycle going forward.
Start a SkyIQ audit →