• joe
  • Administrator
  • Offline
  • Registered: 03/15/2007
  • Posts: 5,118

Topic: Release 2.4.19

Announcement

This is a 2.4.19 stable release with improved PHP 8 compatibility and some minor bugfixes.

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 and 8.4.13.

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.19.

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

  • PHP 8 bug converting string-float in number_format2. Fixed

  • Some troubles with installation on PHP 8. Fixed.

  • Attachments (more than one) do not follow the transaction after edition. Fixed.

  • Spacing adjustment for report Annual Expense Breakdown, rep705.php.

  • Fixed deprecation warning when user error is triggered on php >= 8.4.

  • Fixed deprecation warning logged when sysprefs object is created on php >= 8.2.

  • Mantis Issue 5753: The company logo cannot be set. $padding in TCPDF class must be inside class declaration.

Sales

  • New feature. Copy Delivery/Invoice from Customer Transactions Inquiry.

  • Mantis Issue 5738. Additional search options for sales order (delivery date, excluding auto) and quotation (valid
    until date) inquires.

  • Mantis Feature 5740: On prepaid Sales Orders, Have a "Receive Customer Payment" option on screen following order
    placement. Fixed.

  • Mantis Issue 5594: Combo box to Customer Credit Note and Supplier Credit Note references. Fixed.

Purchases

  • Mantis Issue 5745: Supplier Credit Note Issue: Stock Move Price Overstated Due to Included Tax.

Items and Inventory

  • Mantis Issue 5745: Supplier Credit Note Issue: Stock Move Price Overstated Due to Included Tax.

  • Mantis Issue 5748: Voiding location transfer results in an increased material cost. Fixed.

  • lp
  • Member
  • Offline
  • From: Thailand, Pran Buri
  • Registered: 04/12/2022
  • Posts: 23

Re: Release 2.4.19

Incorporation of XRPL Stable Coins

This update includes two XRPL payment links (USD & EUR) for use when printing sales invoices.

This allows instant payment of those invoices by (for e.g. RLUSD or USDC & EURQ) stable coins on the XRPL using the Xaman app (free).

Additional payment links could easily be added for any stable coin on the XRPL (e.g. AUDD, XSGD) or any other token for that matter. Reply to this message with any such requests.

Instructions for setup and use of the above payment links can be found at Wiki Bank Accounts and Wiki Sales.

lp's Website

3 Reply by lp

  • lp
  • Member
  • Offline
  • From: Thailand, Pran Buri
  • Registered: 04/12/2022
  • Posts: 23

Re: Release 2.4.19

THOUGHTS - Stablecoins in Front Accounting

Just thought I would make a few more comments about the inclusion of a XRPL payment link in sales invoices.

Personally I think this is a very significant development. This paves the way for FA users to get paid in stablecoins on the XRPL. Ultimately, I belive all accounting systems will eventually incorporate some form of blockchain stablecoins into their accounting systems. Whether it is XRPL or some other blockchain or more likely, a combination of blockchains, this will be the way accounting packages will move. And, may I say, FA has taken a pioneering step by embedding XRPL stablecoin payments directly into its sales invoicing system.

How I see this working in FA. Probably to start with, a FA entity could agree with a supplier or customer that payments will be made in RLUSD for goods and services, between the two. This allows for immediate and confirmed settlement of the invoice. If the receiver also has agreements with it's suppliers to use RLUSD, transfer can easily be made, anywhere in the world with next to zero cost. No dealing with banks.

If the FA entity needs to convert the RLUSD to their local currency, than the RLUSD can be converted to XRP through the XRPL DEX and RLUSD AMM (automated market maker) with guaranteed settlement. That XRP can be sold on the FA entity's local exchange for local fiat. The reverse could occur should the FA entity want RLUSD for payment of suppliers or employees. Overall the friction is very very low. Payment can occur online or locally anytime anywhere in the world.

Even just invoicing retail customers, it is not too difficult for them to setup Xaman on their phones, buy some XRP, send to their Xaman wallet, convert to RLUSD (or any other stablecoin) and start making payments of FA Sales invoices on their phone. 

Systems are presently being built that will also allow holdings of XRPL currencies to generate yeilds and returns through entities like Firelight on Flare blockchain. These options will expand. Thus excess XRPL currencies held in accounts, could be used to generate income through mechanisms on other blockchains.

Even though I have used RLUSD as an example, any stable coin on the XRPL could take it's place, such as the USDC stable coin issued by USDC on the XRPL. This could be swapped to USDC on the Uniswap chain for further use cases.

Overall, I think there is a signficant capacity and capability advancement with the inclusion with XRPL payment links on FA Sales invoices.

lp's Website