Reinsurance

CSV Submissions for Reinsurers: Seven Import Errors Fixed

On this page

Last reviewed: November 2026

The cedent's 9,400-row risk listing was a CSV. Double-clicked open, every row sat in column A, separated by semicolons.

Someone split it with Text to Columns. Policy numbers lost their leading zeros and two-thirds of the inception dates swapped day and month.

CSV submissions for reinsurers are plain-text exports of risk, premium or claims data, sent because cedent systems can produce them easily.

A CSV carries no data types, so every value is a guess until you set the rules on import.

This guide gives you seven import errors with symptom, cause, test and fix, detection formulas, a safe import routine and a CSV spec for cedents.

Key Takeaways

  • Never double-click a CSV. Import it through From Text/CSV with settings you choose.
  • Identifiers are text. Policy numbers, postcodes and long references must never be numbers.
  • Encoding is a setting. UTF-8 without a byte order mark can turn names into garbage.
  • Tie it out. Row count and premium totals must match the cedent's email.

What Are CSV Submissions for Reinsurers and Why Do They Break?

CSV submissions for reinsurers are plain-text tables, one record per line, with fields split by a delimiter.

They break because the file says nothing about types. Excel guesses the delimiter, encoding, numbers and dates from your local settings.

Which Import Errors Hit CSV Submissions for Reinsurers?

The import errors that hit CSV submissions for reinsurers fall into seven types, each with a clear test.

Why does a semicolon-delimited CSV open in one column?

A semicolon-delimited CSV opens in one column because the cedent's system used its regional list separator.

  • Symptom. All data in column A, with semicolons visible.
  • Cause. Microsoft notes the separator can change through Windows Region settings.
  • Test. Count delimiters per line; every line should match the header.
  • Fix. Import via From Text/CSV and pick the delimiter yourself.

Why do decimal commas break premium figures in a CSV import?

Decimal commas break premium figures in a CSV import when the file's number format differs from yours.

  • Symptom. 1.250,75 loads as text, or as 125,075.
  • Cause. The cedent writes a comma as the decimal mark.
  • Test. Sum the premium column and compare with the cedent's stated total.
  • Fix. Set the column's locale on import; never find-and-replace blindly.

Why do cedent names turn into garbled characters in a CSV?

Cedent names turn into garbled characters in a CSV when a UTF-8 file is read with a different encoding, such as Windows-1252.

  • Symptom. "Zürich" appears as "Zürich".
  • Cause. Microsoft says UTF-8 CSVs open normally if saved with a byte order mark (BOM).
  • Test. Search for "Ã" in text columns.
  • Fix. Without a BOM, use Data, Get Data, From Text/CSV and set UTF-8.

Why do policy numbers lose their leading zeros in a CSV?

Policy numbers lose their leading zeros in a CSV because Excel reads 00123 as the number 123.

  • Symptom. Policy 00451238 becomes 451238 and no longer matches the cedent's system.
  • Cause. Microsoft confirms Excel automatically removes leading zeros.
  • Test. Check text length against the cedent's format.
  • Fix. Set identifier columns to Text during import.

Why do long reference numbers end in zeros after a CSV import?

Long reference numbers end in zeros after a CSV import because Excel's numeric precision is 15 digits.

  • Symptom. A 16-digit claim reference ends in 0 or shows as 1.23E+15.
  • Cause. Excel specifications list number precision as 15 digits; later digits become zero.
  • Test. Flag any identifier column shown in scientific notation.
  • Fix. Import as Text; re-saving the damaged sheet cannot recover the digits.

Why do CSV dates and codes change after opening in Excel?

CSV dates and codes change after opening in Excel because it converts date-like text using your local date order.

  • Symptom. 03/04/2025 lands as 3 April or 4 March; class code 1-12 becomes a date.
  • Cause. Automatic conversion on open; newer Excel versions let you switch some of it off.
  • Test. Count dates with day 12 or lower; those are ambiguous.
  • Fix. Import dates as text, then convert with the cedent's stated format.

Why does a quoted line break split one CSV record into two?

A quoted line break splits one CSV record into two when the reading tool ignores quoting.

  • Symptom. More rows than records, with half-rows of text.
  • Cause. RFC 4180 says fields with line breaks, quotes or commas should be in double quotes.
  • Test. Row count against the cedent's control count.
  • Fix. Use an importer that honours quotes; ask cedents to strip line breaks from free text.

Which Formulas Detect CSV Import Errors in Treaty Data?

The formulas that detect CSV import errors in treaty data run on a raw text copy and on the imported sheet.

Assume raw lines in column A of a check sheet, and policy numbers in column B of the import.

