Does Mezdoc provide the ACORD 75 form?

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

Will the filled binder keep our ACORD 75's layout and edition?

Yes. Mezdoc fills your original PDF rather than rebuilding it, so the layout, the form number and the edition date stay exactly as they are. Values land where you placed the fields, on every render.

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

Upload the new edition, map its fields, test it on staging and publish it. Links that follow the live version pick it up, a pinned link stays on its version, and binders already issued keep the version that made them.

Can the binder go out in one packet with the quote letter?

Yes. Put the ACORD 75 in a workflow with your quote letter and schedule. Every document fills from the same workflow fields, and the run returns one merged PDF, the separate files, or both.

What data does our system need to send for each binder?

Only what changes per binder: usually the binder number, the effective and expiration dates and times, the insured, the coverages and limits, the premium, the additional interests and the remarks. Values that rarely change, such as your agency block, can be default values on the template.

Our ACORD 75 is a fillable PDF built with XFA. Can Mezdoc read its fields?

Mezdoc reads the AcroForm fields that a fillable XFA-based PDF carries, with their names and positions, so you tie them to data keys instead of drawing them. Where a box has no field, draw one by hand.

Does Mezdoc bind coverage?

No. Your team and your binding authority bind the risk. Mezdoc fills the binder form from the bind data your system sends, and records each render with its template version and a SHA-256 of the PDF.

ACORD 75 insurance binders for US MGAs and wholesale brokers

Automate ACORD 75 insurance binder form filling from approved quote data

The quote your team approved fills the binder form you already use. Each insurance binder comes from the bind data in your PAS or rater, without retyping.

Map your first PDF Book a setup call

A stylized binder, not the ACORD form. Your uploaded ACORD 75 keeps its own layout, form number and edition date.

How to automate ACORD 75 binder form filling.

Bring your ACORD 75
Upload the ACORD 75 edition your organization is licensed or authorized to use, once, as a static PDF template. It stays your form.
Map each field once
Mezdoc reads the form fields already in the PDF, or you draw them. Tie each one to a data key such as binder_number or mortgagee.
Send the bind data
Once your team binds the risk, your PAS, rater or spreadsheet sends the binder number, dates, insured, coverages, limits, premium and additional interests, through the API or a hosted form.
Get the binder
Mezdoc fills your original PDF and returns it. The same mapping fills every binder after that, and a workflow can send it out with the quote letter and the schedule.

Map once. Every binder fills the same boxes.

Each piece of bind data is tied to one field on your form. After that, your system sends the data and the binder fills itself.

binder_numberfills Binder number
binder_effective_datefills Effective date
insured_namefills Named insured
mortgageefills Mortgagee

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

A binder can travel with the quote letter.

Put the ACORD 75 in a workflow and it fills from the same approved quote data as the quote letter and the schedule around it.

Quote letterQuote letter
BinderACORD 75
ScheduleSchedule

One binder packet

See the quote-to-binder document workflow for the quote letter and schedule that go out with the binder

Field mapping for an ACORD 75, key by key.

Mezdoc populates your existing binder form from structured bind data. This is a typical commercial property and general liability binder.

Data key agency_namefills the field AgencyType: Short textDefault value: your agency, so the call can leave it out
Data key insurer_namefills the field CompanyType: Short text
Data key insurer_naicfills the field NAIC codeType: Short text
Data key binder_numberfills the field Binder numberType: Short textYour number, from your PAS or rater
Data key binder_effective_datefills the field Effective dateType: DateSend 2026-06-01; the binder shows 6/1/2026
Data key binder_effective_timefills the field Effective timeType: Short textSent as text, such as 12:01 AM
Data key binder_expiration_datefills the field Expiration dateType: Date
Data key binder_expiration_timefills the field Expiration timeType: Short text
Data key insured_namefills the field Named insuredType: Short textThe same key your certificate template uses
Data key insured_addressfills the field Mailing addressType: Long text
Data key property_coveragefills the field Property (coverage line)Type: CheckboxTicked when the value is true
Data key building_limitfills the field Building limitType: Currency
Data key gl_each_occurrencefills the field General liability, each occurrenceType: Currency
Data key total_premiumfills the field PremiumType: Currency
Data key mortgageefills the field MortgageeType: Long textName and address, wrapped inside the box you drew
Data key loss_payeefills the field Loss payeeType: Long text
Data key remarksfills the field RemarksType: Long textWraps inside the box you drew, and shrinks to fit

Keys use letters, numbers and underscores. Use the same keys on your binder and your certificate, such as insured_name, and one record fills both the same way.

What a static PDF template does with your ACORD 75.

