IP Library Granted Patent US 12,499,429
Granted Patent B2
US 12,499,429 · App. 18/671,397 · Granted Dec 16, 2025

Automated teller machine (ATM) exception identification and analysis

Inventors: Daryl K. Ujita (Alhambra, CA); Cindy L. Cliff (Howell, MI); Jane M. Lauritzen (Seattle, WA); Adam L. Newell (Land O Lakes, FL); Joshua J. White (Terrell, TX); Alex Ledezma (Grand Prairie, TX); Troy B. Hook (Spokane, WA); Purvi Jariwala (Tampa, FL); Chanda Jill Cross (Rockwall, TX)
Assignee: Bank of America Corporation
G06Q20/1085
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,499,429
App. No.
18/671,397
Granted
Dec 16, 2025
Kind
B2
Abstract

Arrangements for identifying, analyzing, and remediating automated teller machine (ATM) exceptions are provided. A computing platform may configure an exception mapping table to match an exception code to a corresponding exception type. The computing platform may receive exception codes associated with one or more automated teller machines (ATMs). The computing platform may map the exception codes to corresponding exception types. The computing platform may compile exception ranking information into a ranked list. The computing platform may identify a subset of ATMs to take action on. The computing platform may identify actions to remediate issues related to the exception codes. The computing platform may automatically execute the identified actions.

Claims (75)

1 . A computing platform comprising:

at least one processor;

a communication interface communicatively coupled to the at least one processor; and

memory storing computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:

configure an exception mapping table to match an exception code to a corresponding exception type;

identify whether a particular exception code corresponds to an exception type;

based on determining that the particular exception code does not correspond to the exception type:

create a new exception type for the particular exception code; and

dynamically update the exception mapping table based on the new exception type;

receive one or more exception codes associated with one or more automated teller machines (ATMs);

map the one or more exception codes to one or more corresponding exception types;

compile exception ranking information, wherein the exception ranking information ranks the one or more exception codes based on a total number of each one of the one or more exception codes;

identify a subset of ATMs, wherein the identifying is based on a top three ranked exception codes of the one or more exception codes; and

identify one or more actions to remediate issues associated with the top three ranked exception codes; and

automatically execute the one or more actions, by sending one or more commands, that when received by the subset of ATMs, direct the subset of ATMs to automatically execute the one or more actions.

2 . The computing platform of claim 1 , wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:

generate an exception report, wherein the exception report comprises the exception ranking information, the subset of ATMs, and the one or more actions.

3 . The computing platform of claim 2 , wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:

send, to an enterprise computing device, the exception report and one or more commands directing the enterprise computing device to display the exception report, wherein sending the one or more commands directing the enterprise computing device to display the exception report causes the enterprise computing device to display the exception report.

4 . The computing platform of claim 1 , wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:

compare a total number of each exception code of the one or more exception codes to a first threshold; and

based on the total number exceeding the first threshold:

identify the one or more actions to remediate issues associated with the exception codes; and

automatically execute the one or more actions.

5 . The computing platform of claim 4 , wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:

compare the total number to a second threshold that is lower than the first threshold; and

based on the total number being equal to or below the first threshold but exceeding the second threshold:

identify the one or more actions; and

not automatically execute the one or more actions.

6 . The computing platform of claim 1 , wherein the creating is performed using a manual process at an enterprise computing device.

7 . The computing platform of claim 1 , wherein the creating is performed by an automated process using a trained model.

8 . The computing platform of claim 1 , wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:

update, using a dynamic feedback loop and based on the configuring, the mapping, the compiling, the identifying the subset of ATMs, and the identifying the one or more actions, an engine associated with the computing platform.

9 . A method comprising:

at a computing platform comprising at least one processor, a communication interface, and memory:

configuring an exception mapping table to match an exception code to a corresponding exception type;

identifying whether a particular exception code corresponds to an exception type;

based on determining that the particular exception code does not correspond to the exception type:

creating a new exception type for the particular exception code; and

dynamically updating the exception mapping table based on the new exception type;

receiving one or more exception codes associated with one or more automated teller machines (ATMs);

mapping the one or more exception codes to one or more corresponding exception types;

compiling exception ranking information, wherein the exception ranking information ranks the one or more exception codes based on a total number of each one of the one or more exception codes;

identifying a subset of ATMs, wherein the identifying is based on a top three ranked exception codes of the one or more exception codes; and

identifying one or more actions to remediate issues associated with the top three ranked exception codes; and

automatically executing the one or more actions, by sending one or more commands, that when received by the subset of ATMs, direct the subset of ATMs to automatically execute the one or more actions.

10 . The method of claim 9 , further comprising:

generating an exception report, wherein the exception report comprises the exception ranking information, the subset of ATMs, and the one or more actions; and

sending, to an enterprise computing device, the exception report and one or more commands directing the enterprise computing device to display the exception report, wherein sending the one or more commands directing the enterprise computing device to display the exception report causes the enterprise computing device to display the exception report.

