[{"data":1,"prerenderedAt":320},["ShallowReactive",2],{"blog-\u002Fblog\u002Finterface-monitoring-and-reconciliation":3,"blog-surround-\u002Fblog\u002Finterface-monitoring-and-reconciliation":300,"blog-related-\u002Fblog\u002Finterface-monitoring-and-reconciliation":309},{"id":4,"title":5,"audience":6,"body":9,"cluster":266,"date":267,"description":268,"draft":269,"extension":270,"factCheckedAt":271,"faq":272,"featured":269,"language":271,"meta":282,"navigation":283,"order":284,"originalAsset":271,"path":285,"pillar":286,"primaryKeyword":287,"relatedProject":271,"releaseScope":271,"reviewCycle":288,"reviewStatus":289,"reviewedBy":290,"searchIntent":291,"seo":292,"sources":271,"stem":293,"tags":294,"type":298,"updated":267,"__hash__":299},"blog\u002Fblog\u002Finterface-monitoring-and-reconciliation.md","Interface Monitoring and Reconciliation for Treasury Systems",[7,8],"treasury-system-lead","solution-architect",{"type":10,"value":11,"toc":255},"minimark",[12,29,34,57,61,68,85,92,96,103,130,133,144,148,159,163,166,188,192,195,199,225,228,231],[13,14,15,28],"p",{},[16,17,18,19,23,24,27],"strong",{},"Interface monitoring proves each interface ",[20,21,22],"em",{},"ran and completed","; interface reconciliation proves ",[20,25,26],{},"all the data arrived intact",". Treasury interfaces need both, because they fail silently and partially — and a feed that quietly doesn't run, or transfers only part of its data, surfaces as a wrong cash position or a missed payment days later."," The interfaces that cause the worst damage aren't the ones that fail loudly; they're the ones that fail quietly. Monitoring and reconciliation are how you make silent failure impossible.",[30,31,33],"h2",{"id":32},"why-interfaces-fail-silently","Why interfaces fail silently",[13,35,36,37,42,43,47,48,52,53,56],{},"A treasury landscape is a ",[38,39,41],"a",{"href":40},"\u002Fblog\u002Ftreasury-integration-patterns-files-apis-middleware","web of feeds",": the ",[38,44,46],{"href":45},"\u002Fblog\u002Fdesigning-erp-tms-integration","ERP to the TMS",", bank statements in, payments out, market data. Each is a point where something can go wrong — a job doesn't run, a file is late or malformed, ",[38,49,51],{"href":50},"\u002Fblog\u002Fdisaster-recovery-business-continuity-treasury","a downstream system is down",", a feed transfers 998 of 1,000 records. None of these announces itself. The system doesn't crash; it just has slightly wrong or missing data. And because a cash position built from a partial statement ",[20,54,55],{},"looks"," like a cash position, the failure is invisible until someone can't reconcile it or a payment doesn't land.",[30,58,60],{"id":59},"monitoring-did-it-run-and-complete","Monitoring: did it run and complete?",[13,62,63,64,67],{},"The first question is existence. For every interface, you need to know it ",[16,65,66],{},"ran when it should, and completed successfully"," — and to be alerted when it didn't. That means:",[69,70,71,75,78],"ul",{},[72,73,74],"li",{},"A schedule or expectation for each feed (this runs at this time \u002F before this event).",[72,76,77],{},"Detection of a run that's missing, late, or ended in error.",[72,79,80,81,84],{},"An ",[16,82,83],{},"alert to a named owner"," — not a log entry someone might read.",[13,86,87,88,91],{},"Monitoring catches the \"the feed didn't run\" and \"the feed errored\" cases. But a feed can run ",[20,89,90],{},"successfully"," and still be wrong — which is where reconciliation comes in.",[30,93,95],{"id":94},"reconciliation-did-the-data-arrive-intact","Reconciliation: did the data arrive intact?",[13,97,98,99,102],{},"The second question is completeness and integrity. The tool is ",[16,100,101],{},"control totals",": the source records how many items and what total amount it sent; the target records how many it received and processed; you compare them, every run.",[104,105,106],"blockquote",{},[13,107,108,109,112,113,116,117,119,120,122,123,119,126,129],{},"Source sent ",[16,110,111],{},"1,000"," AP items totalling ",[16,114,115],{},"€10,000,000",". Target booked ",[16,118,111],{}," totalling ",[16,121,115],{},". ✓ balanced.\nTarget booked ",[16,124,125],{},"998",[16,127,128],{},"€9,900,000",". ✗ break — investigate before trusting the position.",[13,131,132],{},"Counts catch missing records; amount sums catch corrupted or altered values. Together they turn a silent partial failure into a caught, investigable exception.",[134,135,137],"callout",{"type":136},"tip",[13,138,139,140,143],{},"Monitoring without reconciliation gives false comfort: the dashboard is green because the feed ",[20,141,142],{},"ran",", while it quietly moved the wrong data. Reconciliation without monitoring misses the feed that never ran at all. You need both, on every interface that matters.",[30,145,147],{"id":146},"alerting-and-ownership","Alerting and ownership",[13,149,150,151,154,155,158],{},"Detection is worthless if no one acts. Every monitored interface and every reconciliation break needs a ",[16,152,153],{},"named owner"," and an ",[16,156,157],{},"alert that reaches them"," — a channel they actually watch, with enough context to act. A break that lands in an unread log is the same as no monitoring at all. This is as much an operating-model decision as a technical one.",[30,160,162],{"id":161},"statement-and-payment-reconciliation-specifically","Statement and payment reconciliation specifically",[13,164,165],{},"Two flows deserve particular rigour:",[69,167,168,178],{},[72,169,170,173,174,177],{},[16,171,172],{},"Bank statements in."," Confirm you received a statement from ",[20,175,176],{},"every"," account for the day, and that opening\u002Fclosing balances are internally consistent. A missing statement means a wrong position.",[72,179,180,183,184,187],{},[16,181,182],{},"Payments out."," Reconcile what you ",[20,185,186],{},"instructed"," (pain.001) against the acknowledgements and status (pain.002) — so you know each payment was accepted and settled, not silently rejected.",[30,189,191],{"id":190},"build-it-in-dont-bolt-it-on","Build it in, don't bolt it on",[13,193,194],{},"The cheapest time to add monitoring and reconciliation is when you design the interface; the most expensive is after a wrong number has already reached the board. Make control totals and run-monitoring part of every interface's specification, alongside the data and format — not a manual check someone remembers to do.",[30,196,198],{"id":197},"what-usually-goes-wrong","What usually goes wrong",[69,200,201,207,213,219],{},[72,202,203,206],{},[16,204,205],{},"Green-dashboard comfort."," Monitoring that shows feeds ran, with no reconciliation, so partial data passes unnoticed.",[72,208,209,212],{},[16,210,211],{},"Alerts no one owns."," Breaks logged but not routed to a person who acts.",[72,214,215,218],{},[16,216,217],{},"Manual, after-the-fact reconciliation."," Someone eyeballs it \"when there's time,\" until the one time they don't.",[72,220,221,224],{},[16,222,223],{},"Skipping statement completeness."," Not checking that a statement arrived from every account, so a missing feed silently understates cash.",[13,226,227],{},"Monitor that every interface ran, reconcile that every one moved its data intact, route breaks to an owner who acts — and the silent, partial failures that quietly corrupt a treasury landscape stop happening.",[229,230],"hr",{},[13,232,233],{},[20,234,235,236,240,241,244,245,249,250,254],{},"Part of the ",[38,237,239],{"href":238},"\u002Ftopics\u002Ftreasury-systems-architecture","Treasury Systems Architecture guide",". See also ",[38,242,243],{"href":45},"ERP-TMS integration"," and the ",[38,246,248],{"href":247},"\u002Fblog\u002Freference-architecture-for-corporate-treasury","reference architecture",". The ",[38,251,253],{"href":252},"\u002Fnewsletter","newsletter"," sends one finance-systems pattern, product decision or build lesson every two weeks.",{"title":256,"searchDepth":257,"depth":257,"links":258},"",2,[259,260,261,262,263,264,265],{"id":32,"depth":257,"text":33},{"id":59,"depth":257,"text":60},{"id":94,"depth":257,"text":95},{"id":146,"depth":257,"text":147},{"id":161,"depth":257,"text":162},{"id":190,"depth":257,"text":191},{"id":197,"depth":257,"text":198},"integration","2026-07-23","Treasury interfaces fail silently and partially. Monitoring proves each ran; reconciliation proves the data arrived intact. How to design both from the start.",false,"md",null,[273,276,279],{"question":274,"answer":275},"What is interface monitoring in treasury systems?","Interface monitoring is the discipline of confirming that each interface between systems — ERP to TMS, bank statements in, payments out — actually ran and completed as expected, and alerting an owner when it didn't. It answers 'did the feed run?' Without it, a feed that silently fails to run isn't noticed until a position is wrong or a payment is missed.",{"question":277,"answer":278},"What is the difference between interface monitoring and reconciliation?","Monitoring answers 'did the interface run and complete?' Reconciliation answers 'did all the data arrive intact?' A feed can run successfully but transfer only part of the data, or transfer it with errors — monitoring alone wouldn't catch that. Reconciliation uses control totals (record counts and amount sums, sent vs received) to prove completeness and integrity. You need both.",{"question":280,"answer":281},"How do you reconcile system interfaces?","Use control totals: compare the number of records and the sum of amounts sent by the source against what the target received and processed, for every interface run. If a source sends 1,000 items totalling a known amount and the target books fewer or a different total, the reconciliation flags a break to be investigated. Build this into the interface rather than doing it manually after the fact.",{},true,6,"\u002Fblog\u002Finterface-monitoring-and-reconciliation","treasury-systems-architecture","treasury interface monitoring","annual","reviewed","Tan Gravam","informational",{"title":5,"description":268},"blog\u002Finterface-monitoring-and-reconciliation",[295,296,266,297],"treasury","architecture","controls","text","6oZwxvuWGeUFckNMigFV8gF2I7td1fUHsBwcs_V22rs",[301,305],{"title":302,"path":303,"stem":304,"type":298,"language":271,"draft":269,"children":-1},"Interest Rate Risk in Corporate Treasury","\u002Fblog\u002Finterest-rate-risk-in-corporate-treasury","blog\u002Finterest-rate-risk-in-corporate-treasury",{"title":306,"path":307,"stem":308,"type":298,"language":271,"draft":269,"children":-1},"ISDA Agreements, CSAs and Collateral Management","\u002Fblog\u002Fisda-csa-and-collateral-management","blog\u002Fisda-csa-and-collateral-management",[310,313,316],{"path":45,"title":311,"description":312},"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":40,"title":314,"description":315},"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":317,"title":318,"description":319},"\u002Fblog\u002Fmarket-data-in-treasury-systems","Market Data in Treasury Systems","Market data — FX rates, interest curves, prices — is the external reference data treasury needs to value positions. How to source, control and integrate it.",1785182340997]