ISO20022 Payment Investigation Request (camt.056)

This dataset provides a detailed record of ISO20022 payment investigation requests, including missing, duplicate, or incorrect payments. It tracks investigation status, involved parties, payment details, and resolution outcomes, making it ideal for payment tracking, operational risk management, and regulatory compliance in financial institutions.

  • last updated 29 Oct 2025
  • by GoMask
The brief that made it

Automated tracking and resolution of payment investigations

Sample rows

preview · 8 of 250 rows · all 26 columns
investigation_idstringinvestigation_typestringpayment_amountfloatpayment_currencystringoriginal_payment_idstringrequest_datedatetimerequester_namestringrequester_organizationstringrequester_contact_emailstringrequester_contact_phonestringbeneficiary_namestringbeneficiary_account_numberstringbeneficiary_bank_namestringbeneficiary_bank_bicstringpayment_datedatepayment_statusstringresolution_statusstringresolution_datedatetimereference_numberstringpriority_levelstringinitiating_bank_namestringinitiating_bank_bicstringcreated_atdatetimeupdated_atdatetimereason_descriptionstringresolution_notesstring
INV-20240601-001missing8700.5GBPPAY-10000012024-06-01T09:14:35ZMaria GonzalezGlobalPay Inc.maria.gonzalez@globalpay.com+44 7901 123456Arjun MehtaGB29NWBK60161331926819NatWest BankNWBKGB2L2024-05-27pendingopenblankGPI-INV-001highCitibankCITIUS332024-06-01T09:14:35Z2024-06-01T09:14:35ZPayment not received by beneficiary within expected settlement period.blank
INV-20240530-002duplicate42EURPAY-10000022024-05-30T15:54:21ZJohn SmithAcme Corpjohn.smith@acmecorp.com+1 212-555-0198Sophie DuboisFR1420041010050500013M02606BNP ParibasBNPAFRPP2024-05-28completedresolved2024-06-03T11:21:00ZACME-REF-20240530lowHSBCHSBCFRPP2024-05-30T15:54:21Z2024-06-03T11:21:00ZDuplicate payment detected for the same invoice number.Duplicate payment refunded to originator.
INV-20240525-003incorrect0USDPAY-10000032024-05-25T13:22:15ZDavid OseiWestAfricaRemitdavid.osei@westafrica.com+233 24 123 4567blankblankblankblank2024-05-20failedrejected2024-05-27T09:00:00ZWAR-INV-003criticalblankblank2024-05-25T13:22:15Z2024-05-27T09:00:00ZIncorrect beneficiary account resulted in payment rejection.Payment could not be processed due to invalid account details.
INV-20240515-004otherblankblankPAY-10000042024-05-15T08:40:00ZElena RossiAuditProelena.rossi@auditpro.com+39 06 1234567blankblankblankblankblankblankopenblankAUDIT-20240515-004mediumUniCreditUNCRITMM2024-05-15T08:40:00Z2024-05-15T08:40:00ZRegulatory audit requires tracking of payment for compliance review.blank
INV-20240428-005missing15250.6KRWPAY-10000052024-04-28T16:00:12ZChloe WangAsiaTradechloe.wang@asiatrade.com+86 10 1234 5678Lee Min HoKR610081000123456789Kookmin BankCZNBKRSE2024-04-24unknownin_progressblankASIA-INV-005highBank of ChinaBKCHCNBJ2024-04-28T16:00:12Z2024-04-28T16:00:12ZPayment missing in beneficiary account post SWIFT confirmation.blank
INV-20240320-006duplicate25BRLPAY-10000062024-03-20T10:17:49ZAva BrownQuickRemitava.brown@quickremit.com+1 415-555-8923Carlos PereiraBR1800000000001234567890Banco do BrasilBRASBRRJ2024-03-18completedresolved2024-03-25T15:43:00ZQR-20240320-006lowSantanderBSCHBRSP2024-03-20T10:17:49Z2024-03-25T15:43:00ZDouble payment processed due to system error.Second payment reversed successfully.
INV-20240402-007incorrect3400SEKPAY-10000072024-04-02T12:35:05ZLars JensenNordicTradelars.jensen@nordictrade.se+46 8 1234 5678Anna SvenssonSE3550000000054910000003SEB BankESSESESS2024-03-30failedresolved2024-04-09T09:15:00ZNT-REF-007criticalHandelsbankenHANDSESS2024-04-02T12:35:05Z2024-04-09T09:15:00ZPayment failed due to incorrect clearing code for beneficiary bank.Corrected clearing code and resubmitted payment.
INV-20240314-008otherblankblankP2024-03-14T09:18:00ZTest Userblanktest.user@domain.comblankblankblankblankblankblankblankopenblankTEST-REF-008criticalTest BankTESTBANK2024-03-14T09:18:00Z2024-03-14T09:18:00ZEdge case test for payment ID format validation.blank

