Reinsurance

Zip File Submissions for Reinsurers: 7-Stage Unpack Pipeline

On this page

Last reviewed: November 2026

"Can you show that every file inside the broker's zip reached the underwriter?" The CIO asked after an audit sample.

Nobody could. The zip had been opened on a desktop, and two files inside a nested archive were never seen.

Zip file submissions for reinsurers are broker emails that send treaty documents as compressed archives instead of single attachments.

They need a controlled unpack, because what is inside an archive is not visible until someone opens it.

This guide gives you a seven-stage unpack pipeline, six failure modes with fixes and a dated timeline for one submission.

Key Takeaways

  • Scan before and after unpacking. The archive and each file inside it need checking.
  • Unpack nested archives to a set depth. Record every file against the outer zip.
  • Detect duplicates by hash. File names lie; contents do not.
  • Reconcile to the email's list. An archive proves nothing until it matches what the broker said was sent.

What Are the Stages of an Unpack Pipeline for Zip File Submissions?

The stages of an unpack pipeline for zip file submissions run from receipt to filing, with an owner and evidence at each step.

StageTriggerActionOwnerEvidence kept
1. ReceiveEmail with .zip, .7z or .rarLog archive name, size, sender, timeIntake mailboxIntake log entry
2. Malware scanArchive loggedScan archive, then each extracted fileIT securityScan result per file
3. UnpackScan cleanExtract, including nested archives, to a short pathOperationsFile list with parent archive
4. Name and path checksFiles extractedFix garbled names; flag paths over the limitOperationsOriginal and corrected names
5. Duplicate detectionNames fixedHash every file; mark identical contentsOperationsHash list, duplicates marked
6. ReconcileUnique files knownMatch files to the email's attachment listUnderwriting assistantMatched, missing, extra
7. FileReconciledSave to the submission recordUnderwriting assistantFiling location and date

Archives are common for a simple reason. Microsoft's Exchange Online limits default to 35 MB to send and 36 MB to receive.

Stage 6 is the inventory reconciliation. It is the only stage that proves the archive held what the email promised.

Record three counts: matched, missing and extra. Extra files are often older versions the broker forgot to remove.

Unpacked spreadsheets then go to excel submission data extraction. Filing rules are covered in reinsurance email filing.

Which Zip Failures Stop Broker Treaty Files Reaching the Underwriter?

Zip failures that stop broker treaty files reaching the underwriter fall into six types, each with a fix.

What should happen when a broker zip contains another zip?

When a broker zip contains another zip, the pipeline should unpack it too, scan each level and stop at a set depth.

Record each file with its full chain, such as Renewal.zip > Claims.zip > LLL.xlsx. Desktop unzipping often skips the inner archive.

How should .7z and .rar archives in a reinsurance submission be handled?

.7z and .rar archives in a reinsurance submission should be opened only by a tool that supports the format.

Not every unpacking tool reads both. If yours does not, ask the broker for a zip rather than installing tools ad hoc.

What should be done with an encrypted archive from a broker?

An encrypted archive from a broker should be flagged and held, because nothing inside can be scanned or indexed yet.

Log it as received but unopened. Opening it belongs to your separate password-handling process.

Why do unzipped treaty files fail on the Windows 260-character path limit?

Unzipped treaty files fail on the Windows 260-character path limit when the zip's folders are added to a long destination folder.

Microsoft documents MAX_PATH as 260 characters in the Windows API.

Longer paths need a registry setting and an application that declares itself long-path aware. Many tools do not.

Illustration: a 95-character folder, 55 characters of zip folders and a 125-character file name make 275. Extract to a short root.

Why do file names from a broker zip come out garbled?

File names from a broker zip come out garbled when they are stored in one character encoding and read in another.

The PKWARE ZIP specification uses general purpose bit 11 to mark names as UTF-8.

Without that flag, names should follow the original encoding, IBM Code Page 437.

A UTF-8 name such as "Prämienübersicht" read that way shows as "Pr├ñmien├╝bersicht".

Keep the original name in the log and store a corrected one. For content in other languages, see multilingual reinsurance submissions.

How can a zip bomb affect a reinsurer's intake?

A zip bomb can affect a reinsurer's intake by expanding a small archive into enough data to fill a disk or stall a scanner.

A 2019 USENIX WOOT paper by David Fifield describes one expanding 10 MB to 281 TB.

Set limits on total unpacked size, file count and nesting depth. Stop and alert when any limit is hit.

Where Do Handoffs Break in Zip File Intake?

Handoffs break in zip file intake where one team assumes another has opened, checked or listed the files.

  • Security to operations. A clean archive scan is read as "all files clean", though nested files were never scanned.
  • Operations to underwriting. A folder is shared, but nobody says two files were duplicates.
  • Underwriting to broker. A missing file is noticed at pricing, days after the reply-by date.
  • Operations to records. Garbled file names are fixed on a desktop copy, so the filed version keeps the broken name.

Claims archives often hold claimant details. Store unpacked files under the controls in personal data in bordereaux.

