Topic: New Functionalities suggestions

Quick entries is not correct way post VAT (tax) entry. A basic book keeper or data entry person will make mistakes. 3 functionalities which needs to be added in Frontaccounting are

1) Tax to be calculated for G/L expense invoices. At present if I have an invoices from accountant for £10,000 + VAT, you have to add new line (or use quick entries) with GL account for relevant VAT and manually calculate VAT amount. This is prone to mistakes and miss posting by a junior person. Again with quick entries user has to input total of VATable amount. This doesn't make a very good ERP system.

2) Add "Direct Posting Allowed" options on all GL accounts. This is very important in small & big companies as this stops junior person to do miss posting to the important GL accounts like VAT, COGS, etc.

3) To be able to assign tax rate to each GL account (just like items). This way you can stop user wrongly entering VAT (tax) to non-VAT supplies.

With my experience on MS Dynamics NAV for 11 years, I think these functionalities will make Frontaccounting a very robust and user-friendly system.

Deven

Re: New Functionalities suggestions

It would be very helpful if the development team can add chart of accounts view with a column showing current balance of each GL account on right hand side.

Deven

Re: New Functionalities suggestions

When you use the supplier invoice from the right hand side tab in purchase tab, you use the lower GL items for entering direct account booking.
Making quick entries for all your expenses eliminate all the problems for you.
Read about how to use them in the wiki.
In my opinion there are no possible mistakes here if you have created the quick entries correctly.
This has been used over several years, without any kind of problems.
Regarding your post on COA, there is a report, the first one in the banking and general ledger reports. Is you select this report you have the option to show the balances as well

Re: New Functionalities suggestions

I know you can use quick entries but if you have 40-50 different expense accounts then it's lot of work. One more functionality which is missing or needs modifying is "Revenue/Costs Accruals". I think we need proper recurring journal like in many ERP system including open source xTuple. You should be able to save a multiple recurring journals with starting and expire date for accruals and prepayments and post each journal at the end of each period/month or at users wish. At present the system posts transactions for all numbers of period entered and if your prepayment fall in next fiscal year, it throws an error.

Deven

Re: New Functionalities suggestions

Well, sorry to hear that you dislike FA's behaviour. Maybe you should stick with some other ERP system.
The general behaviour in FA has been majured during several years, and our users are somewhat satisfied with it. At present we have about 110.000 downloads and we are glad for that.

Joe

Re: New Functionalities suggestions

I like most of the functionalities of Frontaccounting. I was just giving my suggestions which might help improve the system.

Deven

Re: New Functionalities suggestions

Ok, thanks. But bear in mind that FA is open source and mostly for small companies.

Re: New Functionalities suggestions

1) You should entry such an invoices via normal purchase Direct Invoice interface. Just create separate inventory item with type service for the accounting services and you can use it Direct Invoice. Then you have all needed taxes calculated automatically, there is no place for errors.
2) I'm not sure about this preposition. Where such a constraints should be added? (journal entries has its switch in access setup, so you can keep newbies away from the journal funtcionality)
3) Introducing complex taxed transactions via journal does not make sense. In many countries beside taxes you have to register also respectoive net amount. There is no easy way to link tax lines to net value GL lines in journal, also other things aree important like vat category for posted item etc, so you should just do taxed postings as described above (p1)

Janusz

Re: New Functionalities suggestions

Thank you for your response

1) I've now created quick entry for applying appropriate VAT for Admin expenses entered via supplier invoices. This seems easier way if posting direct invoices.

2) This constraint is added in chart_master table. A new Boolean field to be added and before posting journals or supplier invoices with GL account, this constraint be check. If it doesn't require major code change, I think it will be useful.

3) Again this requires a field in chart_master table. This is useful from UK VAT system. But again if a simple code can do this then it will be useful.

4) I think recurring journal is definitely needed replacing "Revenue & Cost accruals".  You should be able to save multiple recurring journals with starting/expire date, frequency and amount for accruals and prepayments and post each journal at the end of each period/month or at users wish. I hope this utility is added to the system. I’m not a hardcore programmer but can provide my knowledge on system design.

