Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

Accounting Database Design Expand / Collapse
Posted Saturday, July 27, 2013 10:09 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, October 22, 2014 3:30 AM
Points: 8, Visits: 51
Hello everyone i am developing an accounts package for my company using Sql Server 2008 and VB.Net.

I need some help regarding the database design.

I have the following tables


GroupId int
GroupName nvarchar(50)
ParentGroupId int
CatId int
PrimaryGroup bit
CreatedByUser nvarchar(50)
CreatedOn datetime

The above table will store the Groups for the accounts eg: Current Assets etc.

Accounts Table

AccCode nvarchar(6)
AccountName nvarchar(30)
ParentAcc nvarchar(6)
GroupId int

The above table stores the Accounts/Ledgers .

VoucherNo bigint
VoucherDate datetime
DebitCredit int (0 for Credit 1 for Debit)
AccCode nvarchar(6) (Account Code to be debited/Credited)
UserID nvarchar(30)


VoucherNo bigint
SlNo int
AccCode nvarchar(6) (Debit this account if account in VoucherMain credited/ Credit this account if account in VoucherMain Debited)
Amount decimal(18, 2)
Narration nvarchar(MAX)

The above two tables store the transactions.The above two tables linked by the VoucherNo columns

Now my question is whether i should maintain all the bank accounts in the accounts table or should i have a separate table for the bank accounts.
As each bank account should have its respective ledgers.

Please help me in the design of this database.

Post #1478293
Posted Saturday, July 27, 2013 5:06 PM



Group: General Forum Members
Last Login: Today @ 8:40 AM
Points: 42,081, Visits: 39,472
What is the difference between what you've designed the Accounts hold and a Bank Account?

Also, why do you need to identify a "Primary Group" and why are you using 4 bytes to identify a credit or a debit?

I also hope you know enough about "Adjacency List" hierarchies to be able to constrain the tables to prevent "cycles" and duplicates in the hierarchical tables.

You've taken on a lot to chew and we haven't even started on the VB side of the code. My recommendation would be to your company would be to abandon this task and buy a copy of "Quick Books Professional" or some such. It'll save your company a whole lot on time and mistakes.

--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

Helpful Links:
How to post code problems
How to post performance problems
Post #1478319
Posted Wednesday, August 21, 2013 8:07 AM


Group: General Forum Members
Last Login: Wednesday, August 21, 2013 7:48 AM
Points: 17, Visits: 52

You should have a separate table for banking transaction, and a separate one for maintaining the bank name, address, contact that can link to the first one. Looking from your tables above, is that all you have in your ERD?
What about Inventory, Sales and Purchases, don't you think you need a place to store them too? I see you have two tables for voucher, are these for storing payment transaction, if yes, you need to create a referential identifier to your vendor table, and vice-versa for your sales transactions? It's too elaborative to explain further from here, but i do encourage you do find out more on the database structure and designing concepts before you embark further on your project. Derek Liew seems to have some good designing concept for a simple accounting database and you may take a look at it at
Post #1486732
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse