Search options (Page 95 of 246)

All customer payments can be allocated to invoices when they are raised. Prepaid invoice is a special instance where the amounts paid and payable on the invoice match. If a client pays into his deposit account with the company, then an equivalent credit limit too can be provided and then contra-ed when settlement occurs.

Post Release FA 2.4.3+ fixes attached herein.

See this post on db updation and this post on prepaid invoice enablement.

Read this Forum Post if you are on any PHP version older than and not including PHP 5.6.

@itronics: Please fix this commit as above.. Committed.

The function get_full_price_for_item() takes only 5 arguments but the usage in the said commit calls for a change from 6 to 7 arguments now!

FA remains broken till this is fixed.

@joe: rerun with line 121 of sql/alter2.4.php:

'barcodes_on_report')");

being changed to:

'barcodes_on_stock')");

to match variable used in code.

Also update the standard Charts too with it in the sys_prefs table possibly disabling it by default with to match current installs.

1. random barcodes - security - so that it is not easily guessable as serial ones are. It appears to be a common way to do it in some local applications I have seen where an internal serial id is there to keep track by the application and the random one in another field is used for human / external automated interface. This technique is used in some hall ticket in examination systems to thwart "paper chasing" where auto dummy number allocation is resorted to.

2. A company specific config option to suppress the auto random barcode generation will help avoid confusion among those not using barcodes.

3. Which barcode type and how many digits in the barcode (if not specific to the chosen barcode) and the appropriate format for it, possibly without check digits (which should be auto generated) or when given, to be used for verification would make for a slightly more complex interaction best left to custom modules..... Making the function generic in the ammer you sufggested would be welcome even if not implemented fully for now. The barcode.php has anyway been fully "upgraded" manually from the original TCPDF sources of later versions to support a much wider range than was available earlier.

4. Yes, a note on the Show pictures options would be nice and it may double up for the config option or is it to be differentiated in some way by being a new one?

Why was the index:

UNIQUE KEY `name` (`name`,`rate`)

removed from the 0_tax_types table in FA 2.4 while it was there in FA 2.3?

Do we allow the same named tax with the same rate to appear more than once?

If so, how would we distinguish them in the select drop-down boxes?

@joe: what say you?

None of the others have any externally sourced references like a sales order did.

@joe: should the concurrent edit issue have a more generic solution to cover all auto generated references?

Better still - which was the original Chart of Accounts you used to start with?
Did you install any extensions that caused these differences?

You can upload anywhere (delete all insert statements especially for the users table) - just your schema and the differences with en_US-new.sql and paste the link here.

You have merged what should have been 2 separate vouchers. One for the invoice of 995/- and another for expenses of 5/-. Since you issued only 1 cheque for payment of 1000/- you should have got a Pay Instrument (Draft, TT, etc) for 995 and the bank would have debited you 5/- for bank charges. Hence the vouchers should have been:

Purchase Invoice:
=============
Credit AP (Supplier) - 995
Debit COGS: 995

Payment Voucher:
=============
Credit Bank - 1000/-
Debit AP (Supplier) - 995/- (Payment Allocation)
Debit Bank Charges - 5/- (Payment Allocation)

Now the Supplier Payments Report should show 995/- only.