1) Fixed assets and Stock Assets are not the same thing. One depreciates over time, a Stock on the other hand will fluctuate. From a developers (and accountants) point of view the Fixed Asset value is maintained by periodic adjustments to a Contra Asset account that usually depreciates over a period of time, usually on a proscribed schedule. For the developer isn't merely another kind of jornal entry that is made on a periodic basis as the value of the Fixed Asset depreciates.
2) To close an Accounting period you usually have a table of Accounting periods and fields to designate whether that period is open or closed. Usually you also have fields to designate whether specific modules (AR, AP, GL, etc.) are opened or closed and the developer insures that if you close the period in general that all modules are closed as well. The developer will usually create code as well to respond to the event of an accounting period being closed to reccaculate the beginning balances of each general ledger account so that the reports like the Trial Balance, Income Statement, Balance Sheet and the like don't have to go back through the General Ledger table (all the way back to the beginning of time) to determine what the balance of a specific account is. For performance reasons it's much faster to start with the months beginning balance for each account and then just add in the GL transactions that have transpired since the period selected (using of course the most recent beginning blanaces belonging to a closed period. Of course we also insure that the accounting periods are closed in Order, Period 3 can't be open if Period 4 is closed. There's also an End of Year Period that one usually creates that has special code attached to it to sum up all Income Statement account balances for the here and generate an end of year joranl entry to zero out the balance of each Income Statement account and roll over whatever the difference is into the Retained Earnings account.
These types of accounting principles/concepts are pretty much Accounting 101 so just about any accountant should be able to describe in general terms to the developer how the dollars and cents should be reflected on the books. A developer worth their salt should be able to translate that into a program that will perform as required. The one good thing about accounting is that there are well established rules on how it works and it generally lends itself very well to the way data is stored and retrieved. As a developer I tend to find the other requirements of a business to be far more changing. The work a developer has to do to build an accounting system by comparison isn't nearly so rough although I've found some developers have some difficulty following what the needs of the accountant are and in other cases I've found that some accountants have difficulty articulating their needs to the developer since so many of the accounting concepts like these are things they have long since taken for granted. Even so, once the developer understands what the needs are they should have little dificulty building it.
Main Topics
Browse All Topics





by: jimpenPosted on 2008-07-29 at 12:39:07ID: 22114825
This is from a layman's view of supporting accounting apps. The basic difference between a fixed asset is it counts against the books in that you don't expect to sell it on a regular basis. It is a capital investment that is depreciated over a period of time. Where stock/inventory is expected to have a turnover and is counted against revenue.
Think of it as a box of widgets sitting on a shelf. The widget you paid $30 to purchase/ assemble/ manufacture and your customers are going to buy for $50. The shelf, on the other hand, you paid $100 for and expect to keep for 7 years and hold cycle of widgets. Over that 7 years you will divide the cost up and take that amount off you total assets.
You really need to have your hands on the FASB accounting standards next to your VB programming book for this one. ;-)