News

Readysell “Naas” October 2021 update

We’re pleased to announce that Readysell 8.59 (codename “Naas”) is rolling out progressively to all of our Readysell 8 customers. This release is focused on implementing some important service enhancements, improvements to the framework of the whole application, and actioning bugs that have been reported over the last period.

New feature Development

16009 – (applicable to particular customers)Added a select all option when updating the price for multiple style products. Relates to ticket 28161

16009 – Added new return field for Get Products API. “DescriptionText” returns the products description without the html

16009 – Added new query for Get Contracts API. You can return all contracts that include a specific product id or card id

16084 – Added the capability to be able to auto increases meters that have a type of service. Relates to ticket 25091. See the following documentation for how to set this up link to relevant documentation

16197 – Add a new checkbox “One Invoice per Email by Email Batch” in customer settings in cards to optionally send batch emails of invoices as one PDF file instead of one PDF per sale invoice

16198 – Added combined option to turn the ship button into “Ship And Pick” button for sale orders. To enable you need to turn on the ORDER-SHIP-PICK under the Sales system type

16199 – (applicable to particular customers)Import carrier from web orders. If the web order flows into Readysell with a carrier that carrier will be inserted into its sale order. Relates to ticket 28190

16203 – Added “Round to Nearest dropdown” to product import rules. Allows for the product’s Price Sell to be rounded to the nearest five cents, ten cents or whole dollar.

16221 – Modified Machine Last Communication Date. It is now a persistent field that be set outside of a meter count and get be used in the filter editor. link to relevant documentation

Bug Fixed:

15570 – Fixed an issue where Email Variables for email batches were pulling from the email batch header instead of the email batch line. This fix will allow for the Card ID and Transaction Numbers to be parsed per email. Relates to tickets; 28289, 28477, 28494 link to relevant documentation

16195 – Removed the “Warranty Claim” button for stores that do not have the service module

16207 – Added two system types under Product, “ALLOW-RS3-ARCHIVE-PRODUCT-SUPPLIERS”. If true, the RS3 feed can archive product supplier when the supplier has 0 quantity on hand. And “USE-RS3-VARIANCE-CALCULATION” will always update products cost and unit of measure unless set to true as this enables the legacy calculation for determining whether to update the supplier cost and unit of measure for products. Relates to ticket 29411

16214 – (applicable to particular customers)Reworked XchangeIT to use barcodes instead of serial numbers for DD3, SL3, RTF3 files

16220 – Fixed an issue where a store’s Product ID was sending instead of Supplier Product ID For Dynamic EDI Ordering

16239 – Fixed an issue where Manual Qty Scan was disabled for Shipments with a status of InProgress

16242 – Updated Calculate Route within the Delivery module (Previously was not working)

16252 – Fixed an issue where creating new versions of a contract would remove the previous version of the contract from existing sale orders

To check what version of Readysell you are currently running, click file up the top left of any screen and then click about.

And the following window will appear, where you can compare your version number to upcoming release number above.

Readysell “Macleay” September 2021 update

We’re pleased to announce that Readysell 8.59 (codename “Macleay”) is rolling out progressively to all of our Readysell 8 customers. This release is focused on implementing some important service enhancements, improvements to the framework of the whole application, and actioning bugs that have been reported over the last period.

New feature Development

16173 – Added the ability to specify a tender in the sale shipment API

16201 – Web Order API can now generate eGift Voucher numbers and shipment/invoice

16205 – Added user setting to return only new products or no products to the mobile app

16227 – (applicable to particular customers) – Added Integrity check for Gift Vouchers that are retrieved from POS manually

16238 – (applicable to particular customers) – Updated Integration for upcoming Order XML Changes

Bug Fixed:

15728 – Reworded a validation message when trying to close a service order and the period is already closed

15911 – Fixed an issue whereToner pools/Toner tracking was not getting triggered if the supply level equalled zero

15927 – Fixed missing toner levels for print Audit

16081 – Removed the leading zeros from Ingram micro supplier product ID from RS3 feed

16189 – Fixed an issue when creating invoice from CreateShipment API resulting in the invoice having the wrong transaction type

16192 – (applicable to particular customers) – Fixed an issue where integrated product upload wouldn’t finish. This has been moved into its own task

