US2019147543A1PendingUtilityA1

Composite account structure

Assignee: IBMPriority: Nov 14, 2017Filed: Nov 14, 2017Published: May 16, 2019
Est. expiryNov 14, 2037(~11.3 yrs left)· nominal 20-yr term from priority
G06Q 10/109G06Q 40/12G06Q 30/0201G06Q 30/04
60
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

Aspects provide cognitive management of multiple subaccounts that include processors configured to (or include program code that causes a processor to) determine an expense type for an input of an expense event to a linked account structure that links subaccounts that are each associated to different respective ones of a plurality of group members. In response to determining that the input expense event expense type most-strongly matches an expense type of a nearby (in time) calendar expense, aspects allocate expense costs of the input expense to member subaccounts pursuant to a first expense allocation rule utilized in the nearby calendar event for allocating expenses. In response to determining that the input expense event expense type does not match the expense types of a nearby calendar events, aspects further allocate the input expense event costs pursuant to a second expense allocation rule selected as a function matching the input event expense type to behavior data of a member.

Claims

exact text as granted — not AI-modified
1 - 8 . (canceled) 
     
     
         9 . A system, comprising:
 a processor;   a computer readable memory in circuit communication with the processor; and   a computer readable storage medium in circuit communication with the processor;   wherein the processor executes program instructions stored on the computer-readable storage medium via the computer readable memory and thereby:   determines an expense type for an input of an expense event to a linked account structure that links each of a plurality of subaccounts that are each associated to respective ones of a plurality of group members;   identifies historic calendar expense events that occur within a threshold time of the input expense event as nearby calendar expense events;   in response to determining that the input expense event expense type most-strongly matches an expense type of a first of the nearby calendar expense events relative to remaining others of the nearby calendar expense events, allocates expense costs of the input expense to respective ones of the member subaccounts pursuant to a first expense allocation rule utilized in the first nearby calendar event for allocating expense costs to the member subaccounts; and   in response to determining that the input expense event expense type does not match expense types of the nearby calendar expense events, allocates the expense costs of the input expense to respective ones of the member subaccounts pursuant to a second expense allocation rule for allocating expense costs that is selected as a function of strength of match of the input expense event expense type to behavior data of a responsible member of the group members that is identified as generating the input expense event.   
     
     
         10 . The system of  claim 9 , wherein the processor executes the program instructions stored on the computer-readable storage medium via the computer readable memory and thereby allocates the expense costs of the input expense to respective ones of the member subaccounts pursuant to the second expense allocation rule by:
 in response to determining that the input expense event expense matches an expense type that is allocated to the responsible member by third allocation rule of the responsible member behavior data, selecting the third allocation rule as the second allocation rule;   in response to determining that the input expense event expense does not match an expense type that is allocated to the responsible member by allocation rules of the responsible member behavior data, determining whether the input expense event expense matches an expense type that is allocated to others of the group members by allocation rules of their respective member behavior data; and   selecting the second allocation rule as a fourth allocation rule that is different from the third allocation rule as a function of strength of match of the input expense event expense type to an expense type value of the fourth allocation rule within behavior data of one of the others of the group members.   
     
     
         11 . The system of  claim 10 , wherein the processor executes the program instructions stored on the computer-readable storage medium via the computer readable memory and thereby:
 in response to determining that the input expense event expense most-strongly matches an expense type that is allocated to a second of the group members by allocation rules of the behavior data of the second member, generates the fourth allocation rule to allocate an amount of the expense costs of the input expense to the responsible member that is inverse to an amount of the expense costs of the input expense that is allocated to the second member by an allocation rule of the behavior data of the second member that has an expense type value that matches the input event expense type.   
     
     
         12 . The system of  claim 11 , wherein the processor executes the program instructions stored on the computer-readable storage medium via the computer readable memory and thereby:
 in response to determining that the input expense event expense does not match expense types that are allocated to the group members by the allocation rules of the behavior data of the member, generates the fourth allocation rule to allocate an amount of the expense costs of the input expense to the responsible member that is proportionate to an amount of the expense costs of the input expense that is typically allocated within historical allocations of the expense type to a person having demographic data values that are similar to demographic data values of the responsible member.   
     
     
         13 . The system of  claim 12 , wherein the processor executes the program instructions stored on the computer-readable storage medium via the computer readable memory and thereby allocates expense costs of the input expense to respective ones of the member subaccounts pursuant to one of the selected rules in proportion relative levels of income of the members. 
     
     
         14 . The system of  claim 13 , wherein the processor executes the program instructions stored on the computer-readable storage medium via the computer readable memory and thereby arbitrates selection of an allocation rule from a plurality of possible rule selections based on relative respective weighting values that are selected from the group consisting of values representing strength of association to a respective member, and confidence values of association to respective members. 
     
     
         15 . A computer program product for cognitive management of multiple subaccounts, the computer program product comprising:
 a computer readable storage medium having computer readable program code embodied therewith, wherein the computer readable storage medium is not a transitory signal per se, the computer readable program code comprising instructions for execution by a processor that cause the processor to:   determine an expense type for an input of an expense event to a linked account structure that links each of a plurality of subaccounts that are each associated to respective ones of a plurality of group members;   identify historic calendar expense events that occur within a threshold time of the input expense event as nearby calendar expense events;   in response to determining that the input expense event expense type most-strongly matches an expense type of a first of the nearby calendar expense events relative to remaining others of the nearby calendar expense events, allocate expense costs of the input expense to respective ones of the member subaccounts pursuant to a first expense allocation rule utilized in the first nearby calendar event for allocating expense costs to the member subaccounts; and   in response to determining that the input expense event expense type does not match expense types of the nearby calendar expense events, allocate the expense costs of the input expense to respective ones of the member subaccounts pursuant to a second expense allocation rule for allocating expense costs that is selected as a function of strength of match of the input expense event expense type to behavior data of a responsible member of the group members that is identified as generating the input expense event.   
     
     
         16 . The computer program product of  claim 15 , wherein the computer readable program code instructions for execution by the processor further cause the processor to allocate the expense costs of the input expense to respective ones of the member subaccounts pursuant to the second expense allocation rule by:
 in response to determining that the input expense event expense matches an expense type that is allocated to the responsible member by third allocation rule of the responsible member behavior data, selecting the third allocation rule as the second allocation rule;   in response to determining that the input expense event expense does not match an expense type that is allocated to the responsible member by allocation rules of the responsible member behavior data, determining whether the input expense event expense matches an expense type that is allocated to others of the group members by allocation rules of their respective member behavior data; and   selecting the second allocation rule as a fourth allocation rule that is different from the third allocation rule as a function of strength of match of the input expense event expense type to an expense type value of the fourth allocation rule within behavior data of one of the others of the group members.   
     
     
         17 . The computer program product of  claim 16 , wherein the computer readable program code instructions for execution by the processor further cause the processor to:
 in response to determining that the input expense event expense most-strongly matches an expense type that is allocated to a second of the group members by allocation rules of the behavior data of the second member, generate the fourth allocation rule to allocate an amount of the expense costs of the input expense to the responsible member that is inverse to an amount of the expense costs of the input expense that is allocated to the second member by an allocation rule of the behavior data of the second member that has an expense type value that matches the input event expense type.   
     
     
         18 . The computer program product of  claim 17 , wherein the computer readable program code instructions for execution by the processor further cause the processor to:
 in response to determining that the input expense event expense does not match expense types that are allocated to the group members by the allocation rules of the behavior data of the member, generate the fourth allocation rule to allocate an amount of the expense costs of the input expense to the responsible member that is proportionate to an amount of the expense costs of the input expense that is typically allocated within historical allocations of the expense type to a person having demographic data values that are similar to demographic data values of the responsible member.   
     
     
         19 . The computer program product of  claim 18 , wherein the computer readable program code instructions for execution by the processor further cause the processor to allocate expense costs of the input expense to respective ones of the member subaccounts pursuant to one of the selected rules in proportion relative levels of income of the members. 
     
     
         20 . The computer program product of  claim 19 , wherein the computer readable program code instructions for execution by the processor further cause the processor to arbitrate selection of an allocation rule from a plurality of possible rule selections based on relative respective weighting values that are selected from the group consisting of values representing strength of association to a respective member, and confidence values of association to respective members.

Join the waitlist — get patent alerts

Track US2019147543A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.