Fund Subscription Data Synchronization
1. Purpose
Enable customers to automatically replicate Anduin’s source-of-truth data tables into their own Snowflake data warehouse, which can serve as either a backup data source or a centralized hub for dispatching data to various downstream systems.
2. Key Benefits & Features
- Automated data sync between Anduin and Snowflake
- Preserve Snowflake as the customer’s central data hub, with no fragmented data movement
- Comprehensive schema coverage with full relational context, including:
- Fund
- Associated fund close
- Associated subscription and its data, from the online form and from OCR data extraction
- Associated supporting documents
- Control over what syncs and when: choose the data scope, the export method, and the trigger statuses
3. Target Personas
- Any FundSub customers who use Snowflake as their data warehouse
- Especially beneficial for firms with complex and high volume data
4. Data Tables
The integration creates 4 tables in the selected Snowflake schema.
| Table | One row per | Key |
|---|---|---|
anduin_fundsub_integration_funds | Fund | id |
anduin_fundsub_integration_closes | Close | id |
anduin_fundsub_integration_order_standard | Order and data source | id (the order ID) and data_source |
anduin_fundsub_integration_supporting_doc | Supporting document | id (the document ID) |
- Order table: The
data_sourcecolumn issmartformorocr. An order can have one row for each, so join onidto combine them. - IDM columns: The
ie_idandclient_idcolumns are filled when the fund is linked to the customer's IDM instance. Otherwise they are empty. - Supporting document table: The
idis the OCR file ID, or the online supporting form’s submission ID.
5. Prerequisites
5.1 Third party app requirements
- Authentication: Only OAuth and Key Pair authentication methods are currently supported. Customers should be aware of which method they plan to use.
- Credentials: Customers need to provide valid Snowflake credentials. Required parameters vary by authentication type.
- Permission and role: To successfully run the integration, certain permissions need to be granted in Snowflake
- Anduin Table Usage: This integration will create and populate data tables in the customer’s Snowflake environment. Modifying these tables directly is not recommended, as it may break compatibility with automated syncing.
5.2 Anduin app requirements
- Fund access - the user must either:
- Have admin access to their intended funds, or
- Know a team member with admin access who can grant the necessary permissions during setup
- Data scope: Decide which Anduin data to sync. Each option combines a source with a document type:
- Source: Smartform is data entered in the online form. OCR is data extracted from uploaded documents.
- Document type: Subscription or Supporting
- The four options are Smartform Subscription Documents, Smartform Supporting Documents, OCR Subscription Documents, and OCR Supporting Documents. Multiple options can be selected.
- Export method: Decide how the data is exported. One export method applies to the whole integration instance.
- Anduin Default Template (ASA): Universal standard data points used across all customers. Make sure that all funds are mapped with asa.
- Customer Standard Template (CSA): Anduin-defined standard data points per organization.
- A named CSA template (for example, Full CSA Fields Template): A reusable template that must exist on every selected fund. A fund without it exports nothing.
- OCR data (only when an OCR option is selected): OCR data extraction must be set up on each selected fund. Contact your Implementation Manager.
Each export method supports only some data scope options. An option that the chosen method does not support is skipped, and nothing is written for it.
| Export method | Smartform Subscription Documents | Smartform Supporting Documents | OCR Subscription Documents | OCR Supporting Documents |
|---|---|---|---|---|
| Anduin Default Template (ASA) | Yes | Yes | No | No |
| Customer Standard Template (CSA) | Yes | No | No | No |
| A named CSA template | Yes | Yes | Yes | Yes |
To export all four data scope options, choose a named CSA template. To use different export methods for different data scope options, set up a separate integration instance for each method.
6. Pre-Setup Checklist
| Task | Owner | Note | Anduin guide |
|---|---|---|---|
| Snowflake Oauth credentials | Customer | Consulted by Anduin | https://developers.anduintransact.com/docs/prepare-snowflake-credentials#oauth-method |
| Snowflake Key Pair credentials | Customer | Consulted by Anduin | https://developers.anduintransact.com/docs/prepare-snowflake-credentials#key-pair-authentication-method |
| Snowflake permission and role | Customer | Consulted by Anduin | https://developers.anduintransact.com/docs/permission-and-role |
| Snowflake best practice | Customer | Consulted by Anduin | This integration will create and populate data tables in the customer’s Snowflake environment. Modifying these tables directly is not recommended, as it may break compatibility with automated syncing. |
| Fund permission | Customer | Consulted by Anduin | |
| Data scope | Customer | Consulted by Anduin | Which of the four data scope options to sync |
| Export method and template | Customer | Consulted by Anduin | ASA, Customer Standard Template (CSA), or a named CSA template. Each template must exist on every selected fund. |
| OCR data extraction setup | Anduin | Only if an OCR data scope option is selected |
7. Step-By-Step Setup Guide
7.1 Grant access to the Integration Hub
- Customers need to contact their Implementation manager to ensure they have access to the Integration Hub and this integration
7.2 Locate the solution
- In the Browse tab of the Integration Hub, the customer can locate the Snowflake - Fundsub (Key Pair) solution.
7.3 Install the solution
-
Step 1: Click Install to begin setup
-
Step 2: Name the Integration
- Recommend a clear and descriptive name (e.g., “Snowflake integration - Fund Alpha” or “By John Smith”)
- Click Next: Link to Anduin objects
-
Step 3: Grant integration permission to customer’s intended objects (IDM and Funds)
-
Step 3.1: A list of accessible Anduin objects (e.g., IDM, Funds) will appear
-
Step 3.2: Click Open next to your intended funds
-
Step 3.3: In the permission module, find the integration name and click Add
- Step 3.4: Return to the Integration Hub - the IDM and funds should now show a “Linked” tag
If the target funds are not listed, there are 2 options- Customer needs to be added with admin role for that fund, then return to the step 3.2. Customer should be able to see the target fund there
- Customer requests their team member who has admin role in the target funds to perform step 3.3 using Settings > Integrations in the FundSub app and they can continue with step 3.4
-
7.4 Configure the solution
The configuration has three pages.
Step 1: Authentication and destination
-
Enter the Anduin connection and the Snowflake connection. Both are required.
-
Specify the Snowflake destination: Snowflake Identifier URL, Snowflake Account Locator, Warehouse, Database, and Schema (default: PUBLIC).

