Export Settings
Export Settings allow you to create predefined mappings between your Table's data and standardized Excel templates. This is essential for generating reports in specific formats required by regulators, partners, or internal processes.
Why Use Export Settings?
Insurance reporting often requires data in specific formats:
- Regulatory submissions (Lloyd's bordereaux, state filings)
- Partner reports (wholesaler summaries, MGA reports)
- Internal dashboards (management reports, portfolio reviews)
- Standardized templates (industry-standard formats)
Rather than manually reformatting data for each export, you can configure mappings once and reuse them whenever you need to generate a report.
How Export Settings Work
Export Settings create a mapping between:
- Template columns — The column structure of a predefined Excel template
- Table columns — Your Decode Table's columns (row identifier, static, metadata, dynamic)
When you export data using a configured mapping, Decode takes your cleaned data and reorganizes it to match the template's structure.
Accessing Export Settings
- Navigate to Data → Select your Table → Settings
- Expand the Export Settings accordion
Managing Export Mappings
Viewing Existing Mappings
The Export Settings section shows all mappings you've created for this Table:
- Name — Your descriptive name for the mapping
- Template — Which Excel template it maps to
- Edit — Modify the mapping
- Delete — Remove the mapping
Creating a New Mapping
- Click Add New Mapping
- Enter a Name (e.g., "Lloyd's V52 Premium Export")
- Select a Template from the dropdown
Selecting a Template
Templates define the target format for your export. Decode provides a library of common insurance templates, including:
- Lloyd's bordereaux formats
- Regulatory reporting templates
- Industry-standard formats
Each template has a predefined schema (column structure) that your Table data will be mapped to.
Field Mapping
Once you select a template, the Field Mapping section shows all columns from the template. For each template column, you select which Table column should populate it.
Mapping Options
For each template field, you can map to:
| Source Type | Description | Example |
|---|---|---|
| Row Identifier | Your Table's unique record key | Policy_Number |
| Metadata Column | Context added during upload | Wholesaler_Name, Contract_ID |
| Static Column | Fixed record attributes | Policyholder_State, Class_of_Business |
| Dynamic Column | Time-series data | month.Gross_Premium, month.Net_Premium |
| Month | The reporting period itself | month |
| (blank) | Leave the template column empty | — |
Example Mapping
| Template Column | Table Column |
|---|---|
| Policy Reference | Policy_Number |
| Insured Name | Insured_Name |
| Inception Date | Inception_Date |
| Premium Amount | month.Gross_Premium |
| Commission | month.Commission |
| Reporting Period | month |
Per-Time-Period Templates
The current export system supports per-time-period templates. This means:
- The export generates output for each reporting period (month/quarter) in your data
- Dynamic columns are mapped to a single template column that repeats per period
- The
monthfield identifies which period each row represents
This format is ideal for bordereaux-style reports where each row represents a policy-period combination.
Using Export Mappings
Once you've configured an export mapping, you can use it to generate reports from the Data view or through Data Functions.
From the Data View
- Navigate to your Table's data
- Apply any desired filters
- Click Export and select your configured mapping
- Download the generated Excel file
From Data Functions
Export mappings can be referenced in Data Functions for automated report generation.
Tips and Best Practices
Naming Conventions
Use clear, descriptive names that identify:
- The template format (e.g., "Lloyd's V52")
- The data type (e.g., "Premium" vs "Claims")
- Any specific configuration (e.g., "Monthly" vs "Quarterly")
Example: "Lloyd's V52 Premium - Monthly Submission"
Multiple Mappings
You can create multiple mappings for the same Table:
- Different templates for different recipients
- Variations for different time periods
- Customized formats for specific partners
Unmapped Fields
Template columns that you leave unmapped will be empty in the export. This is useful when:
- Your Table doesn't have data for certain template fields
- You'll fill in those fields manually after export
- The template includes optional fields you don't use
Validation
After creating a mapping, test it with a small export to verify:
- All required fields are mapped correctly
- Data types match expectations (dates formatted correctly, numbers not truncated)
- The output matches your recipient's requirements
Saving Changes
Click Save Mapping after configuring your field mappings. The mapping is saved to your Table and can be used immediately for exports.