Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
The Almighty Buck Software Supercomputing News Hardware

Banks' Big Upgrade: Meet Real-Time Processing 89

CWmike writes "It has been years since the banking industry made any large investments in core IT systems, but some of the largest financial services firms in the U.S. are now in the midst of rolling out multi-million dollar projects, say industry experts. About a decade ago, they began replacing decades-old Cobol-based core systems, with open, Web-enabled apps. Now, they are spending more than $100,000,000 to replace aging systems, converting to real-time mobile applications for retail services such as savings and checking accounts and lending systems. The idea behind going real-time: Grab more business — and money — from customers. 'Five of the top 20 banks are engaged in some sort of core banking replacement and we expect to see another three or four in next 12 months,' said Fiaz Sindhu, who leads Accenture's North American core banking practice. 'They're looking at those upgrades as a path to growth.'"
This discussion has been archived. No new comments can be posted.

Banks' Big Upgrade: Meet Real-Time Processing

Comments Filter:
  • competition (Score:4, Funny)

    by cdibbs ( 1979044 ) on Friday July 15, 2011 @05:18PM (#36780266)
    ... with Bitcoin.
  • by Anonymous Coward

    I hope the banks get all the money they need to stay afloat.

  • The idea behind going real-time: Grab more business â" and money â" from customers.

    Yield-management pricing techniques, like airplane tickets, for everything else in your life.

    Just download this handy android banking app that also reports your location data. When you walk by a high-end furniture store it will pop-up a teaser interest rate for any credit card purchases in the next hour.

    I can't wait!!!

  • considering everything is just magnetic ink these days, can someone please explain why is it that paypal transfers still takes a week+ to show up in bank account?

    • Because paypal lies to collect interest for as long as possible, which given interests rates are close to 0% is fair enough?

    • So paypal can get interest on your money.

    • Because PayPal sucks?

      • ACH transfers between banks still take 3 days (some banks offer "express" transfers that complete in one business day...but they usually have something like a $1000 limit).

        Still seems odd that my Amex charges show up in my account minutes after I buy something...but my transfer from checking to savings (at another bank) or my brokerage takes 3 days.

        • by h4rr4r ( 612664 )

          Of course. When they are expecting to be paid that is going to be instant. When they can sit on the money for a few days and make interest at your expense they will do that.

        • by afidel ( 530433 )
          No, they don't. The fed clearing house for ACH payments has I believe a 4 hour SLA. Now if the bank on either end takes an additional day to batch process the results that's their problem. I guess that's kind of the point of the article though, instead of doing one batch run at night the banks are going to doing what most other sane businesses do today which is real time processing. Interestingly electronic check images from vendors almost always process the next day for this very reason, the submit them to
        • But now they'll spend a hundred million!

          They'll fix everything with that amount!
          With that money you could cool the tents in Afganistan for almost 2 days or pay the yearly bonus of a CEO or 2.

        • ACH transfers take less than 24 hours, they all clear the day they are put in. There is no delay. Within 24 hours of the start EVERYONE knows the completion status, thats the advantage of it being controlled by the fed so banks can't dick with you.

          Anyone who says it takes longer is doing it to gain interest from your money before they give it to you. Which is exactly what paypal does. The longer delays you see are because its profitable for them, the person who has the money holds onto it as long as pos

    • by Anonymous Coward

      All banks paypal included use the ACH system and clear checks through the slowest banks and clearing houses available to get more interest. It's an old business model that's been around for ever and will eventually be replaced by real-time systems and a bunch of other possibly scuzzy fee based approaches.

  • by paulsnx2 ( 453081 ) on Friday July 15, 2011 @05:33PM (#36780420)

    None of this should be taken as meaning they should not modernize. It is just that they have taken this long to realize that they might make more money by being fast than by being slow. I expect they have figured out how to be either, depending on how it benefits them.

  • by quietwalker ( 969769 ) <> on Friday July 15, 2011 @05:44PM (#36780522)

    I currently write financial software targeted at small and mid-sized banks. The article was ... confused, so, let me try to clear it up a bit:

    In the computing world, when you say you're going to replace your core systems, you're talking about replacing either the main software or hardware that your systems run on - or both. In the banking world, when you say 'core system' (or 'host system'), you're talking about the software package being used to store your customer's account data, such as Fiserve or Miser.

    The article confusingly references both types of changes and appeared to treat them interchangeably.

    Similarly, the phrase 'realtime' has a loaded meaning in the banking world. Outside of the banking world, 'realtime' means 'instantaneous', such as 'realtime rendering'. Inside the banking world, realtime means that actions (such as transfers) are submitted directly against the core system, as opposed to a proxying system which determines rates ($/day, max $, etc), fees, and tries to keep track of the active balance vs. ledger balance. The alternative to 'realtime' is 'batch' - where everything is performed in one fell swoop at the end of a day - when you reconcile the day's transactions.

    Some transactions - such as inter-bank account to account transfers can usually be handled in 'realtime' even if the core doesn't support it. The necessary proxy can know everything about that bank's transactions, and can guarantee the availability of funds, so it's allowed. External transfers can't be though. Thus the separation between available balance and ledger balance. You can see this on credit card systems too; your payment may show up on the site as being verified, but not yet applied. In fact, with only few exceptions, when money is sent from one location to another, the actual movement is not finalized for a day or two. Both sides make note of it, so funds are made available, but it can be cancelled or reversed at any point in time before that.

    In any case in the banking world, mobile or web (or even atm and point-of-sale teller terminals) don't care much about whether the backend core is in realtime or batch mode. It has nothing to do whatsoever with that functionality. Those are just pieces of software that hook into the core - and the core (or adapters for it) must support that functionality.

    Whew! It was hard to read that article with the mixing of those definitions and a base misunderstanding of their purposes.

    • by BigFire ( 13822 )

      You don't actually expect them to know this? We still have 27 years until the world really comes to end.

    • mod parent up.

      I learned more from that one post that I did in my entire time in reform school. er, I mean, high school.

      (seriously, that post was quite informative. appreciate the inside view, we never get to see that.)

    • It's a hard change for them to make as a very large percentage of the old mainframe folks just don't consider anything but the batch approach. I don't know the number of times I've tried to explain the concept of queue based 'as soon as possible' processing or some other non-batch approach to those that grew up in the lameframe/COBOL world. I hope they're taking the opportunity to decouple things and rewrite things in a more maintainable manner. Those old COBOL systems have generally turned into monolithic
      • Re: (Score:2, Insightful)

        by Anonymous Coward

        Sorry mate:

        It's a hard change for them to make as a very large percentage of the old mainframe folks just don't consider anything but the batch approach.

        The old mainframe folks are likely employed doing the sort of work they have done for longer than you have been alive. They know from experience what works and what does not. The batch approach is reliable, understood and suitable for the problem they have been tasked to solve.

        I don't know the number of times I've tried to explain the concept of queue based 'as soon as possible' processing or some other non-batch approach to those that grew up in the lameframe/COBOL world.

        I would like to hear what the mainframe programmers thought when they were told that everything they have been doing for the past thirty years is wrong by a Slashdotter that uses the term "lameframes".

        I hope they're taking the opportunity to decouple things and rewrite things in a more maintainable manner.

        Batch processing is

      • The mainframe hasn't been all batch since about 1973 when CICS was released and I've worked in several places that used MQSeries. You must have worked at some odd places. I hear you on the spaghetti code front, but if any of the systems written now survives 30 years I bet they'll be just as bad.

        • CICS dates back to 1998, see the recently produced history of CICS page []. CICS does POX, REST, and SOAP, in addition to MQ, so integration with the tried and true can be done and you can migrate to whatever you want on either side of the interface. Boring, I know. We are talking about banking, remember, not Facebook or Twitter.
        • It's not about the tools, it's about the attitude and approach. As someone else commented here, "they know what works and what doesn't". I've found that's not true. They will stick with a batch approach even for things are are quite clearly better using MQ or some other tool. I think it's quite funny that Grace Hopper, the inventor of COBOL said something like "The worst phrase you want to hear is that's the way we've always done it". Of course, perhaps that's just the attitude in the places I've worked.
          • I'm an ex-COBOL man myself and although I have come across "that's the way we've always done it", the majority of places (13 I think) that I worked in wanted to try new stuff as much as possible, especially after Y2K. I never worked anywhere where there wasn't online terminal based software where a batch approach would be impossible to do and the last place I worked had a website that used MQSeries to get information from the CICS backend.

            Speaking personally I've gone from COBOL to VBA to C# and ASP.NET at

        • CICS went generally available in 1969, not 1973. It did move from Palo Alto to Hursley, UK around 1973 though.

          In any case, retail banks mainly used IMS rather than CICS, which was more dominant in utilities (it was first developed at Chicago Power and Light) and insurance.

          The retail banking IMS systems were mainly written in assembler not COBOL. In IMS PL/1 was as likely to be used as COBOL.

  • I've been able to do a transaction, and see it deposited/deducted from my account in less than a second. And have been able to since about 1997, when I started online banking.. But I guess that's another reason credit unions rock.

    Now if only I could figure out why Visa insists on holding CC transactions for 3 days..

    • by geekoid ( 135745 )

      You might want to call you bank and ask if that money is immediately available. Yeah, it shows up right away, but when does the money really move? I'll wager at about 2 AM in the morning.

      • Can't speak to the parent's credit union, but at my small CU - yes, the funds are immediately available. I can have a $100 balance, deposit a $500 check, and walk right outside and withdraw $300 from the ATM.

        • It's not because the money is actually available. It still needs to snake it's way through the Federal ACH. The bank trusts the that the check is good and the $300 you leave with is more like a loan. Try to do that with a larger amount and you may have a problem. For example, my bank will let me walk out with a few hundred after depositing a check but I once had to wait almost a week for a $2500 check from an insurance company to clear before they would let me use that money.

          • That's typically if you do it via ATM or don't ask for the funds to be available right away. My business account's limit is $1K

            However, a few times I've asked for the funds to be made available right away, and the manager or assistant manager would take the check and do some magic in the back and then the funds ($3-4K) would be available.

          • by tlhIngan ( 30335 )

            There are two states for payments - initiated and posted.

            Initiated is when you write a check or use your credit card. Posted is when the money ends up in their final accounts. Initiation takes place in practically real time (they have ot make sure the money's there after all) at which point the funds are "locked", but the actual posting depends on the evidence being presented.

            The thing with cheques is that it's often sent through the mail, so you get a day or two of "float" before the actual initiation begi

  • Not quite (Score:5, Informative)

    We haven't been replacing those aging COBOL-based apps - that's a massive infrastructure that is well proven and works.
    When you have systems that churn through billions of daily transactions across millions of accounts, you don't just swap out the systems that do that processing if those systems are working well. It's not glamorous, but it's reliable and it works - and is not prone to new (and expensive) bugs that come with new development.

    No, what happened a few years ago was that we started upgrading the hardware and building new, more modern layers to fit on top of those back end systems. But replace them? Replacement is something that is happening very, very slowly. Think of it like erosion - the edges get worn down, we shore them up here and there. And when we have NO other choice, we replace them.

    We all ooh and aah over our 1000-TPS Weblogic systems - but forget that the backend COBOL applications are quietly handling all of that load and more.

    Fortunately, I'm not involved in the "legacy" systems, so I can be one of those marveling over how fast our Java stack is ;)

    These statements are my opinion and not representative of the beliefs or actions of my employer. etc, etc

    • by geekoid ( 135745 )

      haha, re replaced our system to get rid of those evil COBOL batch process and go to real time.

      Now we just rub a process at night to update our info.
      Plus it's less reliable and more expensive.
      Way to go upper management.

      • Our real-time systems are COBOL as well...

        Honestly, there's nothing wrong with (as long as I don' thave to maintain it), and it does work. On the other hand, based on the reports we get from that team, it makes it impossible for them to change anything without speccing it out a year ahead of time...

  • by PeanutButterBreath ( 1224570 ) on Friday July 15, 2011 @05:50PM (#36780568)

    Deposits? Pneumatic tube to the abacus room.

  • I don't think I'm grasping the concept here, but if retail stores tap into real-time banking, does that mean we will see digital price tags on products change rapidly in periods of hyper-inflation? That would be fun to watch (not).

    • Nope. The current state for most banks run process on a overnight cycle.

      So if you transfer $1 from checking to savings it will happen overnight.

      If you buy something at a retail store with a check, what normally happens is that
      1. the retail store closes it's book at the end of the day and sends the data to their bank.
      2. The retailer's bank sends the data to your bank overnight.
      3. Your bank processes the data on their overnight cycle.

      So the next time you buy something with your check

  • Banks are hurting right now. And why shouldn't they be? They made boatloads of bad decisions a few years ago, and are trying to make everybody else pay for them.

    A lot of people I know have given up their bank accounts altogether. Too many fees, too much BS. At a time when the banks should have been wooing customers with better deals, they piled on the fees and cut service.

    Let 'em fail. If they bring back good service at a decent price, well, okay. But the whole fractional-reserve banking system in thi
    • "too", damnit. Too big.
    • by afidel ( 530433 )
      I've had a checking accounts for 17 years and never once paid any fees for them, if you are paying tons of fees you are either impoverished or seriously mismanaging your finances (or both).
      • Perhaps you are grandfathered in? I got a TD Bank checking account a few years back where the main feature of the account was that it had no minimum balance. A few months later they added a minimum balance which I never realised until I saw that I had been dinged with multiple low balance fees on a statement I happened to check. The terms on this account I have seem to change month to month. Now I watch it like a hawk whereas before I was under the impression I could drop money into it every once and a

        • by afidel ( 530433 )
          Even when I was unemployed for 7 months I never dropped below $1k in my checking account, but mine actually has no minimum balance (for now, if Congress and the fed squeeze the banks enough they might impose one).
          • "for now, if Congress and the fed squeeze the banks enough they might impose one"

            See? You are illustrating my point. You know very well that if they are "squeezed", rather than luring new customers by giving better service, they will (and have) impose harsher conditions on their existing customers instead. No, that is NOT inevitable. It's just plain bad business. Banks have had it both ways for so long that they just don't seem to know what good business is anymore.

            Take your money out. Let 'em fail. Just don't do it all at once.

  • and 3 days to 2 weeks to clear a check and credit it to me. Hmmm.
    Definitely some room for improvement.

Kill Ugly Processor Architectures - Karl Lehenbauer