File Format Requirements: Automatic Integration

Technical Specification for Data Exchange (CSV)

1. Format and Structure

• File type: Data must be provided as flat text files in CSV format (.csv).
• Field separator: The separator character used is a semicolon (;).
• Line breaks: Each data line must end with standard Windows line breaks, i.e., Line Feed and Carriage Return (CRLF / \r\n).
• Text qualifiers: Text qualifiers (such as quotation marks "text" or apostrophes 'text') must not be used around text fields.

2. Data Validation and Formatting

• Trimming: All data must be fully trimmed. No leading or trailing spaces are allowed.
• Data cleansing: Data must be cleaned of unintended whitespace characters. Double spaces, tabs (\t), or unexpected line breaks inside data fields are not permitted.

3. Encoding and Character Set (Charset)

The default is Windows-1252 (ANSI/Western European), unless otherwise specifically agreed. However, the system supports a range of other standards as listed below.

Overview of supported character sets:

• UTF: UTF-8, UTF-16LE, UTF-16BE, UTF-16
• Windows: Windows-1250, Windows-1251, Windows-1252 (Default), Windows-1253, Windows-1254, Windows-1255, Windows-1256, Windows-1257, Windows-1258, Windows-874
• ISO: ISO-8859-1, ISO-8859-2, ISO-8859-3, ISO-8859-4, ISO-8859-5, ISO-8859-6, ISO-8859-7, ISO-8859-8, ISO-8859-9, ISO-8859-15
• Others: ASCII, KOI8-R, Shift_JIS, EUC-JP, EUC-KR, Big5, GB2312, GB18030, LMBCS

Suggestion for Follow-up / Email to Partner (Agreement on Character Set):

If you are sending this directly to a recipient and want to clarify the last point (alignment on character set), you can add the following:

blockquote

"The above are our technical standard requirements for file deliveries. Please note that our default character set is set to Windows-1252. If your systems require or prefer a different character set – for example, UTF-8 – please inform us before testing begins so we can register and adjust the integration accordingly."