If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
database with yearly split data
sorry Fred, my message was suppose to appear after you, but it is displayed
above your message, please read that. Regards, Fred wrote: Dave, GL in anything except the smallest business environment almost inevitably needs automated ties with and databasing of A/R/ A/P, and invoicing/order transactions. Combined with that, many transactions (e.g. invoicing) must be daabased as events. I've never attampteed it, and instead have used enterprise software. My comments were more from seeing how enterprises software ( which is a database application) appears to handle these things. You having written these before means that you know to actually do this far better than I do. Sincerely, Fred -- Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/For...esign/200809/1 |
#12
|
|||
|
|||
database with yearly split data
You are correct, even in medium sized organizations, GL does have to
interface with AP, AR, Payroll, and other industry specific modules like Sales, Inventory, POS, and a host of others. The typical method for handling this is a posting routine where the external app creates transactions the GL then picks up. To be truely integrated, the external apps have to have access to the Chart of Accounts to do it's posting. -- Dave Hargis, Microsoft Access MVP "Fred" wrote: Dave, GL in anything except the smallest business environment almost inevitably needs automated ties with and databasing of A/R/ A/P, and invoicing/order transactions. Combined with that, many transactions (e.g. invoicing) must be daabased as events. I've never attampteed it, and instead have used enterprise software. My comments were more from seeing how enterprises software ( which is a database application) appears to handle these things. You having written these before means that you know to actually do this far better than I do. Sincerely, Fred |
#13
|
|||
|
|||
database with yearly split data
Dave (Klatuu) would be the more expert one to answer this.
If you'd like my "armchair" thought, the only time that I actually did this (on a very very small scale, and with minimal automatic integration with other "modules" ) vs. using enterprise software to do it, once the dust settled after the end of the year (i.e. a few weeks into the new year) I had them balance / reconcile the previous year's GL, copied/archived the GL from the year being closed into a new little year-specific GL applicaiton and also to a locked archive, made "January 1st" opening entries, and then wiped out the GL entries for the year being closed. I did not do this with or "close out" anything except the GL. After that moment, there could be not GL postings of any type for (with a date of) the previous year. |
|
Thread Tools | |
Display Modes | |
|
|