Sage 200 v2011 Issues Fixed Service Pack 7

Transcription

1 Sage 200 v2011 Issues Fixed Service Pack 7 09/02/2015 Sage (UK) Limited, 2015 Page 1 of 37

2 10/02/2015 Sage (UK) Limited, 2015 Page 2 of 37

3 Table of Contents Early Settlement Discount Legislation Update... 4 Current functionality... 4 New VAT rules for early settlement discount and UK VAT after 1 st April How to record sales transactions with settlement discounts... 5 How to record purchase transactions with settlement discount... 9 Other things to consider VAT 3 Legislation Update (ITS 5396) SEPA Legislation Update Live Issues fixed /02/2015 Sage (UK) Limited, 2015 Page 3 of 37

4 Early Settlement Discount Legislation Update This service pack contains an update for the changes to the VAT legislation regarding invoices with settlement discount. Installing this service pack will allow you to be compliant with the legislation changes and continue to process and print invoices with settlement discount from Sage 200. A fuller solution for early settlement discount has been included with Sage We recommend that customers using early settlement discount upgrade to Current functionality In the UK, when an invoice contains settlement discount, VAT is only charged on the discounted invoice amount. The VAT is always discounted even if the invoice is not paid early enough to qualify for the discount. In Sage 200, when an invoice contains settlement discount, the VAT amount is reduced by the settlement discount percentage by default. New VAT rules for early settlement discount and UK VAT after 1 st April 2015 The HMRC has introduced new rules around how VAT is calculated for settlement discounts. These rules come into effect on 1st April Under the new rules, the VAT on the invoice is only discounted when it is paid within the settlement discount period. VAT must be calculated and shown on the invoice at the full rate. If the customer pays within the settlement discount period the VAT is discounted and a VAT adjustment must be processed. The new rules require businesses to: 1. Notify their customers of the VAT discount available and the amounts the customer is due to pay. This can be done one of two ways: 2. Issue an invoice detailing the full net and VAT payable. If the invoice is paid within the discount period, issue a further VAT only credit note to account for the VAT discount. 3. Issue an invoice document which states the amount of discount (net and VAT) that can be claimed if the invoice is paid early, as well as the full amount (net and VAT) due after the settlement discount period. If the invoice is paid within the discount period, there is no need to issue an additional credit note. However, internal VAT adjustments will be required. 4. When an invoice is paid immediately, the settlement discount is automatically taken. The VAT is discounted on the invoice and no subsequent VAT adjustment is necessary. Note: In Ireland, VAT is always charged at the full value of the invoice, regardless of any settlement discounts. How to turn on the VAT changes applicable after 1 st April 2015 Due to the changes to the way VAT is calculated for invoices with settlement discount, you must turn this on in Sage 200 when you need to start using the new VAT rules. To do this: 1. Open Accounting System Manager > Settings > System Settings Operational Settings. 2. Select Apply new VAT rules for early settlement discount. Once selected, this cannot be turned off. This is because changes are made to your database tables. Do not select this, until the new VAT rules need to be applied. Note: When you create a new company, the new VAT rules are applied by default and this can t be changed from within Sage /02/2015 Sage (UK) Limited, 2015 Page 4 of 37

5 Changes made to Sage 200 VAT will be calculated at the full rate by default for all subsequent invoices with settlement discounts. The VAT will be recalculated on invoices that include settlement discount and haven't been printed. There are new default invoice and credit layouts that contain the additional text and fields required by HMRC to indicate the VAT discount due if the invoice is paid within the discount period. This means that there is no requirement to issue an additional VAT only credit note to you customers but internal VAT adjustments will be required. How to record sales transactions with settlement discounts For sales transactions, the VAT is now calculated at the full value of the invoice by default. When a customer pays within the settlement period, the net and VAT discounts will apply to the invoice. As the VAT has already been recorded at the full rate, you will need to enter adjustments to account for the VAT discount taken by the customer. These adjustments can be recorded in Sage 200 as VAT only credit notes. If you're printing your invoices from Sage 200, then the correct text is printed on the invoice so there's no need to print and send this credit note to your customers. How you record these VAT adjustments depends on the business processes you want to use. You may want to process them per invoice or enter a number of adjustments as one transaction for a customer. Invoices and Orders Record sales invoices When you record the details of an invoice in Sage 200 that has been produced elsewhere, the details you record must match the details printed on the invoice and sent to the customer. If the invoice hasn t been paid, the VAT should be calculated at the full rate. For example, for an invoice with a net value of 100 with a 5% settlement discount, the VAT is calculated at 20 by default. If the invoice was paid straight away, the settlement discount will have been taken, and the VAT on the invoice sent to the customer will already be discounted. When you record this in Sage 200, you must adjust the VAT amount to match the invoice. In this case there is no need to process an adjustment to account for the VAT discount. For example, for an invoice of 100 with a 5% settlement discount, you enter the VAT as /02/2015 Sage (UK) Limited, 2015 Page 5 of 37

6 Free text invoices, sales orders and project bills When you print an invoice from Sage 200, the correct additional text is included on the default layout. This means that there is no need to print and send an additional VAT only credit note to the customer. However, internal VAT adjustments will be required. Invoice text Sales Orders and free text invoices with immediate payment When you enter a full payment with an invoice or order, the net and VAT discounts are used to calculate the payment amount. A receipt for the payment amount plus the net discount is posted and allocated to the invoice, leaving the VAT discount outstanding. You will need to enter a credit note to account for this. 10/02/2015 Sage (UK) Limited, 2015 Page 6 of 37

7 For example, for an invoice for 100 with a 5% discount which is paid in full, the net discount is 5 and the VAT is discounted by 1, making the payment value 114 and the posted receipt value 119. Receipts Before you can process a receipt for a customer offered a settlement discount, we recommend that you establish whether the money you've received represents the full payment with no settlement discount, full payment with a discount or a part payment. If the customer pays within the settlement discount period, they will pay the invoice value less the VAT and net discounts. You can enter the net discount amount when you record the receipt. This posts the net discount to the Discounts Allowed nominal account and adds it to the receipt total. For example, for an invoice of 100 with a 5% settlement discount, the net discount is 5 and the VAT discount is 1, so the customer pays you 114. The receipt value shows as /02/2015 Sage (UK) Limited, 2015 Page 7 of 37

8 Allocation When you allocate the receipt to the invoice, the total receipt value will be less than the invoice value. The remaining amount is the VAT discount. You ll need to make sure that you reduce the allocated amount of the invoice to match the receipt. Tips: If you have a difference on the allocation screen, you can choose to write this off as discount. Make sure you don t do this for any outstanding VAT discounts, as this will incorrectly post the value to your Discounts Allowed nominal account. 10/02/2015 Sage (UK) Limited, 2015 Page 8 of 37

9 We recommend that you don t use Auto Allocation when allocating transactions with settlement discount. This is because the full invoice value is allocated by default when auto allocation is used. This will make it harder for you to work out the VAT adjustments required. Record VAT adjustments Once you've entered and allocated payments received from customers taking settlement discounts, the discounted VAT amount will remain outstanding on the customer's account and the full VAT amount will be recorded on your VAT return. To make sure the VAT is recorded correctly on your VAT return and to clear the outstanding balance on your customer's account, you'll need to process a credit note for the remaining VAT discounts. How you record these VAT adjustments depends on the business processes you want to use. You may want to process them per invoice or enter a number of adjustments as one transaction for a customer. We recommend that you process these adjustments before any credit control activities. How to record purchase transactions with settlement discount For purchase transactions, the process you follow will depend on how your supplier deals with any settlement discounts they offer you. The wording on the invoice you receive should indicate whether your supplier will send you a credit note for the VAT discount. You may receive invoices in the following scenarios: The supplier sends you an invoice with the VAT calculated at the full value of the invoice. This invoice also includes details of any settlement discounts due. When you pay the invoice, you take the discount and pay the reduced amount. When you record the invoice, VAT is calculated at the full rate by default. To make sure the VAT discount is recorded correctly on your VAT return and to clear the outstanding balance on your supplier s account, you'll need to process a credit note for the remaining VAT discounts. How you record these VAT adjustments depends on the business process you want to use. You may want to process them per invoice or enter a number of adjustments as one transaction for a supplier. The supplier sends you an invoice with the VAT calculated at the full value of the invoice. When you pay the invoice, you take the discount and pay the reduced amount. The supplier sends you a VAT only credit note for the VAT discount. When you record the invoice, VAT is calculated at the full rate by default. You ll also need to record the details of the VAT only credit note when you receive it. You've already paid the invoice, so the VAT on the invoice has already been discounted. 10/02/2015 Sage (UK) Limited, 2015 Page 9 of 37

10 When you record the invoice, you ll have to adjust the VAT value to match the invoice you ve received. No further VAT adjustments are necessary. Suggested payments When payments are generated, the VAT discount is not included in the suggested payment amount. For suppliers where you are taking settlement discount, you will need to reduce the payment amount to include the VAT discount. Once the payment is generated, the VAT discount amount will remain outstanding. You ll need to enter a VAT only credit note to clear the balance and update your VAT return. For example, for an invoice of 100 with a 5% discount, the amount you need to pay is 114: (net discount) 1 (VAT discount). When the payment is generated for this invoice, the suggested payment amount is 115. Other things to consider Auto Allocation type accounts We recommend that you don t use these for customer or suppliers with settlement discount. This is because the allocated amount doesn t include the VAT discount by default. When receipts are automatically allocated to invoices, the full value of the invoice is allocated. 10/02/2015 Sage (UK) Limited, 2015 Page 10 of 37

11 Balance forward type accounts We recommend that you don t use these for customers or suppliers with settlement discount. This is because the discount details are lost when individual transactions are replaced with the brought forward balance. Custom invoice and credit note layouts Before installing this service pack, we recommend that you back up all your layouts. This is because new invoice and credit note layouts are included with the service pack and these will overwrite any custom layouts you are currently using. The new invoice and credit note layouts installed with SP7 contain the additional text required by HMRC for invoices that contain settlement discount. We recommend that you add this text to your custom layouts. 10/02/2015 Sage (UK) Limited, 2015 Page 11 of 37

12 VAT 3 Legislation Update (ITS 5396) VAT3 is the form filed by VAT-registered businesses in the Republic of Ireland. Recent changes to legislation have led us to make a number of changes to the way that VAT is calculated and reported for customers operating in the Republic of Ireland. These values are calculated using EC properties on the VAT codes for Sales Non-Related Services and Purchases Non- Related Purchases. Once the service pack is installed, the Vat Return will change if the Country Code is set to IE and the base currency is the euro. The new VAT Return is calculated as follows: Income (such as sales invoices), using Sales Goods & Related Services affects E1. Income using Sales Non-Related Services affects ES1. Expenditure (such as purchase invoices), using Purchase Goods & Related Services affects E2. Expenditure using Purchase Non-Related Services affects ES2. We have also updated the printed VAT Return and the Vat Transactions report to reflect the changes in VAT3 legislation. 10/02/2015 Sage (UK) Limited, 2015 Page 12 of 37

13 SEPA Legislation Update The Single Euro Payments Area (SEPA) was created to simplify cross-border payments between any countries that use the euro currency. These payments use the International Bank Account Number (IBAN) and the Bank Identifier Code (BIC) within Sage 200. In order to use SEPA functionality in Sage 200: Set up the IBAN and BIC/Swift number in your Cash Book Accounts. Set up the IBAN and BIC/Swift number in the Bank Details on your Supplier Accounts. Download the relevant e-banking component for your bank. When you next use e-banking, you can select the new file from the drop-down list. A new file will be listed with the suffix SEPA, for example, Allied Irish (SEPA). 10/02/2015 Sage (UK) Limited, 2015 Page 13 of 37

