8543477

Value Tracking and Reporting of Automated Clearing House Transactions

PublishedSeptember 24, 2013
Assigneenot available in USPTO data we have
Technical Abstract

Patent Claims
56 claims

Legal claims defining the scope of protection, as filed with the USPTO.

1

1. A computer-implemented method for value tracking of automated clearing house (“ACH”) payments processed by an ACH operator, comprising the steps of: receiving via a computer at the ACH operator an ACH file for ACH processing by the ACH operator, the ACH file comprising at least one ACH payment originated by a remote sending point on behalf of an originating depository financial institution (“ODFI”) and forwarded to the ACH operator by the remote sending point; determining via the computer whether the at least one ACH payment creates an accumulated payment value for ACH payments processed for the ODFI during a specified time period that exceeds a pre-established payment cap; processing the at least one ACH payment in response to a determination that the at least one ACH payment does not create an accumulated payment value that exceeds the payment cap; and determining whether to override the payment cap and to process the at least one ACH payment in response to a determination that the at least one ACH payment creates an accumulated payment value that exceeds the payment cap.

2

2. The computer-implemented method according to claim 1 , wherein said step of determining whether the at least one ACH payment creates an accumulated payment value that exceeds the payment cap comprises the steps of: adding a sum value of the at least one ACH payment to a value of prior payments processed for the ODFI during the specified time period to obtain the accumulated payment value; and comparing the accumulated payment value to the payment cap.

3

3. The computer-implemented method according to claim 1 , wherein said step of determining whether to exceed the payment cap comprises the steps of: receiving approval from the ODFI to exceed the payment cap; and processing the at least one ACH payment in response to receiving the approval.

4

4. The computer-implemented method according to claim 1 , wherein said step of determining whether to exceed the payment cap comprises the steps of: receiving a denial of approval from the ODFI to exceed the payment cap; and rejecting the at least one ACH payment in response to receiving the denial of approval.

5

5. The computer-implemented method according to claim 1 , wherein said step of determining whether to exceed the payment cap comprises the step of following default instructions from the ODFI regarding approval to exceed the payment cap.

6

6. The computer-implemented method according to claim 1 , further comprising the steps of: determining whether the ODFI desires value tracking of the at least one ACH payment; and performing said method in response to a determination that the ODFI desires value tracking of the at least one ACH payment.

7

7. The computer-implemented method according to claim 6 , wherein said step of determining whether the ODFI desires value tracking comprises identifying a data string associated with the ACH file which indicates that the ODFI desires value tracking.

8

8. The computer-implemented method according to claim 7 , wherein the data string identifies at least one of the ODFI and the remote sending point.

9

9. The computer-implemented method according to claim 7 , wherein the data string identifies an originator of the ODFI.

10

10. The computer-implemented method according to claim 6 , wherein said step of determining whether the ODFI desires value tracking comprises identifying the ODFI based on a dedicated node via which the ACH operator received the ACH file from the remote sending point.

11

11. The computer-implemented method according to claim 1 , further comprising the step of pending the ACH file prior to performing said step of determining whether the at least one ACH payment creates an accumulated payment value that exceeds the payment cap.

12

12. The computer-implemented method according to claim 1 , wherein the ACH file comprises a plurality of ACH payments, wherein said method further comprises the step of processing a portion of the ACH payments in response to a determination that the at least one ACH payment creates an accumulated payment value that exceeds the payment cap, wherein the portion of the ACH payments does not create an accumulated payment value that exceeds the payment cap.

13

13. The computer-implemented method according to claim 1 , wherein the ACH file comprises an ACH batch that comprises the at least one ACH payment.

14

14. The computer-implemented method according to claim 1 , wherein the at least one ACH payment comprises at least one ACH credit payment and the payment cap comprises a credit payment cap.

15

15. The computer-implemented method according to claim 1 , wherein the at least one ACH payment comprises at least one ACH debit payment and the payment cap comprises a debit payment cap.

16

16. The computer-implemented method according to claim 1 , wherein the specified time period comprises one of a settlement date on which the ACH operator will settle the at least one ACH payment, a process date on which the ACH operator will process the at least one ACH payment, and an exposure period based on processed but unsettled payments.

17

17. The computer-implemented method according to claim 1 , wherein the remote sending point comprises one of a third party direct depositor and a remote originator.

18

18. The computer-implemented method according to claim 1 , wherein the ODFI comprises an originating depository financial institution.

19

