Initially the project team had the expected you-can’t-do-that reaction when the idea of a mid-month go-live was suggested.  We took three main steps to determine whether or not we were crazy or had a viable go-live option:

1. We asked SAP.  As one of the main participants on the project we got them to do an internal review with some platinum consultants with the objective of telling us why we could not go-live mid-month.
2. We asked our project team, both client and consulting resources.  Again, the goal was to tell us why we couldn’t do it.
3. We Googled like maniacs to find something to support and justify the conventional wisdom.  We failed to find anything substantial that would deter us.

Armed with the conviction that there was no reason we couldn’t go-live mid-month we set about defining the details of how we would pull it off.

Conventional Wisdom: Why You Don’t Go-live Mid-Month

My big disclaimer is that each SAP project has unique characteristics and what worked for us may not work for you, nonetheless I encourage you to keep an open mind and push until you find your insurmountable barrier, if it exists.  I would even contend that one of the biggest barriers may be your most experienced project team members and their gut reaction.  I admit my first reaction to the suggestion was “NO,” but as we drilled into the specifics of our project my inchoate objections crumbled.  The conventional wisdom is typically grounded in truth and experience, but conventional wisdom only applies to conventional situations.  To use a consulting cliché: challenge your assumptions.

In our research we found a consensus that there are three main areas that make a mid-month cut-over a bad idea.

Assets: I’m no expert on assets but the general word was that depreciation gets “messed up” if you cut over mid-month.  Owing to my limited experience in this area I’ll take that on faith, but this was not considered an issue as assets was out of scope for our project and asset postings will be done by journal entries.

Payroll: Again, I’m not an expert on payroll, but this was another situation where payroll was out of scope as the process is outsourced to a third party provider and journal entries are posted instead.  It was not considered a show stopping concern.

Year-to-Year Period comparisons: by cutting over mid-month some folks on the interwebs expressed concern that the month-over-month comparison for the go-live year would be no use until the third year.  Let’s say you go-live in the middle of June 2010 with partial balances in SAP (the remainder being in the legacy system), when June 2011 comes around you can’t compare the two Junes because one month is partial and one is complete.  You have to wait until June 2012 for a meaningful comparison.  This was not an issue for us because we converted three prior fiscal years of account balances with the go-live month balances being the balances as of the go-live date along with the transactional activity for the rest of the month.

Factors Leading to an SAP Mid-Month Go-Live

The ugly truth is that we went live mid-month out of necessity, not by choice.  Our original plan was to go-live on the first of the month, but we weren’t ready and a focused re-planning exercise identified that we could go live three weeks later.  Changing the go-live date to the first of the next month was not acceptable for a variety of reasons, including political considerations – it’s never a purely technical decision, so no surprise there.

Adapting the SAP Go-Live Strategy for Mid-Month Cut-Over

Once we knew we were going live mid-month we had to work out how to handle key areas of functionality: particular areas of interest were open A/P items, inventory balances, customer deposits, and the GR/IR account.  On top of this historical account balances needed to be loaded and we needed to ensure that FI conversions reconciled with logistics conversions.

Finance and Logistics Reconciliation

We came up with an approach that allowed us to readily identify differences between account balances converted by FI compared to the conversion by MM.  Consider the example of inventory conversion.

Standard SAP postings for the initial inventory balance with movement type 561 post to a pair of accounts similar to these:

• DR Inventory (135010)
• CR Conversion account (399175)

Instead of making this posting we changed the account determination for MM conversion to post as follows:

• DR Inventory (135010)
• CR Inventory conversion (135011)

Now when we converted historical balances into FI the inventory posting was:

• DR Inventory conversion (135011)
• CR Conversion account (399999)

The benefit of this approach was that any balance on the 135011 account meant there was a difference between what was converted via MM and via FI.  This became the basis of the work list that had to be reconciled.  The actual operational G/L account for inventory (135010) could be used immediately after the go-live without worrying about it becoming part of the ongoing reconciliation process.

Also, standard SAP does not allow direct posting to the inventory account (135010) and this approach allowed us to leave it as delivered.

We used a similar process, i.e. a conversion account instead of operational account, to support the cut over for accounts payable, customer deposits and the GR/IR account.

GR/IR Conversion

In our environment we are fortunate to have a situation where invoices are not received before the goods.  Consequently at the time of conversion there were purchase orders where goods have been received and not invoiced.  The typical GR/IR process is as follows:

Goods Receipt:

• DR Inventory (135010)
• CR GR/IR (211200)

Invoice Receipt:

• DR GR/IR (211200)
• CR Accounts Payable

At the time of conversion the good receipt has already happened and we did not want to reconstruct the PO processing so that we could use MIRO processing when the invoice is received.  Instead we converted historical balances for the GR/IR account by posting to a new account, 211201 as follows:

• DR Conversion account (399999)
• CR GR/IR conversion (211201)

Now when the invoices are received they will be posted with an FB60 transaction as follows:

• DR GR/IR conversion (211201)
• CR Accounts Payable

We know we are giving up some integrated capability for a period of time until these purchase orders and invoices wash through the system, but it means that once the GR/IR conversion account gets to zero we are done.  The typical life cycle for PO is 6-8 weeks so this is a temporary situation.  The true GR/IR account, 211200, will be used as intended and the benefits of MIGO and MIRO processing will be realized.

Month End Processing in the Old System

