This is a 2.4.20 stable release with improved PHP 8 compatibility and a couple of usability and security bugfixes.
Therefore please consider urgent upgrade of your installation to this version, to keep your FA instances safe.
This is especially important in not fully trusted environments like publicly accessible installations (demos or other installations accessibly by not fully trusted users).

This release fixes some problems on php versions 8.2 to 8.4. The following versions has been tested: 8.0.0, 8.0.7, 8.0.12, 8.1.6, 8.2.0, 8.3.2, 8.4.13 and 8.5.5.

Please report any bugs/problems found via our Mantis Bugtracker at http://mantis.frontaccounting.com.
Download instructions

In Sourceforge FrontAccounting (http://sourceforge.net/projects/frontaccounting), select
Files -] FrontAccounting 2.4 -]2.4.20.

For Windows users select the zip file. For all other users select the tar.gz file.
Security

FrontAccounting should NOT be used via unsecure http protocol. If you really need this - change SECURE_ONLY constant in /includes/session.inc to false (comment in the file added). Unfortunately this option cannot be added in sysprefs/config.php because the settings are not available before session is started.
Common

● Multiply cleanups/security fixes in attachments editor.
● Database procedures in reports fixed to be compliant with codebase rules.
● Bug [0005737] Attachment editors: fixed input field width to underlying db field size.
● Attachments should be deleted when related document/entity is deleted. Fixes [0005757].
● Bug [0005750] Fixed hangs in barcode generation.
● Feature [0005712] Added fast date input edition with keyboard shortcuts (CtrlAlt-Arrows).
● Install/Activate Extensions: fixed deprecation warning on php ]=8.2.

Sales

● Feature [0005738] Customer/Supplier Allocation Inquiry: changed default sort order to ascending by Due Date.
● Feature [0005752] Customer Statements Report: added customer reference column.
● Feature [0005751] Customer Payments, Supplier Payments: added contractor reference for easier allocations.

Purchases

● $trans_no was missing in purch_order definition class. Fixed.
● Feature [0005738] Customer/Supplier Allocation Inquiry: changed default sort order to ascending by Due Date.
● Feature [0005751] Customer Payments, Supplier Payments: added contractor reference for easier allocations.

Bank and General Ledger

● Added two XRPL Payment Links. By Leslie Proud.
● Changed Bank Account Reconcile to sort descending.
● New exchange-rates organisation update. Can also fetch historical rated.
● Fixed safety issues in bank and audit reports.

I have progressed to the point where no errors are reported and the FA interface feeds back a line highlighted in green of the data that was processed.  However, when I check to see if a new SO record was created I don't find one.

I would expect that the feed back resulting from a successful upload would be more than the green highlighted information.

Also, the menu option to IMPORT TRANSACTIONS is perpetually greyed out, forcing me to go through the steps to save the access rights for the Administrator (me) each time I want to try to import.  Not sure if this is somehow related but even if it isn't it's very frustrating!

You guys are doing a great Job here. Thank you all.

I discovered that the Stock check sheet reports and the Inventory Item movement report end total are different. What can be the cause of it? Both figure are supposed to be same. KIndly help out.

Secondly, I want the name of the person who raised an Invoice to appear on each Invoice. How can I achieve that?

Thanks

Popsicles12

Pros of Unofficial APIs
* You bypass Meta’s per-message pricing entirely. Whether you are sending a transactional receipt or a promotional blast, there are zero official WhatsApp fees.
* No Approvals or Templates: You do not need to submit message templates to Meta for approval. You can send any content, at any time, without waiting for the official green light.
* No 24-Hour Service Window: Unlike the official API, which restricts free-form replies to a 24-hour window after a customer messages you, unofficial APIs allow you to initiate or reply to conversations whenever you want.
* Simultaneous Mobile App Use: Because these tools typically work by mimicking a "Linked Device" (WhatsApp Web), you can keep your primary phone number active on your physical smartphone while still automating messages through the API.
* Access to Native Features: Unofficial APIs often support features that the official Cloud API restricts, such as creating and managing WhatsApp Groups, updating Statuses, and interacting with Communities.
* Instant Setup: There is no lengthy Meta Business verification process. You can generate a QR code, scan it, and start testing your API integration in minutes.

