by Sharif Mehedi · in Developers · assigned to Sharif Mehedi

Résumé

Concepts sous-jacents

Commentaires

• 4 mois, 2 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : I added a Journal.auto_match field and wrote Voucher.create_ledger_movements which may yield multiple movements depending on the account type, Journal.auto_match and match-able movements.
• 4 mois, 2 semaines ago by Luc Saffre in reply to Sharif Mehedi about #6748 (Managing ledger movements in pronto) : It's worth a try. No principal objection.
• 4 mois, 2 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) (1 reply) : Instead of overriding the register_voucher() method I am tempted to override the call to create_ledger_movement() where lino will call create_ledger_movements (plural) which may yield multiple movements and may also call the original create_ledger_movement to create the individual movements. And the...
• 4 mois, 2 semaines ago by Luc Saffre about #6748 (Managing ledger movements in pronto) : New option "Journal.auto_match" that would "Set the match automatically when registering a voucher to use available credit". And then override the register_voucher() method on Matching or Payable so that it looks up whether the partner has "available credit". What means "available credit"?
• 4 mois, 2 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : And also I could probably create multiple movements matching against different "match" strings. For example if we have two "Unapplied payment (UPJ)" with amount 300 & 600 and if I make a purchase order to the same partner with amount 900, the create_ledger_movement could create two movements on the ...
• 4 mois, 2 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : Wondering if I should only override the "get_match" method!
• 4 mois, 2 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : When I create PaymentReportsByJournal (an instance of finan.PaymentOrder) they seem to match against due suppliers and customers account movements. But When I create an "Unapplied receipt (URJ)" or an "Unapplied payment (UPJ)" (an instance of trading.CashInvoice), and later these "Unapplied ..." ent...
• 5 mois, 3 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : Finally. Now I think I am ready to run the test suite.
• 5 mois, 3 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : Now that we have CashInvoice that works to receive advance payments, not sure how to make this money match against later sales invoices.
• 5 mois, 3 semaines ago by Luc Saffre about #6748 (Managing ledger movements in pronto) : I fixed docs/projects/cosi5.rst and pushed my changes to book and xl.
• 5 mois, 3 semaines ago by Luc Saffre about #6748 (Managing ledger movements in pronto) : Printing a CashInvoice now works. We added cash_received information, and made the site owner in the footer respect ledgers.
• 5 mois, 3 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : Rasel had a look at the invoicing stuff in pronto. He tried doing a sales invoice (which still need some work), printing and sharing a sales invoice to his customers, and afterward he asked if lino could generate him a delivery note after product delivery is done. Of course lino can generate him del...
• 5 mois, 3 semaines ago by Luc Saffre in reply to Sharif Mehedi about #6748 (Managing ledger movements in pronto) : Good idea. Or in the invoicing task? Or both (it gives default value for plan)? Or name it "Edit before registering" and have it False by default.
• 5 mois, 3 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) (1 reply) : Here at this place, I would like the call to invoice.register optional, because after executing a plan, I want to give the users the possibility to add a discount price or any other modifications (to the invoice) that they might want. Having to de-register and re-register (after modifications) seems...
• 5 mois, 3 semaines ago by Luc Saffre in reply to Sharif Mehedi about #6748 (Managing ledger movements in pronto) : Good question. Let's talk about it tomorrow morning.
• 5 mois, 3 semaines ago by Sharif Mehedi in reply to Luc Saffre about #6748 (Managing ledger movements in pronto) (1 reply) : A journal does not have a reference to a PaymentMethod. Instead should I have three journal for the common accounts Bank, Online payments and Cash payments?
• 5 mois, 3 semaines ago by Sharif Mehedi in reply to Luc Saffre about #6748 (Managing ledger movements in pronto) : Why do I need separate journal for these payment methods, can't I use only one journal for them all?
• 5 mois, 3 semaines ago by Luc Saffre in reply to Sharif Mehedi about #6748 (Managing ledger movements in pronto) (2 replies) : I don't think so. If you use payment reports, you must define one journal for each payment method (each of "Cash", "PayPal", "bKash", "Bank"). The common account "Other payments" was useless, it was an alias for "No payment now". And in this case the cash_received field should be read-only and alway...
• 5 mois, 3 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) (1 reply) : I see that you have commented out the other_payments account. But I think I need it, for managing the Payment reports.
• 5 mois, 3 semaines ago by Luc Saffre about #6748 (Managing ledger movements in pronto) : I pushed my changes. One doctest in book is deliberately failing because I want to talk with @8lurry about this.
• 5 mois, 3 semaines ago by Luc Saffre about #6748 (Managing ledger movements in pronto) : I saw the round5() function in /home/luc/work/xl/lino_xl/lib/trading/fixtures/demo_bookings.py. Did I guess correctly that cash payment in Bangladesh amounts are rounded to 5 ৳? This another topic to talk about: rounding.
• 5 mois, 3 semaines ago by Luc Saffre about #6748 (Managing ledger movements in pronto) : The new journal "Sales orders" triggers a little avalanche of changes. I'm still trying to calm it down.
• 5 mois, 3 semaines ago by Luc Saffre about #6748 (Managing ledger movements in pronto) : TODO: minimal_ledger wants to create invoicing tasks together with the different journals, but the demo user doesn't yet exist.
• 5 mois, 4 semaines ago by Luc Saffre about #6748 (Managing ledger movements in pronto) : There seems to be some bug in Lino: in cosi5 we made a SO journal, which has "make ledger movements" switched OFF, but still it creates ledger movements. Theoretically it should work, but reality is different. Payable.get_wanted_movements() calls vat.VatDocument.get_payable_sums_dict().
• 5 mois, 4 semaines ago by Luc Saffre about #6748 (Managing ledger movements in pronto) : todo: create a journal SO (Sales order) in cosi5, then place an order using the cash_received field for prepayment.
• 5 mois, 4 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : Now that the PaymentReports are integrated in pronto, it seems to support partial payment out of the box. But we still need handle payments in advance. Not sure how to do that, need @luc 's help.
• 5 mois, 4 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : I pushed PaymentReports related changes in lino, xl, book and welfare.
• 5 mois, 4 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : Oh the PayPal reports also make the counter movements. So, it's also bi-directional, at least in the sense of what I meant by bi-directional. Without checking the movement, I thought, it only created one movement for each invoice item but now I checked, there are two for each item, and one is in the...
• 5 mois, 4 semaines ago by Luc Saffre about #6748 (Managing ledger movements in pronto) : But why do you think that in pronto we should do it with the bi-directional approach?
• 5 mois, 4 semaines ago by Luc Saffre about #6748 (Managing ledger movements in pronto) : Yes, until now, a payment order generates one counter-movement with the sum of all the amounts of the items. This behaviour is defined in PaymentOrder.get_wanted_movements(). Maybe we want a new feature to make Lino generate one counter-movement per item of the payment order.
• 5 mois, 4 semaines ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : The fill action works good with the do_fill.select_rows to True, It add items to the Content of PPR table. But it doesn't seems to be doing bidirectional stuff like what MSC journal did. I think, in pronto we should do it with the bi-directional approach, a new voucher entry in those journal should ...
• 6 mois ago by Luc Saffre about #6748 (Managing ledger movements in pronto) : @8lurry did you start to work on adapting the book test suite? Commit your changes before you go to sleep, because tomorrow morning I might want to work on them as well.
• 6 mois ago by Luc Saffre in reply to Luc Saffre about #6748 (Managing ledger movements in pronto) : I updated the reference docs about Action.select_rows.
• 6 mois ago by Luc Saffre about #6748 (Managing ledger movements in pronto) (1 reply) : A row action (select_row True) is available *only* when at least one data row is selected while a list action is always available. I fully agree with you if you say that there is something fishy there.
• 6 mois ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : When I set it to true, it raises exception related to sepa not being in installed plugins.
• 6 mois ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : The FillSuggestionsToVoucher action has select_rows set to False, I wonder why.
• 6 mois, 1 semaine ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : Let's say we have a sales invoice, which means that the items in the invoice (which are products) has been delivered to the customer (the partner of the invoice). And this invoice doesn't say anything about the payment against the product delivery. But only specifies the total amount. It creates two...
• 6 mois, 1 semaine ago by Sharif Mehedi about #6748 (Managing ledger movements in pronto) : Created new Ticket #6748 (Managing ledger movements in pronto).