FTR_CREATE — Create Financial Transaction (Treasury)
FTR_CREATE creates financial transactions in SAP Treasury and Risk Management, for example fixed-term deposits, loans, foreign exchange spot and forward deals. The transaction captures counterparty, amounts, dates and conditions, then moves through settlement and posting in back office steps, so treasury deals are recorded, controlled and accounted for in SAP.
Creates treasury deals such as money market, foreign exchange and securities transactions in SAP Treasury and Risk Management.
Published 31 Oct 2026· 474 words
What FTR_CREATE is for
Treasury deals need to be captured consistently so they can be confirmed with counterparties, settled, paid and accounted for, and so their risk can be measured. FTR_CREATE is the front office entry point for many product types; follow-up activities like rollovers, settlements and terminations are done on the same transaction later.
When it is used
Treasury front office staff use it when a deal is concluded with a bank, often on the same day the trade is agreed by phone or on a trading platform. Back office and accounting rely on its data for confirmations, payment and posting. It is also used in testing when Treasury and Risk Management is introduced or extended to new product types.
How it is used in practice
Choose company code, product type and transaction type, enter the counterparty, amounts, interest or rate conditions and dates, and save. Depending on configuration, the deal then needs settlement and correspondence steps before posting. Changes and follow-up activities are done with FTR_EDIT, and accounting entries are created by the treasury posting functions.
Fields and objects that matter
- Company code, product type and transaction type
- Counterparty business partner and contract dates
- Nominal amount, currency, interest conditions or exchange rate
- Status of the transaction and its activities
- Payment details and standing instructions used at settlement
- Portfolio or trader assignment used for reporting and limits
How to prove it in the data
For a new fixed-term deposit, check that the transaction shows the agreed principal, rate and dates, that the confirmation with the bank matches, and that after posting the accounting documents show the principal movement and accrued interest on the configured accounts.
ECC vs S/4HANA
SAP Treasury and Risk Management is available in S/4HANA, with Fiori apps for many treasury processes alongside the classic transactions. Deal data also feeds cash management, so a captured deposit or loan appears in liquidity reporting.
Common pitfalls and how they show up
Treasury errors are expensive and visible to banks and auditors, so the controls around deal entry matter most.
- Deals entered with wrong counterparty or settlement instructions
- No separation between deal entry and settlement
- Product types configured without the needed accounting postings
- Follow-up activities forgotten, such as rollovers or interest settlements
- Deals captured after the cut-off, so the day's cash position is wrong
Whose problem this is
Owned by treasury front office for entry and back office for settlement and confirmations, which should be separate people. Accounting owns the postings and their review, and risk management uses the same deals for exposure and hedge reporting.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Learn this properly
Lessons and topics
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ftr-createERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.