Does Mezdoc supply the ACORD 125, 126 or 140?

No. Mezdoc does not supply ACORD forms. Bring the editions your organization is licensed or authorized to use, and Mezdoc maps and fills the forms you upload.

Do we enter the applicant's details once for all three forms?

Yes. The insured's name, address, FEIN and contact are workflow fields, entered once and mapped to each form that asks for them. Correct a value once and run the workflow again, and every form picks up the fix.

Can the ACORD 126 or 140 be left out when that line is not requested?

Yes. Each form can carry an include rule your team writes, such as gl_requested == true for the 126 and property_requested == true for the 140. When a rule is false, that form is skipped, so the application holds only the sections that apply.

Can we add supplemental applications or our own questionnaires to the same workflow?

Yes. Upload a carrier supplemental as another static PDF template, or write your own questionnaire as a dynamic document, and add it to the workflow with its own include rule. It fills from the same workflow fields as the ACORD forms.

Can a broker fill it through a link without an account?

Yes. Send the workflow as a hosted link. The broker opens it in any browser, with no account and nothing to install, answers once and signs where the forms ask. Each run is completed and signed by one person, and a link can ask for an email code first, expire, and stop after a set number of uses.

Do the forms come back as one PDF or separate files?

Either, or both, set per workflow. The merged PDF holds every included form in the order you set, and each separate file is named by its alias. A run counts as one document on your plan, however many forms it fills.

What happens when ACORD releases a new edition of the 125?

Upload the new edition as a new template version, test it on staging, then publish the workflow again. A published workflow keeps the template versions it froze, so a live application never changes underneath you, and every run records the versions it used.

ACORD commercial applications for US MGAs, wholesale brokers and program administrators

Automate ACORD 125, 126 and 140 commercial applications from one set of answers

Enter the applicant once, through a hosted form or your API. The answers fill the ACORD 125, and your include rules add the 126 when general liability is requested and the 140 when property is.

Build the workflow Book a setup call

General liability requested?Add the ACORD 126.
Property requested?Add the ACORD 140.

ACORD 125

ACORD 126

ACORD 140

One merged PDF, three forms

Stylized pages, not the ACORD forms. The ACORD 125, 126 and 140 you upload keep their own layout, form numbers and edition dates.

How to automate ACORD 125, 126 and 140 applications.

Bring your ACORD forms
Upload the ACORD 125, 126 and 140 editions your organization is licensed or authorized to use, each as a static PDF template. They stay your forms.
Put them in one workflow
Add the three templates to a workflow. Its fields, such as insured_name and fein, are entered once and map to every form that asks for them.
Write the include rules
The ACORD 125 has no rule, so it is always in. The 126 joins when gl_requested is true, and the 140 when property_requested is true.
Collect the answers once
A broker or producer fills the workflow's hosted form, or your system posts the answers to the API. One merged PDF, separate files, or both come back.

One set of answers, on every form that asks for them.

A workflow holds its fields once. Each form maps the ones it has a box for, so the applicant's name, address, FEIN and contact are typed once, not once per form.

Sample workflow fields for an ACORD commercial application, and the forms each one fills
Workflow field	ACORD 125	ACORD 126	ACORD 140
`insured_name`input	Fills the ACORD 125	Fills the ACORD 126	Fills the ACORD 140
`agency_name`fixed value: your agency	Fills the ACORD 125	Fills the ACORD 126	Fills the ACORD 140
`effective_date`input	Fills the ACORD 125	Fills the ACORD 126	Fills the ACORD 140
`mailing_address`input	Fills the ACORD 125	Not on the ACORD 126	Not on the ACORD 140
`fein`input	Fills the ACORD 125	Not on the ACORD 126	Not on the ACORD 140
`contact_email`input	Fills the ACORD 125	Not on the ACORD 126	Not on the ACORD 140
`premises_address`input	Fills the ACORD 125	Not on the ACORD 126	Fills the ACORD 140
`gl_requested`input, yes or no; also the 126's include rule	Fills the ACORD 125	Not on the ACORD 126	Not on the ACORD 140
`property_requested`input, yes or no; also the 140's include rule	Fills the ACORD 125	Not on the ACORD 126	Not on the ACORD 140
`gl_each_occurrence`input	Not on the ACORD 125	Fills the ACORD 126	Not on the ACORD 140
`building_limit`input	Not on the ACORD 125	Not on the ACORD 126	Fills the ACORD 140

