We will put some examples and tips on Quick Entries here. You are welcome to contribute if you have done some smart ones.

Let us start with a simple one. You want to make a Quick Entry for phone bills.

First go into Quick Entries and create a new Quick Entry. Select Bank Payment and call it f.i. Phone. 
Don't set a fixed amount. Save it and select it again. Create 2 Quick Entry Lines.
1. Select 'Tax included, reduce base. Select the relevant tax type.
2. Select 'Remainder' and select the expense account for Phone bills.

If you don't use tax, then omit the first line.

Go into Bank Payments, select Quick Entries and select the Phone. Add the amount from the bill and press go.
Your lines should be there ready for processing.

Here is a more advanced one. If you only have a few employees you probably don't have a payroll program. You can preset a couple of Quick entries for that.

Say your employee has a sallary of $2,000. The payroll tax is 11.02% and the withholding tax is 15%.
First create a Quick Entry, Type: Bank Payment. Call it Salary X. Eventually preset the amount $2,000. And 
some entry lines:
1. % amount, select a Salary account (or create one, expense), 100%, Save
2. % amount, select an account for accrued payroll tax (or create one, liability), -11.02%, Save.
3. % amount, select a payroll tax account (or create one, expense), 11.02%, Save.
4. % amount, select an account for withholding tax (or create one, liability), -15%, Save.

If you have a fixed amount of tax, you could instead have choosen Amount, and the amount (negative).

Go into Bank Payments, select Quick Entries and select the Salary X. Select Go and your lines are ready for processing.

OBS

2009-08-19. The new change to Tax Type instead of Item Tax Type has now been done and committed to CVS Main.

Please remember to change your Quick Entries including tax to the above.

If more lines with other Tax Types are needed, group them together and use the same action.

4,527

(9 replies, posted in Items and Inventory)

Thanks for your nice words.
1. To my knowledge, there are no ongoing Italian translating. Please start with 2.1 beta. You can use the empty.po file in /lang/new_ language_template. Just create a folder it_IT like the other lang folders and a subfolder LC_MESSAGES and put your empty.po file here. Rename it to it_IT.po. Use the poEdit program to translate. It is very easy to work with this program.
2. Please read the readme.txt file in the module. It should explain which fields should be included.
3. The INNOdb part of MySql is used for transactions. If you are using multiuser access to your script, then transactions are needed to secure updating of several tables. There are also some performance issues with the INNOdb. So if you run without INNOdb, then do not access the script with more than one user at the time.
4. I hope somebody in the community will answer this question for you. We are concentrating on the core of FA.

Best regards
Joe

Thanks Jenifer,
This has been reproduced and will be fixed in CVS repository asap.

/Joe

4,529

(2 replies, posted in Translations)

Thanks roblaus for your nice words. I hope a lot of German speaking users will help you smile

/Joe

Hello,
Which release are you running?

/Joe

4,531

(19 replies, posted in Setup)

I'm not quite sure about this, I guess I will ask Janusz to comment on that.

/Joe

Hello dear friends,

Our initial plans were to release 2.1 beta with the AGPLv3 license.

After following the discussion regarding AGPLv3 vs. GPLv3 in the license thread on the Whish-List forum, and after getting loads of emails,
and after talking with people around us, we found that too many were afraid of the AGPLv3 license. We have therefore decided to release 2.1 beta with a GPLv3 license.

This was not an easy decision to make and the authors were not agreed either. We had to find a concensus and it was the GPLv3.

We are aware of that we are not satisfying all parties with this decision, but nevertheless the only difference between these two licenses
is the ASP (Saas) loophole for networked scripts. The license is subject to change in next release if we find better solution satisfactory for all
interested parties.

Many debaters in various forums feel that the AGPLv3 license is what the GPLv3 should have been. Maybe it will end here somewhere in the future.

So we are now releasing 2.1 beta again under the license GPLv3. As soon as the headers are ready this release (and utilities) will be available
for download.


The Development Team
FrontAccounting

4,533

(19 replies, posted in Setup)

The admin that created company no. 0 is the superadmin. Only he can create new companies (=page level 20) and should be logged into company no. 0.

/Joe

4,534

(2 replies, posted in Report Bugs here)

Thanks, I will ask Janusz to fix it.

/Joe

Something strange has happened. Could you please set the variable $go_debug in the file config.php to 1. This will catch more warnings or errors.

/Joe

Hello,
you should create a new supplier (not customer) when you want to make purchase orders (they are sent to your supplier).

/Joe

Please set the $go_debug flag in config.php to 1. This will catch up errors.

/Joe

4,538

(31 replies, posted in Wish List)

I understand Mr. kiang's concern. In the meantime we have got a permission from the author of OpenAccounting to also move to AGPLv3 with the leftover code from OA (about 15-20%). Remember that OA code was totally rewritten by the author of OA. So all in all we have the right to release under either GPLv3 or AGPLv3 and we are a bit confused. We want to do the best for the community and we want to re-release 2.1 beta again as soon as possible.
So please, give us some pros and cons regarding the license type beyond the discussions earlier, please smile

