System for maintaining balance data

• US 20050187870A1
• Filed: 02/22/2005
• Published: 08/25/2005
• Est. Priority Date: 02/24/2004
• Status: Abandoned Application

• Current Assignee: First Data Corporation (Fiserv Incorporated)
• Original Assignee: First Data Corporation (Fiserv Incorporated)
• Inventors: Bell, Richard T., Harrington, Teresa M., Grear, Michael B.
• Application Number:
  US11/064,289
• Publication Number:
  US 20050187870A1
• Time in Patent Office: Days
• US Class Current: 705/39
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/12 Accounting

Abstract

According to one embodiment of the invention, an architecture is provided for a data processing system that processes data for a service provider itself or a client of a service provider as in the case of a third party processor. The elements of the architecture can be managed separately. For example, the architecture can be organized around eight subject areas, such as account, party, communication point, presentation instrument, rules, balances, transactions, and product. Relationships between each of the subject areas as well as between sub-types of each subject area can be established to provide flexibility in the management of the data.

Claims

1. A method of storing balance information, said method comprising:

providing a first database for storing data about a balance type;

providing a second database for storing data about a balance period;

providing a third database for storing balance control data;

associating said balance type data with said balance period data and with said balance control data as a set of data.

2. The method as claimed in claim 1 and further comprising:

providing an account database for storing information identifying an account;

associating said information identifying said account with said set of data.

3. The method as claimed in claim 1 and further comprising:

providing an account party role database for storing information identifying an account party role;

associating said information identifying said account party role with said set of data.

4. The method as claimed in claim 1 wherein said balance type data comprises:

a balance classification code.

5. The method as claimed in claim 1 wherein said balance type data comprises:

a balance type code.

6. The method as claimed in claim 1 wherein said data for said balance type indicates a control balance.

7. The method as claimed in claim 1 wherein said data for said balance type indicates a payable balance.

8. The method as claimed in claim 1 wherein said data for said balance type indicates a memo balance.

9. The method as claimed in claim 1 wherein said balance control data indicates a balance control effective date.

10. The method as claimed in claim 1 wherein said balance control data indicates a balance control amount.

17. The method as claimed in claim 1 wherein said data for said balance type indicates a payable balance.

20. The method as claimed in claim 1 and further comprising:

providing a balance transaction allocation history database;

associating said set of data with data from said balance transaction allocation history database.

11. A method of storing balance information, said method comprising:

providing a first database for storing data about a balance type

providing a second database for storing data about a balance period;

providing a third database for storing balance amount data;

associating said balance type data with said balance period data and with said balance amount data as a set of data.

12. The method as claimed in claim 11 and further comprising:

providing an account database for storing information identifying an account;

associating said information identifying said account with said set of data.

13. The method as claimed in claim 11 and further comprising:

providing an account party role database for storing information identifying an account party role;

associating said information identifying said account party role with said set of data.

14. The method as claimed in claim 11 wherein said balance type data comprises:

a balance classification code.

15. The method as claimed in claim 11 wherein said balance type data comprises:

a balance type code.

16. The method as claimed in claim 11 wherein said data for said balance type indicates a control balance.

18. The method as claimed in claim 11 wherein said data for said balance type indicates a memo balance.

19. The method as claimed in claim 11 wherein said balance amount data comprises balance date data.