In last 7-8 days, I've thoroughly tested and customised Frontaccounting for UK use. After trying various open source and free systems, I strongly feel that Frontaccounting is the best. It easy to use, very comprehensive and covers almost all modules of a good ERP system. A thousand times better than Sage.

I have created a template script for UK setup. I can upload it if you can provide me link or email address. You can test and see if you would like to put it as default UK COA.

Thank you

Re: New Functionalities suggestions

I see you tend to think from accountant perspective, while most people less skilled in accounting have problems with proper GL postings. This is why entering costs via purchase module is preffered over  low level GL journal. When you entry cost invoice via journal  you must to know what you are doing. For example taxes included in invoice depends on your supplier location, so you have to know how to post cost transaction in case o import, trade in EU or domestic supply, and all the 3 cases are posted differently to GL. Taxes can also depend on category of purchased goods. All this can be configured once for ever in supplier/items tables, then used flawlessly entering purchase order. This is why we prefer to not extend GL interface more than needed in favour to other higher level tools (yes, UE trade definitely need more support in FA).

I agree with the 4 preposition. Current accruals interface seems to be not the best way of dealing with the subject.
Finally thank you for all your warm words. Regarding UK COA I will contact you by email, you can also send it to contributions mailbox.
Janusz

Janusz

Re: New Functionalities suggestions

Dear Joe, Deven and Janusz

This is the best discussion I have ever seen on an open source accounting package on the topic of UK VAT.

As a Sage user since 1986 I would love to have an accounting solution to run on linux but have yet to even find one I feel worth trying, until now !

I feel a UK setup script would be a fantastic development for FA.

Thanks for giving me hope.

Dave

Re: New Functionalities suggestions

Janusz

