WoluTools
Find a tool

Finance & Accounting

List the payments in a SEPA pain.001 XML file

Upload a pain.001 XML file. You get a CSV of every payment reference and amount plus basic format checks. It does not validate against the XSD schema or check IBANs.

or drop it here

XML · Up to 50,000 payments
Free account needed for your 3 free jobs a day

No file at hand? See the prepared example

Standard toolIncluded · 3 free jobs a dayFree: 3 jobs a dayPro: up to 200 jobs a day · €12.99/month or €89.99/year
  • XML
  • Up to 50,000 payments
Prepared result preview · fictional sample dataFictional SEPA Payment XML Amount Inventory fixture
Source
1 prepared source file · 191 bytes
Prioritized findings
  • Transactions: 1
  • Total: 10
  • Profile: pain.001 transaction inventory

transactions.csv · findings.csv · manifest.json

BringXML
GetPayment amount/reference CSV, bounded findings and manifest
PrivacyEncrypted source · 24-hour result

One clear job, from source to download

  1. 1

    Add the source

    Supported formats and limits are visible before the upload.

  2. 2

    Confirm the settings

    Review the exact source, options, units and access before processing.

  3. 3

    Inspect and download

    Check the preview and warnings, then unlock the complete package.

Checking the payments inside a SEPA pain.001 file

What you upload and where the limits are

You upload one pain.001 credit-transfer XML file with up to 50,000 payments. The tool reads the declared namespace and rejects a file that does not declare pain.001. Parsing is bounded, so XML that tries to pull in outside content or swell to a huge size while it is read is refused. A file over the payment ceiling stops with a clear message instead of giving you a partial list. Start with the fictional example if you want to see the output first.

What the download contains

You get transactions.csv with one row per payment instruction. Each row carries the reference, amount, currency and remittance information exactly as they appear in the XML. findings.csv lists what the format checks found. manifest.json is a short record of which file was read and what the job produced. To check the result, compare the totals in the preview with the total you expect, then spot-check a few rows against the source. Your original file is not changed.

What stays with you and your bank

There are no settings to choose. The tool only reports facts that are present in the file. It does not validate against the XSD schema, it does not verify IBAN checksums and it does not check that accounts exist. A clean run is not SEPA certification. Whether the file is accepted depends on the rules your bank applies, so treat the result as a review aid and keep the final check with your bank or your finance team.

Questions before you run it

Which SEPA message type does it read?

pain.001 credit-transfer XML. The declared namespace is checked and named in the findings, and a file that does not declare a pain.001 namespace is rejected rather than parsed on a guess.

Does a clean run mean my bank will accept the file?

No. This is an amount and reference inventory with bounded structural checks. It is not XSD validation and not SEPA certification, and acceptance depends on the rules your bank applies.

Are IBANs or account details verified?

No. Account identifiers are read as text for the inventory. Checksum verification and any check that an account exists sit outside what this tool does.

What is in transactions.csv?

One row per payment instruction, carrying the reference, amount, currency and remittance information as they appear in the XML. The totals shown in the preview are sums of those rows.

What protects against a hostile XML file?

Parsing is bounded, so external entity references and structures that expand on parse are refused instead of resolved. A file past the 50,000 payment ceiling stops with a clear message.