146 can cause electronic device 100 to vibrate or shake when activated. Vibration device 146 can be activated to provide an alert or notification to a user of electronic device 100. According to one aspect of the disclosure, display 130, speakers 144, and vibration device 146 can generally and collectively be referred to as output devices. These output devices can be each utilized to present the alert to the user.

Fingerprint sensor 147 can be used to provide biometric data or images to identify or authenticate a user. Location sensor 160 can provide time data and location data about the physical location of electronic device 100. In one embodiment, location sensor 160 can be a global positioning system (GPS) device that uses data received from geospatial input received from GPS satellites. Location information and data received from location sensor 160 can be utilized to identify when a user device is in close vicinity of a store or merchant from which an item can be purchased, where the purchase intent or price would be tracked within and count towards the budgeted amount.

Motion sensor(s) 161 can include one or more accelerometers 162 and gyroscope 163. Motion sensor(s) 161 can detect movement of electronic device 100 and provide motion data to processor 102 indicating the spatial orientation and movement of electronic device 100. Accelerometers 162 measure linear acceleration of movement of electronic device 100 in multiple axes (X, Y and Z). For example, accelerometers 162 can include three accelerometers, where one accelerometer measures linear acceleration in the X axis, one accelerometer measures linear acceleration in the Y axis, and one accelerometer measures linear acceleration in the Z axis. Gyroscope 163 measures rotation or angular rotational velocity of electronic device 100. Electronic device 100 further includes a housing 170 that contains the components of electronic device 100.

In the description of each of the following figures, reference is also made to specific components illustrated within the preceding figure(s). Similar or same components are presented with the same leading reference number.

Turning to FIG. 2, with ongoing reference to FIG. 1, electronic device 100 is shown in communication with application computer system 180. Application computer system 180 is communicatively coupled to wireless network 150 by a wide area network (WAN) 195, such as the Internet. In an embodiment, servers 190 of wireless network 150 support wireless exchange of e-mail, text, data, and other communication between electronic device 100 and application computer system 180.

Electronic device 100 can communicate wirelessly with wireless network 150 via transmission and reception of communication signals 194. Communication network 150 includes communication servers 190 that are communicatively connected to a larger, wide area network (WAN) 195, such as the Internet. Electronic device 100 can also establish connection and communicate with wireless network 150 and with WAN 195 via WiFi router 196 and short-range communication device(s) 164 (FIG. 1).

Application computer system 180 can host one or more applications that provide various functions. Application computer system 180 includes storage 210, such as one or more hard drives or solid state drives. Storage 210 can store a banking application database 220 and a shopping database 230. Banking application database 220 and shopping database 230 can support one or more applications 126 of electronic device 100. Banking application database 220 includes bank account data 222 and a budget data repository 224. Bank account data 222 can include bank account information, credit and debit card information, and loan information. Budget data repository 224 can include budget data 226. In one embodiment, a user can provide budget data 226 based on a user's personal budget. A personal budget is a plan for allocating future income towards expenses, savings, investment, and/or debt payments. In an example embodiment, budget data 226 can include several budget categories and allocated amounts for each budget category. Budget categories can include groceries, restaurant and other food, clothing, rent/mortgage, utilities, entertainment, insurance, etc., for one or more budget periods.

Shopping database 230 includes shopping account data 232, current cost data 234, historical data 236 and transaction data repository 238. Transaction data repository 238 includes transaction data 240. Shopping account data 232 can include merchant information, preferred payment methods, and preferred shipping methods. Current cost data 234 can include the current cost of one or more items or services that are available for purchase at a merchant. Historical data 236 can include the cost of one or more items or services that have been previously purchased at a merchant. In one embodiment, historical data 236 can be gathered from the anonymous historical purchase information of other users.

Transaction data 240 includes data corresponding to a current transaction being performed via electronic device 100. Transaction data 240 can include a merchant identifier, an item or service identifier, a payment amount, and other data related to facilitating a transaction.

According to one aspect of the disclosure, electronic device 100 can transmit a request 260 to application computer system 180 for budget data 226, current cost data 234, historical data 236, and transaction data 240. Electronic device 100 can receive, in response to the request 260, a response 262 that contains the budget data 226, current cost data 234, historical data 236, and transaction data 240. Electronic device 100 and application computer system 180 can perform a validation and authentication routine prior to the exchange of data and information to provide account verification and security.

Referring to FIG. 3A, there is shown one embodiment of example contents of system memory 120 of electronic device 100 configured to complete the various processes described herein. System memory 120 includes data, software, and/or firmware modules, including firmware 122, an operating system (O/S) 124, applications 126, budget alert module 128, and communication module 129.

