Guidance Required for Uploading Adobe Contract Data in ServiceNow

[monica190]

Hi Team,
I need to upload Adobe contract data into ServiceNow. The customer has provided us with invoices from which we are expected to extract key information, such as the agreement number (which maps to the contract number in ServiceNow) and other relevant details.

However, I’ve noticed a few things on invoice particularly :

• The Purchase Order# does not appear to be unique.

• The Agreement Number is the same across three different invoices.

• Two invoices have the same Purchase Order#, while the third has a different one.

• Additionally, the Purchase Order# seems to be purchased date rather than a distinct identifier.

Each of the three invoices has different start and end terms, which adds to the confusion.

Could you please advise how I should proceed with uploading the contract data in such a scenario?

[andynewey]

Read these two pages as first steps.

ServiceNow SAM Entitlement Import User Guide - ServiceNow Community

Software Entitlements without a Publisher Part Number (PPN) - Product Knowledge

It will be your decision if you want to create duplicate entitlements, it should not affect your licence counts.

[monica190]

@andynewey Thank you for your response. I am referring to contracts not the entitlement data load

[dreinhardt]

Hi @monica190 

A somewhat strange approach by your customer, if I may say so. Normally you receive an extract or the entire contract document directly and can derive the most important attributes for the ServiceNow contract from this. In most cases, these are: contract number, start/end date, name/description , renewal details and possibly the person responsible, which is all you need to get started in SN.

The other attributes you mentioned refer to the software entitlement, which will probably also be added to your system in the next step based on the invoices.

hope this helps to get the correct attributes for your contract onboarding.

best, Dennis 

[monica190]

Hi @dreinhardt ,

Thank you for your response!

You're absolutely right, ideally, we would receive the full contract document with all the necessary attributes clearly outlined. However, in this case, the customer chose a different route. Every customer works differently, and sometimes they may not be fully familiar with the templates or processes we provide.

Although we had shared the standard template along with all the required field descriptions and reference values, they ended up providing only the invoices, which they intend to use as the basis for both contract and entitlement creation. So it was up to the BAs and dev team to derive the necessary contract details from those invoices and proceed accordingly.

Thanks again for your helpful insights!