14 Live Issues fixed The list below contains a list of the live issues reported to us; by our business partners, customers and within Sage. It is organised by module. Module Issue Tracking System No. (where applicable) Description Core 200 POP 5600 PA 5945 POP We have fixed an issue where over invoicing a partially received purchase order causes traceable stock discrepancies. Suggested Billing We have fixed an issue where items are incorrectly flagged as Billed if project items have a Status that is not the same as the overall Project. We have fixed an issue where text copied and pasted from a different source (i.e. Microsoft Word) onto a POP Order line may stop the POP Authorisation Notifications process if text contains non-unicode characters. These are now filtered out. CRM RTDV 6381 We have fixed an issue where incorrect results are shown when filters are applied to Real Time Data Views. Service Pack 6 Issues Fixed Module Issue Tracking System No. (where applicable) Description System Administration 5128 We have fixed an issue where a new user might be created with a User ID that is considerably jump numerically from the previous number after a server reboot, where the server has SQL 2012 installed. Core 200 NL 1274 NL 5095 ST 2287 An intermittent issue preventing users from running the consolidation for a second company has been fixed. Nominal analysis values are calculated correctly when using Purchase Ledger authorisation across multiple nominal codes. Allocation selection for projects now works correctly on the Issue Allocation form. 10/02/2015 Sage (UK) Limited, 2015 Page 14 of 37

15 ST 3338 ST 5210 ST 5424 PA 5444 PB 3961 & 4126 SOP 3228 SOP 5645 Memory errors, which were seen when saving changes to an existing Product Group, have been resolved. We have fixed performance issues on data upgrades where there are a large number of stock items. Memory errors when trying to remove large amounts of stock history records via Archive Stock History, has been resolved. Previously, the Suggested Bills routine checked every project on the system, regardless of status. After installing Service Pack 6, Suggested Payments will only check relevant bills The memory errors that occurred when trying to import large price lists has been resolved. We have fixed an issue where the user may receive the following error message, Error converting data type varchar to bigint, when using the Credit button on the SOP List View toolbar. This fixes an issue with the counter table, when it gets larger than int32 ( ). The issue prevented certain processes from operating; for example, when processing SOP orders to completion. We have fixed an issue where, under certain circumstances, duplicate payments can be posted both within Sage200 and SagePay. SagePay 5398 This previously occurred when processing payments via SOP or the Sales Ledger, through to SagePay, when swapping between settings for Use New Card Details and Use Existing Card Details. MFG EST 4802 Amended cost prices on an estimate stage can now be saved. EST 5020 EST 5054 An issue where you could not match invoices to Sales Orders when they are created from an estimate has been fixed. Users had previously found that they were unable to post an invoice with a negative free text line when the estimate was created with more than one stage. The exception error that appeared when opening Estimate Settings or View Estimate Settings has been fixed. WOP 1674 Multi-level back-flushing now works for partially completed works orders. WOP 4181 WOP 4253 Previous versions of WOP did not update the memo field from the manual works order. In order to update memos on works orders, users had to use MRP. Service pack 6 fixes this issue. Nominal Posting Cost of Sales Adjustment calculations now use the specified transaction date rather than the system date. This ensures consistency with the cost of sales postings. 10/02/2015 Sage (UK) Limited, 2015 Page 15 of 37

16 WOP 4863 WOP / ST 5093 Planning 4922 Planning 5027 Planning 5055 Planning 5614 BOM 5118 You can now issue multiple works orders when using the Bulk Issue Components. In previous versions of Sage 200, works orders were part issued even though there was enough stock recorded on the system. You can now amend stock item product groups when there are still outstanding works order issues on the system. Previously the system would appear to freeze or return an out of memory error. We have fixed an issue where stock recommendations are inflated when there is also a ROL demand. This ensures consistency between MTS and warehouse demand. Sales orders created from quotes now link to MRP when you have selected the Flag sales orders as linked option. You can now run MRP and get a recommendation for both the sales order and the estimate. Previously, opening an estimate after raising the sales order lost the link to the record and duplicated the demand in MRP. There was an issue when aggregating demand MRP when warehouses had a similar name (for example, Shed and Shed Main ). This has now been corrected. You can now reverse builds in BOM when the built item is in negative stock and you have selected the Allow negative stock option. Previously, a The Build Session is not eligible error message would appear, preventing you from continuing and requiring you to perform manual stock adjustments to reverse the BOM build. CRM Apostrophes in the company name or address no longer prevent you from using the form-launching functionality. We have fixed an issue where sites have experienced random Catastrophic Failure errors in the Integration Service, due to orders and quotes being linked to deleted opportunities. We have fixed an issue where errors occur when adding free text items and comment lines to web orders. It was previously possible to delete a contact in Sage 200 ERP when that contact has live notes and communications in Sage 200 CRM. When the deletion was synced to Sage 200 CRM, the CRM person was deleted along with all the links to the notes and communications. Active notes disappeared from CRM when the person was deleted. Following this update, delete person messages made during the sync process will start a new process to check if that person has any outstanding notes, cases or communications. If any of the following records / statuses exist on the person, or if a 10/02/2015 Sage (UK) Limited, 2015 Page 16 of 37

