<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[FrontAccounting forum]]></title>
	<link rel="self" href="https://frontaccounting.com/punbb/extern.php?action=feed&amp;type=atom" />
	<updated>2026-11-02T14:06:43Z</updated>
	<generator>PunBB</generator>
	<id>https://frontaccounting.com/punbb/index.php</id>
		<entry>
			<title type="html"><![CDATA[Realized FX not posted when a PO prepayment is moved to the invoice]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10747&amp;action=new" />
			<summary type="html"><![CDATA[<p>Claude Assisted.</p><p>Version: FrontAccounting 2.4.19 and 2.4.20 (same code in both)</p><p>Summary<br />When an advance payment allocated to a Purchase Order is transferred to the<br />supplier invoice on invoice entry, the exchange difference between the payment<br />rate and the invoice rate is never posted. The supplier sub-ledger shows the<br />invoice fully settled, but GL Accounts Payable keeps the FX difference as a<br />residual balance. Normal allocations (Allocate Supplier Payments) post the FX<br />correctly; only the PO-prepayment path is affected.</p><p>Steps to reproduce (home currency CAD, supplier in USD)<br />1. Purchase Order Entry: USD supplier, date 11/01, 1,000.00 USD.<br />2. Supplier payment dated 11/01, 1,000.00 USD at rate 1.30; allocate it to the PO<br />&nbsp; &nbsp;(the PO is only offered for allocation before it is received).<br />3. Receive the PO on 11/02.<br />4. Enter the supplier invoice for that delivery dated 11/03 at rate 1.40.</p><p>Expected<br />The invoice GL shows an exchange variation pair for the advance:<br />&nbsp; Dr Accounts Payable 100.00 / Cr Exchange Variances 100.00<br />&nbsp; (1,000 x (1.40 - 1.30)), and GL AP for the supplier nets to zero.</p><p>Actual<br />No exchange variation is posted. The invoice is fully allocated in the<br />sub-ledger, but GL AP for the supplier is left at Cr 100.00.</p><p>Cause<br />add_supp_invoice() (purchasing/includes/db/invoice_db.inc) moves the PO<br />allocations with get_po_prepayments() -&gt; reallocate_payments() -&gt;<br />allocate_payment(). allocate_payment() only rewrites supp_allocations and the<br />alloc totals; it never calls exchange_variation(), unlike<br />allocation_cart::write().</p><p>Suggested fix<br />After reallocate_payments() in add_supp_invoice(), for supplier invoices, call<br />exchange_variation() for each allocation now pointing at the new invoice,<br />using the payment&#039;s own date (as allocation_cart::write() does):</p><p>&nbsp; if ($trans_type == ST_SUPPINVOICE &amp;&amp; empty($GLOBALS[&#039;no_exchange_variations&#039;])) {<br />&nbsp; &nbsp; &nbsp; $res = db_query(&quot;SELECT a.trans_type_from, a.trans_no_from, a.amt, t.tran_date<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; FROM &quot;.TB_PREF.&quot;supp_allocations a<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; JOIN &quot;.TB_PREF.&quot;supp_trans t ON t.type=a.trans_type_from<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;AND t.trans_no=a.trans_no_from AND t.supplier_id=a.person_id<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; WHERE a.trans_type_to=&quot;.ST_SUPPINVOICE.&quot; AND a.trans_no_to=&quot;.db_escape($invoice_id).&quot;<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; AND a.person_id=&quot;.db_escape($supp_trans-&gt;supplier_id));<br />&nbsp; &nbsp; &nbsp; while ($a = db_fetch($res))<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; if ($a[&#039;trans_type_from&#039;] != ST_JOURNAL)<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; exchange_variation($a[&#039;trans_type_from&#039;], $a[&#039;trans_no_from&#039;],<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ST_SUPPINVOICE, $invoice_id, sql2date($a[&#039;tran_date&#039;]),<br />&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; $a[&#039;amt&#039;], PT_SUPPLIER);<br />&nbsp; }</p><p>Note for invoice re-entry (edit): the invoice gets a new number and existing<br />allocations are moved the same way. FX previously booked on the payment side<br />(memo &quot;Supplier Invoice &lt;old no&gt;&quot;) is not removed by void_transaction(), so a<br />complete fix should remove the old pair&#039;s FX before re-posting. Related: the<br />allocation re-save duplicate FX issue below makes this worse.</p>]]></summary>
			<author>
				<name><![CDATA[andijani]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=20111</uri>
			</author>
			<updated>2026-11-02T14:06:43Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10747&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[re-saving an existing allocation posts its FX difference a second time]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10746&amp;action=new" />
			<summary type="html"><![CDATA[<p>Reproduction steps</p><p>Setup. Home currency CAD. Create a test supplier in USD.</p><p>Exchange rates. In Banking and General Ledger → Exchange Rates, set USD to 1.30 on 11/01/2026 and 1.40 on 11/02/2026.<br />Invoice. Enter a supplier invoice dated 11/01/2026 for 1,000.00 USD. This books AP at 1,300 CAD.<br />Payment. Enter a supplier payment dated 11/02/2026 for 1,000.00 USD and allocate the full amount to the invoice on the payment screen. The payment debits AP at 1,400 CAD.<br />Check. Open the payment’s GL view. You should see one FX pair of 100.00 between AP and Foreign Exchange Gain/(Loss), memo “Supplier Invoice N”. That pair is correct.<br />Trigger. Go to Purchases → Allocate Supplier Payments or Credit Notes and tick Show Settled Items. Click Allocate on the payment. It shows 1,000 already allocated. Click Process without changing anything.<br />Result. Open the payment’s GL view again. There are now two identical 100.00 FX pairs, and each extra Process adds another. Supplier Inquiry still shows everything settled, but GL AP for that supplier is now off by 100 for each extra pair.</p><p>Files modified:</p><p>includes/banking.inc — new remove_exchange_variation() helper<br />includes/ui/allocation_cart.inc — write() now removes the previous FX before re-posting</p>]]></summary>
			<author>
				<name><![CDATA[andijani]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=20111</uri>
			</author>
			<updated>2026-11-02T13:59:41Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10746&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Front Accounting Trendlines]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10745&amp;action=new" />
			<summary type="html"><![CDATA[<p>I am curious where FA is trending and did some research on AI.&nbsp; This is what I got back.&nbsp; I didn&#039;t &quot;write this&quot; nor did I ask for the remarks to be slanted.&nbsp; It&#039;s just what they said.&nbsp; It seems to be pretty much spot on.&nbsp; <br />------------------------------------</p><p>Dolibarr: Trending Strongly Up ????</p><p>Dolibarr is experiencing massive momentum and is behaving like a thriving, modern software project.<br />• Aggressive Code Development: A quick glance at the Dolibarr GitHub repository shows a highly hyperactive community. Developers submit multiple code updates and feature enhancements daily.<br />• Regular Major Releases: The project regularly pushes out major, polished version upgrades (scaling past Version 24+), introducing new security patches, UI improvements, and modern APIs.<br />• Growing Commercial App Store: The &quot;DoliStore&quot; (their plugin marketplace) expands every month because third-party software developers see a growing user base they can build paid extensions for.</p><p>FrontAccounting: Trending Down ????</p><p>FrontAccounting is essentially in maintenance mode. It is a stagnant project that is slowly fading into obsolescence.<br />• Minimal Development: The core FrontAccounting repository goes months at a time without seeing substantial new features or code changes. Most active development has been frozen for a long time.<br />• Security Patches Only: The tiny team left maintaining FrontAccounting primarily focuses on keeping the legacy code compatible with newer versions of PHP and patching critical security bugs, rather than adding new capabilities or modernizing the system.<br />• Shrinking Community: The user forums and third-party extension ecosystems have gone relatively quiet. Developers have largely abandoned it to build for modern platforms like ERPNext or Odoo.</p><p>The Takeaway</p><p>If you deploy FrontAccounting today, you are locking your company into software that looks, feels, and operates like it belongs in 2012.</p>]]></summary>
			<author>
				<name><![CDATA[mckenzie]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=46088</uri>
			</author>
			<updated>2026-10-29T15:19:00Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10745&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[GraphQL API and MCP Server for FrontAccounting]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10744&amp;action=new" />
			<summary type="html"><![CDATA[<p>I&#039;ve built two new modules for FrontAccounting:</p><p>1. A <a href="http://&quot;https://github.com/saygoweb/frontaccounting-module-graphql">GraphQL API</a><br />2. A &#039;Model Context Protocol&#039; <a href="https://github.com/saygoweb/frontaccounting-module-mcp">(MCP) Server</a> for use with AI tools such as Claude.ai and Claude code.</p><p>The GraphQL API incldues an OAuth 2.1 resource server so that users can perform dynamic client registration with tools like Claude code. For automatic documentation there&#039;s Voyager running on &#039;/modules/graphql/&#039;</p><p>The MCP server allows you to &quot;chat&quot; with your accounting system. e.g. &quot;Show me the outstanding invoices for Some Customer&quot;.</p><p>Version v1.0.0 is available on GitHub.</p>]]></summary>
			<author>
				<name><![CDATA[cambell]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=19447</uri>
			</author>
			<updated>2026-10-21T04:18:24Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10744&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Native bank statement import — feature contribution (PR #66)]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10743&amp;action=new" />
			<summary type="html"><![CDATA[<p>Hi everyone,</p><p>I&#039;ve been building a native bank statement import feature for FrontAccounting and<br />would love some feedback from the core team. It&#039;s submitted as a GitHub pull request<br />against the mirror repo, so the code is all there to review:</p><p>&nbsp; Pull request: [github.com/FrontAccountingERP/FA/pull/66]<br />&nbsp; Fork:&nbsp; &nbsp; &nbsp; &nbsp; [github.com/Xarrathh/FA&nbsp; (branch: bank-statement-import)]</p><p>What it does<br />- Imports a fixed-format CSV (Date, Description, Debit, Credit) straight into the<br />&nbsp; General Ledger, no pre-formatting with account codes.<br />- Auto-allocates recurring payees via rules you define (description -&gt; GL account,<br />&nbsp; with payment / deposit / either direction).<br />- Manual review step for unmatched rows.<br />- Optional VAT split per line (net + VAT to the company&#039;s VAT account).<br />- Mandatory &quot;I have made a backup&quot; confirmation before posting.<br />- Per-row error reporting instead of an opaque count.<br />- Rules can be exported/imported as CSV between companies.</p><p>It&#039;s a native core feature (Banking &amp; General Ledger menu), not an extension, and<br />sits alongside the existing import_transactions extension as a simpler alternative<br />for raw bank statements.</p><p>How to test<br />1. Log in as System Administrator.<br />2. Banking &amp; General Ledger -&gt; Bank Statement Import.<br />3. Upload a CSV with the header: Date, Description, Debit, Credit.<br />4. Parse, review, tick the backup confirmation, then Import.</p><p>Tested against 2.4.20. Happy to adjust anything the team wants changed.</p><p>Author: Pierre-Johan Goosen, with the assistance of Hermes Agent (AI).</p>]]></summary>
			<author>
				<name><![CDATA[pierregoosen]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=48884</uri>
			</author>
			<updated>2026-10-14T08:22:25Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10743&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Re:Tax (GST) payments or invoice basis (Alastair Robertson) 04/22/2013]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10742&amp;action=new" />
			<summary type="html"><![CDATA[<p>Firstly, thank you Alastair for the module. This is not a new post but for some reason I was unable to reply to the post above. I may have downloaded the module from the wrong place, but on a payments-basis GST return, the input tax on a paid supplier invoice was added to the output tax instead of being deducted from it.</p><p>For example, output GST of 4,434.79 and input GST of 375.52 was reported as a net payable of 4,810.31. The correct net payable is 4,059.27.</p><p>FrontAccounting stores a supplier payment with a negative ov_amount. The input-tax part of the report joined supp_trans on the payment (trans_type_from) and divided by that payment total. Dividing by a negative amount flipped the sign of the input GST, so collectible + payable added the input tax instead of subtracting it.</p><p>The fix is to divide by the supplier invoice total (trans_type_to). The invoice amount is positive, the existing -1 then makes the input GST a deduction, and the net payable is correct.</p><p>File: includes/tax_cash_db.inc</p><p>In tax_cash_sql(), change the supplier-allocation block from:</p><p>ttd.net_amount*sa.amt/round(ov_amount+ov_gst+ov_discount,6)*ex_rate net_input,<br />-1*ttd.amount*sa.amt/round(ov_amount+ov_gst+ov_discount,6)*ex_rate collectible,<br />...<br />INNER JOIN &quot;.TB_PREF.&quot;supp_trans st<br />&nbsp; &nbsp; ON st.type = sa.trans_type_from<br />&nbsp; &nbsp; AND st.trans_no = sa.trans_no_from</p><p>to:</p><p>ttd.net_amount*sa.amt/round(inv.ov_amount+inv.ov_gst+inv.ov_discount,6)*ex_rate net_input,<br />-1*ttd.amount*sa.amt/round(inv.ov_amount+inv.ov_gst+inv.ov_discount,6)*ex_rate collectible,<br />...<br />INNER JOIN &quot;.TB_PREF.&quot;supp_trans inv<br />&nbsp; &nbsp; ON inv.type = sa.trans_type_to<br />&nbsp; &nbsp; AND inv.trans_no = sa.trans_no_to</p><p>After the change, the input line shows as a negative amount and the total payable is the output GST less the input GST. The same figure is used by the Tax Details (Cash Basis) report.</p>]]></summary>
			<author>
				<name><![CDATA[DiggerNZ]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=48877</uri>
			</author>
			<updated>2026-10-12T10:09:05Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10742&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Session dropped behind Cloudflare (orange-cloud)]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10741&amp;action=new" />
			<summary type="html"><![CDATA[<p>FrontAccounting 2.4.20 on PHP 8.3, site published through Cloudflare with the proxy on (orange cloud).</p><p>Problem:<br />The login was dropped every few screens, and in particular each time a main-menu tab was opened (index.php?application=...). Logging in again worked, until the next tab.</p><p>SessionManager stores the client address on the session and, in preventHijacking(), treats a different address as a hijack and wipes the session. Behind Cloudflare, REMOTE_ADDR is a Cloudflare edge address, and that address changes from one request to the next. The visitor has not changed. The next menu click looks like a hijack, and the login is cleared.</p><p>Solution:<br />I enabled a solution that works for all users as it currently does, but also for servers who use Cloudflare Orange.</p><p>What I changed:<br />1. The address stored and compared is the visitor address Cloudflare sends (CF-Connecting-IP), and only when the request also has Cloudflare&#039;s CF-RAY header. Both headers are required so a client who simply sends CF-Connecting-IP is not trusted.<br />Users who are not coming through Cloudflare orange-cloud, or through another proxy that sets those two headers, are not affected. A LAN client, or a WAN client hitting the server directly, has no CF-RAY header, so clientAddress() returns REMOTE_ADDR and the check is the same as before.</p><p>2. I removed the 5% random call to regenerateSession() on every request. That path is not specific to Cloudflare. On PHP 8, regenerateSession() (session_regenerate_id, session_write_close, then session_start again) drops the logged-in session on the requests where it runs. A real address mismatch still calls regenerateSession().</p><p>Code:<br />------<br />Replaced, in sessionStart():<br />$_SESSION[&#039;IPaddress&#039;] = $_SERVER[&#039;REMOTE_ADDR&#039;];</p><p>with:<br />$_SESSION[&#039;IPaddress&#039;] = $this-&gt;clientAddress();</p><p>------</p><p>Removed, immediately after regenerateSession() in that same block:<br />// Give a 5% chance of the session id changing on any request<br />}<br />elseif (rand(1, 100) &lt;= 5)<br />{<br />&nbsp; &nbsp; $this-&gt;regenerateSession();<br />}</p><p>------</p><p>Replaced, in preventHijacking():<br />if ($_SESSION[&#039;IPaddress&#039;] != $_SERVER[&#039;REMOTE_ADDR&#039;])<br />&nbsp; &nbsp; return false;</p><p>with:</p><p>if ($_SESSION[&#039;IPaddress&#039;] != $this-&gt;clientAddress())<br />&nbsp; &nbsp; return false;</p><p>------</p><p>Added, immediately above preventHijacking():<br />// Visitor address. Cloudflare&#039;s own address changes between requests, so the<br />// session is kept against CF-Connecting-IP when that request came through Cloudflare.<br />function clientAddress()<br />{<br />&nbsp; &nbsp; if (!empty($_SERVER[&#039;HTTP_CF_CONNECTING_IP&#039;]) &amp;&amp; !empty($_SERVER[&#039;HTTP_CF_RAY&#039;]))<br />&nbsp; &nbsp; &nbsp; &nbsp; return $_SERVER[&#039;HTTP_CF_CONNECTING_IP&#039;];<br />&nbsp; &nbsp; return isset($_SERVER[&#039;REMOTE_ADDR&#039;]) ? $_SERVER[&#039;REMOTE_ADDR&#039;] : &#039;&#039;;<br />}</p><p>------<br />After this, one fresh login stays put across the menu tabs. I&#039;m happy for this to be adjusted if there is a preferred way to handle it in the next release.</p>]]></summary>
			<author>
				<name><![CDATA[DiggerNZ]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=48877</uri>
			</author>
			<updated>2026-09-27T20:50:37Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10741&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Cross-company session context issue with stale browser tabs]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10740&amp;action=new" />
			<summary type="html"><![CDATA[<p>I found a reproducible cross-company session/context problem in FrontAccounting 2.4.20 when browser tabs opened under different company contexts remain open.<br />Steps to reproduce<br />1. Open FrontAccounting in company A and open Banking and General Ledger → Journal Inquiry.<br />2. Company A uses - as the date separator, so the page contains dates such as 2025-01-01 and 2025-12-31.<br />3. Change the active FrontAccounting session to company B in another browser tab. Company B uses / as the date separator.<br />4. Return to the old Journal Inquiry tab which was generated while company A was active.<br />5. Press Search without reloading that page.<br />Actual result<br />The old page is still displayed as belonging to company A, but the request is processed using the preferences of the currently active company B session.<br />The following PHP warnings are produced:<br />Undefined array key 1 in /srv/frontaccounting/includes/date_functions.inc at line 398<br />Undefined array key 2 in /srv/frontaccounting/includes/date_functions.inc at line 398<br />A non-numeric value encountered in /srv/frontaccounting/includes/date_functions.inc at line 405</p><p>The call shown in the error output is, for example:<br />date2sql(&#039;2025-01-01&#039;)</p><p>date2sql() obtains the current separator using:<br />$sep = $SysPrefs-&gt;dateseps[user_date_sep()];</p><p>and for the YYYYMMDD date format eventually executes:<br />list($year, $month, $day) = explode($sep, $date_);</p><p>user_date_sep() in includes/current_user.inc gets the separator from the current session:<br />return isset($_SESSION[&quot;wa_current_user&quot;]-&gt;prefs-&gt;date_sep)<br />&nbsp; &nbsp; ? $_SESSION[&quot;wa_current_user&quot;]-&gt;prefs-&gt;date_sep()<br />&nbsp; &nbsp; : $SysPrefs-&gt;dflt_date_sep;</p><p>Therefore the stale company A page submits 2025-01-01, while the current session expects /. This effectively results in:<br />explode(&#039;/&#039;, &#039;2025-01-01&#039;)</p><p>which explains the warnings.<br />Expected result<br />A page generated in the context of company A should not silently be processed in the context of company B after the active session company has changed.<br />Ideally, each submitted form/request should contain enough information to verify that the company context in which the page was generated still matches the current session company. If it does not match, FrontAccounting should reject the request and ask the user to reload the page.<br />Why I think this is more important than the date parsing warning<br />The different date separators made the problem visible. If both companies had identical date settings, this particular request might apparently succeed and there would be no obvious indication that a page generated under company A was being processed using company B&#039;s current session context.<br />I have reproduced the context mismatch with Journal Inquiry. I have not tested submitting an accounting transaction from such a stale tab because I do not want to risk modifying the wrong company&#039;s data. Therefore I cannot say that cross-company writes are possible, but I think this should be checked because it could represent a data-integrity issue.<br />Version: FrontAccounting 2.4.20<br />I can provide a screenshot showing the complete PHP warnings and the stale Journal Inquiry page if useful.</p>]]></summary>
			<author>
				<name><![CDATA[peacecop kalmer:]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=44591</uri>
			</author>
			<updated>2026-09-26T22:29:45Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10740&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Looking for a Reliable Bookkeeper in Melbourne?]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10739&amp;action=new" />
			<summary type="html"><![CDATA[<p>Has anyone else been looking for a reliable bookkeeper in Melbourne for their small business? I came across AffordBooksTax, which offers bookkeeping and accounting support including bank reconciliation, BAS preparation, payroll, financial reporting and Xero services.</p><p>They seem to focus on practical support and transparent pricing, which can be helpful for small businesses trying to stay organised with their accounts and tax obligations.</p><p>If anyone is interested, you can contact AffordBooksTax on (03) 7071 1180, 0416 339 239, or 0402 124 067.</p>]]></summary>
			<author>
				<name><![CDATA[affordbookstax]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=48871</uri>
			</author>
			<updated>2026-09-23T08:15:21Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10739&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Looking for a Reliable Bookkeeper in Melbourne?]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10738&amp;action=new" />
			<summary type="html"><![CDATA[<p>Has anyone else been looking for a reliable bookkeeper in Melbourne for their small business? I came across AffordBooksTax, which offers bookkeeping and accounting support including bank reconciliation, BAS preparation, payroll, financial reporting and Xero services.</p><p>They seem to focus on practical support and transparent pricing, which can be helpful for small businesses trying to stay organised with their accounts and tax obligations.</p><p>If anyone is interested, you can contact AffordBooksTax on (03) 7071 1180, 0416 339 239, or 0402 124 067.</p>]]></summary>
			<author>
				<name><![CDATA[affordbookstax]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=48871</uri>
			</author>
			<updated>2026-09-23T08:10:56Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10738&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Problem with Transaction References not looking at prefix...]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10737&amp;action=new" />
			<summary type="html"><![CDATA[<p>it appears that the Transaction References do not look at the prefix when determining uniqueness.</p><p>I have 2 Supplier Transaction References set up.&nbsp; 1 with no prefix (generic payments) and 1 with a prefix (checking account and check number as a reference)</p><p>When entering a Supplier Payment, only the reference number is check for uniqueness, preventing references with the same number but different prefixes from being accepted.</p><p>It seems that the Supplier Payment form will return the Reference List (ref_list) index but not the prefix value.</p><p>Is there an easy way to allow duplicate reference numbers with different prefixes?<br />Thanks</p>]]></summary>
			<author>
				<name><![CDATA[brucek@pelhamhs.org]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=41547</uri>
			</author>
			<updated>2026-09-13T15:08:36Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10737&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Edit Invoice using posted Wiki]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10735&amp;action=new" />
			<summary type="html"><![CDATA[<p>I tried to to change an existing Invoice using the procedure posted in the Wiki and the results created parts of the new Invoice with redundant invoice numbers instead of creating unique new numbers.&nbsp; I could not find out why.&nbsp; This is the first time I&#039;ve tried to change an invoice with this level of software (2.4.19 Default Theme, Church Chart of Accounts). I&#039;m listing all the changes in the DB when I changed one invoice.&nbsp; If any one can help me or even verify that I should see different results and why, then I&#039;ll know I did something wrong.</p><p>Edit Invoice using posted Wiki <br />Results posted below.</p><p>0_audit_trail<br />(&#039;32595&#039;, &#039;30&#039;, &#039;6472&#039;, &#039;1&#039;, &#039;2026-05-06 07:17:23&#039;, NULL, &#039;8&#039;, &#039;2026-04-26&#039;, &#039;0&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />(&#039;32596&#039;, &#039;13&#039;, &#039;6473&#039;, &#039;1&#039;, &#039;2026-05-06 07:17:23&#039;, NULL, &#039;8&#039;, &#039;2026-04-26&#039;, &#039;0&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />(&#039;32597&#039;, &#039;10&#039;, &#039;6473&#039;, &#039;1&#039;, &#039;2026-05-06 07:17:23&#039;, NULL, &#039;8&#039;, &#039;2026-04-26&#039;, &#039;0&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />*********************************************************************************************<br />(&#039;32595&#039;, &#039;30&#039;, &#039;6472&#039;, &#039;1&#039;, &#039;2026-08-15 19:30:10&#039;, NULL, &#039;8&#039;, &#039;2026-04-26&#039;, NULL),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Changed)<br />(&#039;32596&#039;, &#039;13&#039;, &#039;6473&#039;, &#039;1&#039;, &#039;2026-08-15 19:28:04&#039;, NULL, &#039;8&#039;, &#039;2026-04-26&#039;, NULL),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Changed)<br />(&#039;32597&#039;, &#039;10&#039;, &#039;6473&#039;, &#039;1&#039;, &#039;2026-08-15 19:28:04&#039;, NULL, &#039;8&#039;, &#039;2026-04-26&#039;, NULL),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Changed)<br />*********************************************************************************************<br />(&#039;34130&#039;, &#039;13&#039;, &#039;6473&#039;, &#039;1&#039;, &#039;2026-08-15 19:28:04&#039;, &#039;Voided.&#039;, &#039;8&#039;, &#039;2026-04-26&#039;, &#039;0&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (New Addition)<br />(&#039;34131&#039;, &#039;10&#039;, &#039;6473&#039;, &#039;1&#039;, &#039;2026-08-15 19:28:04&#039;, &#039;Voided.\nedit&#039;, &#039;8&#039;, &#039;2026-08-15&#039;, &#039;0&#039;),&nbsp; &nbsp; &nbsp; &nbsp; (New Addition)<br />(&#039;34132&#039;, &#039;30&#039;, &#039;6472&#039;, &#039;1&#039;, &#039;2026-08-15 19:30:10&#039;, &#039;Updated.&#039;, &#039;8&#039;, &#039;2026-04-26&#039;, &#039;0&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (New Addition)<br />(&#039;34133&#039;, &#039;13&#039;, &#039;6772&#039;, &#039;1&#039;, &#039;2026-08-15 19:31:27&#039;, NULL, &#039;8&#039;, &#039;2026-04-26&#039;, &#039;0&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (New Addition)<br />(&#039;34134&#039;, &#039;10&#039;, &#039;6771&#039;, &#039;1&#039;, &#039;2026-08-15 19:32:22&#039;, NULL, &#039;8&#039;, &#039;2026-04-26&#039;, &#039;0&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (New Addition)<br />(&#039;34135&#039;, &#039;12&#039;, &#039;6769&#039;, &#039;1&#039;, &#039;2026-08-15 19:32:22&#039;, NULL, &#039;8&#039;, &#039;2026-04-26&#039;, &#039;0&#039;);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (New Addition)</p><br /><p>0_bank_trans<br />(&#039;12920&#039;, &#039;12&#039;, &#039;6473&#039;, &#039;4&#039;, &#039;CP260325&#039;, &#039;2026-04-26&#039;, &#039;165&#039;, &#039;0&#039;, &#039;0&#039;, &#039;2&#039;, &#039;217&#039;, NULL),&nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />**************************************************************************************<br />(&#039;13543&#039;, &#039;12&#039;, &#039;6769&#039;, &#039;4&#039;, &#039;CP260621&#039;, &#039;2026-04-26&#039;, &#039;165&#039;, &#039;0&#039;, &#039;0&#039;, &#039;2&#039;, &#039;217&#039;, NULL);&nbsp; &nbsp; &nbsp; &nbsp; (New Addition)</p><br /><p>0_comments<br />(&#039;13&#039;, &#039;6473&#039;, &#039;2026-04-26&#039;, &#039;260426 PayPal $4.93&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />(&#039;10&#039;, &#039;6473&#039;, &#039;2026-04-26&#039;, &#039;260426 PayPal $4.93&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />(&#039;12&#039;, &#039;6473&#039;, &#039;2026-04-26&#039;, &#039;POS_VBC #6473&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />**************************************************************************************<br />(&#039;13&#039;, &#039;6772&#039;, &#039;2026-04-26&#039;, &#039;260426 PayPal $4.93&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (New Addition)<br />(&#039;10&#039;, &#039;6771&#039;, &#039;2026-04-26&#039;, &#039;260426 PayPal $4.93&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (New Addition)<br />(&#039;12&#039;, &#039;6769&#039;, &#039;2026-04-26&#039;, &#039;POS_VBC #6771&#039;);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (New Addition)</p><br /><p>0_cust_allocations<br />(&#039;6485&#039;, &#039;217&#039;, &#039;165&#039;, &#039;2026-04-26&#039;, &#039;6473&#039;, &#039;12&#039;, &#039;6473&#039;, &#039;10&#039;),&nbsp; &nbsp; &nbsp; &nbsp; (Deleted)<br />**************************************************************************************<br />(&#039;6781&#039;, &#039;217&#039;, &#039;165&#039;, &#039;2026-04-26&#039;, &#039;6769&#039;, &#039;12&#039;, &#039;6771&#039;, &#039;10&#039;);&nbsp; &nbsp; &nbsp; &nbsp; (New Addition)</p><br /><p>0_debtor_trans<br />(&#039;6473&#039;, &#039;10&#039;, &#039;0&#039;, &#039;217&#039;, &#039;214&#039;, &#039;2026-04-26&#039;, &#039;2026-04-26&#039;, &#039;Dn260325&#039;, &#039;3&#039;, &#039;6472&#039;, &#039;165&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;165&#039;, &#039;0&#039;, &#039;1&#039;, &#039;1&#039;, &#039;7&#039;, &#039;0&#039;, &#039;4&#039;, &#039;0&#039;), (Original)<br />***************************************************************************************<br />(&#039;6473&#039;, &#039;10&#039;, &#039;2&#039;, &#039;217&#039;, &#039;214&#039;, &#039;2026-04-26&#039;, &#039;2026-04-26&#039;, &#039;Dn260325&#039;, &#039;3&#039;, &#039;6472&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;1&#039;, &#039;1&#039;, &#039;7&#039;, &#039;0&#039;, &#039;4&#039;, &#039;0&#039;),&nbsp; &nbsp;&nbsp; (Changed)<br />***************************************************************************************<br />(&#039;6771&#039;, &#039;10&#039;, &#039;0&#039;, &#039;217&#039;, &#039;214&#039;, &#039;2026-04-26&#039;, &#039;2026-04-26&#039;, &#039;Dn260623&#039;, &#039;3&#039;, &#039;6472&#039;, &#039;165&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;165&#039;, &#039;0&#039;, &#039;1&#039;, &#039;1&#039;, &#039;7&#039;, &#039;0&#039;, &#039;4&#039;, &#039;0&#039;), (New Addition)<br />***************************************************************************************<br />(&#039;6769&#039;, &#039;12&#039;, &#039;0&#039;, &#039;217&#039;, &#039;214&#039;, &#039;2026-04-26&#039;, &#039;0000-00-00&#039;, &#039;CP260621&#039;, &#039;0&#039;, &#039;0&#039;, &#039;165&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;165&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, NULL, &#039;0&#039;),&nbsp; &nbsp;&nbsp; (New Addition)<br />***************************************************************************************<br />(&#039;6772&#039;, &#039;13&#039;, &#039;1&#039;, &#039;217&#039;, &#039;214&#039;, &#039;2026-04-26&#039;, &#039;2026-04-26&#039;, &#039;DN260001&#039;, &#039;3&#039;, &#039;6472&#039;, &#039;165&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;1&#039;, &#039;1&#039;, &#039;7&#039;, &#039;0&#039;, &#039;4&#039;, &#039;0&#039;);&nbsp; &nbsp;&nbsp; (New Addition)</p><br /><p>0_debtor_trans_details<br />(&#039;16227&#039;, &#039;6473&#039;, &#039;13&#039;, &#039;101&#039;, &#039;Donation - Tithe&#039;, &#039;165&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;, &#039;0&#039;, &#039;1&#039;, &#039;8112&#039;),&nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />(&#039;16228&#039;, &#039;6473&#039;, &#039;10&#039;, &#039;101&#039;, &#039;Donation - Tithe&#039;, &#039;165&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;16227&#039;),<br />***************************************************************************************<br />(&#039;16227&#039;, &#039;6473&#039;, &#039;13&#039;, &#039;101&#039;, &#039;Donation - Tithe&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Changed)<br />(&#039;16228&#039;, &#039;6473&#039;, &#039;10&#039;, &#039;101&#039;, &#039;Donation - Tithe&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;),<br />***************************************************************************************<br />(&#039;17075&#039;, &#039;6772&#039;, &#039;13&#039;, &#039;101&#039;, &#039;Donation - Tithe&#039;, &#039;140&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;, &#039;0&#039;, &#039;1&#039;, &#039;8112&#039;),&nbsp; &nbsp; &nbsp; &nbsp; (New Addition)<br />(&#039;17076&#039;, &#039;6772&#039;, &#039;13&#039;, &#039;104&#039;, &#039;Donation - Building&#039;, &#039;25&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;, &#039;0&#039;, &#039;1&#039;, &#039;8536&#039;),<br />(&#039;17077&#039;, &#039;6771&#039;, &#039;10&#039;, &#039;101&#039;, &#039;Donation - Tithe&#039;, &#039;140&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;17075&#039;),<br />(&#039;17078&#039;, &#039;6771&#039;, &#039;10&#039;, &#039;104&#039;, &#039;Donation - Building&#039;, &#039;25&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;17076&#039;);</p><br /><p>0_gl_trans<br />(&#039;40813&#039;, &#039;10&#039;, &#039;6473&#039;, &#039;2026-04-26&#039;, &#039;4011&#039;, &#039;&#039;, &#039;-165&#039;, &#039;7&#039;, &#039;1&#039;, NULL, NULL),&nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />(&#039;40814&#039;, &#039;10&#039;, &#039;6473&#039;, &#039;2026-04-26&#039;, &#039;1200&#039;, &#039;&#039;, &#039;165&#039;, &#039;7&#039;, &#039;0&#039;, &#039;2&#039;, &#039;217&#039;),<br />***************************************************************************************<br />(&#039;40813&#039;, &#039;10&#039;, &#039;6473&#039;, &#039;2026-04-26&#039;, &#039;4011&#039;, &#039;&#039;, &#039;0&#039;, &#039;7&#039;, &#039;1&#039;, NULL, NULL),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Changed)<br />(&#039;40814&#039;, &#039;10&#039;, &#039;6473&#039;, &#039;2026-04-26&#039;, &#039;1200&#039;, &#039;&#039;, &#039;0&#039;, &#039;7&#039;, &#039;0&#039;, &#039;2&#039;, &#039;217&#039;),<br />***************************************************************************************<br />(&#039;42822&#039;, &#039;10&#039;, &#039;6771&#039;, &#039;2026-04-26&#039;, &#039;4011&#039;, &#039;&#039;, &#039;-140&#039;, &#039;7&#039;, &#039;1&#039;, NULL, NULL),&nbsp; &nbsp; &nbsp; &nbsp; (New Addition)<br />(&#039;42823&#039;, &#039;10&#039;, &#039;6771&#039;, &#039;2026-04-26&#039;, &#039;4011&#039;, &#039;&#039;, &#039;-25&#039;, &#039;7&#039;, &#039;4&#039;, NULL, NULL),<br />(&#039;42824&#039;, &#039;10&#039;, &#039;6771&#039;, &#039;2026-04-26&#039;, &#039;1200&#039;, &#039;&#039;, &#039;165&#039;, &#039;7&#039;, &#039;0&#039;, &#039;2&#039;, &#039;217&#039;),<br />(&#039;42825&#039;, &#039;12&#039;, &#039;6769&#039;, &#039;2026-04-26&#039;, &#039;1003&#039;, &#039;&#039;, &#039;165&#039;, &#039;7&#039;, &#039;0&#039;, NULL, NULL),<br />(&#039;42826&#039;, &#039;12&#039;, &#039;6769&#039;, &#039;2026-04-26&#039;, &#039;1200&#039;, &#039;&#039;, &#039;-165&#039;, &#039;7&#039;, &#039;0&#039;, &#039;2&#039;, &#039;217&#039;);</p><br /><p>0_refs<br />(&#039;6771&#039;, &#039;10&#039;, &#039;Dn260623&#039;),<br />**************************************************************************************<br />(&#039;6768&#039;, &#039;12&#039;, &#039;CP260620&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />(&#039;6769&#039;, &#039;12&#039;, &#039;CP260621&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (New Addition)<br />(&#039;6772&#039;, &#039;13&#039;, &#039;DN260001&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (New Addition)<br />(&#039;1&#039;, &#039;20&#039;, &#039;SI19001&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />**************************************************************************************<br />(&#039;6402&#039;, &#039;30&#039;, &#039;SO260002&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />(&#039;6472&#039;, &#039;30&#039;, &#039;SO260003&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (New Addition)<br />(&#039;6530&#039;, &#039;30&#039;, &#039;SO260003&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />(&#039;18&#039;, &#039;40&#039;, &#039;101&#039;),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Original)</p><br /><p>0_sales_order_details<br />(&#039;8112&#039;, &#039;6472&#039;, &#039;30&#039;, &#039;101&#039;, &#039;Donation - Tithe&#039;, &#039;1&#039;, &#039;165&#039;, &#039;1&#039;, &#039;0&#039;, &#039;0&#039;),&nbsp; &nbsp; (Original)<br />**************************************************************************************<br />(&#039;8112&#039;, &#039;6472&#039;, &#039;30&#039;, &#039;101&#039;, &#039;Donation - Tithe&#039;, &#039;1&#039;, &#039;140&#039;, &#039;1&#039;, &#039;0&#039;, &#039;0&#039;),&nbsp; &nbsp; (Changed)<br />**************************************************************************************<br />(&#039;8536&#039;, &#039;6472&#039;, &#039;30&#039;, &#039;104&#039;, &#039;Donation - Building&#039;, &#039;1&#039;, &#039;25&#039;, &#039;1&#039;, &#039;0&#039;, &#039;0&#039;);&nbsp; &nbsp; &nbsp; &nbsp; (New Addition)</p><br /><p>0_sales_orders<br />(&#039;6472&#039;, &#039;30&#039;, &#039;1&#039;, &#039;0&#039;, &#039;217&#039;, &#039;214&#039;, &#039;auto&#039;, &#039;&#039;, &#039;260426 PayPal $4.93&#039;, &#039;2026-04-26&#039;, &#039;3&#039;, &#039;1&#039;, &#039;1313 Garbage Can Lane\r\nBoredom, XZ 12345&#039;, &#039;&#039;, NULL, &#039;John Doe&#039;, &#039;0&#039;, &#039;DEF&#039;, &#039;2026-04-26&#039;, &#039;4&#039;, &#039;165&#039;, &#039;0&#039;, &#039;0&#039;),&nbsp; &nbsp; (Original)<br />***************************************************************************************<br />(&#039;6472&#039;, &#039;30&#039;, &#039;3&#039;, &#039;0&#039;, &#039;217&#039;, &#039;214&#039;, &#039;SO260003&#039;, &#039;&#039;, &#039;260426 PayPal $4.93&#039;, &#039;2026-04-26&#039;, &#039;3&#039;, &#039;1&#039;, &#039;3520 Leith Street\r\nBoredom, XZ 12345&#039;, &#039;&#039;, NULL, &#039;John Doe&#039;, &#039;0&#039;, &#039;DEF&#039;, &#039;2026-04-26&#039;, &#039;4&#039;, &#039;165&#039;, &#039;0&#039;, &#039;0&#039;),&nbsp; &nbsp; (Changed)</p><br /><p>0_stock_moves<br />(&#039;8112&#039;, &#039;6473&#039;, &#039;101&#039;, &#039;13&#039;, &#039;DEF&#039;, &#039;2026-04-26&#039;, &#039;165&#039;, &#039;auto&#039;, &#039;-1&#039;, &#039;0&#039;),&nbsp; &nbsp; &nbsp; &nbsp; (Deleted)<br />***************************************************************************************<br />(&#039;8536&#039;, &#039;6772&#039;, &#039;101&#039;, &#039;13&#039;, &#039;DEF&#039;, &#039;2026-04-26&#039;, &#039;140&#039;, &#039;DN260001&#039;, &#039;-1&#039;, &#039;0&#039;),&nbsp; &nbsp; (New Addition)<br />(&#039;8537&#039;, &#039;6772&#039;, &#039;104&#039;, &#039;13&#039;, &#039;DEF&#039;, &#039;2026-04-26&#039;, &#039;25&#039;, &#039;DN260001&#039;, &#039;-1&#039;, &#039;0&#039;);&nbsp; &nbsp; (New Addition)</p><br /><p>0_trans_tax_details<br />(&#039;12950&#039;, &#039;13&#039;, &#039;6473&#039;, &#039;2026-04-26&#039;, &#039;0&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;, &#039;165&#039;, &#039;0&#039;, &#039;auto&#039;, NULL),&nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />(&#039;12951&#039;, &#039;10&#039;, &#039;6473&#039;, &#039;2026-04-26&#039;, &#039;0&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;, &#039;165&#039;, &#039;0&#039;, &#039;Dn260325&#039;, &#039;0&#039;),&nbsp; &nbsp; &nbsp; &nbsp; (Original)<br />***************************************************************************************<br />(&#039;12950&#039;, &#039;13&#039;, &#039;6473&#039;, &#039;2026-04-26&#039;, &#039;0&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;auto&#039;, NULL),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; (Changed)<br />(&#039;12951&#039;, &#039;10&#039;, &#039;6473&#039;, &#039;2026-04-26&#039;, &#039;0&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;, &#039;0&#039;, &#039;0&#039;, &#039;Dn260325&#039;, &#039;0&#039;),&nbsp; &nbsp; &nbsp; &nbsp; (Changed)<br />***************************************************************************************<br />(&#039;13542&#039;, &#039;13&#039;, &#039;6772&#039;, &#039;2026-04-26&#039;, &#039;0&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;, &#039;165&#039;, &#039;0&#039;, &#039;DN260001&#039;, NULL),&nbsp; &nbsp; (New Addition)<br />(&#039;13543&#039;, &#039;10&#039;, &#039;6771&#039;, &#039;2026-04-26&#039;, &#039;0&#039;, &#039;0&#039;, &#039;1&#039;, &#039;0&#039;, &#039;165&#039;, &#039;0&#039;, &#039;Dn260623&#039;, &#039;0&#039;);&nbsp; &nbsp; &nbsp; &nbsp; (New Addition)</p><br /><p>0_voided<br />(&#039;10&#039;, &#039;6473&#039;, &#039;2026-08-15&#039;, &#039;edit&#039;),&nbsp; &nbsp; (New Addition)<br />**************************************************************************************<br />(&#039;13&#039;, &#039;6473&#039;, &#039;2026-04-26&#039;, &#039;&#039;),&nbsp; &nbsp; &nbsp; &nbsp; (New Addition)</p>]]></summary>
			<author>
				<name><![CDATA[JimmyC]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=42434</uri>
			</author>
			<updated>2026-08-16T00:30:37Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10735&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Upgrade path for huge leap 2.3.19 -> 2.4.20]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10734&amp;action=new" />
			<summary type="html"><![CDATA[<p>I am currently running FA 2.3.19 on Debian 7 (Wheezy) with PHP 5.4. I need to move FA to a new server running Debian 13 (Trixie) and PHP 8.4.</p><p>From what I have found, the start of the upgrade path should be:<br />FA 2.3.19 -&gt; FA 2.3.26 (old server)<br />FA 2.3.26 -&gt; 2.4.1 (old server, includes database conversions)<br />But what then?</p><p>I assume at some point FA 2.4.X does not run on PHP 5.4 anymore and the next version 2.4.Y does not run on PHP 8.4 yet. I have not been able to find the PHP requirements for each FA version.</p><p>I think I need to find 2 versions of FA which<br />- use the same database format<br />- the older version runs on PHP 5.4<br />- the newer version runs on PHP 8.4<br />So I would export the database on the older version, followed by an import on the newer version.</p><p>Does that even exist? Or is there a better way?</p>]]></summary>
			<author>
				<name><![CDATA[jlinkels]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=18827</uri>
			</author>
			<updated>2026-08-13T14:20:54Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10734&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Purchase Return Transaction]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10733&amp;action=new" />
			<summary type="html"><![CDATA[<p>I have a scenario involving a purchase return transaction; what are the steps for entering this transaction in FrontAccounting?</p><p>Note: I use the Direct Goods Receipt Entry (D) method, not the Purchase Order Entry (B) method.</p><p>Any assistance would be appreciated.</p>]]></summary>
			<author>
				<name><![CDATA[dodo.selarassolusindo]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=48868</uri>
			</author>
			<updated>2026-08-09T10:42:49Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10733&amp;action=new</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Can I move config_db file to a safer folder?]]></title>
			<link rel="alternate" href="https://frontaccounting.com/punbb/viewtopic.php?id=10732&amp;action=new" />
			<summary type="html"><![CDATA[<p>Hellosss, I just installed FA on a VPS which also runs a few other websites and databases. I notice that config_db.php - which has access info to MySQL - is located on the root folder of FA. Just to improve the security of this file, I&#039;d like to move to a safer folder on the server - and update FA script(s) which requires config_db.php.</p><p>Any thoughts?</p>]]></summary>
			<author>
				<name><![CDATA[hbx]]></name>
				<uri>https://frontaccounting.com/punbb/profile.php?id=48864</uri>
			</author>
			<updated>2026-07-17T21:29:54Z</updated>
			<id>https://frontaccounting.com/punbb/viewtopic.php?id=10732&amp;action=new</id>
		</entry>
</feed>
