Why Your Business Central Export Keeps Coming Out Flat

Why Changing the File Extension Doesn't Help

It's a common instinct: if the export looks like a text file but you need Excel, just rename it to .xlsx or .csv and see what happens. That doesn't work, because the extension only tells your computer how to open the file — it doesn't change what's actually written inside it. Business Central's Data Exchange framework, which most payment and statement exports run through, writes structured text based on how the export is configured. If the configuration only knows how to produce one flat structure, that's what you get regardless of what you name the file afterward.

The Real Fix Lives in How the Export Is Defined

A header-plus-detail export needs two separate structures defined, not one. One structure describes the header row — the batch total, the date, the account summary, whatever your target system expects at the top. A second, separate structure describes the repeating detail rows underneath it, each mapped to its own source data. When an export only has one structure defined, it can only ever produce one flat list — there's no mechanism for it to know where the header stops and the details begin.

This is a configuration change, not a code change, in most cases. But it does require someone who understands both the Data Exchange framework and the exact shape your target system needs — get the column mappings wrong on either the header or detail side and the file looks right but gets rejected by the bank or software on the other end.

When Configuration Genuinely Isn't Enough

Sometimes the requirement isn't actually a structured text file — it's a real Excel workbook, with formatting, multiple tabs, or formulas the receiving system expects. Business Central's built-in export framework writes text-based files; it was never meant to produce a styled workbook. If that's the real requirement, stop trying to bend the configuration into a shape it wasn't designed for. A small, purpose-built export — driven by the same underlying data, built directly against Excel — gets you the exact layout you need and is easier to maintain going forward than a configuration workaround that breaks the next time the target format changes slightly. This is the same category of work as the broader data export and integration builds we do — getting Business Central data into the exact shape another system needs, reliably.

• Structured text file (header + detail rows) → configuration change, no code needed
• True Excel workbook with formatting or multiple tabs → small custom build
• Either way, test against your bank's or software's actual file validator before going live — a file that "looks right" and a file that passes validation aren't always the same thing

What Good Looks Like

Once it's set up correctly, the export just works — every time, without anyone manually reformatting a file before it goes out the door. That's the actual goal: a payment or statement export your finance team can run and trust, not one they have to babysit and clean up by hand each cycle.