Applications 126 include a primary application 310. Primary application 310 is a single application that provides access to one or more other applications. In one embodiment, primary application 310 can improve a user experience by having a single point of access for multiple applications. Primary application 310 includes a banking application 312, and a shopping application 314. Banking application 312 includes program code that is executed by processor 102 to enable electronic device 100 to access banking services provided by a bank or other financial institution. Shopping application 314 includes program code that is executed by processor 102 to enable electronic device 100 to access websites to browse and buy products or services from a retailer or service provider. While primary application 310 was shown including two applications, primary application 310 can include more or fewer than two applications. Applications 126 further include a navigation application 318. Navigation application 318 includes program code that is executed by processor 102 to enable electronic device 100 to provide access to navigation, mapping and location services.

Budget alert module 128 includes program code that is executed by processor 102 to enable electronic device 100 to perform the various features of the present disclosure. In one or more embodiments, budget alert module 128 enables electronic device 100 to present a budget alert for at least one budget category in response to detecting an over-budget condition. In one or more embodiments, execution of budget alert module 128 by processor 102 configures electronic device 100 to perform the processes presented in the flowcharts of FIGS. 7A-7B and 8A-8B, as will be described below. Communication module 129 enables electronic device 100 to communicate and exchange data with wireless network 150 and/or WiFi router 196 and with other devices.

System memory 120 includes artificial intelligence (AI) engine 320 and current location data 322. AI engine 320 accelerates artificial intelligence, natural language processing (NLP), context evaluation (CE), and machine learning applications. Current location data 322 includes a Current location 322A. Current location 322A is the current location of electronic device 100 as determined by location sensor 160. Location sensor 160, such as a GPS module, can sense, detect, or receive the current location of electronic device 100.

System memory 120 includes budget data 330. Electronic device 100 can receive budget data 330 from application computer system 180. Budget data 330 can include a first budget period 332, second budget period 346, and third budget period 352. While three budget periods are shown, budget data 330 can include more or fewer budget periods. In one example embodiment, budget data 330 can include a budget period for each month of the year for twelve total budget periods. In one example, first budget period 332 can correspond to a personal budget for an individual for the month of June. In another example, first budget period 332 can correspond to a current budget period.

First budget period 332 includes budget categories 334 and overall budget 344. Second budget period 346 includes budget categories 348, planned spending 349, and overall budget 350. Third budget period 352 includes budget categories 354, planned spending 355, and overall budget 356. Planned spending 349 and planned spending 355 can include scheduled spending from the current budget period and any scheduled installment payments.

Example budget categories 334 include rent/mortgage 336, transportation 338, food 340, and clothing 342. Rent/mortgage 336 includes a budgeted amount 336A and a current spend amount 336B. The budgeted amount 336A is the amount planned or allocated for the budget period (i.e., month) to spend and the current spend amount 336B is the amount that has already been spent for the budget period for the budget category. Transportation 338 includes a budgeted amount 338A and a current spend amount 338B. Food 340 includes a budgeted amount 340A and a current spend amount 340B. Clothing 342 includes a budgeted amount 342A and a current spend amount 342B. Budget categories 334 can include more or fewer budget categories than the example budget categories described above. Budget categories 348 for the second budget period and budget categories 354 for the third budget period can each include the same respective budget categories (i.e., rent/mortgage, transportation, food, and clothing) as described for budget categories 334 and/or can further include additional categories that can be unique to the particular budget period. For example, a December budget can include a Christmas/Holiday gift category.

Overall budget 344 includes an overall budgeted amount 344A and an overall current spend amount 344B. The overall budgeted amount 336A is the total amount planned or allocated for the first budget period (i.e., month) to spend for all of the budget categories combined. The overall current spend amount 344B is the total amount that has been already spent for the first budget period for all of the budget categories combined or summed together. Similarly, overall budget 350 for the second budget period and overall budget categories 356 for the third budget period would each include respective overall budgeted amounts and overall current spend amounts.

Turning to FIG. 3B, there is shown additional details of example contents of system memory 120 of electronic device 100 configured to complete the various processes described herein. System memory 120 includes transaction data 360, current cost data 368, and historical data 374. Electronic device 100 can receive transaction data 360, current cost data 368, and historical data 374 from application computer system 180. Transaction data 360 includes data and information that corresponds to one or more transactions that are performed via electronic device 100 or other device associated with the same user and/or user budgeting account. Transaction data 360 can correspond to transaction data 240 received from application computer system 180. In an example embodiment, a transaction to purchase an item can be performed via electronic device 100 and shopping application 314, and completion of the transaction generates corresponding transaction data, including item description and cost, and location, store, or online retailer associated with the transaction. Example transaction data 360 includes a first transaction 361 and a second transaction 364. While transaction data 360 is shown for two transactions, transaction data 360 can include one transaction or more than two transactions.

