Close Menu
    DevStackTipsDevStackTips
    • Home
    • News & Updates
      1. Tech & Work
      2. View All

      CodeSOD: A Unique Way to Primary Key

      July 22, 2025

      BrowserStack launches Figma plugin for detecting accessibility issues in design phase

      July 22, 2025

      Parasoft brings agentic AI to service virtualization in latest release

      July 22, 2025

      Node.js vs. Python for Backend: 7 Reasons C-Level Leaders Choose Node.js Talent

      July 21, 2025

      The best CRM software with email marketing in 2025: Expert tested and reviewed

      July 22, 2025

      This multi-port car charger can power 4 gadgets at once – and it’s surprisingly cheap

      July 22, 2025

      I’m a wearables editor and here are the 7 Pixel Watch 4 rumors I’m most curious about

      July 22, 2025

      8 ways I quickly leveled up my Linux skills – and you can too

      July 22, 2025
    • Development
      1. Algorithms & Data Structures
      2. Artificial Intelligence
      3. Back-End Development
      4. Databases
      5. Front-End Development
      6. Libraries & Frameworks
      7. Machine Learning
      8. Security
      9. Software Engineering
      10. Tools & IDEs
      11. Web Design
      12. Web Development
      13. Web Security
      14. Programming Languages
        • PHP
        • JavaScript
      Featured

      The Intersection of Agile and Accessibility – A Series on Designing for Everyone

      July 22, 2025
      Recent

      The Intersection of Agile and Accessibility – A Series on Designing for Everyone

      July 22, 2025

      Zero Trust & Cybersecurity Mesh: Your Org’s Survival Guide

      July 22, 2025

      Execute Ping Commands and Get Back Structured Data in PHP

      July 22, 2025
    • Operating Systems
      1. Windows
      2. Linux
      3. macOS
      Featured

      A Tomb Raider composer has been jailed — His legacy overshadowed by $75k+ in loan fraud

      July 22, 2025
      Recent

      A Tomb Raider composer has been jailed — His legacy overshadowed by $75k+ in loan fraud

      July 22, 2025

      “I don’t think I changed his mind” — NVIDIA CEO comments on H20 AI GPU sales resuming in China following a meeting with President Trump

      July 22, 2025

      Galaxy Z Fold 7 review: Six years later — Samsung finally cracks the foldable code

      July 22, 2025
    • Learning Resources
      • Books
      • Cheatsheets
      • Tutorials & Guides
    Home»Development»Wire Room Math: AI + SME = (Less Compensation Paid) X (Headline Risk + Payment Errors)^2

    Wire Room Math: AI + SME = (Less Compensation Paid) X (Headline Risk + Payment Errors)^2

    June 30, 2025

    At the absolute basic level, banks take money in and also send money out. Sort of like saying NASA launches spaceships and then bring them back. You know it’s more complicated than the elementary statement, but you know if you had to learn the more advanced functions of banks and NASA, it would likely be much easier to learn how to receive/send money than say landing astronauts on the surface of the moon.

    Despite moving money from inside a bank to someplace else since at least 15th Century Italy, banks still make mistakes sending money outside the bank. When they make a mistake, there are penalties. In the United States, banks, regulators and quasi-regulators such as ACH have set out a series of monetary penalties, called compensation, for mistakes sending money outside the bank. The penalties depend on which party (sending or receiving financial institution) caused the error; the amount of the error; how long the error persisted; and interest rates.

    In an effort to show how payment errors can be reduced, in this blog we’re going to list out the five biggest categories of errors including an example of each type and point out where/when Artificial Intelligence (“AI”) can be used to reduce payment errors and the corresponding compensation on those errors.

    Estimated bank payment errors, also known as improper payments, are a significant concern, with the Government Accountability Office (“GAO”) of the federal government reporting an estimated $247 billion in errors in fiscal year 2022. The government also estimates that 50% of payment errors are attributable to human errors. This emphasizes the value of automated mitigation and both human and software monitoring systems.

    Error Types

    I. Duplicate Payments

    Duplicate payments from banks will often be due to system glitches, such as shown below where a payment was processed twice, or at times the error is caused by bad human input such as a middle office processing a trade incorrectly, sending payment, and later processing the trade correctly but sending payment out a second time incorrectly.

    Software, whether straight through processing or AI software to detect potential double payments is now being established by banks focusing detection on duplicate matching criteria with key payment attributes with transaction identifiers, often an alphanumeric code assigned to each transaction, acting as sort of a digital fingerprint. They enable banks, merchants, and customers to easily identify, track, and reference specific transactions for various purposes, including record-keeping, dispute resolution, and fraud detection. 

    Duplicate Payments

    II. Incorrect Payment Amount

    A landmark case of an incorrect payment amount occurred in April 2024 when a staff member at a bank in New York City copied the account number of one system into the field intended for the dollar figure of a second system.

    The error was caught the next business day and had to be reported to regulators as a “Near-Miss”. The “copy and paste error” as it has become known was manual and unintentional, but still caused bank management embarrassment, and showed how despite billions spent on information technology at financial institutions at times controls haven’t improved much from the days of 8-column ledger cards.

    Straight through processing, which would have avoided a staff member from copying and pasting bank accounts and dollar amounts from one system to another could have avoided the situation altogether. The old four-eyed check, the bank in question had that in place and it was still missed. If you’re a bank executive looking to reduce errors, would you look to instill software that processes payments automatically or would you look to start a six-eyed check?

    III. Incorrect Currency

    Ever see a structured note that you buy in one currency, pays interest in a second currency, and depending on what the stock market indexes return over the period between offering date and maturity date pays the final principal in either the original or depending on the calculation outlined in the Offering Circular, a third, or even a fourth currency?

    If you’re a bank executive looking to improve the payment experience and reduce errors, are you more likely to trust the third worker to take over the account since inception who’s been with the bank since they graduated months ago, or software that can read the final Offering Circular, research and calculate the different payment (interest rate, stock market index returns, foreign currency exchange rates, etc.) and execute the payment? Yeah, me too.

    IV. Incorrect Payee and/or Payor

    Bank Error Card

    Software, particularly AI software that has been coded to look for anomaly detection using individual payments, aggregate payments, frequency, payment trends and debtor-credit payment histories is helping reduce cases where the wrong payee is paid or the correct payee is paid, but with money from the wrong payor account.

    V. Potential Fraud

    AI software enhances fraud protection and detection by leveraging machine learning to analyze vast datasets, identify patterns, and adept itself to evolving fraud tactics. The software improves accuracy, reduces false positives, and enables real-time monitoring for immediate intervention. Compared to four-eyed checks and older payment processing systems, AI-powered fraud detection software platforms offer the advantages of: 

    • monitoring transactions and activities in real-time, flagging suspicious events as they occur.
    • allowing for immediate intervention, such as blocking a fraudulent transaction or freezing an account, preventing further losses, embarrassment (aka “Headline Risk”), and reporting to federal regulators of “near-misses”.
    • Traditional systems often rely on batch processing, which can result in delays and allow fraudulent activities to continue for a longer period. 

    Ready to explore your firm’s payments strategy? 

    Our financial services experts continuously monitor the regulatory landscape and deliver pragmatic, scalable solutions that meet the mandate and more. Reach out to Perficient’s Financial Services Managing Director David Weisel to discover why we’ve been trusted by 18 of the top 20 banks, 16 of the 20 largest wealth and asset management firms, and are regularly recognized by leading analyst firms.

    It’s that component, the Subject Matter Expert (“SME”) that is the most important component of the mathematical expression in the title. Software helps. AI software helps a lot. But it’s the SME installing and reconfiguring processes and controls along with the AI software that helps the most. 

    Source: Read More 

    Facebook Twitter Reddit Email Copy Link
    Previous ArticleUsing AI to Compare Retail Product Performance
    Next Article Spring Boot + Swagger: A Complete Guide to API Documentation

    Related Posts

    Development

    GPT-5 is Coming: Revolutionizing Software Testing

    July 22, 2025
    Development

    Win the Accessibility Game: Combining AI with Human Judgment

    July 22, 2025
    Leave A Reply Cancel Reply

    For security, use of Google's reCAPTCHA service is required which is subject to the Google Privacy Policy and Terms of Use.

    Continue Reading

    CVE-2025-25257 – Fortinet FortiWeb SQL Injection Vulnerability

    Common Vulnerabilities and Exposures (CVEs)

    CVE-2025-46610 – Artec EMA Mail CSRF Vulnerability

    Common Vulnerabilities and Exposures (CVEs)

    The real story behind Steve Ballmer’s “Developers!” chant — a concoction of Microsoft’s flawed “just a platform company” culture and a dire need to collaborate with third-party developers

    News & Updates

    CVE-2025-7021 – OpenAI Operator SaaS Fullscreen API Spoofing and UI Redressing

    Common Vulnerabilities and Exposures (CVEs)

    Highlights

    CVE-2025-20673 – “Netgear Wireless LAN STA Driver Denial of Service Vulnerability”

    June 2, 2025

    CVE ID : CVE-2025-20673

    Published : June 2, 2025, 3:15 a.m. | 4 hours, 6 minutes ago

    Description : In wlan STA driver, there is a possible system crash due to an uncaught exception. This could lead to local denial of service with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00413200; Issue ID: MSV-3304.

    Severity: 0.0 | NA

    Visit the link for more details, such as CVSS details, affected products, timeline, and more…

    CVE-2025-2558 – “WordPress Theme-Wound LFI Vulnerability”

    April 24, 2025

    GNOME Dropping X11 Support May Complicate Next Ubuntu LTS

    May 22, 2025

    The Types of Data Analytics with Real-World Applications

    May 19, 2025
    © DevStackTips 2025. All rights reserved.
    • Contact
    • Privacy Policy

    Type above and press Enter to search. Press Esc to cancel.