x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 4 replies
  • Subscribers 13 subscribers
  • Views 952 views
  • Users 0 members are here
Browse Forums
Announcements
105
topics
4
replies
General Discussion
1k
topics
2k
replies
Lauren Eames

Sage 200 - Importing Supplier Transactions

Posted By

Hi everyone

The company I work for has recently moved over to Sage 200 and there's some little oddities we're having trouble fixing.

The main issue at the moment is importing supplier transactions. We've created the correct CSV file that Sage 200 will read, however when purchase invoices are imported against an account, they automatically have a query code of "U" against them. I know we can go into "Authorisation" and clear them that way, but the import file contains upwards of 200 purchase invoice transactions so it would probably be less time consuming just to manually type every line directly into Sage.

We've delved into the many settings within Sage 200 but haven't been able to find anything that will allow imported purchase invoice transactions to import as automatically authorised.

Could anyone give me an idea of how to get round or fix this issue please?

Many thanks in advance.

  • 0

    In the purchase ledger settings there is a setting that sets transactions to "U" if they are over a value. its on the Processing Tab. in the Purchase ledger settings

  • 0 in reply to Toby

    Hi Toby

    Thank you, this is what I thought too. However, I've set the limit to £1,000,000.00 and it still imports transactions with a "U" query code, regardless of amount. The only way I've found to get round it, is to untick the box, import the file and then re-tick the box when I'm done. But this feels like an unnecessary work round.

    We've just moved from Sage 50 where everything seemed much more straight forward and never came across problems like this.

  • 0 in reply to Lauren Eames

    hi,

    This is a known issue with the import Issue number 4457 .  it was first logged in 2011 and has not been fixed yet.  Contact your Sage support and get them to register you against the bug, and you will be notified when/if its ever resolved

  • 0 in reply to Toby

    Hi Toby

    Realistically, if the issue was first logged 10 years ago, it doesn't seem likely that a fix will ever be created. I'll log the bug through Sage support however, I will continue to use my work round.

    Thank you anyway.

*Community Hub is the new name for Sage City