Deleting an open credit memo invoice using a VI import job

SOLVED

I am using MAS 200 4.10.  We are automating our RMA process, and currently are creating credit memos through a VI import job.  That is working fine.  Now I am expanding the function to include automating credits to customer credit cards.  The problem here is that the credit memo has to be created first to get the value MAS generates for sales tax so that the credit will have the correct amount.  But the credit can then fail because the customer has since decided to have their card info deleted, or because the card has expired, and then the credit memo is no longer valid and may be deleted if we can't get the required information to complete the credit.

I am looking for a way to delete the open credit memo through a VI import job, just as if a user had chosen to hit the delete button and confirmed the deletion.  I hoped that running an import to update the credit memo and give it a type of XD would work, but changing the invoice type is not allowed.  Is there a way to do what I want?  At this point I'm trying to find a perform function that will do the trick, but I'm not hopeful.

Thank you in advance for any assistance.

Parents Reply Children
  • 0 in reply to BigLouie

    We didn't have access to the keys or the serial numbers online, at least at the time, and we've given up on Sage.  Multiple calls boiled down to Sage doesn't support MAS if you bought it through a reseller.  We were told the reseller should provide us with the key, but he still refused to do so until we renewed, and raised the price $4000.  I have very uncomplimentary things to say about Sage, MAS, and our reseller, but I'm stuck having to work with MAS until we get to a point where I can't make it do something we need it to do.

    Thank you, though.  You and many others here are very helpful.

  • 0 in reply to Keith Tyra

    Keith, have you gone here customers.sagenorthamerica.com  and created an account, yes or no?

  • 0 in reply to BigLouie

    It had a different URL at the time, as it was before the December 2011 rebranding, but yes.  it had pretty much the same information available as MAS:  the product key, agreement end date, total user count, module list, and our first registration information; but no BOI key.  At this point I have no interest in the BOI key anyway.  We are switching from MAS, it is just a question of when.