SEPA credit transfer, supplier invoice with an RF creditor reference.
A payment initiation file for France on the sepa-credit-transfer rail, shipped in pain.001.001.03, pain.001.001.09, generated and checked by pain001 0.0.70. It is a synthetic example built from the public scheme rulebooks: no real party, account or bank guideline behind it.
Files#
| Edition | Payment file | ISO 20022 JSON twin | Provenance record |
|---|---|---|---|
pain.001.001.03 |
fr.sepa.sct-supplier.pain.001.001.03.xml | fr.sepa.sct-supplier.pain.001.001.03.iso.json | fr.sepa.sct-supplier.pain.001.001.03.provenance.yaml |
pain.001.001.09 |
fr.sepa.sct-supplier.pain.001.001.09.xml | fr.sepa.sct-supplier.pain.001.001.09.iso.json | fr.sepa.sct-supplier.pain.001.001.09.provenance.yaml |
The twin is the same payment in the ISO 20022 Registration Authority's JSON convention, lossless in both directions; its JSON Schema (2020-12) is published per edition: pain.001.001.03, pain.001.001.09. An agent can produce a twin that validates against the schema and hand it to the library to render the XML.
Run it in your browser#
Open this scenario in the demo: the pain001 library loads in a Python runtime in your browser, rebuilds the file from the 1 record(s) below, checks it against the sepa-sct rulebook and the official XSD, and shows the JSON twin. Nothing leaves your machine.
The flat records the library rebuilds it from (the CSV pipeline's own column names):
id,date,nb_of_txs,ctrl_sum,initiator_name,payment_information_id,payment_method,batch_booking,service_level_code,requested_execution_date,debtor_name,debtor_account_IBAN,debtor_agent_BIC,charge_bearer,payment_id,payment_amount,currency,creditor_agent_BIC,creditor_name,creditor_account_IBAN,initiator_postal_code,initiator_town_name,initiator_country_code,initiator_address_line,initiator_id,initiator_id_scheme,debtor_postal_code,debtor_town_name,debtor_country_code,debtor_address_line,debtor_id,debtor_id_scheme,creditor_postal_code,creditor_town_name,creditor_country_code,purpose_code,creditor_reference,creditor_reference_type,creditor_reference_issuer,payment_currency
ADR-SCT-20260921-01,2026-09-21T08:00:00,1,2340.80,Ateliers du Rhone SAS,SCT-20260921-01,TRF,false,SEPA,2026-09-22,Ateliers du Rhone SAS,FR893354380052HVVA82N96W433,SRKHFRC0,SLEV,FACT-2026-09-0117,2340.80,EUR,RGMPFRJ0,Fournitures Industrielles Nord,FR45661040549856QM2V1TIAZ01,69002,Lyon,FR,Rue de la Republique 42,83201234500017,SREN,69002,Lyon,FR,Rue de la Republique 42,83201234500017,SREN,59000,Lille,FR,GDDS,RF18539007547034,SCOR,ISO,EURHow the library checked it#
- Official XSD: passed.
- ISO message definition rules: passed.
- Rail profile
sepa-sct: passed. - Rail profile
anti-duplicate: passed.
Confidence derived: built from the public rulebook or implementation guide; no published sample was available to compare.
Where the content comes from#
- CFONB, Guide d'utilisation du virement SEPA client-banque V2.6 (Jan 2023) (read 2026-09-10)
- EPC132-08 Customer-to-PSP SCT Implementation Guidelines 2025 v1.0 (read 2026-09-10)
SHA-256 of each file is in its provenance record. Your bank's own usage guideline is not represented here: apply it privately with the library's overlay tooling.