MGA Architecture in OpenInsure
Programs
A Program is the core organizational unit. It defines the product being offered:- Line of business (GL, Cyber, E&O, WC, etc.)
- Carrier and DA agreement
- Eligible states
- Rate table versions
- Auto-bind thresholds (below which no human review is required)
- Minimum and maximum policy terms
- Permitted endorsement forms
Submission Intake Flow
Carrier Relationships
An MGA can have multiple carrier relationships, each with its own DA agreement. The carrier is selected at the program level — a GL program might run on Carrier A’s paper, while a Cyber program runs on Carrier B’s.Reporting Requirements
MGAs have contractual reporting obligations to their carriers. OpenInsure automates:| Report | Frequency | Delivery |
|---|---|---|
| Premium bordereaux | Monthly | Email attachment (CSV/Excel) + API |
| Claims bordereaux | Monthly | Email attachment + API |
| Aggregate DA utilization | Monthly | API / carrier portal |
| Loss runs | Quarterly | PDF per carrier |
| Annual production summary | Annual |
Producer Onboarding
Before a producer can submit business, they must be appointed:- Create the agency record (
POST /v1/producers). - Upload license verification (the compliance engine checks license status via NIPR).
- Configure commission rates (by program).
- Issue API credentials (if the agency is integrating directly).
- Send portal invitation.
@openinsure/producer package includes a NIPR integration for real-time license status
verification. Configure your NIPR credentials in the Admin settings to enable automatic license
monitoring and renewal alerts.
:::
Key Metrics Dashboard
The Admin Dashboard (/admin/analytics) provides real-time MGA KPIs: