1 Reply by alex1452

(16 replies, posted in Banking and General Ledger)

dear @apmuthu, if that is the case, why did you ask me earlier to first "check the Trial Balances for any discrepancy and whether Credit and Debit balances tally." after that to "Test with Debian 6 and MySQL 5.1 and PHP 5.3.3" and to "take assistance of php programmers to inspect variables in the code at the point of failure where the error comes out." and finally stating that "adding a user was a real problem practically all major users of FA would have complained by now."

I clearly stated that, " this happens with a fresh new installation of FrontAccounting". So the issue is a rights issue that I was not aware of that "has been the default since the very beginning over 15 years ago.": The System Administrator does not have the rights to close by default. A simple review of rights solved the issue.

I am writing this, because you seem to mass-answer questions on this forum. This mass-answering might be the reason, why your answers (at least in my case but potentially in other posts that I have seen in the forum) seem to miss the connection to the underlying issue. Maybe answer a little bit less and in instead focus more on moving towards the solution?

While I am extremely grateful for your huge commitment and your energy, I feel that at least in this case, your comments more obstructed the solution than helping to move toward the solution. Anybody reading this because she or he was looking for a solution to the problem might be better off with just the solution of @fburbano without all the tangents/distractions that you introduced.

Go to forum: Banking and General Ledger

2 Topic by alex1452

(3 replies, posted in Installation)

I have endless errors like this "4 Domain file "./lang/C/LC_MESSAGES/C.po" not found." in tmp/errors.log. Some of them in a variation "4 Domain file "../../lang/C/LC_MESSAGES/C.po" not found."
I have already tried to set the language on en_US in php.ini
intl.default_locale = en_US
but the error still exists. Does anybody know how to fix this. I have a standard installation of FA. The only language file available is lang/en_US/LC_MESSAGES/en_US.mo. How can I get FA to use the compiled PO file and change language settings to en_US?

Go to forum: Installation

3 Reply by alex1452

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

I followed exactly your instructions and updated the import extension with the content of the repository you provided. However, nothing has changed by using this repository.

Given our interactions on other issues in the past please allow me the question: How sure are you that changing the repository of the import module might be a step towards solving the issue? Or did you just send me on another "tangent" that ultimately only consumes time but provides no real value?

I still see the following options under "Banking and General Ledger" -> "Import Transactions".
"General Journal Processing"
"Deposit Processing"
"Payment Processing"
"Sales Order Processing"
"Direct Invoice Processing"

I tried ALL of them with the encl. CSV (this is a modified version of modules/import_transactions/templates/bank_en_GB.csv and identical to the screenshot you shared)

NONE of these produced ANY import. All off them showed a green process bar in the top middle of the screen that quickly disappeared after approx. 30 percent. I got no message.

How can I import bank statements into FrontAccounting? Specifically which is the right Menu item to import bank_en_GB.csv? Should I chose "General Journal Processing" to import bank_en_GB.csv?

---------------------

reference,date,memo,payment,receipt,accountcode,taxtype,dim1ref,dim2ref,person_type_id (supplier=3 customer=2),person_id,Branch_id
1,01/01/22,labour,100.5,,5410,0,,,,,
2,02/01/22,cash on account,,300,1065,0,,,2,1,1
QWE2,03/01/22,payment for rent,200.5,,5760,1,,,,,
4,04/01/22,purchased stock,,700,1540,0,,,,,
6,05/01/22,paid supplier,400,,2100,0,,,3,1,

Go to forum: Modules/Add-on's

4 Topic by alex1452

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

I have installed and activated the "Import Transactions" module. I would like to use this module to import bank statements. To test the import, I modified the provided sample:
modules/import_transactions/templates/bank_en_GB.csv
By updating the date and adjusting to the standard US COE.
reference,date,memo,payment,receipt,accountcode,taxtype,dim1ref,dim2ref,person_type_id (supplier=3 customer=2),person_id,Branch_id
1,01/01/22,labour,100.5,,5410,0,,,,,
2,02/01/22,cash on account,,300,1065,0,,,2,1,1
QWE2,03/01/22,payment for rent,200.5,,5760,1,,,,,
4,04/01/22,purchased stock,,700,1540,0,,,,,
6,05/01/22,paid supplier,400,,2100,0,,,3,1,

However, the import does not work. There is no menu for Bank statement import. There is only "General Journal Processing", "Deposit Processing", "Payment Processing", "Sales Order Processing" and "Direct Invoice Processing". When I use "General Journal Processing", I get a quick view of the "green process bar" but then nothing has happened afterwards.

Does anybody have experience in importing CSVs with Bank Statements? How to best do that?

Go to forum: Modules/Add-on's

5 Reply by alex1452

(16 replies, posted in Banking and General Ledger)

hi @fburbano, thank you so much for your help! That was the root cause. It turns out that in the default install, the system user has all rights except for "Closing GL Transaction". I did not expect that this was missing in the default install. So the issue is solved!

Go to forum: Banking and General Ledger

6 Reply by alex1452

(16 replies, posted in Banking and General Ledger)

Sorry, but your comments do not seem to lead anywhere. Did you actually read my post in full?

1. I never said that "adding a user was a real problem". Where in my post did you read that? Adding new users is absolutely no problem. I even offered to add you as a test user so that you can see for yourself. As clearly stated in my title the issue is with "Glosing GL Transactions".

2. Debian 6 is over 10 years old. It is considered "obsolete" by Debian and receives no security-fixes. Where does it say in the FrontAccounting system requirement that you have to use Debian 6?

3. PHP 5.3.3 is also 10 years old and out of service and has multiple severe security issues. The FrontAccounting Release notes for 2.4.18  state "A couple of php 8.2 and 8.3 problems has been fixed. This release should now be PHP 8 compatible. The following versions has been tested: 8.0.0, 8.0.7, 8.0.12, 8.1.6, 8.2.0 and 8.3.2.". Of course reading this now is kind of a strange statement because it states it SHOULD be compatible. What does that even mean? Is it or is it not compatible with PHP 8?

4. I posted clear and easy steps to replicate the issue. This takes less than 5 min. Did you actually follow these steps before commenting: "real problem practically all major users of FA would have complained by now."?

5. If you want to debug the issue I am very happy to support that! However, I would need clearer instructions than "investigation into it in the code given earlier by putting it watch points and logging the variables." What code have you given me earlier? What watch-points do you want me to set? Which variables should I look at? What is expected?

I would like to re-iterate as you can clearly see from my description, that the issue has ABSOLUTELY NOTHING to do with adding a user to the system. You seem to mass answer questions in this forum. Thank you for spending the time to try to help others! However, it seems that we did not get to the issue at hand. I feel this might be an actual bug because it happens on a completely fresh installation that I did not modify in any form.

I have seen that you have deleted my bug report on the issue. That is of course one way to deal with bugs... If FrontAccounting really only works with FULL functionality (incl. "Closing GL Transactions") on Debian 6 with PHP 5.6 may I respectfully suggest to clearly state that in the system requirements? Would have saved me (and potentially others) the time to look into this software.

Go to forum: Banking and General Ledger

7 Reply by alex1452

(16 replies, posted in Banking and General Ledger)

I am sorry, I lack the knowledge to do that. However, I suspect that this is a bug in FrontAccounting because this happens with a fresh new installation of FrontAccounting. Can you please review?

Steps to reproduce:
1. Extract frontaccounting-2.4.18.tar.gz
2. Create empty database and user in mariadb
3. Install FrontAccounting and create sample user and company using "US COA with sample data"
4. Login to Frontaccounting and go to "Banking and General Ledger"
5. Menu entry "Closing GL Transactions" is grey and cannot be used

System:
OS: Debian Bookworm
Webserver: Nginx 1.21.3
PHP: Version 8.2.27
Mariadb: Ver 15.1 Distrib 10.6.22-MariaDB

Since this test-install is on an internet facing server, I am happy to set-up a user account if you want to check for yourself.

Go to forum: Banking and General Ledger

8 Reply by alex1452

(16 replies, posted in Banking and General Ledger)

I have done that. Credit and Debit are fully balanced. I did not spot any discrepancies. What causes the function to be disabled?

Go to forum: Banking and General Ledger

9 Reply by alex1452

(16 replies, posted in Banking and General Ledger)

I have created 2024 and marked it as the active year. However the "Closing GL Transactions" is still grayed out.

Go to forum: Banking and General Ledger

10 Reply by alex1452

(16 replies, posted in Banking and General Ledger)

Thank you, I am aware of that. That is the reason why I put the opening balances in 2023. I want the correct balance for 2024.

My question was really HOW do I close 2023 given that the menu item "Closing GL Transactions" is gray and not clickable. WHY is it gray and what can I do to make it "clickable"?

Go to forum: Banking and General Ledger

11 Topic by alex1452

(16 replies, posted in Banking and General Ledger)

Hi Forum,

I am trying to switch from another accounting software to FrontAccounting. I have done 2023 in the other accounting software and would like to do 2024 in FrontAccounting.

In order to have the right starting balance in FrontAccounting, have created a new GL 3999 Opening Balance Equity and created journal entries for 12/31/2023 to book all positions of the Balance Sheet from the other accounting software. The Profit of 2023 is booked to 3590 "retained earnings". I have reconciled all bank accounts simply by using 0 as starting balance and the actual YE balance as ending balance. I am "System Adminstrator" working on a fresh installation of 2.4.18 with the default US-COA.

I would like to close now 2023 to start posting actual transactions for 2024. However the menu item "Closing GL Transactions" is grayed out. None of the journal entries that I have created for 12/31/2023 is closed. Why is "Closing GL Transactions" grey and what do I have to do to close the "dummy" 2023 to start working on 2024?

Thank you for your help!
alex

Go to forum: Banking and General Ledger