Module

DutyGuard

Every duty-free authorisation you hold — advance authorisation, EPCG and DFIA — what is left on it, what you still owe the government, and what it costs if you miss.

Running in production₹30,000 / month

Watch demo

The duty was never paid. The promise that made it free is on a spreadsheet one person keeps.

The running product, filmed as it works — every number on screen was computed live while the camera was rolling. The voice names no number, so a re-recording can never contradict the screen.

What it produces

  • A register of every open authorisation ranked by money at risk — not by date, because a licence expiring next week with nothing on it matters less than one expiring next month with a crore
  • What is left to import on each entitlement line, by quantity and by value, computed from the bills of entry themselves
  • How much of the export obligation is discharged — at the lower of the quantity and the value percentage, never the average and never whichever flatters
  • What you would owe if you stopped today: duty saved × the share undischarged, with interest only where you have set a rate
  • Value addition achieved against what the licence requires, refused rather than invented when nothing has been imported yet
  • Advance authorisation, EPCG and DFIA on one ledger — EPCG measured against its multiple of the duty saved, a discharged DFIA transferable with its premium recorded
  • A debit beyond the entitlement, a unit that does not match the licence, or a bill of entry after the validity, each refused by name with the balance and the shortfall in the sentence
  • Bills of entry and shipping bills read from your own ICEGATE or DGFT access, or from the statement your CHA already sends, and held as proposals against the licence they name — a number that disagrees with the one you typed is reported as a variance, never written over it
  • What the bank actually realised against each shipping bill — the remittance less freight, insurance and commission, at the export date’s rate — so an export that has not been paid for is known months before a discharge application would be refused for it
  • The discharge application assembled from the ledger: the statement of imports, the statement of exports, Appendix 4H, and every deficiency the office would raise, named with the documents it is about. You print it, sign it and file it

A worked example

0310098765 · advance authorisation · 92 days past the obligation period
45 of 100 MT imported · ₹92,74,000 of ₹2,00,00,000 CIF used
obligation 75% done: 390 of 520 KL by quantity, 76.52% by value — the lower of the two
value addition (3,21,38,000 − 1,16,74,000) ÷ 1,16,74,000 = 175.30% against 15% required
→ ₹7,00,440 duty saved × 25% unmet = ₹1,75,110 at risk, plus ₹6,620.60 interest

Illustrative numbers. On your tenant the same page shows yours.

Why it is hard

The part that is not a report.

An exporter importing inputs without paying duty has made a promise: export this much, of this value, by this date. Miss it and the duty saved becomes duty payable, with interest. Almost every Indian exporter runs that promise on a spreadsheet, and the spreadsheet is maintained by one person who is on leave the week the licence expires. This is the same arithmetic as a ledger rather than a memory: what was allowed, what has been used, what was promised, what has been delivered, and what that leaves at risk — with every number showing the documents it came from, so a disputed number can be walked line by line.

Opened by the logistics manager, the finance director and the administrator — what each of them sees first.

Said before you ask

What we don’t do.

SIAARU decides from your records and nothing else. It carries no copy of the world’s data, states no number your systems have not, and acts in nobody’s name. Where your data does not support an answer, it says so by name rather than producing a confident one — which is the whole reason a decision taken on it holds up later.

The ledger and its refusals across all three schemes, documents read in and staged as proposals, realisation against every shipping bill, and the discharge application assembled, validated and produced as a document. SIAARU prepares and never signs or files. It reads what the government already holds about this exporter — through that exporter’s own credentials, entered by them, or through the statement their CHA sends — proposes entries a person accepts one by one, prepares the application, and records the file number and the certificate the operator brings back. It holds no digital signature, by design. It also answers the question before the shortfall: against this tenant’s own bill of materials, never a shipped copy of the SION table, it reads the open order book and the production plan and says whether each authorisation will meet its date, with the arithmetic under every number and the nightly sweep raising the warning months before the period ends. Appendix 4H works the same way: the consumption per unit exported is proposed from that bill of materials with the working beside it, and stays off the form until a named person accepts it — the certificate is a chartered accountant’s to sign, so the number is yours to take rather than ours to derive. An obligation line linked to no material, an order in a currency with no agreed rate, a product with no bill of materials — each is named and left out rather than guessed at. Next: the portal’s own bulk-upload workbook, built to DGFT’s sample file rather than a guessed column order. Nothing is parsed from a PDF until real documents are in hand, because a parser written against an imagined layout fails quietly. Tax rates, duty saved and the interest rate are your own numbers from your own documents: SIAARU is not a duty calculator, and your CHA is still your CHA.

Where this sits

One of 36 modules, on one engine.

DutyGuard reads the same reconciled data as everything else SIAARU runs — connected read-only to your ERP, scored on the way in, measured in SQL. How that engine works is a page of its own. The other 35 modules, each with the state it is really in and the reason where it is not switched on, are on the module list; what this one costs, and what it costs beside the rest, is on the pricing page.

Get started

Bring one month of data. Leave with your own control tower.

A demo runs on your material master, your purchase orders and your stock — not on ours. Thirty minutes, and you see your own exceptions rather than a scripted one.

Ask a question

Book a demo

Thirty minutes, on your own data. Six fields — the rest only helps us prepare.

Not binding. Tell us the size and we will say which one fits.

The demo connects to it, so this shapes the whole session.

Add context, and the demo runs on your problem rather than a scripted one

We reply within one working day.