Change invoice date

A date should not be revised. If the product was shipped to the customer when originally recorded, a customer request to change the date is grossly inappropriate and should not be considered, as you may facilitate a fraud on their part, for at least financial reporting failures. iproaccou.tant@gmail.com

Just ignore iproaccount. It's one of those.

As for changing the transaction dates in the db... Just try it and see what happens. As long as you have a good backup, you should be able to get back to your current situation no matter what happens.

I'm not familiar enough with the inner workings of FA to give you a "proper" answer, but it seems unlikely to corrupt the database. After all, the whole point of having a database is to avoid storing redundant information.

Hehe... I was upset, I admit.

Yeah, I figured I could try it. My fear was that I changed something which would affect certain queries which I would not see until the year end or so. After all I am poking directly in the database, and if I change something only half my database is inconsistent. If no error occur while testing but suddenly after entering 300 transactions report X or Y proves to be inconsistent you'd wish never to start a business.

I have been using OpenERP 6.0 before, so I can tell you how it feels when your database is non-consistent and you have no idea where the problem is. Only in the case of OpenERP it is the application itself which creates the inconsistencies, you don't have to poke into the database yourself.

Anyway, in the mean time I have finished entering 2013 into FA a few months ago. Now I am maintaining the accounting on a regular basis and all for 2014. A date which is off for a few weeks is awkward but no disaster. And I also learned a very important command: Remove a transaction. So instead of crediting an invoice I can simple remove and re-enter it. Which is satisfactory.

jlinkels

I often find myself in the same situation as jlinkels as I usually enter my transactions in batch.
In fact there are two "traps" that I find I always fall into:
1. The date; having the wrong date for the invoice or payment
2. Wrong bank account for payment.

There is a simple solution that would be nice to have implemented.
A checkbox is added near the Date and also near the Bank Account (In payments). Unless the box is checked, the invoice or payment will not be accepted.

The ability to switch off the extra checkboxes should be made available either in the preferences menu or in the Company Setup menu.

I am also having exactly the same issues...and it is driving me nuts, I have to keep manually correcting in the database.

@cambell: Your commit is quite nice. You might want to restrict the use of the TB_PREF to the FROM table alone and not in the other parts of the select statement. The WHERE clause can check for on or before instead of just before date.

$sql = "SELECT supp_trans.trans_no,
       supp_trans.type,
       supp_trans.supplier_id,
       supp_trans.tran_date,
       supp_trans.ov_amount,
       bank_trans.ref AS bank_ref,
       bank_trans.amount AS bank_amount,
       bank_accounts.id AS bank_id,
       bank_accounts.bank_name,
       bank_accounts.bank_account_name,
       bank_accounts.bank_curr_code 
FROM " . TB_PREF . "supp_trans supp_trans INNER JOIN 
     " . TB_PREF . "bank_trans bank_trans ON (supp_trans.trans_no = bank_trans.trans_no 
                                   AND supp_trans.type=bank_trans.type) INNER JOIN 
     " . TB_PREF . "bank_accounts bank_accounts ON (bank_trans.bank_act = bank_accounts.id)
WHERE supp_trans.supplier_id=" . $supplier_id . "
  AND supp_trans.tran_date <= '" . $date . "' 
  AND supp_trans.type=" . ST_SUPPAYMENT . " 
ORDER BY supp_trans.tran_date DESC 
LIMIT 1";

@joe: Want to pull it in?