17 connection to CRM cannot be made to check the status, then the delete is cancelled: Pending communications In Progress Opportunities In Progress Cases You can no longer synchronise blank contacts to Sage 200 CRM when using the merge person functionality. Previously, users may have seen errors in the sync logs relating to an Invalid column name ParentEntity. While not affecting the functionality of Sage 200 CRM, it created large sized exchange sync logs on the users PC. This has now been fixed. This hotfix is for Sage 200 CRM customers who wish to install Sage 200 CRM 7.1i. CRM Hotfix 12 CRM Patch I Support Hotfix Sage 200 CRM 7.1i synchronises people records differently to previous versions of Sage 200 CRM. Installing this patch ensures that a default person record is always created for a company in Sage 200 CRM, even when the default contact for a customer or supplier account in Sage 200 is blank. 10/02/2015 Sage (UK) Limited, 2015 Page 17 of 37

18 Service Pack 5 Issues Fixed Module Issue Tracking System Reference (where appropriate) Description Core Improved Customer and Supplier Import Account facility. Can now import the address and website address for the preferred contact for customer and supplier accounts When a purchase order is raised for a foreign currency supplier, and an additional charge added, the value of the additional charge is now converted to the correct value in the foreign currency The calculation of nominal values in invoice authorisation is now consistent with values calculated at invoice entry for foreign currency accounts To conform to POP authorisation rules, it is no longer possible to post an invoice from the POP Record Purchase Invoice window. The Post Invoice button is greyed out Project accounting invoices can be printed, even if the title is greater than 60 characters Memory errors, which were seen when allocating a large list of orders, have been resolved Memory errors, which were seen when allocating stock for a large number of SOP allocations, have been resolved Manually adding an Intrastat maintenance entry resets the Tax Month Sales order processing invoices can be printed, even when the customer account name is greater than 50 characters Purchase order direct delivery addresses can be saved, even when the supplier contact name is 60 characters Memory errors, which were seen when running Year End with over 500,000 customers, have been resolved. UI updates in core Various inconsistencies in the user interface, such as misaligned text or boxes and inconsistent capitalisation of field names, have been fixed. Manufacturing 2781 Memory errors, which were seen when running some traceability enquiries, have been resolved BOM components, used on a BOM and attached to an operation, can now be replaced using the Replace Component options. 10/02/2015 Sage (UK) Limited, 2015 Page 18 of 37

19 4620 It is now possible to edit operations on BOMs and estimate records, when the number of items on the BOM or estimate runs into more than one page of information Subassemblies that have a negative quantity in stock are now issued as well as built, during the BOM build process A duplicate operation in a BOM record now holds its own components only, when a works order is created. Previously, the components of all duplicate operations were aggregated and held against each duplicate operation An error regarding too many parameters, which was seen when adding a new entry in the Make to Stock planning module, if the company has more than 3000 product groups, has been resolved. CRM Consolidated Communications now works consistently on IE8 and IE9. Improved error messaging when creating integrations and synchronising data to make it easier to troubleshoot synchronisation issues. There is a new tab on integration which shows the synchronisation status of all companies. Companies with a synchronisation status of error can be re-linked to Sage 200 Accounts by selecting company hyperlink and choosing the re-link from the Financials tab. Synchronisation issues seen when using the batch merge person utility, have been resolved. The shipping address is now always updated when the data is synchronised. When setting up a new integration, the customisation version is now correctly set on the first synchronisation Sales orders containing SOP order items now synchronise correctly Orders entered in CRM where the comment line number has been changed, now synchronise correctly Information entered on the Financials tab for linked CRM companies can now be edited. Support Tool: CRM Data Integrity Module A new Sage 200 test has been added to check for invalid database views. 10/02/2015 Sage (UK) Limited, 2015 Page 19 of 37

