ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

camt.087 — Request to Modify Payment

Request sent to a bank traversed by a payment (pacs.008 / pacs.009) to modify certain parameters before effective execution: amount, value date, charges, references. Allows correcting an in-flight detected error before settlement. Mandatory response via camt.029 (Resolution of Investigation).

Purpose: modify in-flight payment

camt.087 is used for cases where an error is detected after pacs.008 is sent but before final settlement on the correspondent side: wrong amount, value date to correct, wrong SHA/OUR/BEN, beneficiary IBAN with typo. Without camt.087, the only alternative is camt.056 (cancellation) followed by a new pacs.008 — heavier. camt.087 allows "in-flight" modification.

XML structure

Wrapped in <ReqToModfyPmt>. Components: Assgnmt (header), Case (investigation file), Undrlyg (original payment reference), Mod (requested modifications).

ElementRole
Case/IdFile identifier (reused in the camt.029 response).
OrgnlUETRUUIDv4 of payment to modify — SWIFT gpi key.
OrgnlEndToEndIdPayment end-to-end identifier.
Mod/ReqdAmtNew requested amount.
Mod/ReqdExctnDtNew execution date.
Mod/ChrgBrNew charge bearer (DEBT, CRED, SHAR).
Mod/AddtlInfJustification for the modification.

Example: modification request

BNP Paribas asks Citi US to correct amount USD140k → USD125k before settlement:

xml camt-087-modify-request.xml
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.087.001.10">
  <ReqToModfyPmt>
    <Assgnmt>
      <Id>MOD-CBPR-20260519-001</Id>
      <Assgnr>
        <Agt><FinInstnId><BICFI>BNPAFRPP</BICFI></FinInstnId></Agt>
      </Assgnr>
      <Assgne>
        <Agt><FinInstnId><BICFI>CITIUS33</BICFI></FinInstnId></Agt>
      </Assgne>
      <CreDtTm>2026-05-19T11:30:00+02:00</CreDtTm>
    </Assgnmt>
    <Case>
      <Id>CASE-BNPP-20260519-001</Id>
      <Cretr>
        <Agt><FinInstnId><BICFI>BNPAFRPP</BICFI></FinInstnId></Agt>
      </Cretr>
    </Case>
    <Undrlyg>
      <IntrBk>
        <OrgnlGrpInf>
          <OrgnlMsgId>BNPP-CBPR-20260519-001</OrgnlMsgId>
          <OrgnlMsgNmId>pacs.008.001.10</OrgnlMsgNmId>
        </OrgnlGrpInf>
        <OrgnlInstrId>BNPP-INSTR-2026001</OrgnlInstrId>
        <OrgnlEndToEndId>INV2026-187</OrgnlEndToEndId>
        <OrgnlUETR>1a2b3c4d-5e6f-7890-abcd-ef1234567890</OrgnlUETR>
      </IntrBk>
    </Undrlyg>
    <Mod>
      <ReqdAmt>
        <Amt Ccy="USD">125000.00</Amt>
        <CdtDbtInd>CRDT</CdtDbtInd>
      </ReqdAmt>
      <ReqdExctnDt>
        <Dt>2026-05-20</Dt>
      </ReqdExctnDt>
      <AddtlInf>BENEFICIARY REQUESTED CORRECTION OF INVOICE AMOUNT FROM USD140000 TO USD125000 - PLEASE MODIFY PRIOR TO POSTING</AddtlInf>
    </Mod>
  </ReqToModfyPmt>
</Document>

Common pitfalls

  • camt.087 after settlement: too late. Once payment settled on correspondent side, only path is pacs.004 (Payment Return) or bilateral recovery.
  • OrgnlUETR missing: traversed bank cannot locate the payment in its gpi engine.
  • Mod without Case: every modification must open a unique Case for audit traceability (FATF / FinCEN).
  • Confusion camt.087 vs camt.056: camt.056 cancels entirely, camt.087 modifies while keeping the payment. Choose per intent.
  • camt.027 — Claim Non Receipt (variant: payment not received).
  • camt.029 — Resolution of Investigation (mandatory response to camt.087).
  • camt.056 — FI to FI Payment Cancellation Request (cancel entirely).
  • pacs.028 — FI to FI Payment Status Request.
  • pacs.004 — Payment Return (post-settlement case).