First transaction 361 includes a first transaction type 362 and a first payment amount 363. First transaction type 361 identifies the kind of transaction being performed by electronic device 100. In an example embodiment, a transaction at a grocery store can be identified as a food purchase transaction type. First payment amount 363 is the amount of money or funds or credits (e.g., fungible currency) that is needed to complete the first transaction. Second transaction 364 includes a second transaction type 365 and a second payment amount 366.

Current cost data 368 includes data and information that corresponds to a current cost for an item from an online or physical retailer of the intended transaction. Current cost data 368 can correspond to current cost data 234 received from application computer system 180. Current cost data 368 includes first item 369 and second item 371. First item 369 includes a first current cost 370 for the first item. Second item 371 includes a second current cost 372 for the second item. While current cost data 368 is shown for two items, current cost data 368 can include the respective current cost for a single item or more two items.

Historical data 374 includes data and information that corresponds to known previous historical transactions for the same or a similar item as the intended transaction. In one embodiment, application computer system 180 can track transactions for an item over a period of time (e.g., 6 months) and generate corresponding historical data 236. Historical data 374 can correspond to historical data 236 received from application computer system 180. Historical data 374 includes first item historical data 375 and second item historical data 377. First item historical data 375 includes a first historical cost 376 for the first item. Second item historical data 377 includes a second historical cost 378 for the second item. While historical data 374 is shown for two items, historical data 374 can include the respective historical cost for a single item or more than two items.

System memory 120 further includes pre-identified merchant locations 380. Pre-identified merchant locations 380 are known physical locations where a merchant of goods or services are located. Example pre-identified merchant locations 380 include a first merchant location 382 and a second merchant location 386. First merchant location 382 includes a first merchant average spend amount 384 and transaction type 385. Second merchant location 386 includes a second merchant average spend amount 388 and transaction type 389. First merchant average spend amount 384 and second merchant average spend amount 388 are the amounts of money that are spent on average by a consumer when visiting the respective merchant. Transaction types 385 and 389 are the types of transactions that occur at the respective merchants. The first merchant average spend amount 384 and transaction type 385 and second merchant average spend amount 388 and transaction type 389 can be tracked over time by application computer system 180 and stored as part of historical data 236. The first merchant average spend amount 384 and transaction type 385, and second merchant average spend amount 388 and transaction type 389 can be received from application computer system 180 as part of received historical data 236.

System memory 120 includes scheduled payments 390. Scheduled payments 390 incudes installment payments 391 and scheduled transaction payments 396. In one embodiment, during a transaction, a user can select to complete the transaction via installment payments over several time periods. Installment payments 391 can include the installment payment amounts 392 and number of payments 394 for the future budget periods for the intended transaction. Scheduled transaction payments 396 are payments for saved later/scheduled transactions from previous budget periods.

With reference to FIG. 4A, electronic device 100 is shown with an example shopping graphical user interface (GUI) 410 presented on display 130. Shopping GUI 410 allows a user of electronic device 100 to purchase goods and services from a merchant. In one embodiment, electronic device 100 can access a shopping website using shopping application 314 executing on processor 102. Shopping GUI 410 includes a product category page 412 that includes several items or products that have been searched for by a user. In an example embodiment, product category page 412 can be shoes. Product category page 412 includes several different types of shoes 420, 424 and 428 and a respective product description and price 422, 426 and 430 for each of the shoes. Shopping website GUI 410 further includes a budget alert 414, which is a message or notification that the clothing budget for the current budget period (e.g., clothing budget amount 342A) maybe exceeded, depending upon which product (shoe) is selected for purchase.

In the example of FIG. 4A, the purchase of some products (e.g., shoes 420 or 424) would cause the clothing budget to be exceeded for the current budget period and the purchase of other products (e.g., shoes 428) would not cause the clothing budget to be exceeded for the current budget period. In another example, if all of the products shown on the product category page 412 would cause the clothing budget to be exceeded or if the clothing budget is already overrun, the budget alert 414 can state that the clothing budget category 342 for the current budget period is exceeded or overrun.