16216 – Fixed an issue where ESD CustomerAccountAddresses returned isPostal value instead of isPrimary value

16219 – Fixed an issue where the same two tasks could run in parallel

16239 – Resolved an issue where manual Qty Scan was disabled for Shipments with a status of InProgress

*Note: the referenced POS is a standalone POS, only relevant for a particular set of customers. These features are not relevant to the Readysell POS functionality. 

Readysell “Lachlan” August 2021 update

We’re pleased to announce that Readysell 8.59 (codename “Lachlan”) is rolling out progressively to all of our Readysell 8 customers. This release is focused on implementing some important service enhancements, improvements to the framework of the whole application, and actioning bugs that have been reported over the last period.

New feature Development

16088 – Kits Overhaul – Kit components can be in more than one location, components are added as their own line allowing for back-ordering and purchasing, reworked the existing “extract kit component” button to “unlink kit components” delinking the kit components so become a non-kit component line

16177 – Pre-populate the date and invoice number with the current date-time reference number from DDO/DD2 file when completing a purchase receipt

16135 – Added multiple product category support for some customers. Product categories can have multiple category ids allowing for multi-store sites.

16048 – Purchase receipt – Can now select any file extension for DDO/DD2 import module

16051 – Update existing purchase receipt lines if the same product is found when Importing from DDO/DD2 

16050 – Added support for purchase Order import from DD2 

16049 – Purchase Receipt will now create new products with product ID “SPECIAL” if Create-New-Product is false when import from DDO/DD2

Bug Fixed:

16115 – (applicable to particular customers) – Transaction Queue Failed on stock qty adjustment due to missing shift from Standalone Readysell POS

16187 – (applicable to particular customers) – Transaction Queue Failed when a web order was sent back from standalone Readysell POS to Readysell

16152 – Fixed transaction queue fail caused by purchase receipt. Fail was due to product having been allocated to sale shipment

16113 – Fixed a transaction queue Fail for email batches that had a missing image in the email body 

16148 – Fixed an issue for sale shipment API where auto invoicing was turning sale invoice into SALOIN and then not sending email as part of the end of day email batch

16182 – Product Price/Cost adjustment factor resulted negative if using divide method

15613 – Fixed issue affecting some customers where business intelligence was receiving full data instead of delta for contracts

16114 – (applicable to particular customers) – Fixed a transaction queue fail due to the tender from Standalone Readysell POS not rounding correctly

16186 – (applicable to particular customers) – Fixed an issue where a web order could fail to send to Standalone Readysell POS if the order had an empty note 

16175 –  Fixed handling of DDO or DD2 imports when a Purchase Receipt contained a Qty of zero

Readysell operating arrangements for Public holiday

Dear Readysell customers,

On the 4th of October, Queensland, the Australian Capital Territory, New South Wales, and South Australia will be observing the Labour Day public holiday. As the Readysell head office is located in New South Wales, the office will be closed, but our normal ‘after-hours’ support is available for critical issues. We will have a staff member on call to respond to any critical issues that arise.

Readysell “Kalgan” July 2021 update

We’re pleased to announce that Readysell 8.59 (codename “Kalgan”) is rolling out progressively to all of our Readysell 8 customers. This release is focused on implementing some important service enhancements, improvements to the framework of the whole application, and actioning bugs that have been reported over the last period.

New feature Development

15673 – Integration with XchangeIT including DD3 support

16130 – Added support for Canon UGW2

16149 – Added the Sending of consignment labels to the Print Queue as an alternative setting under workstation, report settings.

16159 – Added a new price level called Cost. Is the same as the existing s1-8 price levels

15890 – Mobile App Android – New feature to capture photo (instead of signature) for delivery

*Note: Device Android 10+ updates with Google Play, otherwise visit https://readysell.com.au/product/app/

Bug Fixed:

16127 – Created validation for Product Association and Product Price Level while making changes to a product

16134 – Fixed issue when resetting to default price in the Product file

16136 – Fixed issue when the product was uploading to the web. If the calculated price is changed, the product now uploads as expected

16146 – Update quote with API from web to refresh Last modified Date and Audit Trail. Added handling for the API when Manual cost exists and qty is zero. Can now customise the number of the student text fields in the web quote

16147 – Fixed a bug where a product could be checked for display on eBay without a barcode

16159 – Product Import ONET with more than 6 length characters of supplier code

