Data processing: financial – business practice – management – or co – Automated electrical financial or business practice or... – Finance
Reexamination Certificate
1998-08-21
2003-06-24
Stamber, Eric W. (Department: 3622)
Data processing: financial, business practice, management, or co
Automated electrical financial or business practice or...
Finance
C705S030000, C705S035000, C705S040000
Reexamination Certificate
active
06584453
ABSTRACT:
BACKGROUND
1. Field of the Invention
The present invention relates to computer-based accounting systems. More specifically, the present invention facilitates reversibly moving or merging account balances from at least one source account into a target account in a general ledger accounting system.
2. Related Art
Move/merge operations are often used in general ledger accounting systems to facilitate corporate restatements, reclassifications or chart of account modifications. As the name implies, a move/merge operation moves balances from one account to another or “merges” multiple balances into one.
Move/merge operations can be used for a variety of reasons. (1) A move/merge operation can be used to reflect the results of a corporate reorganization where the responsibility for a cost center is moved and the cost center number is changed to fit into the numbering scheme of the new owner. (2) In another example, when two organizations are being merged, a move/merge operation can be used to compare current balances of the merged organization against the combined balances of the separate organizations. (3) A move/merge operation can additionally be used to change a general ledger account number to facilitate a change in reporting requirements; for example, in moving a balance from an asset to a liability or from a revenue to an expense.
Many existing general ledger systems provide move/merge functionality. However, this move/merge functionality is not well-controlled. In current systems, move/merge operations are typically run in batch mode, with little if any error checking. Balances can be moved between balance sheet and income statement accounts, changing historical balances from those previously reported, and even causing an entity's balance sheet to no longer balance. In current systems, it is even possible to move balances from one legal entity to another, causing the general ledger of each legal entity to be out of balance.
Additionally, once move/merge operations are processed, there is presently no easy way to “undo” the results of the move/merge operation. The only way to undo a move/merge operation is to restore general ledger balances back to a prior version of the general ledger balances, and to repost any entries subsequently posted after the move/merge operation. Hence, a user is typically unable “undo” the results of a move/merge operation because the undo operation must typically be performed with MIS resources.
Finally, in current systems, when balances in the general ledger are moved, the balances no longer reconcile back to the subledger that created the transactions. For example, assume the general ledger has one accounts payable account, which is only posted by the accounts payable system. In this case, the general ledger can be reconciled back to the accounts payable system. However, if the accounts payable balance is moved to another account, reconciliation is no longer possible.
In some systems, the user has the option of changing the underlying transactions to identify the target account instead of the source account. If the transactions are changed, the general ledger balance is supported by the posted transactions. However, there is no longer a link between the general ledger transactions and the transactions sent to the general ledger by the subledger. Consequently, if the transactions are not changed to reflect the target account, the balances in the general ledger can no longer be reconciled back to the underlying transactions.
Hence, what is needed is a system that supports a move/merge operation can be easily reversed without undesirable side effects.
SUMMARY
One embodiment of the present invention provides a system for moving balances from at least one source account into a target account and subsequently reversing the movement. The system operates by receiving a request for a move/merge operation to move the balances from source accounts to the target account. In response to the request, the system creates a list of changes to the source accounts and the target account that are involved in moving the balances. The system stores this list of changes into a memory for later retrieval during a move/merge reversal operation. Next, the system performs the move/merge operation by applying the list of changes to the source accounts and the target account. When the system subsequently receives a request to reverse the move/merge operation, the system reverses the move/merge operation by retrieving the list of changes from the memory and applying the inverse of changes in the list to the source accounts and the target account. In a variation the on above-embodiment, the system validates the move/merge operation according to a set of business rules before performing the move/merge operation. For example, the set of business rules may ensure that the source and target accounts belong to the same financial statement category or the same business entity. In a further variation on the above embodiment, the system additionally creates move/merge audit journal entries to facilitate future auditing of the changes made during the move/merge operation.
REFERENCES:
patent: 4885685 (1989-12-01), Wolfberg et al.
patent: 5117356 (1992-05-01), Marks
patent: 5220501 (1993-06-01), Lawlor et al.
patent: 5390113 (1995-02-01), Sampson
patent: 5604853 (1997-02-01), Nagashima
patent: 5659165 (1997-08-01), Jennings et al.
patent: 5933593 (1999-08-01), Arun et al.
patent: 5958004 (1999-09-01), Helland et al.
patent: 5996088 (1999-11-01), Frank et al.
patent: 6006204 (1999-12-01), Malcolm
patent: 6058375 (2000-05-01), Park
patent: WO 95/04659 (1995-02-01), None
The Use of Databases to Enhance accounting Information; Patricia A. Essex, Feb, 1997, Th ohio CPA Journal.*
Client/serever accounting: accounting systems based on client/server architectures increase productivity. McKie, Stewart, DBMS, v6, n2, p62(5), Feb., 1993.*
Data Reengineering Fits The Bill; Process eases transition form legacy applications to client-server systems.Informationweek, May 26, 1997; Peter Aiken.*
Bellone, Robert; Cohn, Michael; M.Y.O.B; Accounting Technology; v12n5 pp: 28-31, Jun. 1996.*
Cohn Michael; Bellone Robert; Changes in the wind; Accounting Technology v12n6 pp: 21-30, Jul. 1996.*
Bellone, Roberts; Swiss-army accounting software; Accounting Technology; v13n4, pp: 26-37, May 1997.*
Dauphinias et al.; Accounting for Individual Tastes; PC Magazine; v4, n4, p 200-207, Feb. 1985.*
Davis; Low-end accounting software; Accounting Today; New York.*
Giovetti; Client write-up: Conquer the mountain; Accounting Technology; Boston, Oct. 1995.*
Giovetti; Accounting software update; Accounting Technology; Boston, Jul. 1995.*
Salmon; Accounting with a mouse; Accounting Today; New York, Jan. 1994.*
Oracle General Ledger User's Guide, pp. 6-122 through 6-135.
Kaplan Donald H.
Ng Rondy Chi-Tsung
Rahman Sharif M.
Oracle Corporation
Park Vaughan & Fleming LLP
Retta Yehdega
Stamber Eric W.
LandOfFree
Reversible move/merge operation for a general ledger does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Reversible move/merge operation for a general ledger, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Reversible move/merge operation for a general ledger will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3129465