Shopping GUI 410 includes filter option 434, with option on/off indication 436. Shopping GUI 410 further includes filter items by budget option 438, with option on/off indication 440. When selected, filter option 434 enables electronic device 100 to only display items or products within product category page 412 that have been purchased by other users with a similar budget to the user of electronic device 100 (i.e., similar to budget data 330). In one embodiment, historical data 236 of shopping database 230 can include a list of similar items purchased by other users with similar budget profiles (i.e., similar to budget data 330) that can be accessed by electronic device 100. Option on/off indication 436 is filled in or checked when filter option 434 is selected.

When selected, filter option 438, enables electronic device 100 to only display items or products within product category page 412 that would not exceed the user's budget for the budget category and budget period (e.g., clothing budget amount 342A). Option on/off indication 440 is filled in or checked when filter option 438 for filtering items by available budget is selected.

According to one aspect of the disclosure, electronic device 100 can detect a trigger indicative of an intended transaction 361 that falls within a first budget category 334 having a budgeted amount for at least one first budget period 332. In response to detecting the trigger, electronic device 100 transmits, to a budget data repository 224, a request for budget data 330. The budget data 330 includes a corresponding first budget amount (e.g., clothing budget amount 342A) and first current spend amount (e.g., clothing current spend amount 342B) associated with the first budget category (e.g., clothing budget category 342) for the at least one budget period (e.g., first budget period 332). Electronic device 100 identifies an over-budget condition by determining that a first sum of a first transaction payment amount 363 for the intended transaction 361 and the first current spend amount (e.g., clothing current spend amount 342B) is greater than the first budget amount (e.g., clothing budget amount 342A). In response to identifying the over-budget condition, electronic device 100 presents a first budget alert 414 on the display 130. The first budget alert 414 indicates that the first budget amount (e.g., clothing budget amount 342A) will be exceeded if the intended transaction 361 is completed within the at least one budget period (e.g., first budget period 332).

According to another aspect of the disclosure, electronic device 100 can detect a trigger indicative of an intended transaction. In order to detect the trigger, electronic device 100 detects initiation of (i) at least one shopping application 314 or (ii) at least one payment. Electronic device 100 initiates processes resulting in presentation of the budget alert 414, in response to detecting initiation of either (i) at least one shopping application 314 or (ii) at least one payment, which is evaluated to potentially cause an over-budget condition. The budget alert 414 can also be presented in a different format such as an audio notification, a push notification, or via a text or email message.

With reference to FIG. 4B, electronic device 100 is shown with an example shopping graphical user interface (GUI) 450 presented on display 130. Shopping GUI 450 is shown with a shopping cart interface after a user has selected a product for purchase. Shopping GUI 450 includes a shopping cart page 452 that includes an item or product (e.g., shoes 420) that have been selected by a user for purchase. In the example of FIG. 4B, completion of the intended transaction to purchase shoes 420 would cause the clothing budget to be exceeded for the current budget period (e.g., clothing budget amount 342A). Shopping GUI 450 thus includes a budget alert 454 (i.e., a message or notification) that the clothing budget for the current budget period (e.g., clothing budget amount 342A) is exceeded or overrun if the intended transaction for shoes 420 in the shopping cart is completed. Shopping GUI 450 includes a notification 456 that a lower priced alternative to the intended transaction is available from other merchants. Notification 456 can include the merchant name with the lower priced alternative and the price of the lower priced alternative. In one embodiment, electronic device 100 can use historical data 236 to retrospectively recommend alternatives for transactions that would result in a budget overrun.

Shopping GUI 450 further includes continue transaction option 460, with option on/off indication 462, cancel transaction option 464, with option on/off indication 466, schedule transaction later option 470, with option on/off indication 472, and schedule installment payments option 474, with option on/off indication 476.

When selected, continue transaction option 460, enables electronic device 100 to complete the intended transaction (e.g., first transaction 361) with the selected item (e.g., shoes 420) in the shopping cart. Completion of the intended transaction will result in a budget overrun condition (e.g., clothing budget amount 342A exceeded). Option on/off indication 462 is filled in or checked when continue transaction option 460 is selected. When selected, cancel transaction option 464, enables electronic device 100 to cancel the intended transaction (e.g., first transaction 361). Cancellation of the intended transaction will result in the clothing budget amount 342A not being exceeded. Option on/off indication 466 is filled in or checked when cancel transaction option 464 is selected.

