Setup > Accounting > Accounting Lists Type = Term Then edit your term, and you'll see a '% Discount' & 'Days Till Discount Expires" field - these control your early payment settlement.

Has a "% Discount" been set in the Terms setup, allowing a discount for early payment?

Just noticed, that we're still getting a lot of... "We encountered an error trying to access your server at https://system.netsuite.com/app/external/google/notificationlistener.nl?c=XXXXXX -- the error we got is Send failed with code: 500. Response body was:" ...error messages appearing in the Google Integration Detail…

Getting the same problems here, the customer is being set up as a lead, but no sales order is being created. Google then reports the same; "We encountered an error trying to access your server at https://system.netsuite.com/app/external/google/notificationlistener.nl?c=XXXXXX -- the error we got is Send failed with code:…

Still entering my SOs manually, although having the customer data imported does stop this from been a massive pain. NS seem to have accepted it's an issue. Defect 165047 - GCO: using Google Checkout creates a Lead account but not the Sales Order; Google API reported Error: We encountered an error trying to access your…

Looking like the Thursday night upgrade fixed the problem. Our Google Checkout orders are now coming through complete with a SO. Anyone else noticing this?

Just started using this solution, and so far everything seems to be working great. My only question is regarding the "Category" that is sent to Google for each purchase line item. It's currently set as - var category = "<%=getCurrentAttribute('site','name') - which just sends the name of our store. Is there actually a way…

Digging out a very old thread here, but I have a related question. We are selling Matrix Items as 99% of our inventory - however, the quick-pick popup list which appears on the Sales Order, doesn't show us any child-specific data, such as size/color etc - instead we simply see a list of 6 identical descriptions along with…

This means the admin centre provided by your payment processor - in our case this is CyberSource. So now, for the next 3 days, we have to manually check over 500+ transactions everyday! So who's paying for the overtime this is going to cost us?

No need, it's back up now. Was down totally for 6 hours yesterday!

Is there any news on defect 241462? CyberSource are pressuring us to have a resolution in place ASAP.

Today I received what appears to be a full and final official statement about this issue from NS Support. On January 22 CyberSource released changes to their field-level validation requirements aimed at improving data integrity. As a result new rules surrounding the use of special characters have been introduced into their…

Here's a list of the new validated fields. http://support.cybersource.com/cybskb/index?page=content&id=C1251

This whole thing does seem to have been badly thought out by CyberSource, they claim it's to reduce failed transactions further doen the line - but we have never had a single failure from the bank due to a ( in the customer name! Because there are so many free-form fields involved with this, the only logical solution is…

Had a call from support yesterday, telling me basically the same. They claim they're not able to modify the outgoing data, and we should ensure that these fields are not present in our records! They also mentioned that they're asking CyberSource to not require NetSuite customers to have to use the new validation scheme at…

Sorry, I think someone is taking the P right now. Just received this in an email from NS Support, relating to this defect. "We found that the issue has to do with CyberSource field validations applied to incoming data. Since we cannot manipulate the data being submitted to CyberSource, the user needs to adjust their data…

has there been any further update to this? To be honest, I'm losing track of which defect this is now listed under as there seems to have been so many.

What's the special character you're having problems with? I've not heard anything from CYBS abut this change, did you receive an update notification or was it only after you saw errors?

The odd thing, is that we've only been getting this error on the ship_to_firstname field - and I have no idea at all why NetSuite is even sending this. As far as I can see, it's not even sending the ship_to_lastname field at all! I can see some logic in knowing the shipping details - for fraud detection etc, but seems odd…

I've just spoken to CyberSource regarding this. I had asked for specific data regarding these changes after their announcement email, and they have never sent anything through - they now claim that my email reply "got stuck" in their server :) However, because of this, and because we had no information to work with prior…

The more I look into this, the odder it seems to be. The field "shipTo_firstName" that NS sends over to CyberSource as part of the raw request, is actually the Addressee field from the shipping address record. The Bill to fields appear to be the "name on card" field parsed into two, so "Miss XXX YYY" becomes…

When I asked CyberSource for the changes they've made, so that we can ensure we comply with the new data validation, I got this wonderful reply.... We are unable to provide details on the exact changes that will be made as providing this information to the public has been flagged as an ongoing security concern. So, you're…

OK, looked through my transactions today, and I'm seeing the same issue. Any customers with non alphanumeric characters in their name are having their transactions refused. Here's a typical error report from CYBS; The following request field(s) is either invalid or missing: ship_to_firstname This one was caused by the…

We're currently implementing the Decision Manager Device FingerPrinting script. This obviously needs to sit on the final checkout page (which sits outside of NetSuite) - however we are struggling to understand how the SessionID which links the FingerPrint to the CyberSource payment transaction should be implemented. The…

The one thing we haven't been able to ascertain, is whether we can use one of the multiple custom fields for sending over this SessionID in the payment request sent to CyberSource through NetSuite. Are they able to match one of these up to the fingerprint session ID?

Just enter them as a regular customer - you can then use the CRM to try to market to them to try to increase their order rate :)

Have you considered logmein.com?

No, for 2-factor authentication it uses the RSA SecurID App.

I guess one option though, is to set up a very wide IP restriction for the users you want to exclude - 0.0.0.0-255.255.255.255 :)

holy cow this it annoying. I thought those question are incase you forgot or lost your password. Not if you changed computers or browsers. Some of my employees didn't like the question that where asked thought they where to personal. They would like an option to enter in there own question. Sadly, my experience with…