19. A computer-implemented method for value tracking of automated clearing house (“ACH”) payments processed by an ACH operator, comprising the steps of: receiving via a computer an ACH file at the ACH operator for ACH processing by the ACH operator, the ACH file comprising an ACH batch that comprises at least one ACH payment originated by a remote sending point on behalf of an originating depository financial institution (“ODFI”) and forwarded to the ACH operator by the remote sending point; adding via the computer a sum value of the at least one ACH payment in the ACH batch to a value of payments previously processed for the ODFI to obtain an accumulated payment value; comparing via the computer the accumulated payment value to a pre-established payment cap to determine whether the accumulated payment value exceeds the payment cap; processing the at least one ACH payment in response to a determination that the accumulated payment value does not exceed the payment cap; and determining whether to override the payment cap and to process the at least one ACH payment in response to a determination that the accumulated payment value exceeds the payment cap.

20

20. The computer-implemented method according to claim 19 , wherein the ACH file comprises a plurality of ACH batches that each comprise at least one ACH payment, and wherein the method further comprises the step of parsing the ACH file to identify one of the ACH batches that comprises the at least one ACH payment originated by the remote sending point on behalf of the ODFI.

21

21. The computer-implemented method according to claim 19 , wherein said step of determining whether to override the payment cap comprises the steps of: receiving approval from the ODFI to exceed the payment cap; and processing the at least one ACH payment in response to receiving the approval.

22

22. The computer-implemented method according to claim 19 , wherein said step of determining whether to override the payment cap comprises the steps of: receiving a denial of approval to exceed the payment cap from the ODFI; and rejecting the ACH batch in response to receiving the denial of approval.

23

23. The computer-implemented method according to claim 19 , wherein the ACH batch comprises a plurality of ACH payments, and wherein said step of determining whether to override the payment cap comprises the steps of: receiving a denial of approval to exceed the payment cap from the ODFI; and rejecting a portion of the ACH payments in response to receiving the denial of approval.

24

24. The computer-implemented method according to claim 19 , wherein said step of determining whether to override the payment cap comprises the step of following default instructions from the ODFI regarding approval to exceed the payment cap.

25

25. The computer-implemented method according to claim 19 , further comprising the steps of: determining whether the ODFI desires value tracking of the at least one ACH payment; and performing said method in response to a determination that the ODFI desires value tracking of the at least one ACH payment.

26

26. The computer-implemented method according to claim 25 , wherein said step of determining whether the ODFI desires value tracking comprises identifying a data string associated with the ACH batch which indicates that the ODFI desires value tracking.

27

27. The computer-implemented method according to claim 26 , wherein the data string identifies at least one of the ODFI and the remote sending point.

28

28. The computer-implemented method according to claim 26 , wherein the data string identifies an originator of the ODFI.

29

29. The computer-implemented method according to claim 25 , wherein said step of determining whether the ODFI desires value tracking comprises identifying the ODFI based on a dedicated node via which the ACH operator received the ACH file from the remote sending point.

30

30. The computer-implemented method according to claim 19 , further comprising the step of pending the ACH batch prior to performing said comparing step.

31

31. The computer-implemented method according to claim 19 , wherein the ACH batch comprises a plurality of ACH payments, wherein said method further comprises the step of processing a portion of the ACH payments in response to a determination that the accumulated payment value exceeds the payment cap, and wherein a sum value of the portion of the ACH payments added to the value of payments previously processed for the ODFI results in an accumulated payment value that does not exceed the payment cap.

32

32. The computer-implemented method according to claim 19 , wherein the at least one ACH payment comprises at least one ACH credit payment and the payment cap comprises a credit payment cap.

33

33. The computer-implemented method according to claim 19 , wherein the at least one ACH payment comprises at least one ACH debit payment and the payment cap comprises a debit payment cap.

34

34. The computer-implemented method according to claim 19 , wherein the value of prior payments previously processed for the ODFI is based on prior payments processed during a specified time period.

35

35. The computer-implemented method according to claim 34 , wherein the specified time period comprises one of a settlement date on which the ACH operator will settle the at least one ACH payment, a process date on which the ACH operator will process the at least one ACH payment, and an exposure period based on processed but unsettled payments.

36

36. The computer-implemented method according to claim 19 , wherein the remote sending point comprises one of a third party direct depositor and a remote originator.

37

37. The computer-implemented method according to claim 19 , wherein the ODFI comprises an originating depository financial institution.

38

38. A computer-implemented method for value tracking of automated clearing house (“ACH”) payments processed by an ACH operator, comprising the steps of: receiving via a computer at the ACH operator an ACH file for ACH processing by the ACH operator, the ACH file comprising at least one ACH debit payment originated by a remote sending point on behalf of an originating depository financial institution (“ODFI”) and forwarded to the ACH operator by the remote sending point; adding via the computer a sum value of the at least one ACH debit payment to a value of prior debit payments previously processed for the ODFI during a specified time period to obtain an accumulated payment value; determining via the computer whether the accumulated payment value exceeds a pre-established debit payment cap; and rejecting the at least one ACH debit payment in response to a determination that the accumulated payment value exceeds the payment cap.