Step 2: Fund selection
-
Turn on Select All Funds to sync every fund, or turn it off and choose specific funds in Select Funds. The toggle overrides the fund selection.
-
When the integration is installed, 4 data tables are created in the selected Snowflake schema. See section 4 for what each table holds.

Step 3: Data scope, export method, and triggers
-
Step 3.1: Select data scope
- Choose the Anduin data to sync. Multiple options can be selected, and all four are selected by default:
- Smartform Subscription Documents
- Smartform Supporting Documents
- OCR Subscription Documents
- OCR Supporting Documents
- Clear any option you do not need. An option that is not selected is not exported.
- Choose the Anduin data to sync. Multiple options can be selected, and all four are selected by default:
-

-
Step 3.2: Select Export Method
- Choose one export method for the whole integration instance: Anduin Default Template (ASA), Customer Standard Template (CSA), or a named CSA template.
- Check the table in section 5.2 to confirm the method supports the data scope options you selected. An option the method does not support is skipped, and nothing is written for it.
- To export all four data scope options, choose a named CSA template. It must exist on every selected fund.
-
Step 3.3: Select Subscription Doc Status(es)
- Choose the order status or statuses that trigger a sync of Smartform subscription data. Multiple statuses are supported.
- At least one status is required, even if you only selected OCR options.

7.5 Validate the solution
Once configuration is complete:
-
The customer should observe the 4 data tables created in the selected Snowflake schema. Detailed data dictionary can be found HERE
-
Once the trigger occurs in Anduin, a new record is created or an existing record is updated in the corresponding data table in Snowflake. Smartform data and OCR data for the same order appear as separate rows in the order table.
If the automation works end-to-end, the setup is successfully validated.
Updated 10 days ago