When selected, schedule transaction later option 470, enables electronic device 100 to schedule the intended transaction (e.g., first transaction 361) for a future time period (i.e., a future budget period). Option on/off indication 472 is filled in or checked when schedule transaction later option 470 is selected. When selected, schedule installment payments option 474, enables electronic device 100 to complete the intended transaction (e.g., first transaction 361) with payment via installment payments 391 over several future budget periods. The selection of schedule installment payments option 474 can enable electronic device 100 to calculate installment payments 391 for future budget periods such that the budgeted clothing amount 342A is not overrun or exceeded for the current budget period (e.g., first budget period 332) and is not overrun or exceeded for future budget periods. Option on/off indication 476 is filled in or checked when schedule installment payments option 474 is selected. In one or more embodiments, the scheduled installment payment is automatically added to the current spend amount of the associated budget category, as an expended costs, at the start of the billing period.

According to one aspect of the disclosure, electronic device 100 can present GUI 450 on display 130. GUI 450 includes budget alert 454 and a user-selectable option 460 to continue the intended transaction 361. In response to detecting selection of the user-selectable option 460, electronic device 100 triggers completion of the intended transaction 361. Electronic device 100 calculates a second current spend amount of the budget category by adding the first payment amount (e.g., first transaction payment amount 363) to the first current spend amount (e.g., first current spend amount 342B) and stores the second current spend amount to system memory 120.

According to another aspect of the disclosure, GUI 450 includes budget alert 454 and a user-selectable option 464 to cancel the intended transaction 361. In response to detecting selection of the user-selectable option 464 to cancel the intended transaction 361, electronic device 100 cancels the intended transaction 361.

According to an additional aspect of the disclosure, GUI 450 includes budget alert 454 and a user-selectable option 470 to schedule the intended transaction at a later time. In response to detecting selection of the user-selectable option 470 to schedule the intended transaction at a later time, electronic device 100 identifies a number of future budget periods, including second budget period 346 and schedules the intended transaction 361 for completion during a future budget period such as second budget period 346.

According to one more aspect of the disclosure, GUI 450 includes budget alert 454 and a user-selectable option 474 to schedule installment payments for the intended transaction. In response to detecting selection of user-selectable option 474 to schedule installment payments for the intended transaction, electronic device 100 calculates installment payment amounts 392 for a plurality of future budget periods (i.e., second budget period 346, third budget period 352, and other future budget periods) for the intended transaction 361. Electronic device 100 determines if the installment payment amounts 392 for the plurality of future budget periods for the intended transaction 361 are less than corresponding budgeted amounts for the future budget periods. In response to determining that the respective installment payment amounts 392 for the plurality of future budget periods for the intended transaction are less than each corresponding budgeted amounts for the future budget periods, electronic device 100 schedules the installment payments 391 during the plurality of future budget periods, and triggers completion of the intended transaction 361 via installment payments during the plurality of future budget periods.

According to another additional aspect of the disclosure, electronic device 100 can identify a payment amount for the intended transaction (e.g., first transaction payment amount 363) by the electronic device completing at least one of (i) retrieving historical data 374 for purchase of a similar item as the intended transaction, (ii) accessing a current cost listing or data 368 for the intended transaction from an online retailer of the intended transaction, and (iii) identifying a lower priced alternative for the intended transaction, and present a notification 456 that lower priced alternatives for the intended transaction are available.

With reference to FIG. 5A, electronic device 100 is shown with an example shopping graphical user interface (GUI) 510 presented on display 130. Shopping GUI 510 is shown with a shopping cart interface after a user has selected a product for purchase. Shopping GUI 510 includes shopping cart page 522 that includes an item or product (e.g., shoes 420) that have been selected by a user for purchase. Shopping GUI 510 includes an overall budget alert 520 that the overall budget for the current budget period (e.g., overall budget amount 344A) will be exceeded or overrun if the intended transaction for the product (e.g., shoes 420) in the shopping cart is completed.

In the example of FIG. 5A, completion of the intended transaction to purchase shoes 420 would cause the overall budget for the current budget period (e.g., overall budgeted amount 344A) to be exceeded. Shopping GUI 510 includes the same selectable options as previously described for shopping GUI 450 of FIG. 4B. Shopping GUI 510 includes continue transaction option 460, with option on/off indication 462, cancel transaction option 464, with option on/off indication 466, schedule transaction later option 470, with option on/off indication 472, and schedule installment payments option 474, with option on/off indication 476. In one embodiment, overall budget alert 520 can be presented in addition to budget alert 414 of FIG. 4A or can be presented in addition to budget alert 454 of FIG. 4B when the overall budget is determined to be exceeded during an intended transaction.