What the 250 rows show

from the 250-row sample
  • 200.0median payment_amount
  • 4payment statuses
  • 4resolution statuses
  • 4priority levels
investigation_type250 rows by value
0408071missing28%65duplicate26%65incorrect26%49other20%
payment_amount201 rows, in bands of 1B
010020019800000000305B10Bpayment_amount →

Median 200.0, from 0.0 to 10,000,000,000.

payment_currency201 rows with a value · 49 left blank
  1. EUR53
  2. USD33
  3. GBP13
  4. RUB13
  5. KRW9
  6. BRL8
  7. SEK8
  8. INR6
  9. AED6
  10. JPY5
26 columns by typefrom the column list below
  • string 20
  • float 1
  • date 1
  • datetime 4

Columns

26 columns in three groups
blueprint · 26 columns
columntypedescriptionexample
Text 20 columns
investigation_idstringUnique identifier for the payment investigation requestuniqueINV-20240601-001
original_payment_idstringIdentifier of the original payment transaction under investigationPAY-1000001
investigation_typestringType of investigation (e.g., missing, duplicate, incorrect payment)missing · duplicate · incorrect · othermissing
requester_namestringName of the person or entity initiating the investigationMaria Gonzalez
requester_organizationstringOrganization of the requesteroptionalGlobalPay Inc.
requester_contact_emailstringEmail address of the requesterjohn.smith@acmecorp.com
requester_contact_phonestringPhone number of the requesteroptional+44 7901 123456
beneficiary_namestringName of the intended beneficiary of the original paymentoptionalArjun Mehta
beneficiary_account_numberstringAccount number of the beneficiaryoptionalGB29NWBK60161331926819
beneficiary_bank_namestringName of the beneficiary's bankoptionalNatWest Bank
beneficiary_bank_bicstringBank Identifier Code (BIC) of the beneficiary's bankoptionalNWBKGB2L
payment_currencystringCurrency code (ISO 4217) of the payment amountoptionalGBP
payment_statusstringCurrent status of the original payment (e.g., pending, completed, failed)pending · completed · failed · unknown · optionalpending
reason_descriptionstringDetailed description of the issue or reason for investigationPayment not received by b…
resolution_statusstringCurrent status of the investigation request (e.g., open, in_progress, resolved, rejected)open · in_progress · resolved · rejectedopen
resolution_notesstringAdditional notes or comments regarding the resolutionoptionalTest case closed.
reference_numberstringReference number for tracking the investigation (internal or external)optionalGPI-INV-001
priority_levelstringPriority assigned to the investigation requestlow · medium · high · critical · optionalhigh
initiating_bank_namestringName of the bank initiating the investigation requestoptionalCitibank
initiating_bank_bicstringBank Identifier Code (BIC) of the initiating bankoptionalCITIUS33
Numbers 1 column
payment_amountfloatAmount of the original payment under investigation0 or more · optional8700.5
Dates and times 5 columns
request_datedatetimeDate and time when the investigation request was initiated2024-06-01T09:14:35Z
payment_datedateDate when the original payment was madeoptional2024-05-27
resolution_datedatetimeDate and time when the investigation was resolved or closedoptional2024-06-03T11:21:00Z
created_atdatetimeTimestamp when the investigation record was created2024-06-01T09:14:35Z
updated_atdatetimeTimestamp when the investigation record was last updated2024-06-01T09:14:35Z

Use it for

  • median payment…200.0201 rowsrows by investigation…71miss…65dupl…65inco…49other

    A finance dashboard

    Payment_amount by investigation_type and a breakdown of payment_currency. Excel, Power BI or Tableau.

  • What pattern can you find in 250 rows?

    A class exercise

    Hand out the rows and one question. Everyone works from the same 250 rows.

  • A software demo

    Believable investigations with original_payment_id, investigation_type and request_date to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 26 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset250 rows26 columns
Yours1,000 rows26 columns

blueprint · iso20022-payment-investigation-request-camt056

Behind this dataset

Same schema. As many rows as you need.

These 250 rows came out of a blueprint — 26 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Case identification unique
  • Investigation type: missing, duplicate, incorrect
  • Original payment reference if known
  • Claimed amount specified
  • Investigation reason detailed
  • Supporting documentation referenced
  • Requested resolution action
  • Response deadline for investigation
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
iso20022-payment-investigation-request-camt056

More in Finance

Browse all
Also in FinanceISO20022 Payment Cancellation Request (camt.055)Loan Default Prediction DatasetTransaction Categorization DatasetAll 1,966 datasets

What should your data show?

Preview 20 rows free
No signup. No card.