SEZComply turns the work before the filing into a persistent cloud compliance system — bringing master data, permanent registers, classification, reconciliation, MPR, SERF, DSPF, APR, documents and filing history into one connected workspace.
Built for the operational reality of GIFT IFSC units. Independent software — not affiliated with Government, IFSCA, SEZ Online or NDML.
The ten-minute filing is not where most of the work sits. The work is getting the data ready: collecting it, classifying it, reconciling it, proving it and retaining it — every month, for every unit.
Invoice details, FIRC/realisation status, FCY expenses, employee changes, ID-card status, investments and supporting documents come from different people and systems.
Transactions have to be mapped into the right reporting categories and service lines, including export categories and the information that ultimately feeds recurring MPR/SERF/DSPF work.
Portal-populated information still needs to be checked against what actually happened. Duplicate invoices, missing identifiers, unrealised proceeds or wrong classifications need to be caught before filing.
When a DC office, auditor, investor or internal reviewer asks for the history, firms often reconstruct it from Excel, email and PDF acknowledgements. SEZComply keeps the underlying record connected.
Cumulative registers instead of monthly reconstruction.
Checks before figures become filing outputs.
One control layer across units and funds.
The compliance record stays with the organisation.
SEZComply creates a persistent compliance layer for each SEZ unit. Instead of rebuilding the month, the system carries forward the unit's standing data and uses transaction registers to assemble the reporting outputs.
LOA, lease, BLUT/LUT, IEC, GSTIN, RCMC, authorised operations, addresses, directors and other unit facts.
Maintain cumulative registers for invoices, exports, expenses, imports, investments, employees, ID cards and other recurring data.
Carry forward standing records, import structured data, reconcile transactions and identify exceptions before reporting.
Generate MPR, SERF and APR working outputs, complete maker-checker-approver workflow and retain filing acknowledgements.
The product is a unit-level compliance operating system. The recurring reports are outputs of the underlying records — not isolated forms. Twenty-two entries, grouped the way your own compliance file is.
The controlled profile each register and report draws from.
Manage organisation-level information and separate SEZ units with their own master data, registers and reporting configuration.
LOA, lease, BLUT/LUT, IEC, GSTIN, RCMC, authorised operations, addresses, directors and unit facts in one controlled profile.
Versioned configuration for which reporting sections are live for a unit in a particular month, allowing future requirements to slot into the system.
Cumulative by design — captured once, carried forward every month.
Category-wise export records across Outside India, Other IFSC/SEZ and DTA, with cumulative history.
Maintain invoice-level service export records that form the source data for SERF preparation and reconciliation.
Track foreign-currency expenses with structured transaction records and reporting-ready totals.
Maintain imports of services and goods with transaction-level records and cumulative history.
Maintain investment receipt records separately from investment as-at information where required by the reporting model.
Direct and indirect employment, join/exit dates, status and gender data, with month-to-month carry-forward.
Link employee records to SEZ ID cards, card number, validity, issuance and status.
Maintain the structured inputs needed to prepare the DSPF working paper and reconcile zero-rated supply information.
Maintain capital-goods procurement records for cumulative reporting and supporting documentation.
Where registers become filing-ready outputs.
Compute reporting figures from underlying registers, distinguish auto-populated/reconciled figures from user-entered fields and provide click-to-copy outputs.
Build SERF from invoice data, pull unit master data, support Nil declaration and validate duplicates, missing identifiers and unrealised proceeds before filing.
Aggregate cumulative data and maintain the records needed for annual performance and NFE review.
Start the next month from the previous month's standing employees, investments and ID-card records and record only changes.
Bring structured data from CSV or spreadsheet workflows, map columns, preview records and bulk-create transactions.
Identify duplicate invoices, missing master identifiers, incomplete records and reporting inconsistencies before output preparation.
Accountability around the record, not just the number.
Track recurring compliance activities, filing status and document expiries across units. Due-date reminders are configurable and should be verified against applicable instructions.
Keep supporting documents, filing records, acknowledgements and compliance evidence associated with the unit.
Move a filing through Draft, Prepared, Checked, Approved and Filed stages, with acknowledgement capture.
Preserve the working history around records and filings and assemble an organised compliance record for review.
The monthly filing should be an output of the system, not the system itself.
The platform can retain the structured master data that otherwise gets copied into multiple monthly working files.
Illustrative populated profile using supplied unit data. Sensitive operational data should be protected by the production application's access controls.
The product is deliberately positioned as the compliance data and preparation layer around the portal — not as a replacement for the portal itself.
A reporting month has a lifecycle. The workspace should open, carry forward standing information, collect the period's transactions and move into preparation only when the period is ready.
A month with no eligible service exports is not an empty register. SEZComply records the Nil state explicitly and preserves the declaration and filing record.
Each filing can retain its own request/acknowledgement ID and maker identity, rather than treating the unit as having one generic compliance reference.
Use the unit's structured master data and registers to assemble the monthly working figures, with clear distinction between system-derived/reconciled values and fields requiring user entry.
Build invoice-level service export reporting from the Invoice/FIRC Register, with a Nil declaration path and pre-filing validation checks.
Use cumulative records instead of rebuilding the year from scattered monthly files, with investment, export, NFEE and employment information available for aggregation.
SEZ compliance is not only about producing a number. It is about knowing where the number came from and what happened before the filing was completed.
Permanent registers retain cumulative transaction history rather than recreating isolated monthly sheets.
Surface incomplete or inconsistent records before they reach the reporting workflow.
Separate preparation, checking, approval and filing stages for controlled workflows.
Keep acknowledgement information and supporting compliance records connected to the filing cycle.
No long commitment for the trial period. Assisted filing is optional.
SEZComply is a cloud compliance platform for SEZ units. It keeps unit master data and permanent compliance registers together and uses that information to support recurring MPR, SERF, DSPF and annual compliance workflows.
Monthly files recreate the same standing information repeatedly. SEZComply is designed around cumulative registers and month roll-forward, so the next period starts from the existing record and focuses on what changed.
No. SEZComply is a preparation, reconciliation, workflow and record-keeping layer. It does not represent itself as the SEZ Online portal and does not claim to replace government filing infrastructure.
The platform is designed to prepare and validate filing-ready information and preserve the filing workflow. Actual submission remains subject to the applicable portal process and the user's authorised filing action unless a separately supported integration is introduced.
Yes. The SERF workspace includes a Nil declaration workflow so a unit can record and preserve the appropriate filing state for a month where there are no reportable service-export transactions.
Standing information is carried forward. The monthly workflow is intended to show the previous position and ask the user to confirm or record changes rather than recreate the entire register.
The planned workflow supports structured CSV and spreadsheet-based import so transaction data can be mapped, previewed and bulk-added rather than manually re-keyed line by line.
No. SEZComply is an independent software product. Government portals, authorities and organisations referenced in the platform remain separate systems and institutions.
Move from scattered spreadsheets and monthly reconstruction to a persistent compliance system for your SEZ unit.