According to one aspect of the disclosure, in response to transmitting a request 260 for budget data from the budget tracking repository 224, electronic device 100 receives budget data 330 for a plurality of budget categories 334, with corresponding budget amounts and current spend amounts for each of the plurality of budget categories 334 for the at least one budget period (e.g., first budget period 332). Electronic device 100 sums or combines budget amounts (e.g., 336A, 338A, 340A, and 342A) for each of the plurality of budget categories to provide an overall budget amount 344A for the budget period. Electronic device 100 sums or combines current spend amounts (e.g., 336B, 338B, 340B, and 342B) for each of the plurality of budget categories to provide an overall current spend amount 344B for the budget period. Electronic device 100 determines if a second sum of the first payment amount (e.g., first transaction payment amount 363) and the overall current spend amount 344B is greater than the overall budget amount 344A for the budget period. In response to determining the second sum is greater than the overall budget amount 344A for the budget period, electronic device 100 initiates presentation of budget alert 520 on display 130. Budget alert 520 indicates that the overall budget amount 344A will be exceeded if the intended transaction is completed within the at least one budget period.

Turning to FIG. 5B, electronic device 100 is shown with an example location-based budget alert graphical user interface (GUI) 550 presented on display 130. Location-based budget alert GUI 550 includes a map 560. Map 560 can show the current location 322A of electronic device 100. Map 560 includes a pre-identified merchant location (e.g., first merchant location 382) with the name of the merchant (e.g., shoe warehouse). Location-based budget alert GUI 550 includes a budget alert 570 and an overall budget alert 572. Budget alert 570 can indicate that electronic device 100 is at a pre-identified merchant location where the purchase of goods or services may cause a budget overrun condition or a budget to be exceeded for at least one budget category. Overall budget alert 572 can indicate that electronic device 100 is at a pre-identified merchant location where the purchase of goods or services may cause a budget overrun condition for an overall budget.

According to one aspect of the disclosure, electronic device 100 can detect a trigger that is indicative of an intended transaction. The trigger can be movement of electronic device 100 towards or into a pre-identified merchant location (e.g., first merchant location 382). To detect the trigger, electronic device 100 monitors, via location sensor 160, for changes in a current location 322A of the electronic device. Electronic device 100 determines, in part via current location data 322 received from location sensor 160, if the electronic device has moved to the pre-identified merchant location (e.g., first merchant location 382). In response to determining that electronic device 100 has moved to the pre-identified merchant location (i.e., first merchant location 382), electronic device 100 initiates processing to determine whether the intended transaction, at the pre-identified merchant location, causes an over-budget condition that results in presentation of budget alert 570 and/or overall budget alert 572.

According to another aspect of the disclosure, in response to determining the electronic device has moved to the pre-identified merchant location (e.g., first merchant location 382), electronic device 100 retrieves a first average spend amount 384 associated with previous transactions at the pre-identified merchant location. The previous transactions at the pre-identified merchant location can be used to identify the corresponding budget category. Electronic device 100 determines if the first average spend amount 384, when added to the first current spend amount (e.g., current spend amount 342B) is greater than the first budget amount (e.g., budgeted amount 342A). In response to determining that the first average spend amount 384, when added to the first current spending amount (e.g., current spend amount 342B), is greater than the first budget amount (e.g., budgeted amount 342A), electronic device 100 presents budget alert 570 on display 130. The budget alert 570 indicates that electronic device 100 is at the pre-identified merchant location (e.g., first merchant location 382), where the first budget amount for the budget category may be exceeded based on historical spending at that location.

Referring to FIG. 6A, electronic device 100 is shown with an example graphical user interface (GUI) 610 presented on display 130. GUI 610 includes a notification 620 that a previously scheduled transaction will be completed during the current budget period (e.g., second budget period 346). The previously scheduled transaction was scheduled for completion during a prior budget period (e.g., first budget period 332). In one embodiment, electronic device 100 can also determine that scheduled transaction will not result in an over-budget condition at the current time.

GUI 610 further includes a continue scheduled transaction option 630, with option on/off indication 632, and cancel scheduled transaction option 634, with option on/off indication 636. Option on/off indication 632 is filled in or checked when continue scheduled transaction option 630 is selected. When selected, continue scheduled transaction option 630 enables electronic device 100 to complete the intended transaction (e.g., first transaction 361) during the current budget period. When selected, cancel scheduled transaction option 634, enables electronic device 100 to cancel the intended transaction (e.g., first transaction 361) during the current budget period. Option on/off indication 636 is filled in or checked when cancel scheduled transaction option 634 is selected.

