[{"data":1,"prerenderedAt":346},["ShallowReactive",2],{"blog-\u002Fblog\u002Fstraight-through-processing-in-treasury":3,"blog-surround-\u002Fblog\u002Fstraight-through-processing-in-treasury":325,"blog-related-\u002Fblog\u002Fstraight-through-processing-in-treasury":334},{"id":4,"title":5,"audience":6,"body":10,"cluster":290,"date":291,"description":292,"draft":293,"extension":294,"factCheckedAt":295,"faq":296,"featured":293,"language":295,"meta":306,"navigation":307,"order":308,"originalAsset":295,"path":309,"pillar":310,"primaryKeyword":311,"relatedProject":295,"releaseScope":295,"reviewCycle":312,"reviewStatus":313,"reviewedBy":314,"searchIntent":315,"seo":316,"sources":295,"stem":317,"tags":318,"type":323,"updated":291,"__hash__":324},"blog\u002Fblog\u002Fstraight-through-processing-in-treasury.md","Straight-Through Processing in Treasury",[7,8,9],"treasury-system-lead","solution-architect","treasury-analyst",{"type":11,"value":12,"toc":279},"minimark",[13,26,31,44,48,51,88,94,98,101,142,146,154,184,188,203,207,214,218,250,253,256],[14,15,16,20,21,25],"p",{},[17,18,19],"strong",{},"Straight-through processing (STP) means a transaction flows end to end — from initiation through confirmation, settlement and accounting — with no manual re-keying or intervention."," In treasury, high STP means a payment or deal is captured ",[22,23,24],"em",{},"once"," and then flows automatically through every downstream step. It matters because these transactions move real money: every manual touchpoint STP removes is a place where an error can no longer creep in, a delay can no longer form, and a fraud can no longer hide. STP isn't automation for its own sake — it's the systematic removal of the risky, valueless human steps between \"we decided to pay\" and \"it's paid and booked.\"",[27,28,30],"h2",{"id":29},"what-stp-is","What STP is",[14,32,33,34,39,40,43],{},"Picture a payment's journey: someone initiates it, it's approved, sent to the bank, settled, acknowledged, and posted to the ",[35,36,38],"a",{"href":37},"\u002Fblog\u002Ftreasury-system-of-record","ledger",". STP is the degree to which that whole chain happens ",[22,41,42],{},"without anyone re-entering the data",". Full STP: entered once, flows all the way through. No STP: a human re-keys it at every boundary — into the banking portal, then into the accounting system, then into a reconciliation sheet.",[27,45,47],{"id":46},"why-it-matters","Why it matters",[14,49,50],{},"Four benefits, all significant, but the last is the real prize:",[52,53,54,61,67,73],"ul",{},[55,56,57,60],"li",{},[17,58,59],{},"Fewer errors."," Data entered once and reused can't be mistyped at step three.",[55,62,63,66],{},[17,64,65],{},"Lower cost."," Manual re-keying is slow, expensive human effort doing what a machine should.",[55,68,69,72],{},[17,70,71],{},"More speed."," Automated flows settle and post faster, with less lag.",[55,74,75,78,79,82,83,87],{},[17,76,77],{},"Stronger control."," ",[22,80,81],{},"This is the one that matters most."," Every hand that touches a payment is a control risk and a ",[35,84,86],{"href":85},"\u002Fblog\u002Fpayment-fraud-prevention-in-treasury","fraud opportunity",". Fewer touchpoints means fewer places for money to be diverted or a mistake to slip through.",[89,90,91],"pull-quote",{},[14,92,93],{},"Every manual re-keying step in a payment flow is two things at once: a place for an honest error, and a place for a dishonest one. STP closes both at the same time.",[27,95,97],{"id":96},"what-breaks-stp","What breaks STP",[14,99,100],{},"STP degrades wherever a human is forced to copy, translate or re-enter:",[52,102,103,109,125,131],{},[55,104,105,108],{},[17,106,107],{},"Swivel-chair integration."," Systems that don't talk, bridged by a person reading one screen and typing into another.",[55,110,111,114,115,119,120,124],{},[17,112,113],{},"Format mismatches."," A bank or system that needs data in a shape nothing else produces, so someone translates it by hand. (This is why ",[35,116,118],{"href":117},"\u002Fblog\u002Fbank-statement-formats-mt940-camt053-bai2","standard formats"," and ",[35,121,123],{"href":122},"\u002Fblog\u002Fiso-20022-payments-pain-001-pain-002","ISO 20022"," matter for STP.)",[55,126,127,130],{},[17,128,129],{},"Exceptions."," Transactions that fall out of the automated path — a failed match, a missing reference — and land in a manual queue.",[55,132,133,136,137,141],{},[17,134,135],{},"Manual approvals outside workflow."," Approvals done over email or on paper rather than in a system ",[35,138,140],{"href":139},"\u002Fblog\u002Fsegregation-of-duties-in-treasury-systems","workflow",", forcing re-entry to record the decision.",[27,143,145],{"id":144},"the-building-blocks","The building blocks",[14,147,148,149,153],{},"High STP rests on the same foundations as the rest of good ",[35,150,152],{"href":151},"\u002Fblog\u002Freference-architecture-for-corporate-treasury","treasury architecture",":",[52,155,156,162,168,174],{},[55,157,158,161],{},[17,159,160],{},"Integration"," — systems connected so data flows, not swivel-chaired.",[55,163,164,167],{},[17,165,166],{},"Standard formats"," — a common language so no translation step is needed.",[55,169,170,173],{},[17,171,172],{},"Matching"," — automated reconciliation (confirmations, statements, payment status) so the routine cases clear themselves.",[55,175,176,179,180,183],{},[17,177,178],{},"Workflow"," — approvals and controls built ",[22,181,182],{},"into"," the system, so a control step doesn't become a manual break.",[27,185,187],{"id":186},"stp-vs-exceptions-100-is-a-myth","STP vs exceptions: 100% is a myth",[14,189,190,191,194,195,198,199,202],{},"The goal is ",[22,192,193],{},"high"," STP, not total STP. Some transactions genuinely need human judgement — an unusual deal, a genuine exception, a control that ",[22,196,197],{},"should"," pause and ask. Chasing 100% automation means either forcing bad automation onto cases that need a person, or removing controls that should exist. The real target is: ",[17,200,201],{},"automate the routine to near-total, and handle the exceptions well"," — route them fast, to the right person, with context. A good STP design is measured as much by how cleanly it handles the exceptions as by how few there are.",[27,204,206],{"id":205},"measuring-it","Measuring it",[14,208,209,210,213],{},"STP is measurable: the ",[17,211,212],{},"STP rate"," is the proportion of transactions that flow through untouched. Tracking it — by process, by counterparty, by bank — turns \"we should automate more\" into a specific target and shows where the manual breaks actually are. What you measure, you can improve; an unmeasured STP rate is just a vague aspiration.",[27,215,217],{"id":216},"what-usually-goes-wrong","What usually goes wrong",[52,219,220,226,232,238,244],{},[55,221,222,225],{},[17,223,224],{},"Swivel-chair everywhere."," Unintegrated systems bridged by people, accepted as normal.",[55,227,228,231],{},[17,229,230],{},"Re-keying across formats."," Manual translation because formats were never standardised.",[55,233,234,237],{},[17,235,236],{},"Controls as manual breaks."," Approvals done outside workflow, so every control step breaks the flow and gets re-entered.",[55,239,240,243],{},[17,241,242],{},"No measurement."," No STP rate, so no one knows where the manual effort and risk actually concentrate.",[55,245,246,249],{},[17,247,248],{},"Chasing 100%."," Over-automating cases that need judgement, or dropping necessary controls to hit a number.",[14,251,252],{},"Integrate the systems, standardise the formats, automate the matching, build controls into workflow, and measure the STP rate — and treasury processing shifts from a chain of risky manual hand-offs to a flow that's captured once and trusted end to end. That's not just efficiency; for a function that moves money, it's one of the strongest controls you have.",[254,255],"hr",{},[14,257,258],{},[22,259,260,261,265,266,119,270,273,274,278],{},"Part of the ",[35,262,264],{"href":263},"\u002Ftopics\u002Ftreasury-systems-architecture","Treasury Systems Architecture guide",". See also ",[35,267,269],{"href":268},"\u002Fblog\u002Finterface-monitoring-and-reconciliation","interface monitoring and reconciliation",[35,271,272],{"href":139},"segregation of duties",". The ",[35,275,277],{"href":276},"\u002Fnewsletter","newsletter"," sends one finance-systems pattern, product decision or build lesson every two weeks.",{"title":280,"searchDepth":281,"depth":281,"links":282},"",2,[283,284,285,286,287,288,289],{"id":29,"depth":281,"text":30},{"id":46,"depth":281,"text":47},{"id":96,"depth":281,"text":97},{"id":144,"depth":281,"text":145},{"id":186,"depth":281,"text":187},{"id":205,"depth":281,"text":206},{"id":216,"depth":281,"text":217},"integration","2026-07-23","Straight-through processing (STP) means a transaction flows from initiation to settlement with no manual re-keying. Why every manual touchpoint is a risk.",false,"md",null,[297,300,303],{"question":298,"answer":299},"What is straight-through processing (STP) in treasury?","Straight-through processing means a transaction flows end to end — from initiation through confirmation, settlement, the bank, and accounting — without manual re-keying or intervention. In treasury, high STP means a payment or deal is captured once and then flows automatically through every downstream step. Each manual touchpoint that STP removes is a place where an error, a delay, or a fraud can no longer be introduced.",{"question":301,"answer":302},"Why is straight-through processing important in treasury?","Because every manual step in a money-moving process is a risk. Re-keying introduces errors, slows things down, and — critically — creates opportunities for fraud and control failures. STP reduces cost (less manual effort), reduces error (data is entered once and reused), speeds settlement, and strengthens control (fewer hands touching a payment). For treasury, where the transactions move real money, raising STP is one of the highest-leverage improvements available.",{"question":304,"answer":305},"What breaks straight-through processing?","The main culprits are re-keying between systems that aren't integrated (swivel-chair processing), format mismatches that require manual translation, exceptions that fall out of automated flows, and manual approval steps that aren't built into workflow. Anything that forces a human to copy, translate, or re-enter data breaks STP. The goal isn't 100% automation — some exceptions genuinely need judgement — but to remove the manual steps that add risk without adding value.",{},true,7.5,"\u002Fblog\u002Fstraight-through-processing-in-treasury","treasury-systems-architecture","straight-through processing treasury","annual","reviewed","Tan Gravam","informational",{"title":5,"description":292},"blog\u002Fstraight-through-processing-in-treasury",[319,320,321,322,290],"treasury","architecture","stp","automation","text","1tHIWC_Ym2-fS6Cr6MReawdp_UXmo6cWfbqgZSllcR0",[326,330],{"title":327,"path":328,"stem":329,"type":323,"language":295,"draft":293,"children":-1},"Solution Design and Blueprint for Finance Systems","\u002Fblog\u002Fsolution-design-and-blueprint-for-finance-systems","blog\u002Fsolution-design-and-blueprint-for-finance-systems",{"title":331,"path":332,"stem":333,"type":323,"language":295,"draft":293,"children":-1},"Stress Testing and Scenario Analysis in Treasury","\u002Fblog\u002Fstress-testing-and-scenario-analysis-treasury","blog\u002Fstress-testing-and-scenario-analysis-treasury",[335,339,343],{"path":336,"title":337,"description":338},"\u002Fblog\u002Fdesigning-erp-tms-integration","Designing ERP-to-TMS Integration","ERP TMS integration design: what flows each way, batch vs real-time, reconciliation and ownership — so your ERP and treasury system stay in step.",{"path":340,"title":341,"description":342},"\u002Fblog\u002Ftreasury-integration-patterns-files-apis-middleware","Treasury Integration Patterns: Files, APIs and Middleware","Treasury integration patterns — batch files, APIs and middleware — and their trade-offs, plus why point-to-point connections collapse under their own weight.",{"path":268,"title":344,"description":345},"Interface Monitoring and Reconciliation for Treasury Systems","Treasury interfaces fail silently and partially. Monitoring proves each ran; reconciliation proves the data arrived intact. How to design both from the start.",1785182342237]