Going live mid-month also meant that the prior period was closed in the old legacy system and the month end balances were converted over in the same way as any other period.  It was a straightforward extension of our process to pull the mid-month account balances from the legacy system during go-live weekend and load them into SAP, too.

Financial Statement Impacts

The approach that we took meant we introduced several accounts to the chart of accounts for conversion only.  Consequently we had to update our financial statement versions to include these accounts and assign them to the correct positions in the report structure.  Clearly this is not a difficult task, but one that is needed.

SAP Mid-Month Go-Live Conclusions

I am skipping over some of the detailed considerations of how we made a mid-month go-live work for our project.  The details of how to make it work, the nuts and bolts of reconciliation, how we tested it (iteratively!), how we worked the differences identified between FI and MM/SD conversions, etc. aren’t here.  It wasn’t always easy and we had to do it in a short amount of time, but my key message is that we found a way to do it: the conventional wisdom wasn’t and isn’t necessarily wrong, just we found another path.

Most SAP implementations do not provide good visibility into one of the most important assets that your company has, namely your accounts receivables portfolio.

Join Cforia on Thursday July 23, as Cforia Software shares a business improvement process that will help your company improve its receivables visibility.  This will allow your company to implement improved Accounts Receivables workflow.

Attend this webinar to learn the benefits of, and guidelines for maximizing visibility into your AR portfolio:

• Know exactly how many calls, letters and the AR metrics contribution of every Collector in your organization.
• Creation of an audit trail that tracks customers calls, correspondence and outcomes.
• Track credit approvals, and chargeback authorizations.
• Use root-cause analysis to troubleshoot chargebacks.
• Streamline end of month Cash Forecasting so that it is completed in minutes, without manual spreadsheets.
• Have excellent visibility into how your Business Process Outsourcer (BPO) is handling your account.

A practical demonstration will show how Automation Tools can help your receivables department reach increased levels of visibility.

Click here to register

Many companies are looking for answers to help them adapt to the current economic environment.  Your customers are requiring more contact to pay on time, while your management is requesting reduced head count and better cash forecast reporting.

Join Cforia on Wednesday July 22nd as they along with Quote to Cash Solutions (Q2C) present a credit, collections and chargeback automation project planning template that will maximize cash flow and improve customer satisfaction through improving Accounts Receivables Departmental productivity.

Attend this webinar to lean how to create a successful project plan to automate Credit, Collections & Chargebacks.

• How to determine what is ripe for automation in “Your” company.
• Deciding the best approach and calculation “ROI”.
• Effective implementation.
• The advantages of:
  • Process integration
  • Credit scoring
  • Automating the collections and dispute management process.
• A checklist of tools to look for

The formal presentation will be followed by an open Question and Answer session.

Click here to register for the Cforia webinar.

Learn how prioritization of your company’s receivables will increase cash flow.

Most SAP Implementations do not provide prioritization and automation of the receivables collection process.

Join Cforia Software on June 24, 2009, as they share a business improvement process that will help your company improve its receivables management to drive down DSO and delinquency rates without increasing staff.

Attend this webinar to learn the benefits of, and guidelines for prioritizing and automating every action taken throughout your Receivables and Deductions departments.

• Learn why report driven workflows cause loss of productivity through decreased automation
• Serve up data to your Receivables Department that allows them to immediately identify the highest priority items
• Avoid that productivity hit associated with working on muliple systems, and how to avoid the time burner
• The cost of not converting legacy data into SAP, and what to do if it is too late
• Raise Collector productivity and Cash Flow by calculating and prioritizing the correct amount to ask for

A practical demonstration will show how Automation Tools can help your receivables department reach increased levels of efficiency.

SAP Receivables Management Prioritization Webinar Registration Page

Many SAP, Oracle, JD Edwards, PeopleSoft, Baan and Lawson implementations do not provide robust auto cash management and application funtionality.

Join Cforia Software on June 18, 2009 as they and Cashbook Limited share a business improvement process that will help your company achieve auto cash application rates in excess of 90% to increase productivity and accuracy.

Attend this webinar to lean the benefits of, and guidelines for significantly improving your company’s cash management.

• How to achieve straight through processing from Lockbox files into your ERP system
• Automatically handle customer provided remittance files including EDI, XML, Excel, Scanned and Hard Copy
• Automatically reconcile bank statements to your ERP system’s General Ledger
• Work transparently with multiple currencies
• Use elctronic payments to reduce cost and increase transactional accuracy

A practical demonstration will show how Automation Tools can improve cash management.

Most SAP Implementations do not track clean (uncontested, high collection probability) and dirty (invoice line items subject to deductions and disputes) separately.

Cforia Software shares a business improvement process that will help your company better understand the meakeup of your Account Receivable Portfolio and improve the financial performance at the same time.

Attend Cforia’s webinar on May 20, 2009 as Chris Caparon, Vice President Professional Services, discusses the benefits of, and guidelines for seperately tracking clean and dirty receivables.

• Improve Cash Forecast Accuracy
• Avoid over statement of New Receivables Value
• Address auditor concerns about valid long term receivables by a means other than automatic write off’s
• Handling of Litigation Accounts
• Raise collector productivity and Cash Flow by calculating and prioritizing the correct amount to ask for
• Seed up routing to the Deductions Department and increase recover rate

A practical demonstation will show how Automation Tools can track Clean and Dirty Receivables separately.

Click Here to View Replay

DataXstream will be exhibiting with Cforia Software at the SAP Insider Show in Las Vegas, March 17 – 20th. Come and see how Cforia Software can improve your company’s financials.