Curo (T4A) Integration Guide
This guide explains what happens when you push policy data to Curo (T4A) from 4admin.
What Gets Pushed
When you click Push to Curo, the following data is sent to the account's Curo record:
Plan Data
| 4admin Field | Curo Field | Notes |
|---|---|---|
| Plan Number | Plan Number | Plan identifier |
| Start Date | Effective Date | Plan commencement |
| Plan Value | Plan Value | Current value |
| Valuation Date | Valuation Date, Transfer Value Date, Surrender Value Date | All three dates set as valuation date |
| Current Transfer Value | Transfer Value & Surrender Value | Both fields set |
| Waiver of Premium | Waiver of Premium | Yes/No |
| Guaranteed Annuity Rates | Guaranteed Annuity Rates | Yes/No (from GAR section of GMP field) |
| Invested in Lifestyle Strategy? | Life-styling | Yes/No |
| Life Cover | Life Assurance | Yes/No |
| Selected Retirement Date/Age | Retirement Age | Numeric value |
Plan Metadata
When creating a new plan, additional fields are set:
| Field | Value |
|---|---|
| Plan Name | [Provider] - [Policy Type] - [Plan Number] |
| Account | Linked to selected account |
| Contact | Linked to selected contact |
| Ownership | Single Life, Joint Lives, Account, or Scheme |
| Ownership Array | Contact linkage for the plan owner |
Optional Plan Settings
These fields can be set when pushing to either a new or existing plan. They are optional — if left blank, the existing value in Curo is preserved.
| Field | Options |
|---|---|
| Servicing Rights | Full servicing rights, Transferred from another agency, LOA required, Information authorised by client, No information rights, Agency transferred away |
| LOA Status | Generate LOA, LOA requested from client, LOA received from client, Info request sent to provider, Info request acknowledged by provider, Info from provider due, Info from provider incomplete, Info complete – ready for planning |
Fund Holdings
For each fund with valid data, a fund holding record is created:
| Data | Curo Field |
|---|---|
| Fund Name | Name (max 100 characters) |
| Fund Value | Current Value |
| Units Held | Units Held |
| Valuation Date | Units Date |
Contributions
Each contribution is created as an individual record:
| Data | Curo Field | Notes |
|---|---|---|
| Contribution Name | Name | Format: "[Type] - [Date]" |
| Amount | Contribution | Numeric value |
| Date | Effective Date | Contribution date |
| Frequency | Frequency | Always "Single" for individual records |
| Status | Status Code | Set to "Completed" |
Contribution Type Mapping:
| 4admin Type | Curo Contribution Type | Payable By |
|---|---|---|
| Employee | Regular | Self |
| Employer | — | Employer |
| Transfer In | Transfer | — |
Documents
Documents are uploaded to the plan's SharePoint folder:
- Input Document — Original policy PDF
- Checklist Document — Word document with extracted values
The Push Process
Step 1: Sign In to Microsoft
When you click Push to T4A, a Microsoft login window opens. This authenticates 4admin with your organisation's Dynamics environment.
Step 2: Search for the Account
Type the account name in the search box and press Enter. Results show:
- Account name
- Phone number
Curo uses "Accounts" (households/entities), not individual clients directly.
Step 3: Select or Create a Plan
Create New Plan
- Select "Create new..." from the dropdown
- Choose the Contact from the account (the policy owner)
- Choose the Provider (4admin suggests based on the document)
- Choose the Product Type
- Select Ownership:
- Single Life (default)
- Joint Lives
- Account
- Scheme
Update Existing Plan
- Select from existing plans
- Shows plan name and status (Active/Inactive)
Servicing Rights & LOA Status (Optional)
For both new and existing plans, two optional dropdowns appear:
- Servicing Rights — Set the servicing rights level for this plan (e.g., Full servicing rights, LOA required)
- LOA Status — Set the current LOA status (e.g., Generate LOA, LOA received from client)
If left blank, these fields are not sent to Curo, so any existing values on the plan are preserved.
Step 4: Review What Will Be Pushed
Each data item has a toggle switch. Fields shown depend on what was extracted:
- Start Date — Effective date
- Plan Number — Plan identifier
- Plan Value — Current valuation
- Transfer Value — Transfer/surrender value
- Waiver of Premium — If detected as Yes/No
- Guaranteed Annuity Rates — If GAR detected
- Invested in Lifestyle Strategy — If detected
- Life Cover — If detected
- Projections — Shows which projections were found (high, mid, low)
- Contributions — Total contribution history
- Funds — Number of funds (hover to see details)
Step 5: Name Your Documents
Configure each document:
The title for the document you uploaded
- Toggle to include/exclude
- Enter document name
The title for the front sheet document
- Toggle to include/exclude
- Enter checklist name
Step 6: Push the Data
Click Push data. The system:
- Creates/updates the plan
- Creates fund holdings (in background)
- Creates contributions (in background)
- Uploads documents to SharePoint (in background)
What Appears in Curo After Pushing
Plan Record
| Section | Fields |
|---|---|
| General | Plan Name, Plan Number, Effective Date |
| Provider | Provider, Product |
| Ownership | Ownership type, Contact linkage |
| Values | Plan Value, Transfer Value, Surrender Value |
| Dates | Valuation Date, Transfer Value Date, Surrender Value Date |
| Features | Waiver of Premium, GAR, Life-styling, Life Assurance |
| Servicing | Servicing Rights, LOA Status (if set) |
Fund Holdings
Each fund appears as a related record with:
- Fund name
- Current value
- Units held
- Units date
Contributions
Each contribution appears as a separate record showing:
- Contribution name (type and date)
- Amount
- Effective date
- Frequency (Single)
- Type (Regular/Transfer/etc.)
- Payable by (Self/Employer)
Documents (SharePoint)
Documents are stored in the plan's SharePoint folder:
- Location:
[Account Name] - [Provider] - [Policy Type] - [Plan Number] - Files: PDF and DOCX with your chosen names
Ownership Types
When creating a new plan, select the appropriate ownership:
| Type | Use Case |
|---|---|
| Single Life | Plan owned by one individual (default) |
| Joint Lives | Plan owned by two people (e.g., married couple) |
| Account | Account-level ownership |
| Scheme | Scheme membership |
Provider and Product Selection
Curo requires both a Provider and a Product:
- Provider: The pension/investment company (e.g., Aviva, Scottish Widows)
- Product: The specific product type from that provider
4admin shows tooltips with detected values from your document to help you find matches.
Tips for Best Results
-
Select the correct Contact — This is required for new plans and links the plan to the policy owner
-
Check Provider matching — Curo has its own provider list; find the closest match
-
Review funds before pushing — Hover over the funds count to see which will be created
-
Allow time for background tasks — Fund holdings, contributions, and documents are processed in background threads
Troubleshooting
Authentication fails
- Ensure your Microsoft account has access to the Curo environment
- Check that your organisation's IT has approved the 4admin integration
Account not appearing
- Try different search terms
- Check the account exists in Curo with that exact name
Documents not uploading
- SharePoint document locations are created automatically
- Check that your Curo environment has SharePoint integration enabled
Some fields not appearing
- Fields only appear if 4admin detected a valid Yes/No value
- Check the original document extraction for these fields
Contact not in dropdown
- The contact must be linked to the selected account in Curo
- Check the account's Contacts in Curo