Skip to content

Files & Cloud Storage

File Helpers Integration

Zynk's File Helpers integration converts awkward text files into data the rest of a workflow can use. Built on the open source FileHelpers .NET library, its two tasks read fixed-width or delimited files, including order files with header and line rows, and write XML ready for import into Sage, Xero, Business Central or another connected system.

Available for

Capabilities may differ depending on the product.

Benefits

Why businesses connect File Helpers

Fixed-width and delimited layouts

Some banks and older finance systems still write fixed-width text, where each field sits at set character positions. File Helpers reads those layouts, and delimited ones, field by field, so nothing depends on a fragile spreadsheet macro.

Headers and lines kept together

Master Detail Converter handles files where a header row is followed by its item lines, such as an order and its products. The XML it produces keeps every set of lines under the right header, ready for a sales order import.

Conversion rules you control

Each layout is described in a C# class. Attributes set how every field is read, and built-in converters deal with dates, numbers and similar values, so an odd format is solved once instead of being fixed by hand on every run.

Bad rows set aside, not lost

Records that fail to convert go to a separate error file while the rest carry on. Your team sees exactly which lines were rejected, rather than a whole file failing because of one bad row.

Output every Zynk task understands

Most Zynk tasks take XML as input. Once a text file is converted, it can be transformed with XSLT and handed to import tasks for accounting, ERP, ecommerce or warehouse systems within the same workflow.

Capabilities

What you can do with File Helpers

Every task the Zynk File Helpers connector can run, grouped by the direction data moves.

Actions in File Helpers

Tasks Zynk can automate in File Helpers

2 tasks

  • Basic converter → in File Helpers
  • Master detail converter → in File Helpers

Need something that isn't listed?

Most File Helpers projects include at least one custom step. Our team builds it for you.

Talk to us

The problem

Why integrate File Helpers?

Not every system offers an API or a tidy CSV. Banks, older ERPs and some trading partners still produce fixed-width text, or files that mix header and line records. Getting that data into your accounts usually means a spreadsheet, a macro and the one person who knows how they fit together.

Without integration

  • Fixed-width files split into columns by hand in a spreadsheet
  • Order headers and lines losing track of each other during import
  • A whole file rejected because one row carries a bad date
  • A macro only one person understands, run whenever they remember
  • Each new file layout turning into a small development project

With Zynk

  • Fields are read from set positions by a class defined once
  • Master Detail Converter keeps each header with its own lines
  • The failing row goes to an error file and the rest import
  • Conversion runs inside a scheduled workflow with logging
  • A new layout means a new C# class, not a new integration

How it works

How the File Helpers integration works

  1. Step 1: Describe the layout

    A developer writes a C# class for the file's record layout, marking field positions or delimiters and any conversions. For header and line files, a second class and a short method tell the task which rows are headers.

  2. Step 2: Convert to XML

    Basic Converter or Master Detail Converter reads the input file, writes valid records to an XML output file and sends anything it cannot parse to the error file you nominate.

  3. Step 3: Map and import

    XSLT or Zynk's mapping tools reshape the XML into the format the target connector expects, and an import task sends it on to Sage 200, Xero, Business Central or wherever the data belongs.

  4. Step 4: Run it unattended

    The workflow picks up new files on a schedule, often straight from an FTP server or a network folder, converts them and archives the originals once the import has finished.

Example use cases for File Helpers integration

File Helpers and Sage 200

Convert order files that carry a header row followed by item lines, and import them into Sage 200 as sales orders with every line attached to the correct order.

From File Helpers to Sage 200:Sales orders

View the Sage 200 integration →

File Helpers and Xero

Turn fixed-width or delimited bank and payment files into XML, then import the lines into Xero as bank transactions without retyping a statement.

From File Helpers to Xero:Bank transactions

View the Xero integration →

File Helpers and Sage 50 UK

Read invoice files exported from an older billing or EPOS system, keep the header and line structure intact, and post them to Sage 50 as invoices.

From File Helpers to Sage 50 UK:Invoices

View the Sage 50 UK integration →

File Helpers and Microsoft Dynamics 365 Business Central

Convert journal exports from a legacy finance or payroll system into XML and import them into Business Central as journals, line for line.

From File Helpers to Microsoft Dynamics 365 Business Central:Journals

View the Microsoft Dynamics 365 Business Central integration →

File Helpers and Remote File Transfer (FTP, SFTP)

Download the flat files partners leave on an FTP or SFTP server, then pass each one straight to a converter in the same workflow.

From Remote File Transfer (FTP, SFTP) to File Helpers:Flat files

View the Remote File Transfer (FTP, SFTP) integration →

Find your integration →

File Helpers integration FAQs

What is File Helpers in Zynk?
File Helpers is a Zynk Workflow connector built on FileHelpers, a free, open source .NET library for reading fixed length and delimited records. Its two tasks, Basic Converter and Master Detail Converter, turn text files into XML that other Zynk tasks can map and import.
When should I use File Helpers instead of the CSV connector?
For a straightforward delimited file, the CSV connector's CSV To XML task is usually enough. File Helpers suits fixed-width layouts, files that need custom conversion logic, and files that mix header rows with item lines, because each layout is defined precisely in code.
Do I need to know C# to use File Helpers?
Yes, some. Each file layout is described in a C# class, so setup needs someone comfortable with C#, either on your team or ours. Once the class exists, the converter runs like any other Workflow task with no further coding.
What is a master-detail file?
It is a text file where one kind of row introduces a record and the rows after it hold that record's details, such as an order header followed by its order lines. Master Detail Converter supports two levels: a master row and its detail rows.
What happens to rows that fail to convert?
Each converter writes the records it cannot parse to an error file, and the valid records still reach the XML output. You can review or correct the failed rows and run them again, rather than reprocessing the entire file.
Can File Helpers read fixed-width bank files?
Yes. File Helpers reads fixed-width layouts where each field occupies set character positions, a format still used by some banks and older finance systems. Define the layout in a class once, and the converted XML can be mapped into Xero, Sage or another accounting system.

See what Zynk can automate for your File Helpers setup

Book a 20-minute call. We'll review your systems, flag the quick wins and outline a practical route to going live.

Book a callSee pricing →