Oregon recognizes that reporting in XML may be an undue burden for some taxpayers. Therefore, Oregon allows the filing of a spreadsheet template to report the required information. Both filing types are filed on your ROL account.
Filing type 1: Oregon Uniformity spreadsheet
You can download the Oregon Uniformity spreadsheet, fill it out and upload it. After downloading it, open it and click "enable" to enable the edits to work.
When you upload the completed spreadsheet, all fields will again be validated.
Required fields are in orange, optional fields are blue. If a blue field has an asterisk, it is required. For example, if an address is foreign and you chose "yes," all fields with the asterisk must be completed before the spreadsheet will validate.
Cigarette and tobacco spreadsheet guide
Please review the DOR Excel Template User Guide for detailed information regarding the Oregon implementation of the Uniformity cigarette and tobacco filings.
Filing type 2: Oregon Uniformity XML
The data will be formatted using Extensible Markup Language (XML). The format of the XML is based on the FTA e-file standard for state e-file programs. It uses standard building blocks and standard packaging. This process is intended for participants with technical expertise to create and validate an XML document, or those using software that provides that service.
Zero or blank fields: You do not need to transmit any optional element that has a zero or is blank. Send data elements only if they contain data values. Do not send empty data elements (e.g., zero financial fields, unused elements, etc.).
Oregon does not use the timestamp. However, since it's mandatory in the Uniformity schema, the file will not validate if incorrect.
The timestamp represents an absolute moment in time when the file is created. It contains a reference to Greenwich Mean Time (GMT). The format is: ccyy-mm-ddThh:mm:ss-hh:mm, where:
- ccyy-mm-dd is the date;
- followed by "T";
- hh:mm:ss is the time (hours, minutes, seconds); and
- -hh:mm represents the offset from GMT in hours and minutes.
Example: April 12, 2011 at 3:50:23 PM CDT = 2011-04-12T15:50:23-05:00. Central Daylight Time is five hours behind GMT, thus the -05:00 at the end. This offset will vary by time zone and standard vs. daylight saving time.
Please review the Developer Guide
for detailed information regarding the Oregon implementation of the Uniformity schema.
- Ampersand (&) in the file, usually in a business name. An ampersand is a special reserved character in XML. It can still be used but must appear as "&" in the XML file.
- Timestamp format is incorrect. It MUST be ccyy-mm-ddThh:mm:ss-hh:mm where the final -hh:mm represents the GMT offset (number of hours behind GMT).
- Date format: XML date formats are always ccyy-mm-dd (January 8, 2011 = 2011-01-08).
- The values in most text fields in XML are of variable length and will not allow leading or trailing spaces (you will need to trim these off before writing to XML).
- OR license numbers are seven digits. Oregon account numbers for filers who don't need a license are 10 digits. The Oregon identifier must exactly match the Oregon identifier on your ROL account.