Reads the PDF's own form fields, with their names and positions, including the AcroForm fields a fillable XFA-based PDF carries. You can also draw a field by hand.
Gives every field a type, such as text, date, currency or checkbox, from 27 in all.
Fills your original PDF, so nothing on the form is redrawn.
Wraps a long mortgagee, loss payee or remarks entry inside the box you drew, and shrinks it to fit.
Ticks a coverage checkbox when the value is true.

Default values for what rarely changes

A field can carry a default value, used whenever the data leaves it empty. Set your agency name, address and contact once, and your system only sends what changes from one binder to the next.

fill a binder from your system

One API call per binder.

A plain call returns the PDF. Add ?return=url for JSON with a link to it.
?async=true returns a 202 at once, and a signed submission.completed webhook says when it is ready.
An idempotency_key means a retry never issues the same binder twice.
Staging keys render with a STAGING watermark, so test binders are marked as tests.

No integration yet? Underwriters can fill the same template through a hosted form link, which can ask for an email code and expire.

Read the render API reference

POST /api/v1/templates/acord_75/render

curl -X POST "https://api.mezdoc.com/api/v1/templates/acord_75/render?return=url" \
  -H "Authorization: Bearer $MEZDOC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "data": {
      "binder_number": "HB-2026-0192",
      "binder_effective_date": "2026-06-01",
      "binder_effective_time": "12:01 AM",
      "insured_name": "Harbor Point LLC",
      "property_coverage": true,
      "building_limit": 2400000,
      "mortgagee": "Example Savings Bank"
    },
    "idempotency_key": "binder-HB-2026-0192"
  }'

# 200 OK: JSON with a link to the finished binder

New ACORD editions, without breaking a live binder.

Map the new edition next to the live version, render a test binder on staging, then publish.

Links and API calls that follow the environment use the new version from then on.
A link pinned to a version stays on it.
Every binder records the template version that made it.
Test renders from the editor are free, and you can restore an earlier version.

What Mezdoc does with a binder, and what it does not.

Mezdoc fills and records the binder. Rating, terms and the decision to bind stay with your team and your authority.

Mezdoc does

Fills the ACORD 75 you upload, field by field, from the bind data you send
Keeps your form's layout, form number and edition date unchanged
Records each binder with its template version and a SHA-256 of the PDF
Returns the PDF, a link to it, or a webhook when it is ready

Mezdoc does not

Supply ACORD forms, or grant any right to use them
Bind coverage, or act on your binding authority
Rate the risk, or decide the terms and conditions
Track binder expiration dates, or replace a binder with the policy by itself

Questions about ACORD 75 binder form filling.

Does Mezdoc provide the ACORD 75 form?: No. Mezdoc does not supply ACORD forms. Bring the ACORD 75 edition your organization is licensed or authorized to use, and Mezdoc maps and fills the form you upload.
Will the filled binder keep our ACORD 75's layout and edition?: Yes. Mezdoc fills your original PDF rather than rebuilding it, so the layout, the form number and the edition date stay exactly as they are. Values land where you placed the fields, on every render.
What happens when ACORD releases a new edition of the ACORD 75?: Upload the new edition, map its fields, test it on staging and publish it. Links that follow the live version pick it up, a pinned link stays on its version, and binders already issued keep the version that made them.
Can the binder go out in one packet with the quote letter?: Yes. Put the ACORD 75 in a workflow with your quote letter and schedule. Every document fills from the same workflow fields, and the run returns one merged PDF, the separate files, or both.
What data does our system need to send for each binder?: Only what changes per binder: usually the binder number, the effective and expiration dates and times, the insured, the coverages and limits, the premium, the additional interests and the remarks. Values that rarely change, such as your agency block, can be default values on the template.
Our ACORD 75 is a fillable PDF built with XFA. Can Mezdoc read its fields?: Mezdoc reads the AcroForm fields that a fillable XFA-based PDF carries, with their names and positions, so you tie them to data keys instead of drawing them. Where a box has no field, draw one by hand.
Does Mezdoc bind coverage?: No. Your team and your binding authority bind the risk. Mezdoc fills the binder form from the bind data your system sends, and records each render with its template version and a SHA-256 of the PDF.

Certificates usually follow a bind. The same insured and policy data can fill the certificate next: automate ACORD 25 insurance certificate creation from policy data.

All insurance document workflows for US MGAs

Harbor Point LLCGL and property requested
Typed once, three forms filled
commercial applications
ACORD 125, 126 and 140 from one set of answers
Enter the applicant once. Shared fields fill the ACORD 125, and include rules add the 126 when general liability is requested and the 140 when property is.
Automate ACORD 125, 126 and 140 commercial applications from one set of answers
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
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

Map your first binder.

Upload the ACORD 75 your organization is licensed or authorized to use, place the fields and render a test binder. The free plan covers it, with a watermark.