# What is pain.001 (customer credit transfer initiation)?

pain.001 is the ISO 20022 customer credit transfer initiation message: an XML file in which a company instructs its bank to make one or more payments, grouped by debit and by creditor, to be validated and reported back by the bank.

- Source: https://finray.tech/intelligence/glossary/pain-001/
- Published: 2026-11-21
- Updated: 2026-11-21
- Publisher: Finray Technologies Ltd, Cyprus Companies Registry HE 445903

---

## What is pain.001?

pain.001 is the ISO 20022 message called CustomerCreditTransferInitiation. A customer, usually a company, sends it to its bank to initiate one or more credit transfers. In the Swiss Payment Standards, the Swiss implementation guidelines published by SIX Interbank Clearing, the message applies the ISO schema pain.001.001.09 and is valid in the 2026 edition from 14 November 2026. The ISO 20022 family also contains pain.008 for direct debits and pain.002 for the status report that the bank returns.

This entry is a definition of the message. It makes no statement about any Finray product.

## How is a pain.001 structured?

The message has three levels, and the levels mirror how a bank thinks about a payment: one debit with many credits.

| Level | Element | Occurs | Content |
| --- | --- | --- | --- |
| A | Group header | Exactly once | Message identification, creation time, number of transactions, control sum, initiating party |
| B | Payment information | At least once | The debit side: debtor, debit account, requested execution date, payment method |
| C | Credit transfer transaction information | At least once per B level | The credit side: creditor, creditor account, amount and currency, remittance information |

A supplier run therefore has one A level, usually one B level per debit account and date, and one C level per supplier payment.

## What do the Swiss guidelines add to the ISO message?

The guidelines state that the ISO 20022 messages can be used universally and cover all currencies and eventualities, and that for country-specific purposes they are suitably modified, so that not all possibilities of the standard are used. Examples from the document are the permitted character set (a subset of UTF-8 without a byte order mark), rules for structured addresses, and a set of payment types that determine what is required for a given payment, for example a domestic payment, a SEPA payment or a cross-border payment. The guidelines also recommend that software supplies information about itself in the message.

## How do QR-bill references enter a pain.001?

An invoice that uses a [QR-bill](/intelligence/glossary/qr-bill/) carries a structured reference. Whoever pays the invoice, by hand or through software, places that reference in the creditor reference information of the credit transfer transaction. The camt guidelines describe the continuation: the creditor's bank forwards the reference, and it reappears in the [camt.054](/intelligence/glossary/camt-054/) or [camt.053](/intelligence/glossary/camt-053/) report of the creditor.

## What happens after a bank receives the file?

The recipient of a pain.001 returns a pain.002 status report to confirm the result of validation. Later, the debit shows on the payer's account in a camt statement or notification. The status report is not a booking; the camt messages are the record of what was booked.

## Worked example (illustrative, synthetic numbers)

A company prepares a payment file with one debit date and three suppliers:

| C level | Creditor | Amount (CHF) | Reference |
| --- | --- | --- | --- |
| 1 | Supplier A | 2,400.00 | QR reference from invoice |
| 2 | Supplier B | 815.50 | Creditor reference RF from invoice |
| 3 | Supplier C | 200.00 | Free-text message only |

The group header would show three transactions and a control sum of CHF 3,415.50, which is 2,400.00 plus 815.50 plus 200.00. If the control sum did not match the sum of the amounts, the guidelines state that an error in the control sum leads to rejection of the whole message. If the bank booked the debit as one batch entry of 3,415.50, the company's accounting would see a single line in its statement, and might need the notification message to see the three payments behind it.

## What controls apply?

| Risk | Control | Owner |
| --- | --- | --- |
| Payment to a wrong or altered account | Compare the creditor account with approved supplier master data before release | Accounts payable |
| Same file submitted twice | Unique message identification per file and a record of submitted files | Treasury |
| Unauthorised payment | Approval by a person other than the preparer, with a limit that does not depend on the preparer | Finance lead |
| Control sum or count mismatch | Recompute totals before sending, and compare them with the status report | Treasury |
| File changed between approval and sending | Approve a fingerprint of the exact file and refuse to send a changed one | Treasury |
| Wrong debit account or date | Show the debit account and execution date to the approver | Finance lead |

## Why do banks care about the details?

A payment file moves money, so banks validate it strictly. The guidelines state that for some errors the whole message is rejected, and they spell out the character set, the amount format and the identification of the parties. The practical lesson for anyone generating such files is to test with the bank's own validation service or a sample submission before the first live run, and to treat the bank's requirements as binding where they differ from the generic ISO message.

## What this entry does not say

This page defines the message and nothing more. It does not state that any Finray software creates, signs, sends or certifies pain.001 files, and readers should not infer such support from the presence of this entry. Where payment initiation matters for a project, the bank's own format requirements and test procedures are the authority.

## Related terms

[QR-bill](/intelligence/glossary/qr-bill/) is the invoice side that supplies the reference. [camt.053](/intelligence/glossary/camt-053/) and [camt.054](/intelligence/glossary/camt-054/) are the bank's reports on what was booked.

## Frequently asked questions

### What is a pain.001 file used for?

It is used to electronically initiate transfer orders from a customer to the remitting financial institution. A single file can hold many payments, for example a supplier run or a payroll batch, in the structure of group header, payment information and credit transfer transaction information.

### Which schema version do the Swiss guidelines name?

The Swiss Payment Standards, version 2.3 valid from 14 November 2026, apply pain.001 on the basis of the ISO 20022 schema pain.001.001.09. Earlier editions of the guidelines refer to the older schema version 2009, so the current guideline and the bank's own requirements should be checked.

### How does the bank answer a pain.001?

With a customer payment status report, message pain.002, which the recipient of a pain.001 returns to confirm the result of validation. Later account reports in camt messages show what was booked.

### What stops the same file from being paid twice?

Swiss financial institutions check for duplicates at least at the level of the message, using the message identification. The guidelines say that this identification must be assigned uniquely, and that most institutions check uniqueness over at least 90 days.

### Where does the QR-bill reference go in a pain.001?

The payer or the payer's software copies the structured reference from the QR-bill into the creditor reference information of the credit transfer transaction. The Swiss guidelines describe this as the way the creditor later recognises the payment.

## Sources

- [SIX Interbank Clearing: Swiss Implementation Guidelines for Customer-Bank Messages for Credit Transfer (pain.001), SPS 2026 version 2.3, valid from 14 November 2026](https://www.six-group.com/dam/download/banking-services/standardization/sps/ig-credit-transfer-sps-2026-en.pdf)
- [ISO 20022: message definitions catalogue (CustomerCreditTransferInitiation)](https://www.iso20022.org/iso-20022-message-definitions)
- [SIX Interbank Clearing: Swiss Implementation Guidelines for the QR-bill, version 2.4](https://www.six-group.com/dam/download/banking-services/standardization/qr-bill/ig-qr-bill-v2.4-en.pdf)
