01What a pain.001 file contains, and why banks reject
The pain.001 is the ISO 20022 credit-transfer format: a header (ordering party, execution date), then a batch of transactions with IBAN, BIC, amount, currency and label. French banks accept it on their portals or via EBICS.
Rejections almost always come from data: wrong IBAN (an invalid check digit is detectable at entry), missing BIC, forbidden characters in labels, or mixed currencies in a batch declared SEPA. The SEPA service level only applies to euro transfers: a batch containing another currency must be handled differently.
02Organizing clean payment runs
The payment run replaces one-by-one transfers: once or twice a week, the list of approved due invoices becomes a single file deposited at the bank. Benefits: fewer manipulations, cash steered by due dates, and a clean audit history.
Upstream discipline makes file quality: bank details validated on the vendor record (IBAN by check digit, BIC by structure), and invoices eligible only once 3-way matching passes. You do not pay what was not ordered and delivered.
03Payment as the natural end of the purchasing cycle
In Procura, the run is built from approved invoices: selection by due date, automatic bank-detail checks, generation of a compliant pain.001.001.03, deposit on your bank portal, then settlement lettrage in accounting.
The same flow drives other rails by region: CPA-005 EFT for Canada, Mobile Money for West Africa. One run logic, correct local formats.