[{"data":1,"prerenderedAt":332},["ShallowReactive",2],{"blog-\u002Fblog\u002Finterface-monitoring-and-reconciliation":3,"blog-related-\u002Fblog\u002Finterface-monitoring-and-reconciliation":306,"blog-surround-\u002Fblog\u002Finterface-monitoring-and-reconciliation":331},{"id":4,"title":5,"audience":6,"body":9,"cluster":270,"conversionGoal":271,"cornerstone":272,"date":273,"description":274,"draft":272,"extension":275,"factCheckedAt":271,"faq":276,"featured":272,"language":271,"meta":286,"minRead":287,"navigation":288,"order":289,"originalAsset":271,"path":290,"pillar":291,"primaryKeyword":292,"publicationOrder":293,"relatedProject":271,"releaseScope":271,"reviewCycle":294,"reviewMethod":271,"reviewStatus":295,"reviewedAt":271,"reviewedBy":296,"searchIntent":297,"seo":298,"sources":271,"stem":299,"tags":300,"type":304,"updated":273,"__hash__":305},"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":259},"minimark",[12,29,34,57,61,68,85,92,96,103,130,138,149,153,164,168,171,193,197,200,204,240,243,246],[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,133,137],{},"Counts catch missing records; amount sums catch corrupted or altered values. Together they turn a silent partial failure into a caught, investigable exception — one that lands in a proper ",[38,134,136],{"href":135},"\u002Fblog\u002Ftreasury-exception-management","exception-management queue"," with an owner and a clock, rather than in someone's inbox.",[139,140,142],"callout",{"type":141},"tip",[13,143,144,145,148],{},"Monitoring without reconciliation gives false comfort: the dashboard is green because the feed ",[20,146,147],{},"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,150,152],{"id":151},"alerting-and-ownership","Alerting and ownership",[13,154,155,156,159,160,163],{},"Detection is worthless if no one acts. Every monitored interface and every reconciliation break needs a ",[16,157,158],{},"named owner"," and an ",[16,161,162],{},"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,165,167],{"id":166},"statement-and-payment-reconciliation-specifically","Statement and payment reconciliation specifically",[13,169,170],{},"Two flows deserve particular rigour:",[69,172,173,183],{},[72,174,175,178,179,182],{},[16,176,177],{},"Bank statements in."," Confirm you received a statement from ",[20,180,181],{},"every"," account for the day, and that opening\u002Fclosing balances are internally consistent. A missing statement means a wrong position.",[72,184,185,188,189,192],{},[16,186,187],{},"Payments out."," Reconcile what you ",[20,190,191],{},"instructed"," (pain.001) against the acknowledgements and status (pain.002) — so you know each payment was accepted and settled, not silently rejected.",[30,194,196],{"id":195},"build-it-in-dont-bolt-it-on","Build it in, don't bolt it on",[13,198,199],{},"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,201,203],{"id":202},"what-usually-goes-wrong","What usually goes wrong",[69,205,206,217,223,234],{},[72,207,208,211,212,216],{},[16,209,210],{},"Green-dashboard comfort."," Monitoring that shows feeds ran, with no reconciliation, so partial data passes unnoticed. The identical trap appears one layer up in AI systems, where a dashboard of aggregates cannot answer the only question anyone ever asks — ",[38,213,215],{"href":214},"\u002Fblog\u002Fproduction-ai-observability","what happened to this record, on this day",".",[72,218,219,222],{},[16,220,221],{},"Alerts no one owns."," Breaks logged but not routed to a person who acts.",[72,224,225,228,229,233],{},[16,226,227],{},"Manual, after-the-fact reconciliation."," Someone eyeballs it \"when there's time,\" until the one time they don't. Bank reconciliation is the workflow I most often see redesigned — ",[38,230,232],{"href":231},"\u002Fblog\u002Fai-workflow-teardown-bank-reconciliation","taken apart end to end here",", including which parts must stay deterministic.",[72,235,236,239],{},[16,237,238],{},"Skipping statement completeness."," Not checking that a statement arrived from every account, so a missing feed silently understates cash.",[13,241,242],{},"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.",[244,245],"hr",{},[13,247,248],{},[20,249,250,251,254,255,216],{},"See also ",[38,252,253],{"href":45},"ERP-TMS integration"," and the ",[38,256,258],{"href":257},"\u002Fblog\u002Freference-architecture-for-corporate-treasury","reference architecture",{"title":260,"searchDepth":261,"depth":261,"links":262},"",2,[263,264,265,266,267,268,269],{"id":32,"depth":261,"text":33},{"id":59,"depth":261,"text":60},{"id":94,"depth":261,"text":95},{"id":151,"depth":261,"text":152},{"id":166,"depth":261,"text":167},{"id":195,"depth":261,"text":196},{"id":202,"depth":261,"text":203},"integration",null,false,"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.","md",[277,280,283],{"question":278,"answer":279},"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":281,"answer":282},"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":284,"answer":285},"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.",{},4,true,6,"\u002Fblog\u002Finterface-monitoring-and-reconciliation","treasury-systems-architecture","treasury interface monitoring",26,"annual","reviewed","Tan Gravam","informational",{"title":5,"description":274},"blog\u002Finterface-monitoring-and-reconciliation",[301,302,270,303],"treasury","architecture","controls","text","eeXoc6ssFTfVI5vEHNi5GL6v41IU0Q_M3LVkjx6IxiY",{"related":307,"prev":320,"next":322,"hasOrder":288,"place":326},[308,312,316],{"path":309,"title":310,"description":311},"\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.",{"path":313,"title":314,"description":315},"\u002Fblog\u002Fstraight-through-processing-in-treasury","Straight-Through Processing in Treasury","Straight-through processing (STP) means a transaction flows from initiation to settlement with no manual re-keying. Why every manual touchpoint is a risk.",{"path":317,"title":318,"description":319},"\u002Fblog\u002Fsegregation-of-duties-in-treasury-systems","Segregation of Duties in Treasury Systems","Treasury moves money, so it's a prime fraud target. Segregation of duties means no one person can initiate, approve and release a payment or trade alone.",{"path":40,"title":321,"type":304,"language":271},"Treasury Integration Patterns: Files, APIs and Middleware",{"path":323,"title":324,"type":325,"language":271},"\u002Fblog\u002Fbank-connectivity-security","Bank Connectivity Security: Keys, Certificates and Controls","pattern",{"label":327,"position":328,"total":329,"hub":330},"Integration",3,5,"\u002Ftopics\u002Ftreasury-systems-architecture",[],1787475403411]