I'm stuck on a SEPA Direct Debit export that consistently fails with:
Only transactions in euro (EUR) are allowed.
This shows up in File Export Errors on the Direct Debit Collect. Entries page when I try to Export Direct Debit File — and it's happening on every entry I've tried, across multiple separately-created test invoices and collections.
Environment
- Business Central version 28.3.52162.53387
- Sandbox, CRONUS DE-based test company
- SEPA format: pain.008.001.08
- Company LCY: EUR
Error call stack
"SEPA DD-Fill Export Buffer" (CodeUnit 1231).FillExportBuffer line 29
"SEPA DD pain.008.001.08" (XmlPort 1011).InitData line 7
"SEPA DD-Export File" (CodeUnit 1230).Export line 13
"Direct Debit Collection Entry" (Table 1208).ExportSEPA line 7
"Direct Debit Collection" (Table 1207).Export line 6
What I've already confirmed is set to EUR
I've methodically checked every place I can find a Currency Code field, and all of them are consistent:
- General Ledger Setup → LCY Code
- Currencies → EUR → Exchange Rates (valid rate line exists)
- Sales Invoice header Currency Code (tested both explicit "EUR" and blank)
- Customer Card Currency Code
- Customer Bank Account Currency Code
- Company Bank Account (collecting account) Currency Code
- Direct Debit Collect. Entries Currency Code column (displays EUR correctly on-screen)
- The Currency Code filter on the Create Direct Debit Collection dialog (tested both set to EUR and left blank)
Despite all of this, the export still fails on this exact check every time.
One possibly-related detail
The same test company shows a separate, unrelated banner on customer records: "Currency Code EUR must be coupled to a record in Dataverse." This suggests an active Dataverse/CRM sync where EUR isn't fully coupled. I don't know if this is connected to the SEPA export validation, but both issues point at EUR not being fully "recognized" somewhere outside the standard UI fields — so I'm mentioning it in case it's relevant.
My question
Has anyone run into this specific error with Currency Code already confirmed as EUR everywhere visible in the UI? Is there another setting — possibly not exposed directly, or specific to CRONUS DE demo data — that Codeunit 1231's FillExportBuffer, line 29, is actually checking? Any pointers toward what that condition is validating would really help, since I've run out of obvious places to check.
Thanks in advance for any guidance.

Report
All responses (
Answers (