About file upload (XML/XLSX)

Uploading files

The Norwegian Industrial Property Office (NIPO) has developed new software enabling our larger customers to automatically upload or submit cases they wish to renew. You can upload an Excel file or XML file with a number of cases so that you can renew several cases without typing the case numbers one by one. The file may include both patent, trademarks and designs, and you can upload a maximum of 999 cases in one single file.

The file must be built on a structure defined in the template or the XML schemas you find on this page. The advantage is faster, simpler and more cost efficient system integration and more effective use of the service. 

Technical specifications Excel

This is a simple form of uploading. Excel files may be uploaded from your own system (requires IT development) or you can punch or paste data into the template.

The uploaded file must follow NIPO's simple standard so that the system will be able to read it correctly:

• Domain (patent, trademark or design) must be inserted by digit code in column A for each case (1=patent, 2=trademark, 3=design)
• Application number and/or registration number must be inserted in columns B and/or C
• Expected fee may be inserted in column D*, otherwise column D should be empty
• Listing of cases must start in row 10
• Numbers must be formatted as Text**
• The file format must be (*.XLSX)
  

*If you insert expected fee in column D this will be checked against NIPO's system, and you will be notified if any deviance is found.

**The reason that numbers must be formatted as text is that some registration numbers starts with a 0. Without text formatting prepositive 0 will be deleted and there is a risk that Payment retrieves incorrect case. Please mark relevant columns in Excel and right-click, choose "Format cells" and "Text" to format as text.

Domain and application number or registration number is sufficient for the system for find the correct case, and information about how much should be paid. Other fields may be used at your own desire.

• Template

Technical specifications XML

A key consideration is to create the lowest possible barrier for customers to develop their own integration to the Payment solution. We therefore have two versions of our schema:

• A simplified version, containing only the IDs required for specifying elements for renewal. This schema does not refer to WIPO standard ST.96, but is based on ST.96
• The second version contains a more comprehensive data structure, making it possible to include payment validation and data cleansing. This schema refers to WIPO standard ST.96

Note:
Note that we include all three areas (patents/trademarks/designs) in the same schema.
The element <CustomData> is ignored by the receiving system, and may be used to store any internal data for references from the exporting system.
The element <Order Receipt> should be removed. This will be used / filled with data when NIPO offers to download a receipt in the form of an XML file.

Schema options

Simplified schema

• Schema (XSD)
• Example file (XML)