| From: | "Isak Hansen" <isak(dot)hansen(at)gmail(dot)com> |
|---|---|
| To: | justin <justin(at)emproshunts(dot)com> |
| Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Chart of Accounts |
| Date: | 2008-10-14 21:28:24 |
| Message-ID: | 6b9e1eb20810141428q733930e2l9b0d01e2a33bfa2b@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Oct 14, 2008 at 5:07 PM, justin <justin(at)emproshunts(dot)com> wrote:
> because a credit account is a liability account aka a negative account so
> credit a credit account causes it to go UP not down.
As you say, "a negative account". Our liability accounts go further
down when credited. I work with accountants all day, and this is what
they expect.
Of course either approach works, but I've come to prefer the single-column one.
> Isak Hansen wrote:
>
> On Mon, Oct 13, 2008 at 2:57 AM, justin <justin(at)emproshunts(dot)com> wrote:
>
> [...] Also you want to split out the debit and credits instead of
> using one column. Example one column accounting table to track values
> entered how do you handle Crediting a Credit Account Type. is it a negative
> or positive entry???
>
>
> How is crediting a credit account different from crediting any other
> account?
>
> YMMV, but I think a single amount column makes for a more consistent design.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Thoen | 2008-10-14 21:38:37 | Re: Update with a Repeating Sequence |
| Previous Message | Merlin Moncure | 2008-10-14 21:22:09 | Re: Drupal and PostgreSQL - performance issues? |