/Joe

4,539

(31 replies, posted in Wish List)

Dear all,
We have stopped the release 2.1.0 beta until this issue is solved. We might need to release under GPLv3.

/Joe

4,540

(31 replies, posted in Wish List)

Kiang, what is your point? Do you mean that we should stay with the GPLv3 and not use AGPLv3?

/Joe

4,541

(1 replies, posted in Installation)

Please make a search in the forums for this topic. There are several answers to your question.

/Joe

4,542

(1 replies, posted in Installation)

You should follow the instructions in the update.html file. Remember to backup your config_db.php file.
If you override and existing 2.0.X installation, login and go to Setup tab, Software Upgrade. Mark Install and Press Upgrade.
All your companies will be upgraded.

/Joe

4,543

(4 replies, posted in Translations)

Hello khadem,
I have informed you in a direct email how to attach the file. The ar_EG po file is UTF-8 and it works allright according to
Language-Team: www.infotechaccountants.com/forums admin@infotechaccountants.com Maybe you can exchange some information with them.

Best regards
Joe

4,544

(31 replies, posted in Wish List)

I just want to clarify things a bit. OpenAccounting was a fork of WebErp, but the code was totally rewritten by the authors of OA.
We have got a permission from the author of OpenAccounting to increase the license to GPL v.3. OA was discontinued back in 2005. And the GPL v3 and AGPL v.3 are compatible, so there should be no problems by using the license GNU AGPL v.3 (or later) for FA.

/Joe

Hello,
I'm not sure if I fully understand what you are trying to achieve by doing these operations. You said you have uploaded the GL balances. How?
If you have done this by a script directly through phpMyAdmin or so, then you have no sync with the bank accounts.
Normally you enter you opening balances (as admin) in the GL Journal entries the first time you start your company accounting. If you have entered an account that is also a bank account, the bank account balance will also be updated.
Therefore it is a good idea to first create your bank accounts.
The bank account reconciliation feature is implemented in release 2.1 Beta, that are shipping next week.
It is a little dangerous to export/import data outside FrontAccounting due to the relationship between the data tables in the database.

/Joe

4,546

(38 replies, posted in Modules Add-on's)

We have prepared an extension manager for release 2.1. Look at the sticky topic in this forum. We do not have the resources to develop these types of extensions ourselves, but concentrating on the accounting core. This is our main duty.
A couple of companies have been interesting in making a CRM extension to FA and at least one is almost ready. They are waiting for the release 2.1 Beta to ship next week.
I guess they will tell us more when time is ready.

/Joe

4,547

(1 replies, posted in Modules Add-on's)

Thanks, a new release has been uploaded.

/Joe

4,548

(4 replies, posted in Reporting)

Hello,
The document texts are taken from these two files, doctext.inc and doctext2.inc in /reporting/includes directory. The doctext.inc is for domestic documents (the text inside is gettextized), the doctext2.inc is for your foreign documents. Unfortunately we only have these two to choose among. Initially this foreign document is in English, but can be made to whatever language you want.

/Joe

Extensions to FrontAccounting

We have prepared for installation of Extensions. Like installed modules.
In the root directory there is a file, installed_extensions.php. This file contains an array over installed extensions, $installed_extensions.
There is an example array in the file.

app_file = the application to be put inside the /applications directory
name = array key name of the application
title = menu title
folder = directory where the extension resides. Use same structure inside this as the core extensions.

The Extension will be placed as the second last menu, before 'Setup'.

At present there is no automatic installation of the extensions. They will have to be done manuelly.

Bank Reconciliation

1. Select the account you want to reconcile.
2. Get your bank statement (from the bank)
3. The first time you reconcile you will need to enter a reconcile date and a start balance... Or 0 for the start balance if it is actually a new account.
4. Enter the end balance from the statement
5. Check entries that match the entries from your bank statement
6. If all entries match, 'Difference' should be 0. If it is, you are done and you have reconciled your account for the period.     If you have some transactions unchecked, they will wait for next bank statement to be reconciled. If you have some transactions on bank statement but absent in system, go to the Bank Payments/Deposits and enter missing transactions, then repeat step 5.
7. All checked items are recorded as reconciled in the bank_trans table and the last ending balance and reconciled date is recorded for that account in the bank_accounts table.
8. The next time you reconcile against a bank statement, the ending balance from the last reconciliation is automatically used as the starting balance for this reconciliation. You enter the ending balance for this reconciliation and repeat steps 5-7
9. If you want for some reason to find transactions reconciled with bank statement on given date select the document date with the selector. If you have a lot of bank statements entered you can skip the bank statement selector and enter date of bank statement in Reconcile Date directly. If there is no bank statement reconciled on given date the selector will display 'New'.