Sir, I am creating a very simple database. Which will be checked first and then used. And I got this task from my manager.Bit like learning to drive an F1 car then. Then employing an F1 driver for the actual races?
Account | Dr | Cr |
Sales | 100 | |
Sales Tax | 15 | |
Sales Ledger | 115 |
Yes CJ exactly my manager needs simple database like this.Accounting is about double entry book keeping - for every group of entries there is an equal and opposite group of entries. It can be one to one, but not always. At the moment your general ledger account resembles what is called a 'cash book'. You are only showing one side of the transaction, the other is assumed - to be a cash 'box' or a bank account
Consider the situation where you have made a credit sale - you want to credit the sales account, but the opposite entry can't be the bank account because you haven't received the money yet. So you need a sales ledger account. Then when the money is received you credit the sales ledger account and debit bank.
And sticking with that example, you no doubt have a sales tax of some sort. so you also need to credit the sales tax account - and debit that to the salesledger account as well
so for a simple one line sale you would have
Account Dr Cr Sales 100 Sales Tax 15 Sales Ledger 115
and perhaps you need further entries for tracking things like discounts, cost of sales, shipping, etc
and against all of these you will need to know as a minimum the customer account, invoice number and invoice date so when the payment is made you can match the payment to the correct invoice.
Cash books are relatively easy to create and a good task for Access. If that is all your manager requires then go for it. An accounting app is a different task all together.
Yes CJ exactly my manager needs simple database like this.
My boss wanted me to create a small database so that I could also learn the basics of accounts and because of my interest in access databases I could learn accounting with more interest. And when a small database is created, people using it will become familiar with computerized accounting.
I really like your advice. I agree with you. And my managers know that I am a beginner and that is part of my learning. That is why they are not stopping manual accounting. Rather, they will run the manual accounting side by side until they are satisfied with the database I have created. They know that this database will not last long term. And they don't even want to run it long term. When our accounting staff becomes familiar with computerized accounting, our managers will purchase a complete accounting software in consultation with company owners.You are not seeing the big picture here. Do you know the difference between London's "Big Ben" clock and a cheap Timex wrist watch? The size of the gears - but not the complexity. There is no difference in complexity for clocks that tell time on the 12-hour or 24-hour clock - both have gears that do 60:1 reduction for minutes and for seconds. But some are huge because they drive big "hands" while some are tiny because they are small enough to wear on your wrist.
Similarly, a "small" database that acts as a "general ledger" package is just as complex as one that drives a 50,000 employee factory. The mistake is confusing physical size of the company and procedural complexity of the corresponding package requirements. You use the same process for ONE transaction as you do for 10,000 transactions.
In the end analysis, it is your project, your problem. I can only cheer you on from the sidelines and offer advice. My first level of advice is to take the time to develop a procedural specification before you do any coding. My second level of advice is to clarify to the managers that your product will not be fully functional for a long time, and the size of the company has NOTHING to do with the complexity of the project.
quite a reasonable manager - prepares a specialist in advance who will help master the accounting program in the future - there are too many flaws in themI want to tell you that my boss gave me the task of creating this accounting database because our company is currently running manual accounting.
So, they are willing to invest months and months of your salary in building a completely custom accounting system, while paying the regular accounting staff to do the accounting as always. Then train the staff to use your new custom accounting system. THEN, invest again in a purchased accounting system and invest AGAIN in retraining them to use that purchased accounting system. Not afraid of spending money, apparently.When our accounting staff becomes familiar with computerized accounting, our managers will purchase a complete accounting software in consultation with company owners.I really like your advice. I agree with you. And my managers know that I am a beginner and that is part of my learning. That is why they are not stopping manual accounting. Rather, they will run the manual accounting side by side until they are satisfied with the database I have created. They know that this database will not last long term. And they don't even want to run it long term.