Desktop App User Guide

Step-by-step guide to generate FATCA Model 1, FATCA Model 2 (IRS IDES), and CRS v3.0 XML files — entirely on your own machine.

What is the Novus Compliance Desktop App?

The Novus Compliance Desktop App is a locally installed application that generates FATCA and CRS XML files directly on your machine. No client financial data is uploaded to our servers, stored in any database, or transmitted anywhere. Your data stays with you at all times.

It supports three reporting modules from a single interface:

  • FATCA Model 1 — Local Authority Reporting (India, UK, Luxembourg, Canada, Ireland)
  • FATCA Model 2 — IRS IDES Submission (Switzerland, Japan, Hong Kong)
  • CRS v3.0 — OECD Common Reporting Standard (CRS 2.0 / CRS 3.0 schema)
Privacy by design: The Desktop App runs a proprietary in-house AI validation engine locally on your machine. It does not connect to the internet, does not call any external AI service (OpenAI, Google, Anthropic), and does not transmit your data anywhere.

Before you begin

System

Windows 10 or later. macOS support available on request.

Credentials

Username and password provided by your Novus Compliance administrator.

License Key

Issued at sign-up and entered in the Settings tab after first login.

Excel Template

Download the latest FATCA or CRS template from our Download Templates page.

Step 1

Login to the Desktop App

Launch the Novus Compliance Desktop App. Enter the username and password provided by your administrator, then click Secure Login.

On first login, you'll be prompted to change your password and enter your license key in the Settings tab. See Step 9 for details.

First-time login: If your administrator hasn't yet issued your license key, contact them before proceeding. The app requires a valid license key to enable XML generation.
Novus Compliance Desktop App login screen with username and password fields
Click to enlarge — Login screen
Step 2

Choose your reporting module

After login, the left sidebar shows the four tabs of the app. Select the module that matches your reporting obligation:

FATCA Model 1 (Local)
FATCA Model 2 (IRS IDES)
CRS (v3.0)
Settings
Module Use when Output
FATCA Model 1 You report to a local tax authority (India, UK, Luxembourg, Canada, Ireland) FATCA XML v2.0.1
FATCA Model 2 You file directly with the IRS via IDES (Switzerland, Japan, Hong Kong) Raw XML + AES-256 encrypted IDES package
CRS v3.0 You report under the OECD Common Reporting Standard CRS XML Schema v3.0
Not sure which model applies? Most jurisdictions (India, UK, Canada, Luxembourg, Ireland) use FATCA Model 1. Switzerland, Japan, and Hong Kong use FATCA Model 2. See our FATCA Reporting Guide for the full breakdown.
Step 3

Configure the reporting entity

Before loading any data, you must configure the Reporting Entity fields for your chosen module. The app will display different fields depending on which module you're in.

FATCA Model 1 — Local Authority Reporting

Enter your Reporting GIIN (mandatory) and select your Reporting Jurisdiction from the dropdown (e.g., "US — United States — IRS IDES" or "IN — India — CBDT"). The app shows a help hint confirming which XML element the GIIN populates.

FATCA Model 1 configuration screen with Reporting GIIN, Reporting Jurisdiction dropdown, and Generate Model 1 XML button
Click to enlarge — FATCA Model 1 configuration

FATCA Model 2 — IRS IDES Submission

FATCA Model 2 requires cryptographic credentials for the encrypted IDES package. Enter:

  • Reporting GIIN — your institution's GIIN
  • Private Cert (.p12) — click Browse .p12 to select your institution's private key file
  • Cert Passphrase — the password protecting the .p12 file
  • IRS Cert (.cer) — click Browse .cer to select the IRS public certificate
Important: The .p12 certificate and passphrase are used to sign and encrypt your IDES package with AES-256. Without them, the app cannot generate a valid submission file. Contact your administrator if you don't have these credentials.
FATCA Model 2 configuration screen with Reporting GIIN, Private Cert .p12, Cert Passphrase, and IRS Cert .cer fields
Click to enlarge — FATCA Model 2 configuration

CRS v3.0 — Data Preparation

For CRS, enter your Reporting FI TIN — the Tax Identification Number of the reporting financial institution. This populates the CRS XML header.

CRS v3.0 Data Preparation screen with Reporting FI TIN, Load CRS Excel Template, Run AI Validation Pipeline, and Generate CRS v3.0 XML buttons
Click to enlarge — CRS v3.0 configuration
Step 4

Load your Excel template

Download the correct template for your reporting module from the Download Templates page, fill in your account holder data, and save it as an .xlsx file.

Then, in the app:

  1. Click Load Excel Template (or Load CRS Excel Template in the CRS module)
  2. Browse to your completed .xlsx file and select it
  3. The app will confirm the file name is loaded (replacing "No file selected")
Do not modify the template structure. Do NOT remove, rename, reorder, or add columns/headers. The app relies on the exact column names to map your data to the correct XML fields.
Step 5

Run the AI validation pipeline

Click Run AI Validation Pipeline (labeled Run Validation Pipeline in the FATCA Model 1 module). The app validates your data across multiple layers — all locally on your machine:

  • Input validation — data format, completeness, required fields
  • Business rules — FATCA/CRS rules such as "if balance > $50,000, TIN is mandatory"
  • AI-assisted anomaly detection — powered by our in-house AI engine to spot data-quality issues
  • Schema (XSD) validation — against the official FATCA v2.0.1 or CRS v3.0 schema

Results appear in the Validation Dashboard below, showing each row with its Account Type, Name, Status, and any issue Details.

