Generate an automatic memo per line could be useful for who reads GL Transactions. Something like "Transference to Bank Account XXX" (origin account memo) and "Transference from Bank Account YYY" (destiny account memo).
Thanks in advance.
It's much more fun, when you can discuss your problems with others...
You are not logged in. Please login or register.
FrontAccounting forum → Posts by jsantand
Pages 1
Generate an automatic memo per line could be useful for who reads GL Transactions. Something like "Transference to Bank Account XXX" (origin account memo) and "Transference from Bank Account YYY" (destiny account memo).
Thanks in advance.
FA 2.2.9: The proposed workaround does not work. Same problem described by jconnor: "At least one transaction is overallocated".
Ok.
Thanks.
Hi all.
After upgrade to 2.2 from 2.1.5, i only get errors like next, attempting to allocate payments to providers:
ERROR DE BASE DE DATOS : no debtor trans found for given params
sql that failed was : SELECT 0_debtor_trans.*, ov_amount+ov_gst+ov_freight+ov_freight_tax+ov_discount AS Total, 0_debtors_master.name AS DebtorName, 0_debtors_master.address, 0_debtors_master.email AS email2, 0_debtors_master.curr_code, 0_debtors_master.tax_id, 0_debtors_master.payment_terms FROM 0_debtor_trans, 0_debtors_master WHERE 0_debtor_trans.trans_no='50' AND 0_debtor_trans.type='1' AND 0_debtor_trans.debtor_no=0_debtors_master.debtor_no
Anybody can help me?
Thanks in advance
Eduardo Santander
Hi all,
The situation: My bank allows me to pay multiple providers through a single payment.
Is there a way to allocate a payment (not assigned to a specific provider) to one or more providers?
Thanks in advance for your response.
Saludos
In Chile, that's a problem. The SII (chilean tax authority) requires a report called "Purchases book" in wich every supp invoice is registered with its original data (20/Jul), in the opportunity that issues occur (Aug). So both, supplier invoice date and GL transaction date, must be preserved.
Is it possible to add a new field (inv_date) to 0_supp_trans where invoice date is registered?
Anyway, thanks for your prompt response
Saludos
The Supplier's invoice date has not to be necessarily the same date of the generated GL transaction. F.i, if today (12/Aug) I receive a invoice dated on 20/Jul, the GL transaction must be dated on 12/Aug, nevertheless the invoice must to preserve its original date.
I suggest add a date field to specify the GL transaction date in the "Supplier invoices" form. So, invoice and transaction will have its proper date.
Saludos
Another point of view over the same problem: the voiding process could allow the creation of a editable copy of the transaction that is being voiding, but including a reference (non-editable) to the voided transaction. In this way, you preserve the common practice and facilitate the accountant's work.
Saludos
Hi all.
Kalido's solution for groups (types) is WHAT i was been looking for. Reporting over subgroups is very easy in that way, just need sql statements. Moreover, from my point of view, the structure of the COA becomes more flexible to futures requirements of the enterprise.
I vote for him!
Saludos
Pages 1
FrontAccounting forum → Posts by jsantand
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.