[{"data":1,"prerenderedAt":298},["ShallowReactive",2],{"blog-\u002Fblog\u002Fsap-trm-period-end-close":3,"blog-related-\u002Fblog\u002Fsap-trm-period-end-close":270},{"id":4,"title":5,"audience":6,"body":10,"cluster":221,"conversionGoal":222,"cornerstone":223,"date":224,"description":225,"draft":223,"extension":226,"factCheckedAt":224,"faq":227,"featured":223,"language":237,"meta":238,"minRead":239,"navigation":240,"order":241,"originalAsset":237,"path":242,"pillar":243,"primaryKeyword":244,"publicationOrder":245,"relatedProject":237,"releaseScope":246,"reviewCycle":247,"reviewMethod":248,"reviewStatus":249,"reviewedAt":224,"reviewedBy":250,"searchIntent":251,"seo":252,"sources":253,"stem":263,"tags":264,"type":268,"updated":224,"__hash__":269},"blog\u002Fblog\u002Fsap-trm-period-end-close.md","SAP TRM Period-End Close: The Posting Sequence",[7,8,9],"sap-treasury-consultant","treasury-accountant","financial-controller",{"type":11,"value":12,"toc":213},"minimark",[13,21,30,35,102,105,108,112,115,122,125,128,132,135,155,158,162,187,190,193],[14,15,16,20],"p",{},[17,18,19],"strong",{},"The TRM close is a sequence, not a list of transactions you may run in any order."," Operative flows first. Derived flows next. Accruals after that. Valuation last. Run them out of order and the subledger will still post something. It will post the wrong generation of the derived flow, and the reversal will not be in the selection you usually use.",[14,22,23,24,29],{},"This is the process page next to ",[25,26,28],"a",{"href":27},"\u002Fblog\u002Fsap-trm-position-management-and-valuation","position management and valuation",". That page is why the posting is hard. This one is the order in which a month is actually closed.",[31,32,34],"h2",{"id":33},"the-four-steps","The four steps",[36,37,38,54],"table",{},[39,40,41],"thead",{},[42,43,44,48,51],"tr",{},[45,46,47],"th",{},"Step",[45,49,50],{},"Transaction",[45,52,53],{},"What it posts",[55,56,57,69,80,91],"tbody",{},[42,58,59,63,66],{},[60,61,62],"td",{},"1",[60,64,65],{},"TBB1, then TPM10",[60,67,68],{},"Operative flows. TPM10 also posts or reverses flows still sitting at ToF (to be fixed) or ToR (to be reversed), and it reverses documents TBB1 already posted.",[42,70,71,74,77],{},[60,72,73],{},"2",[60,75,76],{},"TPM18",[60,78,79],{},"Derived business transactions. Realized FX gain and loss is the one the close cares about. Derived flows are generated from the operative flows and they depend on the valuation area.",[42,81,82,85,88],{},[60,83,84],{},"3",[60,86,87],{},"TPM44",[60,89,90],{},"Accrued and deferred interest on outstanding deals. On older enhancement packages this step is TBB4.",[42,92,93,96,99],{},[60,94,95],{},"4",[60,97,98],{},"TPM1",[60,100,101],{},"Valuation, the unrealized result. Where the Market Risk Analyzer is active, OTC net present values are generated first (TPM60) and then TPM1 posts.",[14,103,104],{},"Hedge-accounting deals should sit on their own product types. Their valuation is not the reset procedure you use for the trading book. If someone runs one TPM1 variant for both, the hedge book is either skipped or valued as if it were a trading position. Neither is a close.",[14,106,107],{},"Fixing a flow in the treasury subledger is not the same as posting it to FI. Update types can be configured as not relevant for posting. A transfer between security accounts inside one account group can fix in the subledger and post nothing to the general ledger. A transfer across account groups posts to FI. The close checklist has to say which of those your position management level actually does, or accounting will wait for a document that treasury never configured.",[31,109,111],{"id":110},"why-tpm18-before-tbb1-looks-like-it-worked","Why TPM18 before TBB1 looks like it worked",[14,113,114],{},"SAP Support's reply on the community, in the thread about a derived flow that could not be reversed, is the part teams do not believe until they have done it:",[14,116,117,118,121],{},"Posting derived flows with TPM18 before the operative flows is standard. During TBB1 the operative posting recalculates the derived flows, because the rate may have moved. The derived flows you already posted are set to \"to be reversed\". New derived flows are generated. You reverse the old ones with TPM10, and the selection that finds them is ",[17,119,120],{},"Limit by Subledger Position",". The selection people habitually use does not show them, which is why the error reads as \"flow not found\" rather than \"you posted the derived flow too early\".",[14,123,124],{},"If you do not want that order to be possible, SAP note 944311 is a soft modification. The code may already be in the system. It does nothing until you activate it the way the note describes. After that, TPM18 will not post derived flows before the operative flows are posted. Decide this in design, not in the first close. A close that depends on everyone remembering the sequence will fail in December.",[14,126,127],{},"There is a second, related rule from the same era of the product: if the position decreased during the period, or part of it matured, realized gain and loss has to be booked before unrealized valuation. That is TPM18 before TPM1. Valuation without the realized piece books the wrong residual.",[31,129,131],{"id":130},"what-the-close-owner-actually-checks","What the close owner actually checks",[14,133,134],{},"A transaction list is not a close. The person who signs the pack looks at four reconciliations:",[136,137,138,142,145,152],"ul",{},[139,140,141],"li",{},"Every operative flow that was due in the period is fixed. ToF left in the period is an unposted cash movement.",[139,143,144],{},"Derived flows from this generation are posted, and the previous generation was reversed. Two TPM18 documents for one deal is the symptom from the community thread.",[139,146,147,148,151],{},"Accruals in TPM44 agree to the FI accrual accounts, by valuation area. Parallel valuation areas do not share one accrual account. ",[25,149,150],{"href":27},"The posting design"," is what makes them different.",[139,153,154],{},"TPM1's unrealized result is the movement after realized, not instead of it.",[14,156,157],{},"None of those four is a traffic light inside the transactions. They are a report the close owner keeps, or they are a surprise in the audit.",[31,159,161],{"id":160},"what-i-left-out-on-purpose","What I left out, on purpose",[136,163,164,170,181],{},[139,165,166,169],{},[17,167,168],{},"A release-by-release close script."," TBB4 versus TPM44, and whether TPM60 is in your scope, depends on the enhancement package and on whether the Market Risk Analyzer is active. The sequence above is the one that survives those differences.",[139,171,172,175,176,180],{},[17,173,174],{},"Hedge-accounting effectiveness and the hedge ratio."," That is ",[25,177,179],{"href":178},"\u002Fblog\u002Fhedge-effectiveness-testing","hedge effectiveness testing",", not a step you fold into TPM1.",[139,182,183,186],{},[17,184,185],{},"Note 944311's activation steps."," I am not reproducing a soft modification from memory. Read the note on your release before you switch the sequence from \"possible\" to \"blocked\".",[14,188,189],{},"The subledger will post in whatever order you ask. The close is the decision to ask in one order, every month, and to reverse the generation you no longer mean.",[191,192],"hr",{},[14,194,195],{},[196,197,198,199,202,203,207,208,212],"em",{},"See also ",[25,200,201],{"href":27},"SAP TRM position management and valuation",", ",[25,204,206],{"href":205},"\u002Fblog\u002Fsap-transaction-manager","the SAP Transaction Manager"," and ",[25,209,211],{"href":210},"\u002Fblog\u002Fhedge-accounting-explained","hedge accounting",".",{"title":214,"searchDepth":215,"depth":215,"links":216},"",2,[217,218,219,220],{"id":33,"depth":215,"text":34},{"id":110,"depth":215,"text":111},{"id":130,"depth":215,"text":131},{"id":160,"depth":215,"text":161},"transactions","topic-hub",false,"2026-10-27","The SAP TRM close order: operative flows, derived transactions, accruals, then valuation, and what breaks if TPM18 runs before TBB1.","md",[228,231,234],{"question":229,"answer":230},"What is the period-end sequence in SAP TRM?","Post the operative flows first (TBB1, and TPM10 where a flow is still to be fixed or reversed). Then fix derived business transactions with TPM18, including realized foreign-exchange gains and losses. Then post accruals and deferrals with TPM44 (TBB4 on older releases). Then run valuation with TPM1. If the Market Risk Analyzer is in use, net present values for OTC deals are generated before that valuation posts. Hedge-accounting positions are valued on their own product types; the reset procedure does not value them.",{"question":232,"answer":233},"What is the difference between TPM10 and TPM18?","TPM10 fixes, posts or reverses position business transactions in the treasury subledger, including reversing a document that TBB1 posted. TPM18 fixes derived business transactions, which the system generates from the operative flows and which depend on the valuation area. Realized foreign-exchange gain and loss is the derived flow people mean when they say 'run TPM18'.",{"question":235,"answer":236},"Can TPM18 be run before TBB1?","Yes, unless you have activated SAP note 944311. SAP Support has described that order as standard: posting the operative flow in TBB1 recalculates the derived flows, sets the previously posted derived flows to 'to be reversed', and generates new ones. You then reverse the old derived flows with TPM10, using 'Limit by Subledger Position'. Activating 944311 stops TPM18 from posting derived flows before the operative flows are posted.",null,{},4,true,6.4,"\u002Fblog\u002Fsap-trm-period-end-close","sap-treasury","SAP TRM period end close",256,"SAP Treasury and Risk Management on ERP and S\u002F4HANA. TBB1 posts operative flows. TPM10 fixes, posts or reverses subledger flows, including reversals of TBB1 documents. TPM18 fixes derived business transactions. TPM44 posts accruals and deferrals (TBB4 on older releases). TPM1 posts valuation. Claims about the order were checked on 2026-10-27 against SAP Community threads in which SAP Support described TPM18-before-TBB1 as standard unless note 944311 is activated, and against KBA 1829413. This is not a substitute for the close checklist in your own release.","annual","editorial-and-factual","reviewed","Tan Gravam","informational",{"title":5,"description":225},[254,257,260],{"title":255,"url":256,"accessed":224},"SAP KBA 1829413 — How to post or reverse flows with status ToF or ToR","https:\u002F\u002Fuserapps.support.sap.com\u002Fsap\u002Fsupport\u002Fknowledge\u002Fen\u002F1829413",{"title":258,"url":259,"accessed":224},"SAP Community — Could not find flow to be reversed in TPM10 (SAP Support reply on TPM18 before TBB1)","https:\u002F\u002Fcommunity.sap.com\u002Ft5\u002Fenterprise-resource-planning-q-a\u002Fcould-not-find-flow-to-be-reversed-in-tpm10\u002Fqaq-p\u002F7040233",{"title":261,"url":262,"accessed":224},"SAP Community — Differences between TPM10 and TPM18","https:\u002F\u002Fcommunity.sap.com\u002Ft5\u002Fenterprise-resource-planning-q-a\u002Fdifferences-between-tpm10-and-tmp18\u002Fqaq-p\u002F11712160","blog\u002Fsap-trm-period-end-close",[265,266,267],"sap","trm","process","text","lnxZNdAe6Mu5qnacqu708GJD3z4dzGBuOOR30OQQyag",{"related":271,"bridge":283,"next":287,"guide":291,"place":294},[272,275,279],{"path":205,"title":273,"description":274},"SAP Transaction Manager: Deals and Instruments","The Transaction Manager is the core of SAP TRM, where financial deals live — money market, FX, securities and derivatives, from capture to accounting.",{"path":276,"title":277,"description":278},"\u002Fblog\u002Fsap-treasury-transaction-codes","SAP Treasury Transaction Codes: The Ones That Matter","A verified reference of SAP Treasury and Risk Management transaction codes — FTR_CREATE to TPM20 — grouped by working area and checked against SAP Help.",{"path":280,"title":281,"description":282},"\u002Fblog\u002Fsap-treasury-fiori-apps","SAP Treasury Fiori Apps: What Replaces Which Transaction","A verified map of the Fiori apps for SAP Treasury and Cash Management in S\u002F4HANA — F6157 to F2332 — with the classic transaction each replaces or complements.",{"path":284,"title":285,"description":286,"specific":240},"\u002Fblog\u002Fai-agents-in-sap-what-actually-posts","AI Agents in SAP: What Actually Lands in the System","Role-aware is not segregation-safe. What an agent posting in S\u002F4HANA leaves on the document, in the release path, and in front of the auditor at period end.",{"path":288,"title":289,"description":290},"\u002Fblog\u002Fbusiness-partner-configuration-sap-treasury","Business Partner Configuration for SAP Treasury","The SAP Business Partner is the master-data object for the counterparties, issuers and banks a treasury deals with — and every TRM deal is captured against it.",{"slug":243,"name":292,"total":293},"SAP Treasury & Cash Management",40,{"label":295,"position":215,"total":296,"hub":297},"Transactions",11,"\u002Ftopics\u002Fsap-treasury#cluster-transactions",1793124402323]