DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:to:subject:mime-version:content-type;
	b=XeS302JVNnjHJdHqagX44Ufv/HC5A1mKi/57M7hBceuZLveSv/Ifn1xOl3CwVkJd0XqKMSwD8xBY1jYu6c/FM/3iu3oM5Gozo3QIYjtRUeqOXT6eDJsHDolTiBUGj2Z/JD5kBomZgLxJxL/2974WlZMc2A0v/VbGyCBi2pLKklM=
Message-ID: <8078a1730802061708q17c72234xe61be822459a24a8@mail.gmail.com>
Date: Wed, 6 Feb 2008 17:08:54 -0800
From: "Medi Montaseri" <montaseri@gmail.com>
To: pgsql-sql@postgresql.org
Subject: accounting schema
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_22629_29569223.1202346534612"

------=_Part_22629_29569223.1202346534612
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,

I am learning my way into Accounting and was wondering how Accounting
applications are designed. perhaps you could point the way....

On one hand, accountants talk about a sacret equation A = L + OE (Asset =
Libility + Owner Equity) and then under each categories there are one or
many account. On the other hand a DBA thinks in terms of tables and
relations. Instead of getting theoritical, allow me to setup an example

Say you have have construction project (like a room addition) or one of
those flip this house deals

Owner brings the land (equity) of say worth $100K
Expenses begin to mount ( that is a minus against OE)
Account Payble begins to mount (that is a liability)
And one day you experience a sale

As a DBA, (and keeping it simple) I am thinking I need a table for every
account which migh look like

id, description, credit, debit, validated, created_on, created_by,
modified_on, modified_by

Is that pretty match it ?
Please let me know if you have seen some accounting or DB book that
addresses this problem domain.

Thanks
Medi

------=_Part_22629_29569223.1202346534612
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi,<br><br>I am learning my way into Accounting and was wondering how Accounting applications are designed. perhaps you could point the way....<br><br>On one hand, accountants talk about a sacret equation A = L + OE (Asset = Libility + Owner Equity) and then under each categories there are one or many account. On the other hand a DBA thinks in terms of tables and relations. Instead of getting theoritical, allow me to setup an example<br>
<br>Say you have have construction project (like a room addition) or one of those flip this house deals<br><br>Owner brings the land (equity) of say worth $100K<br>Expenses begin to mount ( that is a minus against OE)<br>
Account Payble begins to mount (that is a liability)<br>And one day you experience a sale <br><br>As a DBA, (and keeping it simple) I am thinking I need a table for every account which migh look like<br><br>id, description, credit, debit, validated, created_on, created_by, modified_on, modified_by<br>
<br>Is that pretty match it ?<br>Please let me know if you have seen some accounting or DB book that addresses this problem domain.<br><br>Thanks<br>Medi<br><br>

------=_Part_22629_29569223.1202346534612--