39

39. The computer-implemented method according to claim 38 , wherein said rejecting step comprises the steps of: determining whether to override the payment cap and to process the at least one ACH debit payment in response to a determination that the accumulated payment value exceeds the payment cap; and rejecting the at least one ACH debit payment in response to a determination not to override the payment cap and to process the at least one ACH debit payment.

40

40. The computer-implemented method according to claim 38 , further comprising the step of processing the at least one ACH debit payment in response to a determination that the accumulated payment value does not exceed the payment cap.

41

41. The computer-implemented method according to claim 39 , wherein said step of determining whether to override the payment cap comprises the steps of: receiving a denial of approval from the ODFI to exceed the payment cap; and rejecting the at least one ACH debit payment in response to receiving the denial of approval.

42

42. The computer-implemented method according to claim 39 , wherein the ACH file comprises an ACH batch that comprises the at least one ACH debit payment.

43

43. The computer-implemented method according to claim 42 , wherein said step of determining whether to override the payment cap comprises the steps of: receiving a denial of approval from the ODFI to exceed the payment cap; and rejecting the ACH batch in response to receiving the denial of approval.

44

44. The computer-implemented method according to claim 42 , wherein the ACH batch comprises a plurality of ACH debit payments, and wherein said step of determining whether to override the payment cap comprises the steps of: receiving a denial of approval from the ODFI to exceed the payment cap; and rejecting a portion of the ACH batch in response to receiving the denial of approval, the portion comprising ACH debit payments that cause the accumulated value to exceed the debit payment cap when added to the value of prior debit payments.

45

45. The computer-implemented method according to claim 39 , wherein said step of determining whether to override the payment cap comprises the steps of: receiving approval from the ODFI to exceed the payment cap; and processing the at least one ACH debit payment in response to receiving the approval.

46

46. The computer-implemented method according to claim 39 , wherein said step of determining whether to override the payment cap comprises the step of following default instructions from the ODFI regarding approval to exceed the payment cap.

47

47. The computer-implemented method according to claim 38 , wherein the ACH file comprises a plurality of ACH batches that each comprise at least one ACH debit payment, and wherein the method further comprises the step of parsing the ACH file to identify one of the ACH batches that comprises the at least one ACH debit payment originated by a remote sending point on behalf of the ODFI.

48

48. The computer-implemented method according to claim 38 , further comprising the steps of: determining whether the ODFI desires value tracking of the at least one ACH debit payment; and performing said method in response to a determination that the ODFI desires value tracking of the at least one ACH debit payment.

49

49. The computer-implemented method according to claim 48 , wherein said step of determining whether the ODFI desires value tracking comprises identifying a data string associated with the ACH file which indicates that the ODFI desires value tracking.

50

50. The computer-implemented method according to claim 49 , wherein the data string identifies at least one of the ODFI and the remote sending point.

51

51. The computer-implemented method according to claim 49 , wherein the data string identifies an originator of the ODFI.

52

52. The computer-implemented method according to claim 48 , wherein said step of determining whether the ODFI desires value tracking comprises identifying the ODFI based on a dedicated node via which the ACH operator received the ACH file from the remote sending point.

53

53. The computer-implemented method according to claim 38 , further comprising the step of pending the ACH file prior to performing said step of determining whether the accumulated payment value exceeds the debit payment cap.

54

54. The computer-implemented method according to claim 38 , wherein the specified time period comprises one of a settlement date on which the ACH operator will settle the at least one ACH debit payment, a process date on which the ACH operator will process the at least one ACH debit payment, and an exposure period based on processed but unsettled payments.

55

55. The computer-implemented method according to claim 38 , wherein the remote sending point comprises one of a third party direct depositor and a remote originator.

56

56. The computer-implemented method according to claim 38 , wherein the ODFI comprises an originating depository financial institution.

Patent Metadata

Filing Date

Unknown

Publication Date

September 24, 2013

Inventors

Robert Anthony Love
Lantanya Neale Mauriello
Nesta Valerie Reckord-Yarde
Susan Lynne Robertson
Robert Williams
Donald E. Nelson

Want to explore more patents?

Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.

Citation & reuse

Analysis on this page is generated by Patentable — an AI-powered patent intelligence platform. AI-generated summaries, explanations, and analysis may be reused with attribution and a visible link back to the canonical URL below. Patent abstracts and claims are USPTO public domain.

Cite as: Patentable. “VALUE TRACKING AND REPORTING OF AUTOMATED CLEARING HOUSE TRANSACTIONS” (8543477). https://patentable.app/patents/8543477

© 2026 Patentable. All rights reserved.

Patentable is a research and drafting-assistant tool, not a law firm, and does not provide legal advice. Documents we generate are drafts for review by a licensed patent attorney.