[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: importing daily data to LedgerSMB
- Subject: Re: importing daily data to LedgerSMB
- From: WK <..hidden..>
- Date: Mon, 8 Mar 2010 23:58:22 +0200
2010/3/8 Chris Travers <..hidden..>:
> If you do that, LSMB will quite happily calculate COGS and tax for you
> which is probably not what you want.
I hope i understand you correctly: COGS is something like "how much i
made money from this particular product" and depending from that LSMB
calculates some taxes?
If i got you right, this is not issue for me. At least now. We have
only different VAT rates and taxes from dividends, other taxes are
bound with payroll.
As far i understand, i can't enter purchase (sales too) invoices as
transaction, because i need them be liabilities not as expenses
(Purchases etc) in my balance.
> What I would suggest instead is:
>
> 1) ÂCreate an import schema with tables representing the info to be imported.
> 2) ÂUse some sort of stored procedures to import these as GL and AP
> transactions (if in 1.3, create batches of GL/AP vouchers)
> 3) ÂHave a nightly job which writes to the import tables and runs the
> stored procedures.
There is still stranger procedures to me, but something like that i
imagined. (Except invoices instead of transactsions.) In 1.2 dataset
is around 60 tables. Is there some place to get overview of relations
between them? Or maybe you can just point me which tables are
neccessary when i need to import for example purchase invoices?
Btw, what are "batches of GL/AP vouchers"?
> If this is all you are doing, I would recommend seriously working on
> moving to 1.3 even at this point. ÂThe vendor/gl and batch-draft
> systems are rock solid and well tested, and it would allow you to
> review the data before posting it to your books. ÂThis keeps you in
> control and allows you to handle integration errors before, well, you
> insert a lot of data into your accounting db.
Sounds very much what i wanted, i still need to do some homework to
understand some termins and getting clear how many Postgres differs
from MySQL.
I am definitely movin towards 2.0 but i still got 1.3 not working :)
I try first make some basics clear on 1.2 and hope 1.3 will settle
during this time little bit.
--
Wbr,
KÃike hÃÃd,
WK