[{"data":1,"prerenderedAt":444},["ShallowReactive",2],{"blog-\u002Fblog\u002Fsap-trm-accounting-and-posting-architecture":3,"blog-surround-\u002Fblog\u002Fsap-trm-accounting-and-posting-architecture":423,"blog-related-\u002Fblog\u002Fsap-trm-accounting-and-posting-architecture":431},{"id":4,"title":5,"audience":6,"body":10,"cluster":375,"contentRole":376,"conversionGoal":376,"cornerstone":377,"date":378,"description":379,"draft":377,"extension":380,"factCheckedAt":378,"faq":381,"featured":377,"language":376,"meta":391,"navigation":392,"order":393,"originalAsset":376,"path":394,"pillar":395,"primaryKeyword":396,"publicationOrder":397,"relatedProject":376,"releaseScope":398,"reviewCycle":399,"reviewMethod":400,"reviewStatus":401,"reviewedAt":378,"reviewedBy":402,"searchIntent":403,"seo":404,"sources":405,"stem":412,"tags":413,"type":421,"updated":376,"__hash__":422},"blog\u002Fblog\u002Fsap-trm-accounting-and-posting-architecture.md","SAP TRM Accounting & Posting Architecture",[7,8,9],"sap-treasury-consultant","treasury-accountant","solution-architect",{"type":11,"value":12,"toc":366},"minimark",[13,26,35,40,43,144,156,160,175,186,189,200,203,223,227,238,244,247,251,266,270,273,300,307,311,337,340,343],[14,15,16,25],"p",{},[17,18,19,20,24],"strong",{},"In SAP TRM, a deal isn't an accounting entry — it's the start of a chain that ",[21,22,23],"em",{},"becomes"," one."," Capture a deal in Transaction Manager and you've created a business fact. Between that fact and a line in the general ledger sits an architecture most treasury projects underestimate: a position, its flows, valuation under one or more accounting principles, and an account-determination mechanism that turns abstract intent into real G\u002FL accounts. Get that architecture right and the ledger reconciles quietly, close after close. Get it wrong and you spend every period-end chasing why the subledger and the G\u002FL disagree.",[14,27,28,29,34],{},"This is the part the ",[30,31,33],"a",{"href":32},"\u002Fblog\u002Fsap-trm-position-management-and-valuation","position-and-valuation"," view sets up and the standard documentation treats as scattered configuration. Here it's one picture: how a deal becomes a posting, and where it reconciles.",[36,37,39],"h2",{"id":38},"the-lifecycle-deal-position-flows-valuation-posting","The lifecycle: deal → position → flows → valuation → posting",[14,41,42],{},"Every accounting-relevant thing TRM does moves through the same stages. Knowing the stage a number is at tells you which configuration governs it.",[44,45,46,62],"table",{},[47,48,49],"thead",{},[50,51,52,56,59],"tr",{},[53,54,55],"th",{},"Stage",[53,57,58],{},"What it is",[53,60,61],{},"What governs the accounting",[63,64,65,79,92,105,118,131],"tbody",{},[50,66,67,73,76],{},[68,69,70],"td",{},[17,71,72],{},"Deal",[68,74,75],{},"The business transaction captured in Transaction Manager",[68,77,78],{},"Product & transaction type; nothing posts yet",[50,80,81,86,89],{},[68,82,83],{},[17,84,85],{},"Position",[68,87,88],{},"The holding the deal contributes to",[68,90,91],{},"Position management; the account assignment reference",[50,93,94,99,102],{},[68,95,96],{},[17,97,98],{},"Flows",[68,100,101],{},"The datable cash and accounting events the deal generates",[68,103,104],{},"Flow types \u002F update types — which events are relevant",[50,106,107,112,115],{},[68,108,109],{},[17,110,111],{},"Valuation",[68,113,114],{},"Period-end measurement under an accounting principle",[68,116,117],{},"Valuation area and its valuation rules",[50,119,120,125,128],{},[68,121,122],{},[17,123,124],{},"Posting",[68,126,127],{},"The transfer of relevant flows and valuation results into FI",[68,129,130],{},"Account determination (symbols → assignment reference → G\u002FL)",[50,132,133,138,141],{},[68,134,135],{},[17,136,137],{},"Reconciliation",[68,139,140],{},"Proving the subledger and the G\u002FL represent the same events",[68,142,143],{},"All of the above, working together",[14,145,146,147,150,151,155],{},"The discipline this buys you: when a number is wrong, you don't ask \"why is the posting wrong?\" — you ask ",[21,148,149],{},"which stage",". A missing accrual is a flow\u002Frelevance question; a wrong account is determination; a valuation that only hit one ledger is a valuation-area question. Same as ",[30,152,154],{"href":153},"\u002Fblog\u002Ffqm-flow-reconciliation-and-troubleshooting","debugging cash flows",": localise the stage, then fix the cause.",[36,157,159],{"id":158},"account-determination-symbols-references-accounts","Account determination: symbols, references, accounts",[14,161,162,163,166,167,170,171,174],{},"This is the heart of it, and the part that most rewards understanding ",[21,164,165],{},"why"," it's built the way it is. TRM never posts to a hard-coded G\u002FL account. It posts to an ",[17,168,169],{},"account symbol"," — an abstract placeholder for a ",[21,172,173],{},"role"," in the entry: the position account, interest revenue, an accrual\u002Fdeferral account, a bank clearing account, a payment account.",[14,176,177,178,181,182,185],{},"Each symbol resolves to a real G\u002FL account depending on the ",[17,179,180],{},"account assignment reference"," — a key that groups positions which should post to the same accounts. The reference is ",[21,183,184],{},"derived"," for a position (via substitution rules) at the moment the position is created, and from then on it drives every posting for that position.",[14,187,188],{},"So the chain is always:",[190,191,196],"pre",{"className":192,"code":194,"language":195},[193],"language-text","Business event  →  Account symbol  →  Account assignment reference  →  G\u002FL account\n   (a flow)         (the role)          (the grouping key)              (the real account)\n","text",[197,198,194],"code",{"__ignoreMap":199},"",[14,201,202],{},"Two consequences worth internalising:",[204,205,206,217],"ul",{},[207,208,209,212,213,216],"li",{},[17,210,211],{},"The reference is set at position creation and drives everything after."," If it derived wrong, later postings inherit the mistake. You can maintain the account assignment reference manually on the position indicator when derivation fails — but only ",[17,214,215],{},"before the first posting"," for that position; once something has posted, it's locked. That single rule explains a large share of \"we can't fix the account now\" situations.",[207,218,219,222],{},[17,220,221],{},"Symbols keep the chart of accounts out of the treasury logic."," The same TRM configuration works across company codes with different accounts, because the account lives at the end of the chain, not inside the deal.",[36,224,226],{"id":225},"parallel-accounting-one-deal-many-ledgers","Parallel accounting: one deal, many ledgers",[14,228,229,230,233,234,237],{},"A single instrument rarely has one \"value.\" Under local GAAP and IFRS it can be measured differently — amortised cost here, fair value there, different accrual treatment. TRM handles this with ",[17,231,232],{},"valuation areas",": each area carries its own valuation rules and ",[17,235,236],{},"posts its results separately",", so one deal produces parallel valuation and accounting entries under each principle without being entered twice.",[239,240,241],"pull-quote",{},[14,242,243],{},"The deal and the position are shared. The valuation and its postings are per valuation area. That single split is what lets one treasury book satisfy two accounting worlds from one entry.",[14,245,246],{},"This is also where accrual\u002Fdeferral and period-end valuation live: the accruals that spread interest across periods and the valuation runs that mark positions at period-end are executed per valuation area and posted through the same account-determination chain. When one ledger is right and another is wrong, the fault is almost always a valuation-area configuration gap — not the deal.",[36,248,250],{"id":249},"hedge-accounting-sits-on-top-not-beside","Hedge accounting sits on top, not beside",[14,252,253,257,258,261,262,265],{},[30,254,256],{"href":255},"\u002Fblog\u002Fhedge-accounting-explained","Hedge accounting"," doesn't replace this architecture — it constrains it. A designated hedge relationship changes ",[21,259,260],{},"which"," valuation and posting treatment applies (deferring fair-value movements to a reserve rather than P&L, for instance), but it still flows through valuation areas and account determination to reach the ledger. Treat hedge accounting as a layer that changes the ",[21,263,264],{},"rules"," a valuation area applies, not a separate posting path, and it stops feeling like a bolt-on.",[36,267,269],{"id":268},"reconciling-to-the-ledger","Reconciling to the ledger",[14,271,272],{},"Because Transaction Manager transfers the accounting-relevant results into FI, the subledger (deals and positions) and the G\u002FL are two views of the same events. Reconciliation is proving they still agree — and when they don't, the break is almost never in the ledger. Work it in this order:",[274,275,276,282,288,294],"ol",{},[207,277,278,281],{},[17,279,280],{},"Unposted flows."," An accrual, payment or valuation result that's relevant but hasn't posted. The subledger \"knows\" about an event the G\u002FL hasn't seen.",[207,283,284,287],{},[17,285,286],{},"Account determination."," A missing or wrong account assignment reference sending a symbol to the wrong (or no) account — the classic source of a position that posts \"somewhere odd.\"",[207,289,290,293],{},[17,291,292],{},"Valuation-area gaps."," A principle that valued but didn't post, or posted to one ledger and not the parallel one.",[207,295,296,299],{},[17,297,298],{},"Timing \u002F date basis."," A flow posted in a different period than the view you're reconciling.",[14,301,302,303,306],{},"The through-line with the rest of the module is the same: ",[17,304,305],{},"the ledger is faithfully recording what it was told."," The fix is upstream — in relevance, determination or valuation config — not in a manual G\u002FL correction that papers over the cause until next close.",[36,308,310],{"id":309},"what-good-looks-like","What good looks like",[204,312,313,319,325,331],{},[207,314,315,318],{},[17,316,317],{},"Account assignment references derived, not maintained by hand."," Manual maintenance is the escape hatch for a derivation gap, not the operating model — and it's impossible once a position has posted, so fix the derivation.",[207,320,321,324],{},[17,322,323],{},"Valuation areas mapped deliberately to your accounting principles",", each posting its own results, so parallel accounting is by design rather than reconciled after the fact.",[207,326,327,330],{},[17,328,329],{},"A per-stage mental model."," When a number's wrong, name the stage — flow, valuation, determination, timing — before touching anything.",[207,332,333,336],{},[17,334,335],{},"Reconciliation as evidence, not a hunt."," Subledger-to-G\u002FL agreement proven each period, with breaks traced to a stage, not smoothed over in the ledger.",[14,338,339],{},"Understand TRM's posting architecture as one chain — deal to position to flows to valuation to posting — and treasury accounting stops being a black box between the front office and the close. It becomes what it should be: a set of rules you can read, in the order the system reads them.",[341,342],"hr",{},[14,344,345],{},[21,346,347,348,352,353,356,357,360,361,365],{},"Part of the ",[30,349,351],{"href":350},"\u002Ftopics\u002Fsap-treasury","SAP Treasury & Cash Management guide",". See also ",[30,354,355],{"href":32},"SAP TRM position management & valuation"," and ",[30,358,359],{"href":255},"hedge accounting explained",". The ",[30,362,364],{"href":363},"\u002Fnewsletter","newsletter"," sends one finance-systems pattern, product decision or build lesson every two weeks.",{"title":199,"searchDepth":367,"depth":367,"links":368},2,[369,370,371,372,373,374],{"id":38,"depth":367,"text":39},{"id":158,"depth":367,"text":159},{"id":225,"depth":367,"text":226},{"id":249,"depth":367,"text":250},{"id":268,"depth":367,"text":269},{"id":309,"depth":367,"text":310},"transaction-manager",null,false,"2026-07-28","How a treasury deal becomes a G\u002FL posting in SAP TRM: the lifecycle, account determination via symbols and assignment references, valuation areas for parallel accounting, and where it reconciles to the ledger.","md",[382,385,388],{"question":383,"answer":384},"How does account determination work in SAP Transaction Manager?","Postings are made to account symbols — abstract placeholders like position, interest revenue, accrual or bank clearing — and each symbol resolves to a real G\u002FL account depending on the account assignment reference. The account assignment reference is derived for a treasury position (via substitution rules) when the position is created, and it groups positions that should post to the same accounts. So the chain is: business event → account symbol → account assignment reference → G\u002FL account. If derivation fails and no reference is found, you can maintain it manually on the position indicator — but only while no posting has yet been made for that position.",{"question":386,"answer":387},"What are valuation areas in SAP TRM used for?","Valuation areas let you value and post the same financial instruments in parallel under different accounting principles — for example local GAAP and IFRS — at the same time. Each valuation area carries its own valuation rules and posts its results separately, so one deal produces parallel sets of valuation and accounting entries without being entered twice. This is how TRM supports parallel accounting: the deal and position are shared; the valuation and its postings are per valuation area.",{"question":389,"answer":390},"How does SAP TRM reconcile to the general ledger?","Transaction Manager transfers the accounting-relevant results of the deal lifecycle — postings for positions, payments, accruals\u002Fdeferrals and valuation — into Financial Accounting through account determination, so the subledger view (the deals and positions) and the G\u002FL view are two representations of the same events. Reconciliation is proving they still agree: that every accounting-relevant flow and valuation posted, posted once, and posted to the intended accounts. Breaks usually trace to a missing or wrong account assignment reference, an unposted flow, or a valuation-area configuration gap — not to the ledger itself.",{},true,8.5,"\u002Fblog\u002Fsap-trm-accounting-and-posting-architecture","sap-treasury","SAP TRM accounting posting",164,"SAP S\u002F4HANA — Transaction Manager, valuation areas and account-determination apps\u002Fcustomizing differ by release and between on-premise and Cloud; verify against the documentation for your system.","annual","editorial-and-factual","reviewed","Tan Gravam","informational",{"title":5,"description":379},[406,409],{"title":407,"url":408,"accessed":378},"SAP Help — Treasury and Risk Management (SAP S\u002F4HANA)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002F3b3e7e53c4d1cc26e10000000a4450e5.html",{"title":410,"url":411,"accessed":378},"SAP Help — Treasury Accounting (SAP S\u002F4HANA Cloud)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_CLOUD\u002Fe5ec5859d8e54df98492d80564a734c0\u002Fbc153a383f0d4c39a34a26523af97751.html","blog\u002Fsap-trm-accounting-and-posting-architecture",[414,415,416,375,417,418,419,420],"sap","treasury","trm","accounting","posting","valuation","hedge-accounting","pattern","KNlqXWigZlbY7QGfr_hCntkX_RdWdKioajTaGp24NUk",[424,428],{"title":425,"path":426,"stem":427,"type":195,"language":376,"draft":377,"children":-1},"Market Data in SAP Treasury","\u002Fblog\u002Fsap-treasury-market-data-management","blog\u002Fsap-treasury-market-data-management",{"title":429,"path":32,"stem":430,"type":195,"language":376,"draft":377,"children":-1},"SAP TRM Position Management and Valuation","blog\u002Fsap-trm-position-management-and-valuation",[432,436,440],{"path":433,"title":434,"description":435},"\u002Fblog\u002Fwhat-is-sap-treasury-and-risk-management","What Is SAP Treasury and Risk Management (TRM)?","SAP Treasury and Risk Management (TRM) manages financial transactions and risk — capturing deals, valuing them, measuring risk, and posting to accounting.",{"path":437,"title":438,"description":439},"\u002Fblog\u002Fsap-cash-management-s4hana","SAP Cash Management in S\u002F4HANA","SAP Cash Management in S\u002F4HANA — the redesigned cash and liquidity solution: Bank Account Management, Cash Operations and Liquidity Management, on One Exposure.",{"path":441,"title":442,"description":443},"\u002Fblog\u002Fsap-bank-account-management-s4hana","SAP Bank Account Management (BAM) in S\u002F4HANA","SAP Bank Account Management (BAM) governs bank accounts and house banks as master data in S\u002F4HANA — the base cash position, statements and payments rest on.",1785267483466]