Missing items belong on the list in incomplete reinsurance submissions.

What Does a Dated Timeline for One Zipped Treaty Submission Look Like?

A dated timeline for one zipped treaty submission shows where files are found, lost and recovered. This one is illustrative.

Date and timeEventRunning position
Mon 23 Nov, 09:12Email arrives with a 31 MB zip; email lists 22 documentsLogged
Mon 23 Nov, 09:13Archive scanned cleanUnpack approved
Mon 23 Nov, 09:2015 files plus Claims.zip (5 files) unpacked; Cat.rar not supported20 files, rar held
Mon 23 Nov, 09:25One Claims.zip file at 275 characters; re-extracted to a short root20 files readable
Mon 23 Nov, 09:30Hashing finds 2 duplicates18 unique files
Mon 23 Nov, 09:40Reconciled: 18 matched, 3 in the rar, 1 not sentBroker asked for zip and premium history
Tue 24 Nov, 10:05Cat files re-sent as zip; 3 files scanned and unpacked21 of 22
Wed 25 Nov, 14:30Premium history arrives22 of 22; filed

Without stages 5 and 6, the underwriter would have priced on Monday with three cat files and the premium history missing.

How Does Insurnest Fit Around Zip File Submissions for Reinsurers?

Insurnest fits around zip file submissions for reinsurers after the unpack pipeline has done its work.

Reinsurance Email Intelligence does not unpack zip archives, scan for malware or open encrypted files.

Once files are unpacked, it reads PDFs, spreadsheets and claims files and identifies the attachments of a submission.

It extracts structure, premium, limits and claims history into one view and flags missing information.

See also submission acknowledgement automation.

Key Terms

  • Nested archive: An archive stored inside another archive, which must be unpacked separately.
  • File hash: A fingerprint of a file's contents; identical hashes mean identical files.
  • MAX_PATH: The 260-character path limit in the Windows API unless long paths are enabled.

Sources

Frequently Asked Questions

What are the stages of an unpack pipeline for zip file submissions?

The stages of an unpack pipeline for zip file submissions are receive, malware scan, unpack, name and path checks, duplicate detection, reconciliation to the email's list, and filing.

What should happen when a broker zip contains another zip?

When a broker zip contains another zip, the pipeline should unpack it too, scan each level and stop at a set depth, recording every file against the outer archive.

How should .7z and .rar archives in a reinsurance submission be handled?

.7z and .rar archives in a reinsurance submission should be opened only by a tool that supports them. If yours does not, ask the broker for a zip.

What should be done with an encrypted archive from a broker?

An encrypted archive from a broker should be flagged and held, because its contents cannot be scanned or indexed until it is opened under your password process.

Why do unzipped treaty files fail on the Windows 260-character path limit?

Unzipped treaty files fail on the Windows 260-character path limit when long folder names inside the zip are added to a long destination path.

Why do file names from a broker zip come out garbled?

File names from a broker zip come out garbled when they were stored in one character encoding and read in another, often UTF-8 names read as Code Page 437.

How can a zip bomb affect a reinsurer's intake?

A zip bomb can affect a reinsurer's intake by expanding a small file into enough data to fill disks or stall scanners. Set size and file-count limits.

How does Insurnest fit around zip file submissions for reinsurers?

Insurnest fits around zip file submissions for reinsurers after unpacking. Reinsurance Email Intelligence does not unpack zips; it reads the unpacked documents into one view.

Hitul Mistry

Hitul Mistry

CEO, Insurnest

An InsurTech leader with more than a decade of experience across insurance and technology, focused on solving business problems with the help of technology. Has worked with brokers, insurance carriers, and reinsurance firms across the India, UAE, and US markets.

View LinkedIn profile →
ShareLinkedInX

Read our latest blogs and research

Featured Resources

Reinsurance

Reinsurance Email Filing: Link Emails to Treaty and Claim

Reinsurance email filing done right: a filing taxonomy of email type, link key, filing location and owner, plus real misfiling examples and escalation rules.

Read more
Reinsurance

Incomplete Reinsurance Submissions: Catch Gaps Before Quote

Incomplete reinsurance submissions stall quotes in peak renewal weeks. See how reinsurers detect missing, inconsistent and stale data at intake, not mid-review.

Read more
Reinsurance

Submission Acknowledgement Automation: Confirm in Minutes

Submission acknowledgement automation confirms every broker submission fast. Get a stage-by-stage timeline, a message template and metrics for underwriting ops.

Read more

Meet Our Innovators:

We aim to revolutionize how businesses operate through digital technology driving industry growth and positioning ourselves as global leaders.

circle basecircle base
Pioneering Digital Solutions in Insurance

Insurnest

Empowering insurers, re-insurers, and brokers to excel with innovative technology.

Insurnest specializes in digital solutions for the insurance sector, helping insurers, re-insurers, and brokers enhance operations and customer experiences with cutting-edge technology. Our deep industry expertise enables us to address unique challenges and drive competitiveness in a dynamic market.

Get in Touch with us

Ready to transform your business? Contact us now!

We respond within one business day.