I think you misinterpreted my comment. An invoice from supplier SHOULD NEVER be posted via a journal. You have to use purchase module i.e. Supplier Invoices to post expense invoices on any accounting system. General Journals are only used to reallocate costs from one department to another or accruals/prepayments or nominal adjustments. Firstly I feel that when posting expense invoices via Supplier Invoices, we should have auto calculation of tax for each line value or total taxable amount on the invoice (Just like purchase order entry form). Now tax rate assignment to each GL Account (which I suggested in my first comment) is useful for calculating tax on a purchase invoice. For example, a supplier has supplied me few items of which some are VATable @ 20% and some are Non-Vatable. On current FA supplier invoice form there is no auto calculation of tax. You can enter VAT amount either by creating new line with VAT GL account (not advisable as you don't want users to enter amounts in VAT accounts) or do a quick entry which enters tax amount for you based on the amount you put in the left text box. The user has to manually calculate total VATable amount to do the correct taxing and exclude non-vatable amount. Less user intervention/calculations in terms of taxes are highly recommend and should be auto-calculated be the system.

My suggestion is if you have tax rate assigned to each GL Account, then at the invoice level you can write a short code which calculates totals for each different tax rate for the GL accounts on the invoice and then auto insert tax line/s as per the tax rate of the GL account. Or for each GL account line VAT is auto calculated based on the tax rate of the GL account. i.e. On a supplier invoice I have 2 different GL account line (stationery & uniform which are VATable @ 20%) and 1 GL account line (refreshments – Tea which is non-vatable). The Invoice form then total of stationery & uniform line and generates a line with 20% tax. There is no tax line generated for non-vatable amount and is excluded for taxable/VATable purchases.

I think to do this you will have to create a 2 new columns in chart_master table (tax/vat rate & tax/vat amount) and a small script in supplier_invoice.php.

I hope it’s not too demanding.

Please let know contribution box email.

Many thanks

Re: New Functionalities suggestions

On current FA supplier invoice form there is no auto calculation of tax.

There is some fundamental misunderstanding here. Every defined item has assigned Item tax group, which determines tax type and rate.  When item is included in invoice respective taxes are calculated. This works the same both in sales and purchase side.
Please read carefully Tax Configuration wiki topic.
Janusz

Re: New Functionalities suggestions

Janusz

As I said before, I have thoroughly tested FA and I think I know each and every module and the working of it. I know that you can assign tax group to each and every item. This is the correct way to set up taxes on the system. I am not at all taking about items and “Purchase Order Entry” & “Direct Invoice”. These parts of purchase module are fine. I am discussing about GL account (posting general expenses invoices). All I am saying is that just like item is assigned a tax group/tax code, all GL account should have tax rate assigned. If you read my previous post again, I have not mentioned Items or purchase order entries as I know it calculates tax/VAT automatically depending on assigned tax group. The general expenses are posted on “Supplier Invoices” this is where my previous comment was related to. Please test me COA I have email. This will make things clear.

Deven

Re: New Functionalities suggestions

Ok, why do you prefer to entry general expenses via Supplier Invoice, instead of generic Direct Invoice form? Can you point out any cost type which cannot be entered here, and use of Supplier Invoice form is just necessary?
In my FA setup I use everyday I have just defined a couple of additional items like 'Electric energy', 'Communication services' and generic editable 'Other services' item, all with item type set to 'Service'. Using them with supplier Direct Invoice makes me free from any tax calculations, all is posted properly without manual calculations.

Janusz

Re: New Functionalities suggestions

Janusz

Yes it can be done by creating service item for any GL account but than option to post GL item expenses in "Supplier Invoice" doesn't make sense. Another issue is if you have categories GL ledger format then using service item is not possible. Please have a look at my COA.

Deven

Re: New Functionalities suggestions

Yes, IMO there is no big sense in GL lines on Supplier Invoice form. We have preserved the GL list here just for backward compatibility, the newer Direct Invoice does not contains this element.

Another issue is if you have categories GL ledger format then using service item is not possible. Please have a look at my COA.

I'm not sure what you mean here. Could you explain me the problem?

Janusz

Re: New Functionalities suggestions

Hello guys,

The Gl Items in supplier invoice is an extreme fine possibility to enter supplier invoice for phone bills, maintenance, various cost scenarious. Especielly if we use quick entries for this.

I see no way of entering these kind of cost elsewhere.

If we remove this, I guess we loose many users.

Joe

Re: New Functionalities suggestions

It could well be helpful if in case the development team can add chart of accounts see via a column showing current balance of each and every GL account in appropriate give side.

Re: New Functionalities suggestions

When you make a COA report, you can select to see the balances.

Joe

Re: New Functionalities suggestions

itronics wrote:

Ok, why do you prefer to entry general expenses via Supplier Invoice, instead of generic Direct Invoice form? Can you point out any cost type which cannot be entered here, and use of Supplier Invoice form is just necessary?
In my FA setup I use everyday I have just defined a couple of additional items like 'Electric energy', 'Communication services' and generic editable 'Other services' item, all with item type set to 'Service'. Using them with supplier Direct Invoice makes me free from any tax calculations, all is posted properly without manual calculations.

Janusz

A question to add is: what is legal? In Belgium the journal has to show all bookings made for that invoice especially VAT. VAT must be linked to the invoice ( supplier) and to the GL account where the amounts are booked. So, the most logic way is to book an invoice received via Supplier invoice. Editable tax fields are necessary for entering suppliers invoices because only VAT that is printed on the invoice may be declared and not the VAT the program may calculate. When VAT registration comes to check my books they only use the journals and invoices as legal documents. Direct invoicing from supplies can be easy but is it legal?

Re: New Functionalities suggestions

FA core is okay as it is. Make extensions for peculiar (country specific / rare legal) needs. The programming paradigm - KISS - is well protected here and that is why most non-programmers have found it easy to fathom the code. Extending the COA is inadvisable - porting from other accounting systems / fa versions, inadvertant switch flag type fields, backward compatibility issues pervade.

[RANT]:
Non Accountants and Non Programmers must be able manage FA without having to bother with Government - businesses need simple acounting info / capability for day to day operations. Most countries have begun to question the need for Statutory Audit - Self Audit is being encouraged. In the aftermath of Enron / Arthur Anderson / and other major corporations / audit firms / banks fudging accounts, Governments too will soon have automatic billing systems in their countries from which their VATs will be auto-calculated instead of summary submissions each month/quarter/year! There seems to be little trusted data on countries printing / creating money and providing huge windfalls to select individuals of choice - insurance, subsidies, rights.

{NICE]
If you do not sell in currencies (debt denominator) issued by governments - you do not need to pay tax! Corollary - no one pays any taxes for using FA! No one's paying Joe/Janusz any monies for coding and preserving the FA source! Yet FA users will look after you (tax free) when you visit their countries.....People like them are the real assets worth preserving.

Re: New Functionalities suggestions

@apmuthu
Thanks for support, all you have written is true. On the other hand usrr's response is main factor which drive the code changes to right direction. This application is made free available to help people do their everyday business, so it any feedback is highly appreciated. Lets don't discourage FA users smile.

@demille
I understand your objections regarding supplier invoice posting, but you are at least partially wrong, and probably it is effect of misunderstanding of FA Direct Invoice functionality.

So, Direct Invoice is just Supplier Invoice, GRN and PO made in one step. The additional cost GL lines available in Supplier Invoice form (and absent in Direct Invoice), are for special use and in most cases just sparse. Therefore _all_ journal entry postings generated by Supplier Invoice (without GL lines used) are the same as those generated when invoice is entered via direct Invoice page.

I agree it is sometimes useful to have editable tax entries on Supplier Invoice. When FA is properly configured taxes should be properly calculated, and there should be no  difference between real invoice and calculated VAT. The only reason I can see for this is small rounding errors which can be different in your supplier's invoicing soft.

Currently those differences are not supported directly in supplier invoice form in FA, but you can fix this by separated journal entry.

Again, I agree whether this is legally acceptable depends on local law. I can only say we are working on improvements in code which will make both EU intracommunity trade and above situation better supported in FA. Unfortunatelly this will not be available before next major release,a s additional databse changes are needed for this.

Janusz

Re: New Functionalities suggestions

itronics wrote:

@demille
I understand your objections regarding supplier invoice posting, but you are at least partially wrong, and probably it is effect of misunderstanding of FA Direct Invoice functionality.

So, Direct Invoice is just Supplier Invoice, GRN and PO made in one step. The additional cost GL lines available in Supplier Invoice form (and absent in Direct Invoice), are for special use and in most cases just sparse. Therefore _all_ journal entry postings generated by Supplier Invoice (without GL lines used) are the same as those generated when invoice is entered via direct Invoice page.

I agree it is sometimes useful to have editable tax entries on Supplier Invoice. When FA is properly configured taxes should be properly calculated, and there should be no  difference between real invoice and calculated VAT. The only reason I can see for this is small rounding errors which can be different in your supplier's invoicing soft.

Currently those differences are not supported directly in supplier invoice form in FA, but you can fix this by separated journal entry.

Again, I agree whether this is legally acceptable depends on local law. I can only say we are working on improvements in code which will make both EU intracommunity trade and above situation better supported in FA. Unfortunatelly this will not be available before next major release,a s additional databse changes are needed for this.

Janusz

Thank you for the explanation, it helped me a lot. If everybody will use FA in the future we would not have a discussion about editable tax entry possibility. But for the moment it would be ideal to have a TAX field that is normally calculated automatically but which can be erased and changed to the amount we want it to be. This way we do not have to make an other entry line to make things Legal and saving a lot of work.
Thank You

Re: New Functionalities suggestions

dvarsani wrote:

3) To be able to assign tax rate to each GL account (just like items). This way you can stop user wrongly entering VAT (tax) to non-VAT supplies.

With my experience on MS Dynamics NAV for 11 years, I think these functionalities will make Frontaccounting a very robust and user-friendly system.

Deven

Can't this be solved with making an item category  for each GL account which you want to monitor and an item for each GL account you want tax calculation?
I am new here and I made a Belgian Legal account three for FA  but to solve the Belgian and EU VAT problem I assigned the GL accounts I need for VAT declaration to an item category. EU, non EU and some other totals I need for VAT declaration I have assigned to the suppliers. I hope it will work, otherwise I have had a lot of work for nothing. I think I finally get some feeling of how this ERP system works. It should be after more then a week every day's work and study.