Posted by: istewart | September 22, 2013

SEPA – the dust settles a bit.

SEPA [Single European Payment Area] – what is it?
SEPA is a European Regulation that is intended to simplify processing payment and receipt transactions across all 32 EU member states. It affects both banks and their clients. Banks need to be able to accept debit and credit transactions in SEPA formatted files, and their clients need to be able to produce SEPA files. Its coming up hot and heavy with the compliance date for SEPA I [there's always a phase II to these things!!] set for February 1 2014. SEPA I is concerned with transacting in Euro across the EU. SEPA II is concerned with transacting in any currency across the EU.

Grand. But how will it affect us?
All that follows is a brain dump of things we have encountered helping Dynamics GP users in Europe become SEPA compliant. The real big issue is for clients who collect customer payments. Under SEPA the responsibility for maintaining Direct Debit Mandates switches from the Bank to the client. So if today you collect payments by DD – you will need to implement a Mandate process. All banks require to see the confirmation letter you send to new customers. Easiest is to ask them for a copy of their recommended letter and modify it for your needs. Each mandate is required to have a Unique Mandate Reference in order to allow direct debits to be refunded / queried.

So, that said – how does SEPA affect your business? First, contact your bank and see are they SEPA compliant…or when they plan to be. Until they are ready you won’t be able to send a test file [generally...however some may accept files depending on how far down the road they are with their side]. Most of the main Irish banks are SEPA compliant at this stage or will be very soon. We’ve seen some differences in how they interpret the various nodes in the SEPA XML schemas- its supposed to be standardised, right? – well it is up to a point apparently. So don’t take it for granted that a file that works with one bank will work with all.

Some banks are offering a service to clients where existing EFT formatted Credit files will be converted to SEPA by the bank…so clients in theory don’t need to worry about re-configuring their outputs. But there are end dates on these services…and they are not offered for Debit transactions. Additionally, previously there was some elbow room when it came to submitting flat files – not now – the banks have tightened up on the flat file specs if you want to use their conversion process. In all cases so far we have had to edit the existing exports for GP users who have chosen to use this interim bank service.

Some things to watch out for:
There are disallowed characters in SEPA that were allowed in flat files. Get a list of these and make sure you either remove them from such things as Vendor Name, or you engage a utility to remove / convert them prior to producing your SEPA file. Also, in the past DD files survived muster with really any Payment Type ID. Under SEPA these rules are rigidly enforced – so make sure your output uses the correct code.

What are your options in Dynamics GP?
Realistically, you have two: 1. Create an XML EFT output using the XML File types in standard Dynamics GP EFT Module…get your partner to become authorised by the bank…and submit you and your partner to endless testing. 2. Engage the services of an expert in the field that specialises in maintaining all of the file standard outputs including SEPA. Make sure they are authorised by your bank as a supplier. Continue with your current GP process and just modify the output to be an upload to this specialist partners software.

Having reviewed all of the possibilities, our advice is option 2 and we are encouraging all our Dynamics GP clients towards this. Its far more economical [annual usage fees are as low as Euro 250.00] and you’re always up to date…and when SEPA II kicks in, it will be just a matter of applying an update. Anyone who is facing SEPA issues in Europe feel free to reach out to me.

Ian.

Posted by: istewart | September 18, 2013

Update to Clear Activity in Bank Management

Had a support query today from one of our clients in the UK. They were getting the error message where Bank Management figured a user was still accessing a batch of transactions. This was after a hard close [aka 'crash'!!]. Ran the clear Activity utility in Bank Management to no avail, and then queried the CBEU1020 table – but no records. Searching around I found the User ID and Batch ID in table CB10006. The CBEU1020 table tracks activity for Euro denominated transactions, so this is why the activity record was not in there…the batch was for a GBP denominated bank account.
Delete CB10006 where Dex_Row_ID = ‘the relevant record’…did the trick.

Related post here:http://dynamicsgp.wordpress.com/2009/12/19/clear-activity-on-bank-management-doesnt/

Posted by: istewart | September 9, 2013

Purchase Order Prepayments – Dynamics GP 2013

Another cool feature and one no doubt driven by customer requests. In GP 2013 you can enter prepayments against Purchase Orders. These can be manual payments – or can be picked up by automatic check/EFT runs. If using the Auto Checks/EFT process, the PO appears like any other Supplier invoice and the resultant payment references the PO Number as the Document number on the remittance. When it comes to entering the Invoice[s], until the PO is closed, the prepayment cannot be assigned to unrelated invoices which makes sense.

To set up POP Prepayments go to the Purchasing Setup Window. Down the bottom, there are new fields added where you can enable this feature, add a password if required and dictate the Prepayments GL account to be used.

When in use, on the Purchase Order window – you will see a Prepayments field at the bottom where you can record the prepayment. A red hash to the left of this field tells you the payment hasn’t been made yet – it will disappear when the payment is recorded. Additionally, the GL is updated once the payment is complete – not before, which again makes perfect sense.

One issue at the moment is that the maximum prepayment you can enter seems to be the total of the line amounts. I.e. footer amounts like Purchase Tax cannot be prepaid. I can only assume that this is an oversight? I will update this post when I know more.

Posted by: istewart | May 14, 2013

Business Portal for GP2013 – the skinny

RTM release now issued following the issue of GP2013 SP 1.

Its 64 Bit only and supported on Windows Server 2008 SP2 and 2oo8 R2 SP1 + Sharepoint Server and Foundation 2010.  (BP 6.1 will be supported on SharePoint 2013 when its released).

Not supported on Windows Server 2012 because Sharepoint is not currently supported – wait for Sharepoint SP2.

Upgrade paths direct to 6 from BP version 4 SP2. Moving from 4 and 5 will require upgrading SharePoint to 2010…first! If you’re dropping any Business Portal applications – uninstall them before upgrading. The sequence is:

….Upgrade to Sharepoint 2010, upgrade to GP 2013,  upgrade web services if in use, finally upgrade business portal.

Posted by: istewart | April 19, 2013

GP Manufacturing Order to Sales Order link

One of those days. Took me an age to find the relevant table. Eventually copped on to myself and reached out to a pal in the US who didn’t even have to look at Resource Descriptions to tell me. For those in the same boat – here’s the answer.

When you create a newDynamics GP Manufacturing Order based on a Sales Order the link information is stored in table IS010001 (ICONrol Sales Order Line). Remember that each sales item line on a sales order will create an individual manufacturing order to make that product. So this table also stores the sales order line item sequence number.

A quick query (where ???? is the manufacturing order number) would look something like:

SELECT SOPNUMBE, LNITMSEQ FROM IS010001 WHERE MANUFACTUREORDER_I = ‘?????’

Additionally table WO010032 (Manufacture Order Master) may contain the Sales Order number in the DSCRIPTN field – if users haven’t overwritten the Description field when the manufacturing order is created.

Hopefully save someone some time!

Web Client functionality for Dynamics GP Project Accounting module is planned for release with GP 2013 SP2. Just thought you should know!

Posted by: istewart | February 2, 2013

Dynamics GP Web Client

The GP web client. What functional areas are available now? Phase I concentrated on core Financials and Distribution.

General ledger, Accounts Receivable and Sales Order Processing, Accounts Payable and Purchase Order Processing, Inventory control. These modules were released as part of Phase I. Any changes you make using Modifier will render in the Web Client…but VBA code will not run. (Check out Rubal’s post about migrating VBA code). For Excel reports to run, you need to be connected to the domain.

Whats coming next and in what sequence? The latest news is:

  • Human Resources and Payroll, then
  • Field Service and Project Accounting, then
  • Manufacturing

 

Posted by: istewart | November 26, 2012

Sample XL Dashboards to download

The Dynamics GP team have provided Business Intelligence dashboard samples for download from their Blog. These are created in Microsoft Excel 2013 and show the real power of the XL refreshable reporting. The Financial Dashboard is free to download and use with your existing data, and the guys would welcome feed back.

Check out the free dashboards here.

Dynamics GP Financial Dashboard - Refreshable XL Report

Dynamics GP Financial Dashboard – Refreshable XL Report

« Newer Posts - Older Posts »

Categories

Follow

Get every new post delivered to your Inbox.

Join 30 other followers