According to one aspect of the disclosure, electronic device 100 can determine if a current budget period (e.g., second budget period 346) corresponds to a budget period with a scheduled intended transaction. In response to determining that the current budget period corresponds to a budget period with a scheduled intended transaction, electronic device 100 presents GUI 610 including notification 620 that the intended transaction is scheduled to be completed in the current budget period and including option 630 for either completing the intended transaction or not completing the intended transaction option 634 during the current budget period.

Referring to FIG. 6B, electronic device 100 is shown with an example graphical user interface (GUI) 650 presented on display 130. GUI 650 includes a notification 660 that the previously scheduled transaction was completed during the current budget period (e.g., second budget period 346). The previously scheduled transaction was scheduled for completion during a prior budget period (e.g., first budget period 332).

According to one aspect of the disclosure, electronic device 100 can determine if a current budget period (e.g., second budget period 346) corresponds to a budget period with a scheduled intended transaction. In response to determining that the current budget period corresponds to a budget period with a scheduled intended transaction, electronic device 100 executes the scheduled intended transaction and presents GUI 650 including notification 660 that the scheduled intended transaction was completed.

FIGS. 7A-7B depicts method 700 by which electronic device 100 identifies an over-budget condition and presents a budget alert for at least one budget category. FIGS. 8A-8B depicts method 800 by which electronic device 100 identifies that the electronic device is at a pre-identified merchant location where an over-budget condition can occur and presents a location-based budget alert. The description of methods 700 and 800 will be described with reference to the components and examples of FIGS. 1-6B. The operations depicted in FIGS. 7A-7B and 8A-8B can be performed by electronic device 100 or any suitable electronic device that includes the one or more functional components of electronic device 100 that provide/enable the described features. One or more of the processes of the methods described in FIGS. 7A-7B and 8A-8B may be performed by processor 102 executing program code associated with budget alert module 128.

With specific reference to FIG. 7A method 700 begins at the start block 702. At block 704, method 700 includes detecting a trigger that is indicative of an intended transaction (e.g., first transaction 361). In one embodiment, the trigger can be the initiation of at least one shopping application 314 or initiation at least one payment. Method 700 includes transmitting a request 260 for budget data 226 to budget tracking repository 224 (block 706) and transmitting a request 260 for transaction data 240 to transaction data repository 238 (block 708). Method 700 includes receiving a response 262 from budget tracking repository 224 including the budget data 226 (block 710) and receiving a response 262 from transaction data repository 238 including the transaction data 240 (block 712).

Method 700 includes identifying a transaction type (e.g., first transaction type 362 for shoes 420) and transaction payment amount (e.g., first transaction payment amount 363) for an intended transaction (e.g., first transaction 361) based on the transaction data (block 714). Method 700 includes identifying, from among the budget categories 334, the budget category (e.g., budget category 342 “clothing”) corresponding to the transaction type (e.g., first transaction type 362) (block 716). Method 700 includes identifying a budget amount 342A and current spend amount 342B for the identified budget category (e.g., budget category 342 “clothing”) and identifying an overall budget amount 344A and current spend amount 344B for the current budget period (e.g., first budget period 332) (block 718).

Method 700 includes summing the transaction payment amount (e.g., first transaction payment amount 363) and the current spend amount (e.g., clothing current spend amount 342B) for the identified budget category and current time period (block 720). At decision block 722, method 700 determines if the sum of the transaction payment amount (e.g., first transaction payment amount 363) and the current spend amount (e.g., clothing current spend amount 342B) is greater than the budget amount (e.g., clothing budget amount 342A). In one embodiment, if the clothing budget amount 342A is already overrun or exceeded, block 720 can be omitted. In such an instance, method 700 can proceed from block 718 to an alternate version of block 724 where a budget alert is presented indicating the budget has already been exceeded. The amount by which the budget has been exceeded can also be presented with the budget alert GUI so the user can be more fully/completely informed.

Returning to decision block 722, in response to determining that the sum of the transaction payment amount (e.g., first transaction payment amount 363) and the current spend amount (e.g., clothing current spend amount 342B) is greater than the budget amount (e.g., clothing budget amount 342A), method 700 includes presenting a first budget alert 414 (block 724) on the display 130. The first budget alert 414 indicates that the first budget amount (e.g., clothing budget amount 342A) will be overrun or exceeded for the budget category if the intended transaction 361 is completed within the at least one budget period (e.g., first budget period 332). A budget overrun or a transaction resulting in exceeding a budget can also be referred to as an over-budget condition. In one or more embodiments, the amount by which the budget will been exceeded can also be presented with the budget alert GUI so the user can be more fully/completely informed.

