Sass Trucking, Inc. v. Security Bank and Trust Co.

Decision Date05 May 1987
Docket NumberNo. 62621,62621
Citation737 P.2d 113
Parties, 3 UCC Rep.Serv.2d 927, 1987 OK 33 SASS TRUCKING, INC., Appellee, v. SECURITY BANK AND TRUST COMPANY, Blackwell, Oklahoma, Appellant.
CourtOklahoma Supreme Court

Guy Clark, Northcutt, Raley, Clark and Gardner, Ponca City, for appellee.

James R. Rodgers, Blackwell, for appellant.

Laura N. Pringle, Vice President and Gen. Counsel of the Oklahoma Bankers Ass'n, Oklahoma City, for amicus curiae Oklahoma Bankers Ass'n.

OPALA, Justice.

The narrow first-impression question for today's decision is whether a data processing center, sole agent for the payor bank, is a place of presentment for items triggering the "midnight deadline rule" of 12A O.S. 1981 § 4-302. 1 We answer in the affirmative and hold that the check-collecting

process, together with the constructive designation by the payor bank, constituted presentment at the data processing center for purposes of the midnight deadline rule.

PROCEDURAL HISTORY

Sass Trucking, Inc. [Sass], appellee, brought an action against Security Bank and Trust Company of Blackwell [Security or payor bank], appellant, to recover the amount of six checks drawn upon it as payor bank, which were made payable to Sass. The petition asserted a claim on two alternative theories; one based on 12A O.S. 1981 § 4-302 which sets a midnight deadline for the timely dishonoring of checks, and the other alleged that sufficient funds were available for collection during the time period in question. The trial court found after a bench trial that (a) the data processing center was not a collecting bank within the chain of check processing; (b) as to each of the six checks in contest, the bank failed to return the checks by its midnight deadline and (c) by its failure, the bank became legally accountable for the amount of the checks. Judgment was rendered for Sass in the sum of $19,827.09 plus interest and court costs.

ANALYSIS OF CHECK PROCESSING FUNCTION

Sass received six checks from Gordon Riecken which were drawn upon Security. Sass deposited the checks to its account at the Bank of Bennington in Bennington, Nebraska. The checks arrived in this state at the Oklahoma City branch of the Federal Reserve Bank. They were then dispatched by courier to First Data Management Corporation [FDMC], a data processing center located in Oklahoma City, leaving the Federal Reserve Bank at 2 a.m. and arriving at the data processing center at 9 the same morning. The checks were then sent from FDMC to the payor bank [Security] and arrived at 8 a.m. the next morning before the staff entered the bank. Each time the checks reached FDMC on one banking day, they were delivered to the payor bank on the next banking day, and then were returned to Sass's bank in Nebraska the following day.

The FDMC processed and posted checks for Security. Its tasks consisted of posting books, sorting the checks in numeric sequence so that the payor bank could file them in the customer's account and printing reports that showed sufficient items and those that were rejected. FDMC's service, in effect, took the place of the bank's bookkeeping department by carrying out the electronic process for the bank. The data processing center would pay on the customer's account unless the check was "kicked out" 2 for insufficient funds or for some other reason. Kicked-out checks are sent back to the bank, and the accounts are manually pulled to determine if the problem was attributable to a wrong number or to insufficient funds. The payor bank then makes its decision to dishonor.

FDMC did not have a connection with any government agency. It is a private bookkeeping computer service that had a written agreement with Security authorizing it to accept cash letters from the Federal Reserve Bank's courier on Security's behalf. In performance of the bank's particular cash letter and check sorting functions, FDMC is entirely under Security's employ or is the bank's agent. In essence, the facts reveal that payor bank had moved its bookkeeping to an external source.

I

The Code provisions that govern presentment, dishonor and the applicable deadline are pertinent to our consideration of whether the receipt of checks by FDMC triggered the running of the midnight deadline for the return of the checks.

