RM Assistant for Vertafore IMS
ACORD forms, loss runs and vehicle schedules extracted from broker email and mapped to your IMS field schema — so nobody on your team types them again.
Being built now with a design partner. Available for pilot engagements — talk to us about timing before you plan around it.
What RM Assistant does with Vertafore IMS
Data flows into your system of record. We are the intake layer, not another place your data has to live.
Removes the re-keying step into IMS
The manual work between a broker's email landing and a record existing in IMS — opening each attachment, reading the ACORD, typing the fields — is what this integration replaces. Extraction happens once, against the source documents.
Mapped to your IMS field schema
Extracted data is typed against the schema your IMS instance actually uses, including the custom fields your programs depend on, rather than a generic shape you would then have to translate.
Human review before anything posts
Data lands in a review queue with field-level confidence scores and links back to the source page. A person approves, and only then is the record written to IMS.
Auditable end to end
Each posted value keeps a pointer to the document it came from, so an IMS record can be reconciled against the original submission long after the fact.
Vertafore IMS integration, answered
Is the Vertafore IMS integration available today?
It is in active development with a design partner rather than generally available. The extraction pipeline that feeds it is live in production; the IMS connector specifically is being built now. If IMS is your system of record, talk to us about pilot timing before you plan around a date.
What does RM Assistant do before the data reaches IMS?
It receives the broker email, classifies every attachment — ACORD 125, 127 and 140, loss runs, vehicle schedules, MVRs, supplementals — extracts the underwriting data with a confidence score per field, and presents it for human review. IMS is the destination at the end of that pipeline.
Do we have to change our IMS configuration?
No. Field mapping is configured on our side against how your instance is already set up, including custom fields. The integration adapts to your IMS rather than the other way round.
Can we evaluate accuracy before committing?
Yes. Standard onboarding runs your real historical submissions through the extraction pipeline so you can measure accuracy on your own documents. That evaluation does not depend on the IMS connector being finished.
What if we move off IMS later?
The extraction layer is independent of the destination. Structured records can be routed to a different policy administration system, or to a custom API, without re-doing the document work.
Talk to us about Vertafore IMS
30 minutes, a real submission from your book, and a straight answer about where this integration stands for your instance.
Book a demoNo sales pressure. We confirm within one business day.