# SAP TRM Correspondence and Confirmations Source: https://gravam.com/blog/sap-trm-correspondence-and-confirmations Author: Tan Gravam Published: 2026-10-27 Reviewed: 2026-10-27 Summary: How SAP Treasury matches your confirmation to the counterparty's, and why an unmatched confirmation is still an open control. **Correspondence in SAP Treasury is the confirmation of the deal, matched to the counterparty's confirmation.** The [Transaction Manager](https://gravam.com/blog/sap-transaction-manager) already says that skipping it is how booking errors and fraud get through. This page is the queue that sentence assumes: what is matched, what is only printed, and which transaction you open on a Monday. ## Objects, not printouts SAP's correspondence framework holds correspondence as objects. A BAdI can check an object and match it to another, and the object can be assigned to a deal. That is a different thing from a PDF in a folder. The folder cannot tell you the object is still unmatched. The functions the Help pages name: - **Automatic matching** (`FTR_COMATCH`) links incoming and outgoing correspondence. The Help text says they are matched through their respective references, and that a user exit can also match an outgoing confirmation back to the original incoming one. - **Alerts** (`FTR_ALERT`) open for correspondence that is delivered and has no match, and for correspondence that is delivered and matched but still open for a counter-confirmation. An alert is not a report you might run. It is the item that says the control is open. - **Manual creation** (`FTR_COCREATE`) is how an object gets into the framework when the counterparty sent a fax, or nothing. If every exception is created by hand and never matched, you have rebuilt the folder inside the system. - **Import** (`FTR_IMPORT`) is how an incoming message arrives. A confirmation that never enters the system cannot be matched, and the alert will not see it either. The community transaction list is a member post, not a release note. The names above are the ones that list and the Help pages agree on. Before you put them in a training guide, confirm them on your system. S/4HANA has moved other TRM transactions. Correspondence is one of the items the [ECC-to-S/4HANA migration](https://gravam.com/blog/migrating-sap-treasury-ecc-to-s4hana) simplification list tells you to re-test, not to assume survived unchanged. ## What "done" means A confirmation is done when it is matched, or when a person has closed the alert with a reason. Generated is not done. Sent is not done. Delivered and waiting for a counter-confirmation is explicitly still an alert in SAP's own description. The operating rules that make the transaction worth having: 1. Every external deal produces a correspondence object. Internal deals you have chosen not to confirm are on a written list, not a habit. 2. Incoming confirmations are imported the day they arrive. A mailbox is not the framework. 3. Someone works `FTR_ALERT` on a cycle shorter than the deal's settlement. An unmatched FX spot found after value date is a reconciliation item, not a confirmation break. 4. A manual match has a reason. The exit that auto-matches on company code and deal number will also auto-match the wrong pair if the reference is sloppy. Review what it matched, not only what it left. 5. The count of open alerts is a treasury operations number, next to the unfixed flows. It is not an IT log. ## What I left out, on purpose - **The full customising tree** for correspondence types, output forms and partner determination. It is release-specific and it is long. The control fails in the queue, not in the form layout. - **A field-by-field map of a SWIFT MT300.** The confirmation's content has to agree with the deal. The message standard is a separate page the day a project is mapping one. This page is the match. - **Legal effect of a confirmation under an ISDA.** That is the master agreement. The system control is whether your record and theirs are the same deal. Generate the confirmation if you want. The control is the match, and the aged alert is how you know you do not have it. *** _See also [the SAP Transaction Manager](https://gravam.com/blog/sap-transaction-manager), [the TRM period-end close](https://gravam.com/blog/sap-trm-period-end-close) and [the ECC to S/4HANA treasury migration](https://gravam.com/blog/migrating-sap-treasury-ecc-to-s4hana)._ ## Primary sources SAP Treasury and Risk Management correspondence framework, as described in SAP Help for the correspondence functions (matching, alerts, the correspondence framework) and in the transaction list published on SAP Community. The Help pages consulted are the older SFIN documentation set, not a current S/4HANA FPS page read in full. Transaction names below are the ones those pages and that list actually use: FTR_COMATCH, FTR_ALERT, FTR_COCREATE, FTR_IMPORT. Confirm the transaction on your release before you train on it. - SAP Help — Correspondence framework — accessed 2026-10-27 — https://help.sap.com/doc/fe0eda531198434de10000000a174cb4/700_SFIN3E%20006/en-US/001f59060464450eb9b0f02b3b1f5c00.html - SAP Help — Individual functions: automatic matching of correspondence (FTR_COMATCH) — accessed 2026-10-27 — https://help.sap.com/doc/fe0eda531198434de10000000a174cb4/700_SFIN3E%20006/en-US/700cda531198434de10000000a174cb4.html - SAP Help — Correspondence alerts — accessed 2026-10-27 — https://help.sap.com/doc/fe0eda531198434de10000000a174cb4/700_SFIN3E%20006/en-US/adacd9d3cc474502b00841a69112a191.html - SAP Community — Major transactions used in TRM (member list, including FTR_COMATCH, FTR_ALERT, FTR_IMPORT) — accessed 2026-10-27 — https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-members/major-transactions-used-in-trm/ba-p/13241776 ## Questions this article answers **Q: What is correspondence in SAP Treasury?** The confirmation you send the counterparty, and the confirmation they send you, held as correspondence objects against the deal. Matching them is the control that the deal you booked is the deal they booked. Printing a confirmation and filing it is not the same control. **Q: Which transaction matches treasury confirmations?** FTR_COMATCH matches unmatched incoming and outgoing correspondence. FTR_ALERT is the monitor for items that are delivered and still unmatched, and for items that are matched but still waiting on a counter-confirmation. FTR_IMPORT brings incoming messages in. FTR_COCREATE creates a correspondence object by hand when no message arrived. Check the names on your release. The SAP Help pages that describe this framework are from an older SFIN documentation set. **Q: Why do unmatched confirmations matter?** A deal that only exists on your side, or only on theirs, is either a booking error or a deal one of you does not have. The Transaction Manager page already names skipped confirmations as the control that catches booking errors and fraud. The queue of unmatched items, aged, is that control. A confirmation that was generated and never matched is paper.