From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Invoice Table Design |
Date: | 2016-11-29 16:53:04 |
Message-ID: | alpine.LNX.2.11.1611290847410.6484@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 29 Nov 2016, btober(at)computer(dot)org wrote:
> The other bit of experience I'll share is the suggestion that invoicing is
> a situation that lends itself to the uniformly incremented sequence
> pattern. Accountants and comptrollers love this.
Reading your message brought to mind a suggestion for Rob: look at the
source code for ledger-123 <http://www.ledger123.com/>. It's a fork of
SQL-Ledger which I've used for my business for almost 20 years. It has a
functional invoicing capability and should give you ideas on how to
structure your database and tables.
I know you'll need customer, invoice, line-item tables at the minimum. But
since I use it only to generate service invoices and post them to accounts
payable I don't know the details of how it works. I do use postgres
(currently -9.6.1) and httpd with it.
HTH,
Rich
From | Date | Subject | |
---|---|---|---|
Next Message | Israel Brewster | 2016-11-29 17:12:14 | Re: Backup "Best Practices" |
Previous Message | btober@computer.org | 2016-11-29 16:31:07 | Re: Invoice Table Design |