Portfolio accounting system and method for handling uncertainty in accounting information

• US 7,653,578 B2
• Filed: 11/15/2004
• Issued: 01/26/2010
• Est. Priority Date: 11/15/2004
• Status: Active Grant

• Current Assignee: Infonic AG
• Original Assignee: Thomas Furrer
• Inventors: Furrer, Thomas
• Primary Examiner(s): Cheung; Mary
• Application Number:
  US10/986,849
• Publication Number:
  US 20060106715A1
• Time in Patent Office: 1,898 Days
• Field of Search: 705/30, 705/35, 705/36.R, 705/37, 707100-104, 707/200, 902 37- 41
• US Class Current: 705/35
• 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/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/06 Asset management; Financial planning or analysis

Abstract

Portfolio accounting systems and methods are adapted to handle uncertainty in accounting information due to time delay in information issuance. Accounting information is represented by streams of sequenced simple transaction states, each individual state describing the state of an account or its changes as known at a certain point in time while the stream ties the consecutive states into a life cycle of the information improving over time. A first simple transaction state attribute corresponds to the traditional value date. A second attribute corresponds to a reporting date. A third attribute corresponds to the traditional account value or relative/absolute changes thereof.

Claims

1. A method for handling uncertainty in accounting information due to time delay in information issuance comprising:

representing the accounting information by streams of sequenced simple transaction states, each simple transaction state comprising at least four attributes, among which;

a first attribute corresponds to a value date,

a second attribute corresponds to a reporting date,

a third attribute corresponds to a value parameter, and

a fourth attribute is an account reference, said value date being a date said value parameter refers to and said reporting date being a date or a time said value date and said value parameter together with their account reference are entered into or are deemed to have become known to a portfolio accounting system, while each stream links all consecutive simple transaction states representing views of the same accounting information as known to the system over time; and

entering a corrective simple transaction state in an information correction mode;

wherein a reporting date of the corrective simple transaction state corresponds to a reporting date of an original, corrected simple transaction state, and the portfolio accounting system is implemented by a computer executing a computer-executable program stored on a computer-readable medium.

2. The method according to claim 1, further comprising entering a simple transaction state into an accounting system when new accounting information occurs, and storing said simple transaction state.

3. A method for handling uncertainty in accounting information due to time delay in information issuance comprising:

representing the accounting information by streams of sequenced simple transaction states, each simple transaction state comprising at least four attributes, among which;

a first attribute corresponds to a value date,

a second attribute corresponds to a reporting date,

a third attribute corresponds to a value parameter, and

a fourth attribute is an account reference, said value date being a date said value parameter refers to and said reporting date being a date or a time said value date and said value parameter together with their account reference are entered into or are deemed to have become known to a portfolio accounting system, while each stream links all consecutive simple transaction states representing views of the same accounting information as known to the system over time; and

determining an absolute value of a predetermined account for a requested value date by considering simple transaction states having a reporting date smaller than or equal a requested reporting date;

wherein the portfolio accounting system is implemented by a computer executing a computer-executable program stored on a computer-readable medium.

4. The method according to claim 3, further comprising automatically retrieving the reporting date from a central clock or entering the reporting date entered by a user or supplied by another system, such that, in an information update mode, the reporting date corresponds to an actual date or an actual time of entry of the simple transaction state into the accounting system.

5. The method according to claim 3, wherein said step of determining the absolute value of the predetermined account comprises changing a value function upon or after entry of a simple transaction state which account reference refers to the predetermined account according to the value parameter of said simple transaction state.

6. The method according to claim 5, further comprising storing said value function as a function of the value date and the reporting date.

7. The method according to claim 5, further comprising providing for at least one account a consistent multi-period Profit/Loss statement for any sequence of consecutive sub-periods between two value dates, with each sub-period having a reporting date for both a starting value date and an ending value date, with the reporting date for the starting value date of one sub-period being equal to the reporting date for the ending value date of a preceding sub-period.

8. The method according to claim 3, further comprising providing for at least one account a Balance Sheet for a given combination of any value date and reporting date, by reflecting a state of all simple transactions referring to corresponding accounts as of the given combination of the value date and reporting date.

9. The method according to claim 3, further comprising providing for at least one account a Profit and Loss statement for any period between two value dates, each of the value dates being paired with an individually selectable reporting date, by reflecting a transition of all simple transaction states referring to a same account between the two pairs of value dates and reporting dates.

10. The method according to claim 3, further comprising providing at least one of the following operations of a traditional accounting system:

(a) correction of accounting data item states for a given value date leading to changing balances and Profit/Loss statements; and

(b) entry of unchecked accounting information only impacting accounting if checked by a second person.

11. The method according to claim 3, further comprising checking whether a simple transaction state fulfils predetermined rules corresponding to transaction business rules.

12. A method for handling uncertainty in accounting information due to time delay in information issuance comprising:

representing the accounting information by streams of sequenced simple transaction states, each simple transaction state comprising at least four attributes, among which;

a first attribute corresponds to a value date,

a second attribute corresponds to a reporting date,

a third attribute corresponds to a value parameter, and

a fourth attribute is an account reference, said value date being a date said value parameter refers to and said reporting date being a date or a time said value date and said value parameter together with their account reference are entered into or are deemed to have become known to a portfolio accounting system, while each stream links all consecutive simple transaction states representing views of the same accounting information as known to the system over time; and

grouping one or a multitude of simple transactions in a composite transaction affecting one or a multitude of accounts;

wherein the portfolio accounting system is implemented by a computer executing a computer-executable program stored on a computer-readable medium.

13. The method according to claim 12, further comprising generating a composite transaction state for each state of all of the simple transaction states grouped under said composite transaction.

14. The method according to claim 13, further comprising checking whether said composite transaction state or a state sequencing fulfills predetermined rules corresponding to transaction business rules.

15. The method according to claim 12, comprising defining and hard or soft enforcing business rules governing consistency of transactions regarding individual states or state sequencing, both at a simple and a composite transaction level.

16. The method according to claim 12, further comprising consistently managing and tracking the streams of simple transaction states both at a simple and a composite transaction level for both information update and information correction operations.

17. The method according to claim 12, further comprising making fully available the streams of simple transaction states, both on a simple and a composite transaction level at any time both for retrieval, navigation along the state sequence and entry/update, wherein all transaction states are available and treated equally both for the retrieval and the entry/update.