Readysell “Jardine” June 2021 update

We’re pleased to announce that Readysell 8.59 (codename “Jardine”) is rolling out progressively to all of our Readysell 8 customers. This release is focused on implementing some important service enhancements, improvements to the framework of the whole application, and actioning bugs that have been reported over the last period.

New feature Development

15767 – Developed Integration with new IFS framework

15724 (applicable to particular customers) – Developed standalone Readysell POS integration with new IFS framework

16105 – Modified functionality so Readysell will ignore and/or not update unit price/cost when doing an import – if the fields ‘Price Import Adjustment Factor’ on Product and ‘Cost Import Adjustment Factor’ on Product Supplier have value

16108 – Developed integration with a new FTP server to upload BI files for some customers.

16102 – Modified functionality to use ‘system date’ not ‘transaction date’ on-contract price for sales. We have created a new system type: ‘RETAIN-CONTRACT-STARTDATE’ under CONTRACT where, if set to true, the system will retain the existing start date of a contract when creating a new version of an existing contract

15916 – Increased service order repair description.  Increased maximum character count from 2048 characters to 4,294,967,295 characters.

Bug Fixed:

15895 – Post Delivery overriding the existing delivery date and time. This has been changed to only override with current date and time if a delivery date time is missing.

16092 – Purchase Run that generates indent product, now uses the same logic as back-order calculation – instead of using min/max or average calculations.

16109 – Updated ESD to try and fetch images from the web before trying to fetch from local storage. This now matches API logic.

16111 – Fixed a bug where – if a machine had a product type of either ‘comment’ or ‘MeterChargeComment’ – the machine would fail a validation check and stop the further creation of shipment lines.

16118 – Fixed an issue where monthly sales runs were not running as scheduled.

*Note: the referenced POS is a standalone POS – only relevant for a particular set of customers. These features are not relevant to the Readysell POS functionality.

KeyPay EOFY Processing and STP Finalisation

With the End of Financial Year fast approaching, we would like to make all of our clients using Keypay aware of the latest STP Finalisation webinar released by Keypay.

The webinar can be accessed at the attached link https://www.youtube.com/watch?v=jiZrU6wmzf8.  It goes for approximately 38 minutes and covers:

•             Tips on reconciling data to ensure everything is correct before lodging finalisation event

•             Using the EOFY wizard to report a finalisation event

•             How to report FBT amounts via STP

•             ATO deadlines for reporting your End of Year finalisation

•             Difference between Payment Summaries vs Income

•             Statements and what it means to your employees

•             How to report an amended finalisation event to correct originally reported data to the ATO

The webinar will give you all of the information you need to get ready for July 1 with KeyPay, but KeyPay has also compiled a list of questions asked during the webinar and have provided answers so everyone can enjoy. You can access them via the following link:  https://support.yourpayroll.com.au/hc/en-au/articles/4401838510095-End-of-Financial-Year-2020-2021-Frequently-asked-questions-when-processing-via-STPutm_source=webinar_au_customer&utm_medium=email&utm_campaign=webinar_au_eofy_stp_webinar_20210623

Other useful resources include:

End of Financial Year Guide 2020/21 – Reporting for STP:  https://support.yourpayroll.com.au/hc/en-au/articles/360004806815?utm_source=webinar_au_customer&utm_medium=email&utm_campaign=webinar_au_eofy_stp_webinar_20210623

This article will guide you through year end reporting using STP.

Readysell “Isaac” May 2021 update

We’re pleased to announce that Readysell 8.59 (codename “Isaac”) is rolling out progressively to all of our Readysell 8 customers. This release is focused on implementing some important service enhancements, improvements to the framework of the whole application, and actioning bugs that have been reported over the last period.

New feature Development

16038 – Users can now generate, print and scan barcodes from cards to be used in sale transactions. This label can be downloaded from Readysell Store. “Card Label”

15570 – Added the ability to use variables in email batch template subject line.

16053 – Readysell Import/Export now allows users to import service call activities into an existing service call.

15838 – oData v3 is now importing new fields (Details, Specification, UNSPSC) to the price book and product details.

15970 – If a card’s default site is changed, Readysell now sends the previous site as ‘Inactive’ and the new site as ‘Active’ to external core systems (where implemented) through the ‘Business Intelligence’ task.

16044 – Email batch for Sale Quotes, now includes a URL link to web for customer to modify product quantity in quote

15562 – Added new fields ‘Price Import Adjustment Factor’ on Product, and ‘Cost Import Adjustment Factor’ on Product Supplier, for multiply or divide Sell Price/Cost when doing an import from Group or Suppliers.

Bug Fixed:

15923 – Barcodes are now being added to products when importing from a DDO or DD2 file.

16035 – We have fixed an issue where some product images were not getting fetched from the web.

16058 – While creating a service order – if a machine and technician were assigned – an issue resulted where the event would appear on the schedule without the machine’s location. This has been resolved, and the machine location now appears on the schedule.

16074 – We have Increased the maximum allowed character length for the following fields in ‘Bank Reconciliation’: ‘Payment reference’; ‘Matched reference’, and ‘Search reference’. We have also increased the maximum allowed length for the column named ’Default Order Unit Code’ for product suppliers in the price book

16060 – An issue was identified where POS was missing the Customer on an Order after it was converted from a Sale. This issue now has been fixed.

16014 – A one-cent discrepancy was identified between a web order and a Readysell order after it was imported. This issue now has been fixed. Readysell will create another sale order line called ‘Rounding’.

KeyPay – Important changes to the definition of ‘Active Employee’ for billing purposes – please read

Attention all KeyPay users: Important changes to the definition of ‘Active Employee’ for billing purposes – please read

This alert is to inform you of some planned changes that may affect how you are charged for use of the KeyPay platform in the near future.  

KeyPay’s current billing model defines an ‘active employee’ as an employee who has been included in a finalised pay run at least once within our billing cycle. Unfortunately, this has led to a small number of users significantly exploiting a loophole to avoid paying for use of the payroll platform.

This problem has prompted KeyPay to change their definition of an ‘active employee’:

Please note that the previous KeyPay correspondence was missing the action regarding ‘approved timesheet’; we apologise for any confusion this may have caused

An employee will be considered ‘active’ when at least one of the following actions have been completed for that employee during the billing cycle:

  • Included in a finalised pay run
  • Has had an approved leave request                        
  • Has had an approved expense request
  • Has had a published roster shift  
  • Has had an approved timesheet

Please note that if a user unlocks the pay run in any given month, any of the actions above are still counted towards an ‘active employee’.

This change will come into effect from the 1st of July 2021. You will see the change (if there is one) on the invoice you receive on the 1st of August 2021.

Please notify the other areas of your business that need to be made aware of this change. Feel free to reach out to me if you have any questions or concerns about this.

Readysell “Hastings” April 2021 update

We’re pleased to announce that Readysell 8.59 (codename “Hastings”) is rolling out progressively to all of our Readysell 8 customers. This release is focused on implementing some important service enhancements, improvements to the framework of the whole application, and actioning bugs that have been reported over the last period.

New feature Development

15997 – We’ve added a new field “Number of students” Student in Sales Quotes. Once a sales quote is converted into a sales order, the Product Sale Quantity field will be multiplied by the Number of Students.

15995 – Education project: New executable form report: F-147 Sale Quote EDU Report (By Supplier)

15994 – Education project: New Standard note button on sale order and quote

15987 (applicable to particular customers) – POS Gift voucher: when a user opens a completed order, POS will pop up warning if any gift voucher sales without voucher number and user can click the warning to send the voucher number to Readysell support team.

16046 – Users can now generate, print, and scan barcodes from a product’s Oid – to be used in the same way as existing product labels

Bug Fixed:

15759 – We fixed an issue where the product feed from Ingram Micro was too large and needed to be broken into smaller feeds.

15760 –  RS3 Product Import was not updating the quantity on hand or cost price for product suppliers in the Pricebook and product file. This issue has been fixed.

16072 – RS3 Product Import was overriding the cost price for primary suppliers in the Pricebook. This has been fixed.

16047 – Clicking the Extract banking button multiple times on the Bank Reconciliation will result in duplicate bank reconciliation lines to appear. This issue has been fixed

15988 (applicable to particular customers) – An issue was identified where not every web order from POS was being synced with the orders at head office.

*Note: the referenced POS is a standalone POS, only relevant for a particular set of customers. These features are not relevant to the Readysell POS functionality.