Cons of Unofficial APIs
* High Risk of Permanent Bans: This is the biggest drawback. Unofficial APIs strictly violate Meta’s Terms of Service. If WhatsApp's automated systems detect bot-like behavior, non-human typing speeds, or spam patterns, your phone number can be permanently banned without warning.
* Zero Official Support: If your number gets banned or a message fails to deliver, you have no recourse or customer support from Meta.
* No Official "Green Tick": You cannot apply for the verified Official Business Account badge (the green checkmark), which can lower trust for customers interacting with your brand.

I am attaching the zip file here.
Install it in the latest version of FA.

1. Create Invoice.
2. Add Chat Id in the customer setup. It can be number with country code without + Or the Customers Group Id.
3. Open Customer INquiry page
4. Send WhatsApp.
5. It will check for company email (if not defined) for creating session
6. It will ask for scanning like whatsapp web
7. Now you can send invoice, payments, delivery notes

Let me know your feedback.

ON line 69 there is a function call

add_bank_transaction($entry->trans_type, $bank_account, $entry, $entry->tran_date, // FA built-in function
            false, false, false, $entry->reference, $entry->memo_, false);

But there is no bulit in function with this name.

bank_account_reconcile did NOT list the items, so I searched the GL Enquiry for transactions in case they were registered against wrong GLs.

gl_account_inquiry listed these items with the non zero values (the values I was expecting - but with extra lines)

gl_trans_view.php opened the items, displayed looking like a Journal Entry rather than the normal Payment/Deposit pop ups.

gl_journal.php?ModifyGL=yes opened into the Bank Deposit or Bank Payment editored, but all lines were of zero value, and the date was today's date.  Altering and saving resulted in the next screen saying transaction 0 was updated.

I am currently on 2.4.19 but was on 2.4.1 until a month or so ago, so this data corruption could be from a while ago.

PROPOSAL:
1) A report that cross references the various tables that store this data and reports mis-matches.
2) an editor to clean these up - either a "force" for void or similar zero everything.  I haven't worked through this yet as EOY tax reporting is less than a week away.

How I can import COA for Serbia. I have .csv file tor this.

Thks in advance,
Leka

At the same time when I translate frontacount to serbian I need click many times on menu to see translate.

Thks in advance

trial and error in attachments.php around line 37, replacing the following:

                        $type = ($row['filetype']) ? $row['filetype'] : 'application/octet-stream';
                        header("Content-type: ".$type);
                        header('Content-Length: '.$row['filesize']);
                        header("Content-Disposition: inline");
                        echo file_get_contents(company_path(). "/attachments/".$row['unique_name']);
                exit();

with

                      header( "location: " . $_SERVER['PHP_SELF'] . "/../" . company_path(). "/attachments/".$row['unique_name'] );
                exit();

works.  I don't see any security issue by passing a URL instead of a stream?

I've been working on a Chart of Accounts (COA) specifically for individual users in Pakistan, and I’d like to share it with the community. My goal is to see if we can eventually get this added to the "Install/Activate Chart of Accounts" list in the official setup.

I have hosted the project on GitHub to make it easier for others to contribute or review: https://github.com/xehroz/fa-pakistan-coa

The main challenge for users in Pakistan is that the FBR (Federal Board of Revenue) requires very specific reporting for the annual Wealth Statement and Income Tax Return. A standard business COA usually doesn't cut it for a freelancer who also has agricultural land or diverse investments.

I have designed this COA to solve those specific problems. It includes:

1. Tax Receivable Tracking: I have set up a 13xx series under Current Assets to track Withholding Taxes (WHT). This is a lifesaver for tracking tax deducted on University Fees, mobile bills, and bank transactions so they can be claimed back during filing.
2. Freelance & IT Export Logic: Dedicated accounts for IT revenue to help with PSEB (Pakistan Software Export Board) documentation.
3. Agricultural Support: Separate categories for Farm Land and Agri Income to keep Federal and Provincial tax data distinct.
4. Personal Wealth Assets: Proper slots for Household effects, PSX (Stocks), and Mutual Funds, which are required for the FBR Wealth Reconciliation.

IMPORTANT NOTE ON TESTING:
Please note that this is a first draft based on the required financial structure. It has not been fully field-tested in a live production environment yet. I am sharing it for community testing, evaluation, and feedback before it is considered for full incorporation into the main FrontAccounting package.

Implementation Notes:

* It’s best to enable USD for the Freelance Revenue and Foreign Currency bank accounts to handle remittances correctly.
* The WHT accounts are intentionally placed in Assets (not Expenses) so they don't get wiped out at year-end before the tax return is filed.

Feel free to check out the repo, submit pull requests, or leave feedback here. I would love to get some guidance from the devs on how to refine this into a standard installable module.

Thank You!

Shehroz Kaleem

I would like to submit a feature request for consideration in a future version of FrontAccounting. Currently, I am using Version 2.4.19 (Build 07.11.2025), and while the system successfully sends emails for user registration and password reset through SMTP, there is no built-in option to email General Ledger or other financial reports directly from the reporting screen.

My suggestion is to add an “Email Report” button within the report output screen for reports such as General Ledger, Trial Balance, Profit and Loss, Balance Sheet, and similar financial statements. After generating a report and viewing it in PDF format, the user should have the option to click an “Email Report” button. Upon clicking, the system should prompt the user with a simple form asking for the recipient’s email address (and optionally subject and message body). Once submitted, FrontAccounting should automatically attach the generated PDF report and send it using the already configured SMTP settings.

This would significantly improve workflow efficiency, especially for companies that regularly send financial reports to accountants, auditors, directors, or branch managers. Currently, the process requires manually generating the PDF, downloading it, and then composing an email outside the system. Integrating this feature directly into the reporting module would save time and reduce repetitive manual steps.

Since SMTP configuration is already part of FrontAccounting and works correctly for system-generated emails, it seems technically feasible to extend this functionality to financial reports. The system already generates PDFs, so attaching them to an email would be a natural extension of existing capabilities.

This feature would enhance usability and make FrontAccounting more competitive with other accounting systems that allow direct emailing of financial reports. It would also maintain consistency with the existing email functionality available for sales invoices and statements.

Thank you for considering this request. I believe many users would find this enhancement valuable in their day-to-day operations.

Kind regards,
Shehroz Kaleem

function NewPage() 
    {
        if ($this->pageNumber==0)
        {
            // check if there is pdf header template for this report
            // and set if it is found
            $tmpl_pdf = find_custom_file("/reporting/forms/".$this->headerTmpl.".pdf");
            if ($tmpl_pdf) {
                $this->tmplSize = $this->setSourceFile($tmpl_pdf);
            }
        }

        $this->pageNumber++;
        parent::newPage();

        if ($this->tmplSize) {
            $this->row = $this->pageHeight - $this->topMargin; // reset row
            $id = $this->importPage(min($this->pageNumber, $this->tmplSize));
            $this->useTemplate($id);
        }

        // include related php file if any
        $tmpl_php = find_custom_file("/reporting/forms/".$this->headerTmpl.".php");
        if ($tmpl_php) {
            include($tmpl_php);
        }

        if (method_exists($this, $this->headerTmpl))    // draw predefined page layout if any
            $this->{$this->headerTmpl}();
    }

I am not sure How to use this If I add some custom header page in my module. Any help, ideas, sample?