In response to determining that the sum of the transaction payment amount (e.g., first transaction payment amount 363) and the current spend amount (e.g., clothing current spend amount 342B) is not greater than the budget amount (e.g., clothing budget amount 342A) and after block 724, method 700 includes summing the transaction payment amount (e.g., first transaction payment amount 363) and the overall current spend amount (e.g., overall current spend amount 344B) for the current time period (block 726). At decision block 728, method 700 determines if the sum of the transaction payment amount (e.g., first transaction payment amount 363) and the overall current spend amount 344B is greater than the overall budget amount 344A for the current time period. In one embodiment, if the overall budget amount 344A for the current time period is already overrun or exceeded, block 720 can be omitted. In such an instance, method 700 can proceed from block 718 to an alternate version of block 730 where a budget alert is presented indicating the overall budget amount 344A for the current time period has already been exceeded.

In response to determining that the sum of the transaction payment amount (e.g., first transaction payment amount 363) and the overall current spend amount 344B is greater than the overall budget amount 344A for the current time period, method 700 includes presenting a second budget alert 520 on the display 130 (block 730). The second budget alert 520 indicates that the overall budget amount 344B will be overrun or exceeded for the budget category if the intended transaction 361 is completed within the at least one budget period (e.g., first budget period 332).

Turning to FIG. 7B, after block 730 and in response to determining that the sum of the transaction payment amount (e.g., first transaction payment amount 363) and the overall current spend amount 344B is not greater than the overall budget amount 344A for the current time period, (decision block 728), method 700 includes determining if the transaction (e.g., first transaction 361) has been completed (decision block 732). In response to determining that the transaction has not been completed, method 700 ends at end block 750.

In response to determining that the transaction has been completed, method 700 includes updating the current spend amount (e.g., clothing current spend amount 342B) for the budget category with the transaction payment amount (e.g., first transaction payment amount 363) and updating the overall current spend amount (e.g., overall current spend amount 344B) with the with the transaction payment amount (e.g., first transaction payment amount 363) (block 734). Method 700 includes transmitting the current spend amount for the budget category and the overall current spend amount to budget data repository 224 (block 736). Method 700 terminates at end block 750.

FIGS. 8A-8B illustrates method 800 by which electronic device 100 identifies that the electronic device is at a pre-identified merchant location where an over-budget condition can occur and presents a predictive location-based budget alert. With specific reference to FIG. 8A, method 800 begins at the start block 802. Method 800 includes triggering location sensor 160 to provide current location data 322 including current location 322A (block 804) and receiving the current location data 322 (block 806). Method 800 includes retrieving pre-identified merchant locations 380 from system memory 120 (block 808). Method 800 includes determining if the current location 322A of electronic device 100 substantially matches at least one of the pre-identified merchant locations 380 (decision block 810).

In response to determining that the current location 322A of electronic device 100 does not substantially match at least one of the pre-identified merchant locations 380, method 800 returns to block 804 to continue monitoring for whether current location data 322 substantially matches at least one of the pre-identified merchant locations 380 (i.e., performing the processes of blocks 804-810).

In response to determining that the current location data 322 of electronic device 100 substantially matches at least one of the pre-identified merchant locations 380, (e.g., first merchant location 382), method 800 includes retrieving an average spend amount 384 and transaction type 385 associated with previous transactions at the pre-identified first merchant location 382 (block 812).

Method 800 includes transmitting a request 260 for budget data 226 to budget tracking repository 224 (block 814) and receiving a response 262 from budget tracking repository 224 including the budget data 226 (block 816). In one embodiment, the received budget data can be stored as budget data 330 to system memory 120. Method 800 includes identifying, from among the budget categories 334, the budget category (e.g., budget category 342 “clothing”) corresponding to the transaction type (e.g., first transaction type 385) (block 818). Method 800 includes identifying a budget amount 342A and current spend amount 342B for the identified budget category (e.g., budget category 342 “clothing”) and identifying an overall budget amount 344A and current spend amount 344B for the current budget period (e.g., first budget period 332) from the received budget data (block 820). Method 800 includes summing the average spend amount 384 at the merchant location and the current spend amount (e.g., clothing current spend amount 342B) for the identified budget category and current time period (block 822).

Turning to FIG. 8B, method 800 includes determining at decision block 824 if the sum of the average spend amount 384 at the merchant location and the current spend amount (e.g., clothing current spend amount 342B) is greater than the budget amount (e.g., clothing budget amount 342A). In response to determining that the sum of the average spend amount 384 and the current spend amount (e.g., clothing current spend amount 342B) is greater than the budget amount (e.g., clothing budget amount 342A), method 800 includes presenting budget alert