This was already so in FA v2.3.x which needs no correction. This error in the FA 2.4.x branch crept in sometime around 2015-03-25.

Since the FA project devs chose to merge the FA 2.4 with FA 2.3 master instead of making the FA 2.4 as the master and keeping the FA 2.3 master as just the FA 2.3 branch, such comparisons cannot be made in the official FA GitHub repo to pinpoint the commit.

Probably does not have the opening balances.....

The Balance Sheet Drilldown page does what you want.
Also the General Ledger Enquiry too provides the single ledger folio.

Attached is a sample screenshot and the tb summary file for your reference.

The name2 gets populated only from second contact for customer/branch onwards. The first contect for each customer/supplier is assumed to be the entity itself.

Alternatively output the necessary lines to a separate file and use it.

Edit by commenting out the inner loop echo statements in gl/inquiry/gl_trial_balance.php.

Checkout the lines 171 to 182 in reporting/rep112.php:

            $rep->TextCol(6, 7, _("Received / Sign"), - 2);
            $rep->NewLine();
            $rep->TextCol(0, 2, _("By Cash / Cheque* / Draft No."), - 2);
            $rep->TextCol(2, 4, "______________________________", - 2);
            $rep->TextCol(4, 5, _("Dated"), - 2);
            $rep->TextCol(5, 6, "__________________", - 2);
            $rep->NewLine(1);
            $rep->TextCol(0, 2, _("Drawn on Bank"), - 2);
            $rep->TextCol(2, 4, "______________________________", - 2);
            $rep->TextCol(4, 5, _("Branch"), - 2);
            $rep->TextCol(5, 6, "__________________", - 2);
            $rep->TextCol(6, 7, "__________________");

The "_()" are the gettext translatable strings that may be hardcoded if you want or change them in your language's .po file and compile into a .mo file and use.

Hope you are using the Git Master code that has a lot of fixes included.

There is a trial balance report that provides all the ledger balances.

1,461

(6 replies, posted in Report Bugs here)

A generic function encapsulating the error displayed and the checks may be in order. This may need to be done in a multitude of forms bloating the codebase otherwise.

@joe: There have been more than 50 commits since the last version release over 6 months ago - time for a another one with all translation strings as well?

1,462

(29 replies, posted in Installation)

Also check the contents of the installed_extensions.php in both the FA webroot and in the company folders.

Whilst it is not directly related, the fact is that dimensions and bank entries for Suppliers do not gel as of now in FA. This is possibly also related to another post where debit/credit note to suppliers needed a workaround. In FA 2.5, hopefully a few years from now (projecting from past experience) a more complete and predictable means would be in place. Payment allocation and possibly inventory tracking will be available only if supplier invoice gets created and the GRN is populated.

1,464

(3 replies, posted in Accounts Payable)

I am sure that whilst the thought did arise during the design, in most instances it is the last invoice that is chosen to be printed and hence the ease of choosing last invoice to last invoice was preferred. Furthermore, assuming that a large number of invoices existed, the dropdown would be tough to navigate. The only remnant of discord in such a sequence would be if there is a mixture of auto numbering and actual numbering interspersed.

1,465

(0 replies, posted in Installation)

Undocumented PHP 7.2 BC break:

https://bugs.php.net/bug.php?id=75682
http://php.net/manual/en/migration72.php
https://www.reddit.com/r/PHP/comments/82w04e/it_sucksphp72_count_break_bc/

https://frontaccounting.com/punbb/viewtopic.php?id=7680

1,467

(3 replies, posted in Accounts Payable)

Make sure the Ordering Sequence of the records is from the smaller / first to the bigger / last one.

IIT Mumbai, India's Video Tutorials on FrontAccounting are now available in English, Gujarati, Malayalam from Spoken Tutorial site.

1,469

(3 replies, posted in Translations)

@ngicon: Added Translator for Bengali

No need for extra field in any table.

Use the function get_customer_trans() in sales/includes/db/cust_trans_db.inc and use the trans_date field for the delivery date in your report. An example of the sql used in the said function is:

SET @TRANS_ID:=5;
SET @TRANS_TYPE=13; -- ST_CUSTDELIVERY

SELECT trans.*
      , ov_amount+ov_gst+ov_freight+ov_freight_tax+ov_discount AS Total
      , cust.name AS DebtorName
      , cust.address
      , cust.curr_code
      , cust.tax_id
      , trans.prep_amount>0 AS prepaid
      , com.memo_
      , shippers.shipper_name
      , sales_types.sales_type
      , sales_types.tax_included
      , branch.*
      , cust.discount
      , tax_groups.name AS tax_group_name
      , tax_groups.id AS tax_group_id 
FROM 1_debtor_trans trans
     LEFT JOIN 1_comments com ON trans.type=com.type AND trans.trans_no=com.id
     LEFT JOIN 1_shippers shippers ON shippers.shipper_id=trans.ship_via
     , 1_debtors_master cust
     , 1_sales_types sales_types
     , 1_cust_branch branch
     , 1_tax_groups tax_groups
WHERE trans.trans_no=@TRANS_ID
  AND trans.type=@TRANS_TYPE
  AND trans.debtor_no=cust.debtor_no
  AND sales_types.id = trans.tpe
  AND branch.branch_code = trans.branch_code
  AND branch.tax_group_id = tax_groups.id

This appears correct as it is a single account that has Gain and Loss in it and the Gain is a Credit in it.

@joe: any changes needed here?

Latest Hindi and Tamil inclusions for the install wizard are in the GitHub Master and the session file is at:
https://github.com/FrontAccountingERP/FA/blob/master/install/isession.inc
see lines 112 and 121.

Any updates to the install wizard will be in my repo's FA24Mods at https://github.com/apmuthu/frontac24/tree/master/FA24Mods/install

Further po translations are on Transifex.

1,473

(10 replies, posted in Setup)

Can also PM me. Try posting your requirements on the Job board.

1,474

(7 replies, posted in Setup)

The setting is in the config.php file.

1,475

(5 replies, posted in Report Bugs here)

Thanks for the feedback.