11 . The method of claim 9 , further comprising:

comparing a total number of exception codes to a first threshold; and

based on the total number of exception codes exceeding the first threshold:

identifying the one or more actions to remediate issues associated with the exception codes; and

automatically executing the one or more actions.

12 . The method of claim 11 , further comprising:

comparing the total number of exception codes to a second threshold that is lower than the first threshold; and

based on the total number of exception codes being equal to or below the first threshold but exceeding the second threshold:

identifying the one or more actions; and

not automatically executing the one or more actions.

13 . The method of claim 9 , wherein the creating is performed using a manual process at an enterprise computing device.

14 . The method of claim 9 , wherein the creating is performed by an automated process using a trained model.

15 . The method of claim 9 , further comprising:

updating, using a dynamic feedback loop and based on the configuring, the mapping, the compiling, the identifying the subset of ATMs, and the identifying the one or more actions, an engine associated with the computing platform.

16 . One or more non-transitory computer-readable storing instructions that, when executed by a computing platform comprising at least one processor, a communication interface, and memory, cause the computing platform to:

configure an exception mapping table to match an exception code to a corresponding exception type;

identify whether a particular exception code corresponds to an exception type;

based on determining that the particular exception code does not correspond to the exception type:

create a new exception type for the particular exception code; and

dynamically update the exception mapping table based on the new exception type;

receive one or more exception codes associated with one or more automated teller machines (ATMs);

map the one or more exception codes to one or more corresponding exception types;

compile exception ranking information, wherein the exception ranking information ranks the one or more exception codes based on a total number of each one of the one or more exception codes;

identify a subset of ATMs, wherein the identifying is based on a top three ranked exception codes of the one or more exception codes; and

identify one or more actions to remediate issues associated with the top three ranked exception codes; and

automatically execute the one or more actions, by sending one or more commands, that when received by the subset of ATMs, direct the subset of ATMs to automatically execute the one or more actions.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 22, 2024
From: UJITA, DARYL K.; CLIFF, CINDY L.; LAURITZEN, JANE M.; NEWELL, ADAM L.; WHITE, JOSHUA J.; LEDEZMA, ALEX; HOOK, TROY B.; JARIWALA, PURVI; CROSS, CHANDA JILL
To: BANK OF AMERICA CORPORATION
Reel/Frame 067496/0298 →
Continuity (1)
Related Publication 20250363473A1 · Nov 27, 2025
References Cited (28)
US 6726097B2 · Graef et al. · 2004 [cited by applicant]
US 7377425B1 · Ma et al. · 2008 [cited by applicant]
US 7974922B1 · Hecht, Jr. · 2011 [cited by examiner]
US 8169602B2 · Jones et al. · 2012 [cited by applicant]
US 8225989B1 · Turocy et al. · 2012 [cited by applicant]
US 8231049B2 · Agrawal · 2012 [cited by applicant]
US 8448849B1 · Jenkins et al. · 2013 [cited by applicant]
US 8739150B2 · Gass et al. · 2014 [cited by applicant]
US 8843391B2 · Fordyce, III et al. · 2014 [cited by applicant]
US 8983877B2 · Chari et al. · 2015 [cited by applicant]
US 9031860B2 · Winters et al. · 2015 [cited by applicant]
US 9280764B2 · Faith et al. · 2016 [cited by applicant]
US 9317745B2 · Smith et al. · 2016 [cited by applicant]
US 9491104B2 · Melick et al. · 2016 [cited by applicant]
US 9990636B1 · Lewis et al. · 2018 [cited by applicant]
US 10129777B2 · Austin et al. · 2018 [cited by applicant]
US 10339554B2 · Yoder et al. · 2019 [cited by applicant]
US 10607244B2 · Fordyce et al. · 2020 [cited by applicant]
US 10645022B2 · Kaminski et al. · 2020 [cited by applicant]
US 20160379180A1 · Smith · 2016 [cited by examiner]
US 20200074545A1 · Rose et al. · 2020 [cited by applicant]
US 20210082042A1 · Bhakta et al. · 2021 [cited by applicant]
US 20210398094A1 · Hunt · 2021 [cited by examiner]
IN 476KO2010A · 2010 [cited by examiner]
WO WO2014117240A1 · 2014 [cited by examiner]
Iven. Amber: 5 Common ATM error and How to Fix Them, Jun. 29, 2021, ATM Depot, pp. 1-10 (Year: 2021). [cited by examiner]
Petrlic, Ronald: Integrity Protection for Automated Teller Machine, 2011, International Joint Conference of IEEE TrustCom, pp. 829-834 (Year: 2011). [cited by examiner]
Cabral et al.: A transactional model for automatic exception handling, 2011, Computer languages, Systems & Structures, pp. 43-61 (Year: 2011). [cited by examiner]