Runs entirely on your machine. The AI validation engine is not on the internet. No data is transmitted to any server — ours or any third party.
Step 6

Fix validation errors

If the validation dashboard shows errors, each row is flagged with a specific Status and a Details message explaining what's wrong. Common issues include:

  • Missing or invalid TIN for a reportable account
  • Invalid country code (must be ISO 3166-1 alpha-2)
  • Malformed GIIN (must follow the XXXXXX.XXXXX.XX.XXX format)
  • Balance formatting (must use 1000.00, no commas)
  • Missing controlling person for a Passive NFE

Correct the issues in your Excel file, save it, and click Load Excel Template again to re-import. Then re-run the validation.

Tip: Fix all errors in a single pass — the validation dashboard shows every issue at once. There's no need to re-run the pipeline after fixing each individual row.
Step 7

Generate XML / IDES package

Once the validation dashboard shows all rows as passed, click the generate button for your module:

Module Button Output
FATCA Model 1 Generate Model 1 XML FATCA XML v2.0.1 file, ready for upload to your local tax authority portal
FATCA Model 2 Generate Raw XML or Generate IDES Package Raw XML (for verification) or AES-256 signed and encrypted .zip for IDES
CRS v3.0 Generate CRS v3.0 XML CRS XML Schema v3.0 file, ready for upload to your local authority portal
FATCA Model 2 users: Ensure your .p12 certificate and passphrase are correct before generating the IDES package. The output .zip will be signed and encrypted using those credentials — if they're wrong, the IRS will reject the submission.
Step 8

Upload to tax authority portal

Take your generated file (XML or IDES .zip) and upload it to the relevant tax authority portal:

Reporting Type Where to upload
FATCA Model 1 (India) Income Tax Department Insight Portal (Form 61B)
FATCA Model 1 (UK) HMRC AEOI online service
FATCA Model 1 (Luxembourg) ACD portal (SOFIE / FUNDSQUARE)
FATCA Model 2 IRS IDES Gateway
CRS (India) Income Tax Department Insight Portal (Form 61B, Report Type 02)
CRS (Other) Your local tax authority's CRS portal

See our jurisdiction-specific guides for detailed upload instructions: India, UK, Luxembourg, Ireland, Canada, Switzerland.

Step 9

Manage settings & license

The Settings tab handles two things:

Change Password

Enter your current password, then your new password twice, and click Update Password. We recommend changing your password if you've shared your workstation or if you suspect your credentials may have been compromised.

Update License Key

Paste your new license key and click Apply New License. The app validates the key and unlocks any additional modules (e.g., upgrading from a single-module to a multi-module license).

Application Settings screen with Change Password and Update License Key sections
Click to enlarge — Settings tab
Step 10

Security & privacy

The Desktop App is designed for maximum data privacy. Here's what happens to your data:

Aspect Desktop App behavior
Data storage None. Your data is processed in memory and discarded when the XML is generated.
Internet connection Not required for XML generation. The app runs offline.
AI validation Runs locally on your machine — no data sent to any server.
Third-party services None. No connection to OpenAI, Google, Anthropic, or any external AI provider.
Training data Your data is never used to train or improve any AI model.
Full data residency: Because the Desktop App processes everything locally, your client financial data never leaves your infrastructure. This is ideal for institutions with strict data residency, privacy, or regulatory requirements.

Read more in our Privacy Policy and Technology & Security pages.

FAQs

Frequently asked questions

Is the Desktop App the same as the Cloud Platform?

No. The Cloud Platform is a web-based application hosted on our secure servers. The Desktop App is a locally installed application that runs entirely on your machine. Both generate the same schema-valid XML — but the Desktop App never transmits your data.

Can I use the Desktop App offline?

Yes. XML generation, AI validation, and CRS/FATCA processing all run locally. You only need internet access to download the app, activate your license, and upload the final XML to the tax authority portal.

What certificates do I need for FATCA Model 2?

You need (1) your institution's Private Certificate (.p12) with its passphrase, and (2) the IRS Public Certificate (.cer). Both are available from the IRS FATCA Registration System. If you don't have these, contact your administrator.

Does the AI validation send my data anywhere?

No. The AI validation engine is bundled with the Desktop App and runs entirely on your machine. It is a proprietary in-house system — not a wrapper around any external AI service. Your data is never sent to OpenAI, Google, Anthropic, or any other provider.

What if I have multiple reporting entities?

You can process them one at a time — load the template, run validation, generate XML, then repeat for the next entity. Each run is independent and does not affect previous outputs.

What happens if validation fails?

The Validation Dashboard shows every error with its row number and a description. Fix the issues in your Excel file, reload it, and re-run the pipeline. Only rows marked as "valid" will be included in the generated XML — so no invalid data can reach the tax authority.

How do I get a license key?

License keys are issued when you sign up. Existing customers can request a new key from their account manager or by contacting support.

Can the app handle both FATCA and CRS in one session?

Yes. Use the sidebar to switch between modules. Each module maintains its own settings (GIIN, certificates, jurisdiction) so you don't need to re-enter them.

Does the Desktop App support CRS 2.0 / Schema v3.0?

Yes. The CRS v3.0 module generates XML against the OECD CRS XML Schema v3.0 — including the new crypto, self-certification, and controlling person role fields. See our CRS Reporting Guide for details on what changed.

What if I need to correct a filing?

The Desktop App supports corrections using the standard DocRefID / CorrDocRefID workflow. Use our Correction Filing Checklist to verify every step before submission.

Need help getting started?

Our team can walk you through the Desktop App setup, certificate configuration, and first filing.

Contact Support