Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics GP (Archived)

Moving AR transactions form one company to another

Posted on by 210

We currently maintain AR in a separate database from my GL, as it is maintained in a different currency and at startup MC was not available.  There are both receivables transactions (Credit Memos, Debit Memos, and Cash Payments) and SOP Invoices. Inventory is not being used.

We are now migrating the AR to the GL company.  The AR setup has already been done, and the customers with their beginning balances as at the end of July 2016 have already been loaded.  We will be going live starting with August so moving forward is not an issue

The problem is, we would like to carry over all transactions for 2016 into the new company to facilitate reporting or inquiries.  

what is the best way to achieve this?

*This post is locked for comments

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Moving AR transactions form one company to another

    Ok, I understand now.

    If you want to be able to run an AR aging in the new database it might make more sense to go back in and enter one debit memo per invoice. You'd use the original invoice date as the date on the debit memo. This way you can tie your AR in the old database to the AR in your new database and your aging report would look the exact same for July 31 in both databases.

    Otherwise,  in order to get an AR aging report that looks right you'd need to build either an Excel or SSRS version of your aging report that pulls data from both companies. In order for this report to work though you'd also need to enter cash receipts in both companies for any invoice that was in the old system. Same goes for any credits you give to the customer. Basically, you'd have to keep the AR in both companies in sync until all of the debit memos you entered in the new system were fully applied and in history.

  • Jackie McNab Profile Picture
    Jackie McNab 210 on at
    RE: Moving AR transactions form one company to another

    Your first scenario is correct, a single transaction (a debit memo) representing the $400 was entered for that customer.  

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Moving AR transactions form one company to another

    OK, let me make sure I understand with an example...

    Customer A has four unpaid invoices in the old database totaling $400, so in the new system one AR invoice was entered for $400. Is that correct? Or would you have entered each invoice separately?

  • Jackie McNab Profile Picture
    Jackie McNab 210 on at
    RE: Moving AR transactions form one company to another

    For startup, we added the customers with their current balances as at the end of July and the plan is to move on from there by inputting all transaction as of August 1st.

     

    There are no transactions on the system prior to the startup hence my first question, which was how could I get these transactions into the system,  having already applied and/or posted them in the old?   These transactions are already in the opening balances so I could not use IM to bring them in as batches to be processed.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Moving AR transactions form one company to another

    Hmm I'm not sure I understand. How did you convert open invoices? Did you just aggregate all of the invoices for each customer and post a lump sum?

  • Jackie McNab Profile Picture
    Jackie McNab 210 on at
    RE: Moving AR transactions form one company to another

    Hello Mike,

    As a follow up to my first question,  I agree that bringing in the historical data is risky and so we are leaving them in the old DB and moving forward,  However I do have one issue in relation to the ageing, that is of concern.   How can I have the ageing reflect the current position at the time that we cut over?  Is there any to incorporate that information?

    I expect that this should be possible but I am not aware of how this is done. 

  • Jackie McNab Profile Picture
    Jackie McNab 210 on at
    RE: Moving AR transactions form one company to another

    Michael,

    It is not a lot of history, but we wanted to keep this year's data all in one DB.  Unfortunately, IM is not an option as these trans have already been applied/posted so I can't go that route.  I agree that bringing the data over by any other means is risky as there is no validation being done.  

    Thanks for your response.

  • Verified answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Moving AR transactions form one company to another

    How much history is in the AR database, and is the AR database also a GP database?

    There are a number of things you can do, but I think your best bet is leaving the history in the separate AR database and running reports on the historical data as necessary.  If you have someone on staff who knows SQL, you could create SQL view that holds data from both companies. Check GP Table Reference to see which tables you'd need to include in those views. You may also need to have that person build some logic into the views that handles exchange rates. Again, I think leaving the data in the old database is your best bet.

    Getting the actual data out of the other database and into your new database might prove challenging. You could use integration manager to bring over AR transactions and SOP invoices. You'd then need to post them in GP, review and make sure everything ticks and ties to what's in the old database. Lastly you'd need to import cash receipts and apply/post. This could also be done manually. I'd recommend testing the heck out of any integration manager jobs too. I've never used IM for historical data.

    You could also have your dba build an SSIS package that moves the data from your old database to your new database. The risk here is that there's no GP validation like there is using IM. You could also do direct SQL insert. What you'd need to do is validate that you're not importing duplicate transaction numbers into your new database. Or you could just append an "_OLD" to each transaction number in your old data. Again, test the heck out of this one too.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans