Our procurement and AP department is starting a Coupa implementation and I have been helping on the NS side. The implantation partners are having an issue with creating bills and expense reports due to us having the Department, Class, and Location mandatory as a global setting. Basically the integration fails since it doesn't know what DCL to place in the header. Supposedly the implementation partner has done 100's of NS integrations but we are the first to have this requirement. We are not willing to turn off this global setting, as it would cause issues with revenue mappings and AR. On the AP side how is the DCL from the header used in downstream transactions? I know that Amortizations and GL postings are driven off the transaction line, what issues would we cause if we just defaulted None, None, None in the header? Would it impact fx revaluations?

This may not be a valid answer to your question, but one possibility would be to turn off those global settings but enforce the Dept/Class/Location fields at the form level. That's what we've done from day one.

Oh good point, so if we turn off the global setting we could possibly change the form, then re-enable the global setting only removing the DCL from the Bill and expense report form? I tried to take it off the form but it wouldn't allow me to remove it, but I think the global policy was in place at the time

No I mean leave the global setting off, and set the fields as mandatory on the forms you need it to be. Again, it may not be a good solution for you, but I think it would get you around the implementation woes.

I know this is 25 days late but this is what we did.. these params are on the Coupa Invoice Integration Script. Your Coupa implementors should know what this means.

Thank you I have a feeling this is still an issue. They haven’t talked to me in some time