A sample setup: which boxes each form has depends on the editions you upload. A form field fills from a workflow field, a formula or a fixed value, such as your agency's name. Correct a typo once and run the workflow again, and every form picks up the fix.

Include rules add the sections the risk asks for.

The ACORD 125 has no rule, so it is in every application. The 126 and the 140 each carry a rule your team writes. A property-only risk gets the 125 and the 140; a liability-only risk gets the 125 and the 126.

Carrier supplementals and your own questionnaires join the same way, each with its own rule. Mezdoc applies the rules the same way on every run; it does not decide which sections a risk needs.

Sample include rules for an ACORD commercial application
Include rule	Form it includes
`gl_requested == true`	ACORD 126, general liability section
`property_requested == true`	ACORD 140, property section
`property_requested == true && building_limit > 5000000`	Your own property supplemental questionnaire

How the answers reach Mezdoc.

Entered once, by the person who has them or the system that holds them. There is no prebuilt connector to install.

from a broker or producer
A hosted link
Send the workflow as a link. The broker fills it in any browser, with no account, and signs where the forms ask. A link can ask for an email code first, expire, and stop after a set number of uses.
from your system
The REST API
Your submission intake or PAS posts the answers to the workflow and gets the forms back, or a signed webhook when they are ready.
inside your portal
An embedded form
A single template's form, such as a supplemental questionnaire, in an iframe on your own site, allowed only on the origins you list. An embed holds one template, not the whole workflow.

Three forms in. One application out.

The included forms line up in the order you set. Send the carrier one PDF, or a file per form.

Applicant informationACORD 125
General liabilityACORD 126
PropertyACORD 140

One merged application

One merged PDF
Every included form, in the order you set, as one file.
Separate PDFs
Each form as its own file, named by its alias.
Both
The merged application and the separate files, or a zip of everything.

New ACORD editions, without breaking a live application.

Each form is its own template with its own versions. The workflow pins the versions it was published with.

Publishing the workflow freezes the template version of each form in it.
Map a new ACORD 125 edition as a new template version and test it on staging.
Publish the workflow again to pick it up; until then, live runs keep the old edition.
Every run records the versions it used, and you can restore an earlier one.

for large MGAs and high-volume brokers

One API call per application.

POST the answers to the workflow run API. The response links the merged PDF and each form, with its alias.
?async=true returns a 202 at once, and a signed workflow.run.completed webhook says when the forms are ready.
Staging keys render the version published to staging, with a STAGING watermark. Production keys render the version published to production.
Rendering one form on its own? A single template render takes an idempotency_key, so a retry never renders it twice.

A run counts as one document on your plan, however many forms it fills.

Read the workflow run API reference

POST /api/v1/workflows/commercial_application/runs?async=true

curl -X POST "https://api.mezdoc.com/api/v1/workflows/commercial_application/runs?async=true" \
  -H "Authorization: Bearer $MEZDOC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "data": {
        "insured_name": "Harbor Point LLC",
        "fein": "12-3456789",
        "mailing_address": "200 Example Way, Tampa FL 33602",
        "contact_email": "jordan@example.com",
        "effective_date": "2026-06-01",
        "gl_requested": true,
        "gl_each_occurrence": 1000000,
        "property_requested": true,
        "building_limit": 2400000
      } }'

# 202 Accepted: run_id, status, poll_url
# later, to your endpoint:
workflow.run.completed

What Mezdoc does with an application, and what it does not.

Mezdoc fills and assembles the forms. The answers, the underwriting and the submission to the carrier stay with you.

Mezdoc does

Fills the ACORD 125, 126 and 140 you upload from one set of answers
Includes each form only when the rule your team wrote is true
Returns one merged PDF, the separate files, or both
Records each run with the workflow version it used