Presentment is a demand for acceptance or payment made upon the maker, acceptor, drawee, or other payor by or on behalf of the holder. § 3-504(1). A payor bank is liable to pay the check if the bank, after the item has been "presented and received," does not settle for, pay, return or send notice of dishonor until after the midnight deadline. § 4-301(1). If a bank decides to dishonor a check drawn on it, notice must be given to the party presenting the check for payment. Sections 3-508(2), 4-301 and 4-302 of the Code govern the payor bank's ability to dishonor an item. Section 3-508(2) provides that any notice of dishonor "must be given by a bank before its midnight deadline." The midnight deadline, with respect to a bank, "is midnight on its next banking day following the banking day on which it receives the relevant item or notice or from which the time for taking action commences to run, whichever is later." § 4-104(1)(h). A "banking day" under § 4-104(1)(c) means "that part of any day on which a bank is open to the public for carrying on substantially all its banking functions."

II

Check sorting by computer is done either internally at the payor bank or externally at another location designated by the payor bank to perform this function. The checks in contest went through a data processing system that was separate from the bank site. Security employed FDMC to perform duties that otherwise would have been handled within the bank. By the time the case came to trial, Security had established its own data processing center at the bank and checks were being forwarded directly to it. Testimony of bank employees revealed that when Security had its own computer the time interval allowed for the check processing was no different from that when FDMC performed these duties. Items from the Federal Reserve Bank arrived at the same time--9 a.m.--regardless of whether they were sent first to a data processing center or directly to the bank. The first banking day of receipt is used to sort the items either at the bank, if the bank has its own computer, or at the data processing center. The record clearly demonstrates that no time is lost in transporting the items from a data processing center to the bank because the items are waiting for the bank staff on the morning of the second banking day. According to the testimony, the process of pulling and dishonoring items is made on the second day even if the processing is done by the bank's own computer service. In essence, we cannot find on this record that there would be greater hardship for banks which employ a data processing service than for those that maintain one as an on-site facility.

Presentment should not be governed here by strict construction of the agreement between the parties nor by mere technicalities. Upon its physical arrival at the payor bank, an item is stamped by an employee who is without power to dishonor, while a data processing center does not affix a stamp. Because the receiving and sorting of checks is identical in both situations, "stamping" is merely a formality for midnight deadline purposes and is not critical to presentment. The item would be received either by the bank's employee or by its agent. The focus of the agreement between the payor bank and the data processing center should be on the content and the duties to be performed under the written agreement rather than on mere formalities. Banks could otherwise circumvent midnight deadlines by leaving out legal terms in its contracts such as "presentment" and focusing on formalities such as stamping. At best Security asserts a very narrow interpretation of presentment. It would require presentment to have a physical situs at the same place as where the power to dishonor resides. Arguably then, even under a direct system where the bank has its own computer, presentment will not be made until the second banking day because the people sorting the items do not have the power to dishonor. We choose a more realistic interpretation. Based on the circumstances of this case, the process of deciding whether to pay begins on the first banking day of the item's receipt. It is logical to extend presentment to the data processing center when it performs the same duties which begin the process of dishonor.

Security argues that Oklahoma's Code provisions governing "presentment" do not allow such a result because a necessary provision that is found in the statutory scheme of many other states is omitted from 12A O.S.1981 § 4-204. Subsection (3) of the cited section, which was not adopted in Oklahoma, provides:

"(3) Presentment may be made by a presenting bank at a place where the payor bank has requested that presentment be made."

Security reasons that since Oklahoma's version of § 4-204, which lists the methods of sending and presenting checks by a collecting bank, does not contain the quoted text in the section, presentment must be made directly to the payor. Had this section been in our statutory scheme, it may have removed some doubt but it does not necessarily follow that its absence requires a different result. Its omission only stresses the importance of conformity when applying the midnight deadline rule. The purpose of the rule is to allow adequate time for processing of checks as well as to increase efficiency from the customer's standpoint. The trial court correctly foresaw a danger of payor banks decreasing efficiency by attempting to capture float benefits if they are not required to pay for one additional day. Banks could also manipulate the midnight deadline by controlling the time to forward the check from the data processing center. 3

Other jurisdictions offer little...

To continue reading

Request your trial

VLEX uses login cookies to provide you with a better browsing experience. If you click on 'Accept' or continue browsing this site we consider that you accept our cookie policy. ACCEPT