20 False positives have been removed from the Support Tool New check added to make sure Suppress Account is set to Y. New check added to make sure Use Account is set to Y. The MergeByForeignID script has been replaced with individual scripts for Address, , and Phone. Migration 3439 All versions of the migration tool, used for migrating BOM data, now work consistently, so it is now possible to use a newer version of the migration tool, even if an older one has been used before Slow performance, seen when migrating Financials-only data, has been resolved. 10/02/2015 Sage (UK) Limited, 2015 Page 20 of 37

21 Service Pack 4 Issues Rolled into Service Pack 5 Module Issue Tracking System Reference (where appropriate) Description Core 200 NL 4545 Out of Memory error when consolidating companies with large numbers of nominal accounts (more than 50,000). SL / PL 4548 Out of Memory error when amending allocations for a customer account with large numbers of allocated transactions. SOP / POP 460 / 4666 Cannot sort order lines by column when amending multi line sales and purchase orders. The following error message is shown; Invalid Column Name is Incomplete. MRP BOM 4618 Out of Memory error when expanding MRP tags. This occurs when the parent tag has multiple recommendations MRP not considering the demand quantity when tagging multiple replenishments Time out errors when refreshing the MRP Recommendations View on large datasets (over 100,000 Recommendations). EST 4576 Stock not allocated to the parent works order when a sub assembly BOM is completed and the Allocate Parent Works Orders setting is selected. WOP 4526 Cannot convert a one off estimate to a BOM when: The estimate had been created using the Rapid Estimate Entry form, and There is one resource on an operation Components on an existing stage are duplicated when the estimate is amended Stock item lines which have a UOM with a stock/base ratio other than 1 are being recalculated incorrectly on estimates when the stage is closed The Qty Outstanding is displayed incorrectly on the Order Enquiry 10/02/2015 Sage (UK) Limited, 2015 Page 21 of 37

22 screen Incorrect cost is posted to the WIP nominal account when a cost of sales variance is posted for the purchase order The unit of measure is not displayed on the One-Off Works Order screen Time out error or slow response when selecting a works order from the desktop list. Business Intelligence Errors updating or creating a data warehouse using SQL CRM Sales Order Line RTDV also shows lines from quotes and pro formas. When the website details on a company or person are cleared in CRM, they are not cleared in Sage 200 Accounts when the data is synchronised. Billing and Shipping addresses are not updating correctly in Sage 200 Accounts when the billing and shipping address flags are changed in CRM. Companies not merging correctly when using the Merge Retain Target option. Cannot link a CRM company to Sage 200 Accounts when the company has a prospect quote in a different currency. The customisation version has been updated to version Service Pack 3 Issues Rolled into Service Pack 4 Module Issue Tracking System Reference (where appropriate) Description Core 200 NL 1274 Error when running a consolidation for a second company. This occurs when a consolidation is run for one company. The Change Company option is used to select a second company and a second consolidation is run. 10/02/2015 Sage (UK) Limited, 2015 Page 22 of 37

23 4478 Out of memory error when updating a large number of waiting postings. NL / CB 4350 Currently users can post different sides of a transaction to different periods. This means that the trial balance will not balance for a single period. Note: This current process was included to retain functionality that was present in Line 100. New Functionality: An Accounting Period Date Validation option has been added to the Accounting System Manager ( ASM > Settings> System Settings Transactions settings ). This allows you to specify whether to allow the posting of different sides of a transaction to different accounting periods. SL / PL 2626 Cannot import Sales and Purchase Accounts with Contact Names longer than 20 characters. Cannot validate the second reference on the invoice/credit note entry screens for SL and PL. New Functionality: Validation check added to the Invoice and Credit Note entry screens. SOP 4335 Cannot print / reprint SOP Credit Notes when a customer s credit note layout has been deleted. 10/02/2015 Sage (UK) Limited, 2015 Page 23 of 37