Mezdoc does not

Supply ACORD forms, or grant any right to use them
Read data out of completed applications you receive
Decide which sections or supplementals a risk needs
Underwrite, rate or quote the risk
Submit the application to a carrier or its portal

Good to know before you build

An embed holds one template: A hosted link or the API runs the whole workflow. An embed puts a single template's form on your site.
One signer per run: Each workflow run is completed and signed by one person. Mezdoc does not route the application to another signer.
No idempotency key on workflow runs: Single template renders take an idempotency_key; workflow runs do not today. Keep the run_id your call returns and poll it, rather than posting the run again.
No prebuilt AMS or PAS connector: Your system calls the REST API, or a person fills the hosted form. There is nothing to install.

Questions about ACORD application workflows.

Does Mezdoc supply the ACORD 125, 126 or 140?: No. Mezdoc does not supply ACORD forms. Bring the editions your organization is licensed or authorized to use, and Mezdoc maps and fills the forms you upload.
Do we enter the applicant's details once for all three forms?: Yes. The insured's name, address, FEIN and contact are workflow fields, entered once and mapped to each form that asks for them. Correct a value once and run the workflow again, and every form picks up the fix.
Can the ACORD 126 or 140 be left out when that line is not requested?: Yes. Each form can carry an include rule your team writes, such as gl_requested == true for the 126 and property_requested == true for the 140. When a rule is false, that form is skipped, so the application holds only the sections that apply.
Can we add supplemental applications or our own questionnaires to the same workflow?: Yes. Upload a carrier supplemental as another static PDF template, or write your own questionnaire as a dynamic document, and add it to the workflow with its own include rule. It fills from the same workflow fields as the ACORD forms.
Can a broker fill it through a link without an account?: Yes. Send the workflow as a hosted link. The broker opens it in any browser, with no account and nothing to install, answers once and signs where the forms ask. Each run is completed and signed by one person, and a link can ask for an email code first, expire, and stop after a set number of uses.
Do the forms come back as one PDF or separate files?: Either, or both, set per workflow. The merged PDF holds every included form in the order you set, and each separate file is named by its alias. A run counts as one document on your plan, however many forms it fills.
What happens when ACORD releases a new edition of the 125?: Upload the new edition as a new template version, test it on staging, then publish the workflow again. A published workflow keeps the template versions it froze, so a live application never changes underneath you, and every run records the versions it used.

Once the risk is quoted and approved, the same insured data carries on: see the quote-to-binder document workflow.

All insurance document workflows for US MGAs

quote and bind
Quote letter, binder and schedule from approved quote data
Once a quote is approved in your PAS or rater, send the data once and get back the quote letter, the binder, the schedule and the forms your rules call for.
See the quote-to-binder document workflow
insurance binders
Automate ACORD 75 binder form filling
Map the ACORD 75 your organization is licensed or authorized to use once. Each insurance binder then fills from the approved quote and bind data you send.
Automate ACORD 75 insurance binder form filling from bind data
policy issuance
Policy packets and the schedule of forms
Declarations, coverage forms, state notices and endorsements, each included by a rule your team configured, then merged into one policy packet.
Explore insurance policy packet automation for US MGAs
certificates of insurance
Automate ACORD 25 certificate creation
Map the ACORD 25 your organization is licensed or authorized to use once. Each certificate of insurance then fills from the policy, insured and holder data you send.
Automate ACORD 25 insurance certificate creation from policy data

Bring the application your team retypes most.

Upload the ACORD 125, 126 and 140 your organization is licensed or authorized to use. We build the first workflow with you on a call, and you keep whatever we build.

Build the workflow Book a setup call

Free plan, no card

Automate ACORD 125, 126 and 140 commercial applications from one set of answers

One set of applicant answers filling the ACORD 125, 126 and 140

How to automate ACORD 125, 126 and 140 applications.

Bring your ACORD forms

Put them in one workflow

Write the include rules

Collect the answers once

One set of answers, on every form that asks for them.

Include rules add the sections the risk asks for.

How the answers reach Mezdoc.

A hosted link

The REST API

An embedded form