Category: Sage 200


On 01 April 2015, the legislation when raising or receiving a VAT invoice including early settlement discount will change. The change affects you as a supplier who offers early settlement, and/or as a customer who receives early settlement discount, where an invoice is issued.

For the current legislation, up to 31 March 2015, suppliers who offer early settlement discounts are permitted to account for and include the VAT due on the discounted price on their invoice, even if the full price (i.e. the undiscounted amount) is what is eventually paid. Customers who are offered an early settlement discount are only able to recover the VAT stated on the invoice even if they do not pay within the settlement days permitted.

From the 01 April 2015, suppliers must account for VAT on the amount they actually receive and customers may recover the amount of VAT that is actually paid to the supplier. Because of these changes Sage are releasing updates for Sage 200 however you must be aware how this impacts your version of Sage 200.

Sage 200 2015 will be fully compliant with the new legislation when it is released (end of February). It will also make it easier to process in accordance with the new guidelines. It includes two elements – compliance and usability. Sage therefore recommend that all Sage 200 sites which are affected by this legislation change upgrade their software to Sage 200 2015 as soon as possible.

Some older versions of Sage 200 will have a Service Pack released to assist with the changes however this relates strictly to the point of compliance only. Sites which have installed the relevant update will be able to continue printing compliant invoices.

Sage and indeed my recommendation for Sage 200 2011, 2013 and 2013 R2 sites is to upgrade to Sage 200 2015 as these versions will be less efficient and more prone to human error. That is unless the site has a very limited number of accounts where Early Settlement Discount is effective.

There will be no updates made available for Sage 200 2009 or Sage 200 2010. All sites on one of these versions, that are affected by Early Settlement Discount, should upgrade their software to reduce the amount of manual changes.

Sage 200 2009 End of Life

Sage 200 2009 will become end of life from 31 October 2015.

If you are using this version of Sage 200 now is the time to look at your options.

Whilst Sage 200 2009 will continue to work after 31 October 2015, no updates will be issued and Sage will no longer offer support to your Business Partner.

The good news is that’s Sage 200 2015 is soon to be released with many enhancements. I’m currently playing with a Beta copy so will post more about this soon.

Sage 200 2015

Business Partners got their hands on the Sage 200 2015 Beta copy this week.

I am having a good play at the moment and will get some posts out very soon.

Fast, yes fast, login.

A really nice, modern, new look and feel.

List Views and Process maps back (I know they were only hidden and most people switched on straight away but they are now prominent again!).

Fixed Assets

Graphical Summaries

Excel reporting (Still have Excel Integration and BI)

Ideas Hub

When the first Sales order line of a Sales Order has a zero value and no Nominal analysis but further order lines do have Nominal analysis, the  nominal drill down within the SL Transaction enquiry shows the Narrative ‘Intended For -//’

  1. Create a Sales Order with a Free text line with a zero value and no nominal analysis.
  2. Add a second and third order line with Nominal analysis
  3. Save the order and process through to completion (post the invoice).
  4. Within the Sales Ledger open the transaction enquiry for the selected customer and highlight the Invoice
  5. Select the Nominal Drill Down and see the narrative. All lines show ‘Intended for -//’

My occurrence was due to the user using the Free Text line for a comment/note. This is what the Comment line is intended for. The alternative is to enter the Free Text Line at the end.

When logging in to Sage 200 the following error will occur due to certain Authentication settings being configured incorrectly. The error will only be on the clients machines. Logging in to Sage 200 on the server will not cause this error.

Communication Error

IIS Windows authentication settings

  1. Within IIS, expand Sites > select Sage 200 App Services > double-click the Authentication icon in the Features area.
  2. Select Windows Authentication. Ensure this is set to Enabled. If not, select Enable in the Actions panel on the right.
  3. Also in the Actions panel, select Advanced Settings…
  4. Ensure the checkbox for ‘Enable Kernel-mode authentication’ is ticked > OK.
  5. Reset IIS

IIS Anonymous Authentication settings

  1. Within IIS, expand Sites > select Sage 200 App Services > double-click the Authentication icon in the Features area.
  2. Select Anonymous Authentication.. Ensure this is set to Enabled. If not, select Enable in the Actions panel on the right.
  3. Also in the Actions panel, select Edit…
  4. Ensure ‘Specific user’ is selected > Set…
  5. Enter the fully qualified Sage 200 Services username and password. This is the username and password you specified during the installation of Sage 200. For example, <domain>\Sage200Services.
  6. Press OK and reset IIS.

LAN Manager Authentication level

  1. Select Start > Control Panel > Administrative Tools > Local Security Policy.
  2. Double-click the Local Policies folder and select Security Options.
  3. From the list of policies, double-click ‘Network security: LAN Manager authentication level’.
  4. From the drop-down list, select ‘Send LM & NTLM – use NTLMv2 session security if negotiated’ and select OK.

If the error persists…

  • If you are using a Workgroup, password protected sharing will cause the above message to appear. This should be turned off within the Control Panel > Network and Sharing Centre > Change Advanced Sharing Settings.
  • Ensure the server that hosts the Sage 200 Web Services has been added as trusted site within Internet Explorer Options. You can access this within Internet Explorer > Tools > Internet Options > Security tab > Trusted Sites > Sites.

Where an IIS reset is required above, all users must be logged out of Sage 200 and indeed any other system which use’s IIS.

I have recently started looking into and working with a number of the great Sage 200 add-ons available from Eureka Solutions.

Eureka Solutions have created a large portfolio of add-on’s which make Sage 200 even better than it is.

What can often happen during a Sage 200 implementation is the need to fulfil a GAP in customer requirements, which Sage 200 doesn’t do itself. This is then fulfilled with bespoke development which can have huge knock on effects to the project in terms of time frames and costs.

What Eureka Solutions have done is identified and filled a lot of the more common (and often basic/obvious) gaps. In particular differences between Sage 50 and Sage 200, speed of order entry, ease of creating new records such as Stock items, and customers.

As well as this they have identified industry specific requirements to suit Retail, Telecommunications and Wholesale (to name a few).

So the question that I ask is why would you recreate something that already exists as an ‘Out of the box’ solution? My recommendation is that you shouldn’t. Especially considering there are no additional costs when it comes around to upgrading as recompiles are done as part of support.

A free ‘Starter Pack’ of Sage 200 add-ons is available. This can be installed and used at no cost and gives access to 10 functions such as creating a New Stock Item during order entry, creating a New Customer during order entry, the ability to save and despatch a sales order and create a Return from a Sales order.

Most recently I have been working with the Stock Alias, Stock Kitting and Data Exchange products.

Stock Alias (part of the plus pack for Sage 200) allows you to set up additional codes to identify stock items. Ideal if your Sage 200 Stock Code is different from say your Website code, the SKU in EBay or some other form of identification.

Stock Kitting is much more like the Sage 50 BOM. It is Ideal for kit type products as opposed to items that are assembled or manufactured. For example you sell individual items such as Dinner Plates, Side Plates, Dessert Bowls and Mugs but you also sell these together as part of a Dinner Service of 6 of each individual item.

The Standard Sage 200 Stock record has an extra tick box to identify an item as a kit. Selecting this enables a Kitting tab where the individual parts and their quantity in the ‘Kit’ can be specified.

Finally I have been using Data Exchange, something which I have had experience of using before. This allows for an automated Export and/or Upload functionality for exchanging data between Sage 200 and other systems such as Websites. With my current project we are using plugins that link Data Exchange to EBay and Amazon accounts and extract orders from these to then import into Sage 200.

As I say, more to come on the specific functions available, but what I enjoy about these products is they are simple to use, quick and easy to set up and they are not over complicated in any way.

Ctayts

A question that often makes us shiver is when a Sage 200 user poses the question “How do I make my Stock Control reconcile to my Nominal Ledger?”

Now, its not often helped by it being the first time in Months, Years or maybe ever, that they have tried to reconcile.

However, it is an area that I cannot help but admit is not easy. There are a mass of variables that impact on this subject. Costing method, Stock Settings, POP Settings, SOP Settings, Nominal structure………and so on……

I have created the following document which details the settings that need to be considered, some common errors and some Sage 200 functional issues that should be considered.

Enjoy, and good luck!

Talking Sage 200 – Stock Reconciliation Checks

The new versions of Spindle Professional have been released and are now available to download.

Spindle Professional 5.87 includes
support for Sage 200 2013 R2 On Premise and Online.

Originally posted on Journey to SQL Authority with Pinal Dave:

[Notes from Pinal]: I am working with SQL Server for almost 10 years. I have seen the most ignored databases on any database server is system database. We hardly pay attention to them. Just for the sake of it – try to run queries in your master database and see how many user databases already exists there. I am sure unless and until you have strict policies in the place, there will be a handful of the tables available there. Similarly try to ask DBA question about what is the exact importance of the MSDB database and you will find it that there are so many of the DBA without its knowledge. I often talk about this with my friend Tim. I asked him if he can help us out  with the tricks to keep MSDB system database at its optimal settings.

Linchpin People are database coaches and…

View original 418 more words

Originally posted on Journey to SQL Authority with Pinal Dave:

When we have to move a database from one server to another server or when we have to move a database from one file to another file, we commonly use Database Attach or Detach process. I have been doing this for quite a while as well. Recently, when I was visiting an organization I found that in this organization lots of developers are still using an older version of the code to attach the database. I quickly pointed that out to them the new method to attach the database, however it was really interesting to find out that they really did not know that sp_attach_db is now a deprecated method to attach the database. This really made me to do today’s SQL in Sixty Seconds. I demonstrate in this SQL in Sixty Seconds how to attach or detach the database using a new method of attaching database.

The code which…

View original 220 more words