Validation of SCT, SDD, XCT and ICT files, address conversion to the ISO 20022 structured format, file generation from a CSV and reject diagnosis. Everything runs in your browser, with no integration project.
Swift postponed its deadline on 27 August, the EPC lifted its own on 9 September, and German banks are keeping 15 November for file formats. The full picture: both calendars, the XML fields, the CFONB mapping rules and the common traps.
Read the guideEvery code has its own page: the official meaning, what it means in plain words, the likely causes and the action to take. Here is everything published to date.
EBICS 2.5 and 3.0, from transport failures to signature refusals, with the standard label (EBICS_…) for each.
On every page: standard label, category, severity, EBICS versions concerned, description, common causes and recommended action.
The reasons seen on SEPA credit transfers and direct debits, with their CFONB equivalent and the message to pass on to the customer.
On every page: standard label and CFONB equivalent, plain-language meaning, likely causes, recommended action, who should act and whether a retry is possible.
Each module answers a concrete situation in an accounting department, a treasury team or a payments back office.
SCT, SDD, XCT, ICT: schema structure, mandatory tags, character set and field lengths. Every finding points to the tag and the line.
Explore validation →Mapping to ISO 20022 following the CFONB guide, with a confidence score, XML export, and the cases where the rule is not to split the line.
Explore the converter →A CSV export from your accounting tool becomes a compliant credit transfer or direct debit — or a fictitious test batch to exercise your own controls.
Explore the generator →With a pacs.002, a pain.002 or an EBICS return in hand, the reason becomes a real cause, a correction to apply and a message you can send to the customer.
Explore the diagnosis →A French free-format address becomes a compliant structured address, tag by tag. The three examples below are processed by the same rules as in the app.
No vague promises: here are the schemas, protocols and rules the tool relies on.
No commitment. Validation, file comparison and both reference sets stay free.
Validate, compare, generate a test file, consult the 72 codes.
Unlimited address conversion and file export. €250 per year.
CSV to SCT and SDD, rulebook check included. €220 per year.
The whole tool, no limits, resolutions included. €360 per year.
Founder of EDI Insight · ten years in cash management and EDI consulting
I spent a decade looking for the right rule in the right place before a mistake got expensive, between outdated documentation, emails and undocumented know-how. EDI Insight brings that work together in one tool: reference data, rulebooks and mapping rules, kept up to date and sourced. Read more.
Validation and the reference data are free. The rest opens with a magic link, no password.