Delimiters per line : =LEN(A2)-LEN(SUBSTITUTE(A2,";",""))
Mismatch with header: =C2<>C$1   (C holds the count above)
Garbled encoding    : =ISNUMBER(SEARCH("Ã",D2))
Lost leading zero   : =LEN(B2)<>8   (8 = cedent's policy length)
Stored as number    : =ISNUMBER(B2)  (identifier should be text)
Ambiguous date      : =AND(ISNUMBER(E2),DAY(E2)<=12)
Row tie-out         : =COUNTA(B:B)-1 = cedent's stated row count

Any TRUE in the first five checks stops the load. Fix the import settings, not the cells.

How Should Reinsurers Import CSV Submissions Safely?

Reinsurers should import CSV submissions safely by setting every rule before Excel can guess.

  1. Keep the original. Save the CSV untouched with the email.
  2. Use From Text/CSV. Data, Get Data, From Text/CSV; choose Transform Data.
  3. Set encoding and delimiter. UTF-8 unless the cedent says otherwise.
  4. Type identifiers as Text. Policy, claim, postcode and broker reference columns.
  5. Load dates as text. Convert with the cedent's stated format.
  6. Tie out. Row count and premium total against the covering email.
  7. Save a working copy. As .xlsx, with the import steps recorded.

For layout and unit problems inside workbooks, see Excel submission data extraction.

What CSV specification should reinsurers send to cedents?

The CSV specification reinsurers send to cedents should remove every guess listed above.

CSV SPECIFICATION FOR SUBMISSIONS
Encoding      : UTF-8 with BOM
Delimiter     : comma; text fields in double quotes
Decimal mark  : point, no thousands separators
Dates         : YYYY-MM-DD
Identifiers   : as issued, leading zeros kept
Free text     : no line breaks
Control email : row count, premium total, currency

Map the fields once with bordereau template mapping, and reuse it every period.

How Does Insurnest Fit CSV Submissions Into Intake?

Reinsurance Email Intelligence reads the submission email body and its PDFs, spreadsheets and other supporting files.

It extracts cedent, treaty structure, premium, limits and claims history into one submission view, and surfaces missing information.

Its page makes no CSV-specific claim, so test it on your cedents' own exports. The import checks above still apply.

Key Terms

  • Delimiter: The character that separates fields, usually a comma or semicolon.
  • Byte order mark (BOM): A marker at the start of a file that signals its Unicode encoding.
  • Control count: The row count the sender states, used to prove nothing was lost.

Sources

Frequently Asked Questions

What are CSV submissions for reinsurers and why do they break?

CSV submissions for reinsurers are plain-text exports of risk, premium or claims data. They break because the file carries no data types, so Excel guesses delimiters, encodings, numbers and dates.

Why does a semicolon-delimited CSV open in one column?

A semicolon-delimited CSV opens in one column because the cedent's system used its regional list separator. Import through From Text/CSV and choose semicolon as the delimiter.

Why do policy numbers lose their leading zeros in a CSV?

Policy numbers lose their leading zeros in a CSV because Excel treats 00123 as a number and drops the zeros. Import identifier columns as Text so they survive.

Why do long reference numbers end in zeros after a CSV import?

Long reference numbers end in zeros after a CSV import because Excel keeps only 15 digits of precision. Any digit after the 15th becomes zero, often shown in scientific notation.

Why do CSV dates and codes change after opening in Excel?

CSV dates and codes change after opening in Excel because it converts date-like text using local settings, so 03/04/2025 may become 4 March or 3 April and codes like 1-12 become dates.

Why does a quoted line break split one CSV record into two?

A quoted line break splits one CSV record into two when the reading tool ignores quoting. RFC 4180 says fields containing line breaks, quotes or commas should be enclosed in double quotes.

How should reinsurers import CSV submissions safely?

Reinsurers should import CSV submissions safely by never double-clicking, using From Text/CSV, setting encoding and delimiter, typing identifiers as Text, and tying row counts and totals to the cedent.

How does Insurnest fit CSV submissions into intake?

Insurnest Reinsurance Email Intelligence reads submission emails with PDFs, spreadsheets and other supporting files. Its page makes no CSV-specific claim, so test it on your own exports.

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

Excel Submission Data Extraction: Clean Cedent Spreadsheets

Excel submission data extraction turns messy cedent spreadsheets into clean underwriting data. See the common traps, key checks and a 6-step fix for reinsurers.

Read more
Reinsurance

Reinsurance Bordereaux Format Conversion: Pitfalls & Fixes

reinsurance bordereaux format conversion: a pitfalls table for CSV, Excel and XML files, a corrupted 19-digit policy number example and a file test plan.

Read more
Reinsurance

Policy Number Mapping Between Cedent and Reinsurer: Key Spec

policy number mapping between cedent and reinsurer: a field-by-field key map spec, the shortcuts that fail and a filled example of a reissued life policy.

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.