SSTGB Technology Guide (SST160.9)

October 6, 2022

Created and Maintained by: Streamlined Sales Tax Certification and Registration Committee

Written January 2006; Revised September 2011; September 2013; May 2016; May 2018; December 2018; August 2019; January 2021; May 2021; May 2022, October 2022

---

Table of Contents

• Chapter 1: Introduction
• Chapter 2: State Checklist
• Chapter 3: Change Control Process
• Chapter 4: Certification Testing
• Chapter 5: Rates and Boundary Databases
• Chapter 6: SST Simplified Return Transmissions: SER
• Chapter 7: Simplified Return Transmission: Financial Transaction
• Chapter 8: SST Receipt
• Chapter 9: SSTP Acknowledgement
• Chapter 10: Communications Technology: SER
• Chapter 11: Web Service Implementation: SER
• Chapter 12: Registration
• Chapter 13: Communications Technology: Registration
• Chapter 14: Bulk Registration Rules (CSP USE ONLY)
• Chapter 15: CSP Query, Extract and Fail to Pay Notices
• Chapter 16: SST2015V01 XML Schema Prints
• Chapter 17: SST Definitions

---

Resources

• Surveys: Available in SST Library at http://www.streamlinedsalestax.org/ ↗ and in SST ShareFile under Certification Committee at https://sstgb.sharefile.com/login.aspx ↗
• Official XML schemas and Minimal Required Error Messages: Available on the FTA E-Standards (formerly TIGERS) website at http://www.statemef.com ↗, under Index of E-Standards XML Schema Packages, Sales and Excise, Streamlined Sales
• Technology Guide: Available on the Streamlined Sales Tax website
• Current Schema Set: SST2015V01
• Basic SER Fields list: Available on SST website

---

Chapter 1: Introduction

Document Purpose

The purpose of this document is to serve as a technical implementation guide for a State to use in complying with the Streamlined Sales and Use Tax Agreement's (SSUTA) requirements for use of the Streamlined Sales Tax Registration System (SSTRS), the Simplified Electronic Return (SER), and the Rates and Boundary Databases.

Executive Summary / Project Overview

State governments, with input from local governments and the private sector, created Streamlined Sales Tax to simplify and modernize sales and use tax collection and administration. The organization focuses on improving sales and use tax administration systems for both main street and remote sellers for all types of commerce.

Key Features of SST

• Uniform definitions of sales and use tax terms
• Rate simplification
• Uniformity of state and local tax bases
• State level tax administration of all state and local sales and use taxes
• Uniform sourcing rules
• Uniform administration of exempt sales
• A central electronic registration system for all member states
• Simplified tax returns and tax remittances
• State funding of the system

For a complete description of the Streamlined Sales Tax organization and the SSUTA please go to www.streamlinedsalestax.org ↗.

Contacts

Testing Central: The administrative section of the Governing Board staff responsible for managing and documenting the communication between the states and the CSPs including items such as certification of product categories and rate or boundary file issues.

Certification Committee: Advises the Governing Board on matters pertaining to the certification and recertification of service providers and automated systems. Reviews and discusses all issues concerning:

• Certification of the CSPs or CAS providers
• The Registration system
• The use and transmission of simplified electronic returns (SER)
• The rate and boundary files

Each member state should have a representative that participates in the Certification Committee. The chair of the committee is appointed annually by the President, with approval of the Executive Committee.

---

Chapter 2: State Checklist

State Action Items for Implementation

What a state needs to know and do to implement the streamlined sales tax program:

1. Review Information

• Streamlined website: www.streamlinedsalestax.org ↗
• Streamlined Sales and Use Tax Agreement (SSUTA)
• Streamlined Sales Tax Governing Board Rules and Procedures (including appendices)
• SST Technology Guide and associated links and information

2. Establish Contacts

• Contact your state's Streamlined Sales Tax participant(s)
• Contact SST Testing Central for technology questions
• Participate in SST Certification Committee Meetings
• Participate in FTA E-Standards group (formerly TIGERS)
• Form an SST Implementation Team with business and technology members
• Establish contacts with current member states

3. Technology

• Commit to using the SST technology standards and the established Change Control process
• Web services is the required standard for receiving registration data and SERs
• Obtain technical training in SOAP, XML, and communications technologies

4. Audit and Operational Procedures

• Determine necessary changes to existing processing and audit systems
• Determine changes to operational processes, error corrections, and audit processes

5. Rates & Boundary Databases

• See Chapter 5 for instructions
• Determine requirements for rates and boundaries database (Zip/Zip+4 or address-level)
• Publish databases using standards in Chapter 5
• Upload copies to sstgb.sharefile.com
• Provide methods to download the entire database

6. Registration

• Design and develop technology to process Streamlined registrations
• Test with the SST registration system

7. Simplified Electronic Return (SER)

• Design, develop, and test technology to process a SER
• SER data may contain less data than currently required

8. Payments

• Design, develop, and test technology to process electronic payments including:
  • ACH Debit payments
  • ACH Credit payments
  • Bulk payments

9. Certification Testing

• All SST Full, Contingent and Associate Member states conduct testing and certification
• Appoint an active representative on the Certification Committee
• States joining after initial certification must certify all current CSPs and CAS providers

10. Education

Internal:

• Educate Department employees on SST requirements, processes, definitions
• Establish contacts for SST questions
• Develop guidelines to process SERs, payments, and registrations

External:

• Educate sellers on law changes
• Make sellers aware of online taxability matrix and certificate of compliance
• Prepare educational information for mail and website

Sample State Information Document

States should develop and post a State Information Document including:

1. Introduction (join date, program description)
2. Contact Personnel
3. Developer Responsibilities
4. Publications (URLs for certificate of compliance, taxability matrix, rates & boundaries)
5. Filing of SERs
6. Payment Handling and Acceptance
7. Acknowledgement System
8. URL of State's Registration System
9. State Sales and Use Filing Program
10. Appendix (file size limits, jurisdiction codes, sample XML documents)

---

Chapter 3: Change Control Process

Overview

The SST Governing Board governs all aspects of the SST schemas and the SSTRS.

Process

1. States, vendors, and service providers requesting changes should discuss with the SST IT Director
2. Proposed changes are referred to the Certification Committee
3. Committee reviews, determines necessity, and presents to SST Governing Board
4. Governing Board approves or disapproves the change
5. Approved changes are sent to FTA E-Standards and discussed at their meeting
6. New schema versions are posted to FTA E-Standards website and SST Technology page
7. Testing Central coordinates implementation of all changes

---

Chapter 4: Certification Testing

Certification testing for CSPs and CAS providers and applicants is conducted in accordance with Article V of the SSUTA through a joint effort of all SST Full, Contingent and Associate member states as described in Rule 501 of the SSTGB Rules and Procedures.

See Appendix E of the SSTGB Rules for the testing process for applicants, recertification, and quarterly testing.

Test Decks

Appendix E provides details on Test Deck usage. Test decks determine if the CSP has correct tax rules, can properly source transactions, and calculates tax correctly.

Tax Rule Testing

At a minimum, all states should have a quarterly test deck that includes all tax rules listed in the Taxability Matrix: Library of Definitions (excluding lines 11110+, 11120+, 11130+, 31000, 32000, 31121, and 41045).

Tips for Testing Tax Rules:

• Assign record numbers in order (smallest to largest)
• Use a valid SSTID assigned to your state
• Use a valid, standardized address (e.g., your office address)
• Use the same address for all taxability rules
• Use Customer Entity Code "T" for all tax rule testing

Sourcing Testing (Tax Jurisdictions and Rates)

States may test as many addresses for sourcing as they feel necessary.

Tips:

• Use valid addresses (streets, PO Boxes, rural addresses)
• Use a reference code for a taxable item
• Use Customer Entity Code "T"
• Order received address is for states with Origin Sourcing only

Exemptions Testing

Test if Customer Entity Code "E" returns no tax. Recommended to use only on one or two lines.

Tax Calculations (Rounding)

Rounding is based on the 3rd decimal, rounded up or down.

Examples:

• $687.35 × 5% = 34.365 → rounds to $34.37
• $687.55 × 5% = 34.3775 → rounds to $34.38
• $27.40 × 6% = 13.524 → rounds to $13.52
• $27.29 × 5% = 1.3645 → rounds to $1.36

Test Deck File Format

• Save as .csv file
• File naming: [StateAbbr][Year]Q[Quarter] (e.g., AR22Q1)
• Send to Testing Central (testingcentral@sstgb.org) by the 25th of the 2nd month of each quarter

Results File Format

Beginning December 2022, the Error Code/Comments column is added to keep all listings in the same order as provided by states.

---

Chapter 5: Rates and Boundary Databases

I. Overview

The SSUTA requires states develop and maintain rate and boundary files for use in determining tax rates based on destination or origin sourced sales.

Key Points

1. State requirements for creating and maintaining databases
2. Format requirements for rate and boundary databases
3. When and where databases are to be posted
4. How to use files to determine taxing jurisdictions and rates

II. Summary of Agreement Language

A. State and Local Tax Bases (SSUTA Section 302)

• Local jurisdiction tax base must be identical to state tax base (unless prohibited by federal law)
• Exceptions: fuel for motor vehicles/aircraft/locomotives/watercraft, electricity, piped gas, motor vehicles, aircraft, watercraft, modular/manufactured/mobile homes, energy for manufacturing

B. State and Local Tax Rates (SSUTA Section 308)

• No multiple state sales/use tax rates except for food/drugs
• Only one local sales tax rate and one local use tax rate per jurisdiction
• Local sales and use tax rates must be identical

C. Notice for State Tax Changes (SSUTA Section 304)

• Provide sellers with as much notice as practicable
• Limit effective dates to first day of calendar quarter

D. Local Rate and Boundary Changes (SSUTA Section 305)

• Rate changes effective first day of calendar quarter after minimum 60 days' notice
• Boundary changes effective first day of calendar quarter after minimum 60 days' notice
• 120 days' notice for printed catalog purchases

III. Database Requirements

States must provide and maintain:

• Database assigning each 5-digit and 9-digit zip code to proper FIPS codes
• Optional address-level database
• Database of all sales and use tax rates for all jurisdictions

IV. Technical Directions

A. Database Format

• Standard relational table format
• CSV format (comma delimited)
• Fields must NOT be truncated
• Leading zeros must be included

B. File Names

Format: [StateAbbr][R/B/A][Year]Q[Quarter][Month][Day]

• R = Rate file
• B = Boundary file
• A = Alternate Boundary file

Example: ARR2021Q1NOV27 (Arkansas Rate File for Q1 2021, uploaded November 27)

C. Database Location and Posting Dates

• Must be available by first day of month prior to calendar quarter
• Available at https://sstgb.sharefile.com/ ↗
• Public access at streamlinedsalestax.org

V. Boundary Database Format

Record Types

"A" - Address Level Records

• Most specific level
• Contains full address information
• Zip extension fields are null

"4" - 9-Digit Zip Code Records

• Street name field is null
• Used as fallback when address not found
• Contains lowest rates for that 9-digit zip

"Z" - 5-Digit Zip Code Records

• Street name and zip extension fields are null
• Contains lowest rates for that zip code
• Used as final fallback

Key Fields (54 columns total)

VI. Rate Database Format

The rate database contains tax rates for each jurisdiction FIPS code.

Rate Format: Decimal fractions (e.g., 5% = 0.0500). Do NOT include % sign.

VII. Taxing Authority Type Codes (X12 Data Element 1721)

VIII. Calculating Tax

1. Query boundary database for FIPS codes
2. Query rate database for rates using FIPS codes
3. Calculate tax for each FIPS code separately
4. Sum all jurisdiction taxes for total

IX. Alternate Boundary File

For products with different rate or base as allowed by SSUTA Sections 302 and 308.

Products that may have alternate rates:

• Fuel (MV, Aircraft, Locomotive, Watercraft)
• Electricity
• Piped Natural/Artificial Gas
• Other Fuels
• Motor Vehicle
• Aircraft
• Watercraft
• Modular Homes
• Manufactured Homes
• Energy Manufacturing
• Food

---

Chapter 6: SST Simplified Return Transmissions: SER

SSUTA Section 318 Requirements

1. Each state must offer at least two methods of filing
2. States must accept SER from any CSP and any registered seller
3. Local returns may not be required in addition to state filing
4. Due date no earlier than 20th of following month
5. SER may have negative tax due
6. State may require electronic payment
7. SER submission is part of CSP/CAS certification

Who Can Use SER?

• Any seller may use SER (as of January 1, 2013)
• Model 1 sellers: CSP must file monthly for each member state
• Model 2 and Model 3 sellers: Must file monthly for each member state
• Model 4 sellers: May file SER or use other methods

Filing Architecture

Each transmission contains:

1. Transmission Header (Required)
2. Simplified Return Document(s) (Required) - containing:
   • SER without Financial Transaction
   • SER with Financial Transaction
   • Financial Transaction (payment only)
3. Financial Transaction - bulk payment (Optional)

Data Elements

1. Transmission Header

• TransmissionId: Transmitter ID + Julian date (5 char) + unique identifier (6 char)
• TimeStamp: Optional
• Transmitter ETIN: Required (SSTPID, CSPID, or FEIN)
• ProcessType: T (Test) or P (Production)
• DocumentCount: Number of documents
• TransmissionPaymentHash: Optional (ACH Debit only)

2. SSTFilingHeader

• ElectronicPostmark: Required - date return transmitted
• Tax Period Start/End Dates: Required
• DateReceived: Optional (state use)
• Preparer: Optional
• FilingType: SER without payment, SER with payment, payment only, or resend
• SSTPID or StateID: One required
• TIN: FEIN or SSN - Required
• FIPSCode: Required - 2-digit state code

3. SimplifiedElectronicReturn

• ReturnType: O (Original) or A (Amended)
• TotalSales: Required (may be negative)
• ExemptionsDeductions: Required
• Exemption Deduction Breakout (Part 2): Optional (states may require)
  • Agriculture
  • Direct Pay
  • Government/Exempt Organization
  • Manufacturing
  • Resale
  • Other
• TaxableSales: Required (may be negative)
• StateTaxDueSalesInState: Required
• StateTaxDueOrigOutOfState: Required
• StateTaxDueOwnPurchWithdraw: Required (consumer use tax)
• StateTaxDueFoodDrug: For states with separate food/drug rate
• JurisdictionDetail: Required for states with local jurisdictions
  • Jurisdiction Code (FIPS)
  • JurisTaxDueSalesInState
  • JurisTaxDueSalesOrigOutOfState
  • JurisTaxDueOwnPurchWithdraw
• TotalTaxDue: Required (may be negative)
• InterestDue: State-specific
• PenaltyDue: State-specific
• Discounts: State allowances
• SSTPAllowance: For CSPs and CAS
• PriorPayments: State-specific
• NewPrepayments: State-specific
• AmountDueOrRefund: Required

---

Chapter 7: Simplified Return Transmission: Financial Transaction

SSUTA Section 319 Requirements

1. Allow electronic payments by ACH Credit and ACH Debit
2. Provide alternate method for same-day payments (Fedwire)
3. Due dates falling on weekends/holidays extend to next business day
4. Uniform tax type and payment type codes
5. Only one remittance per return (with exceptions for large sellers)

Financial Transaction Options

1. State Payment (ACH Debit)

• Type of Account (Checking/Savings)
• RoutingTransitNumber
• BankAccountNumber
• PaymentAmount
• IdentificationNumber (Optional)
• AccountHolderName (Optional)
• RequestedPaymentDate (Optional)
• AddendaRecord (Required)

2. RefundDirectDeposit

Not available at this time.

3. ACHCreditInfo

• PaymentAmount
• IdentificationNumber (Optional)
• RequestedPaymentDate (Optional)
• AddendaRecord (Required)

AddendaRecord Fields (Required)

• SellerIdentification: SSTID or State License Number
• TaxTypeCode: Sales/Use Tax Type
• TaxPeriodEndDate
• Amount: Payment for this account

Bulk Payments

A single payment covering multiple SERs in the same transmission. The bulk payment amount must equal the sum of all SERs without individual payments.

---

Chapter 8: SST Receipt

The receipt confirms the communications system was functioning correctly but does NOT indicate acceptance or rejection of the filing.

---

Chapter 9: SSTP Acknowledgement

The acknowledgement indicates:

• If the transmission was accepted or rejected
• If any document within the transmission was rejected
• Error codes and descriptions for rejections

---

Chapter 10: Communications Technology: SER

Requirements

States must implement technology to receive SERs using web services as the standardized transmission process.

---

Chapter 11: Web Service Implementation: SER

WSDL and Implementation

Web services definition language (WSDL) is posted for states to adapt. Uses HTTP/S protocol with SSL encryption.

---

Chapter 12: Registration

Streamlined Sales Tax Registration System (SSTRS)

Azavar hosts the SSTRS and makes registration data available to participating states using SOAP enveloping and Registration schemas.

Registration Document Types

RegNew (New Registration)

Contains all seller information for a new registration.

RegCou (Change of Use)

Contains changes to an existing registration with Action Codes:

• C - Change (address update, state indicator changes)
• U - Unregister/Unvolunteer from selected states
• O - Out of Business (close entire account)

Key Registration Fields

• SSTPID: Unique SST identifier (S########)
• TIN: Federal Tax Identification Number (FEIN or SSN)
• BusinessName / IndividualName
• DBAName: Doing Business As
• PhysicalAddress / MailingAddress
• NAICSCode: Business classification
• StateIncorporated
• TechnologyModel: Model 1, 2, 3, or 4
• StateRegistrationIndicator: Per-state registration details
  • RegistrationIndicator (R=Registering, A=Already Registered, N=Not Registering)
  • FirstSalesDate
  • RemoteSellerID (Y/N)
  • SSTPAllowanceIndicator (Y/N/U)

---

Chapter 13: Communications Technology: Registration

State Access to SSTRS

Each Streamlined Full, Associate, and Contingent Member state has direct access to their SSTRS state administration page.

Key Points:

• Each state has an assigned administrator
• Administrators can add/delete users
• States must designate person(s) to receive Fail to Pay Notices
• Usernames cannot be changed; emails and passwords can be changed

Registration Queries

States may query SST registrations based on:

• SSTID
• FEIN/SSN
• Business Name

Query Options:

• Active SSTIDs only
• Inactive SSTIDs only
• Either (recommended)

Wildcard Character: %

Obtaining Data from SSTRS

Recommended: Web Services

The SSTRS provides a web service to "push" SOAP messages to the state. The state implements a web service client using WSDL from https://github.com/azavar/SST-API ↗

Alternate: HTTP/S Download

State logs onto SSTRS website to download registration files using secure HTTP/S.

GetDocuments Request

AcknowledgementStatus codes:

• U (Unacknowledged): Documents not yet acknowledged or rejected
• A (Acknowledged): Most recent acknowledged documents
• R (Rejected): Most recent rejected documents
• Z (All): All documents regardless of status

AcknowledgeTransmission

• A: Acknowledge (received and processed)
• R: Reject (with reasons)

Rules:

• R3: Fails if more recent document already acknowledged/rejected
• R4: Fails if older unacknowledged document with ActionCode=N exists
• R5: Acknowledging implicitly acknowledges all older documents with same SSTPID
• R6: Rejecting does not affect other documents

Processing Order

Documents in a transmission are ordered by date (oldest first). Process in this order to correctly acknowledge all documents.

---

Chapter 14: Bulk Registration Rules (CSP USE ONLY)

Overview

Certified Service Providers (CSPs) and Certified Automated Systems (CAS) use bulk registration to:

1. Register a seller as Model 1
2. Become CSP/CAS for an existing seller
3. Set allowance indicators
4. Update seller registration
5. Stop being seller's CSP/CAS
6. Unregister seller from selected/all states
7. Close seller's SSTRS account

General Rules

• Only available for certified service providers
• TransmissionId/DocumentId format: Service Provider ID (9 char) + Year (2) + Julian Day (3) + Sequence (6)
• TransmissionId/DocumentId cannot be reused
• EffectiveDate must be current date

Create New Registration (BulkNEW) - Action Code "N"

Required Fields:

• RegistrationEntity
• BusinessName (or IndividualName)
• DBAName (if applicable)
• NAICSCode
• PhysicalAddress / MailingAddress
• SellerPhone
• SSTPContact
• StateIncorporated
• TechnologyModel
• StateRegistrationIndicator for each state (State, RegistrationIndicator, FirstSalesDate, RemoteSellerID, SSTPAllowanceIndicator)
• EffectiveDate
• FirstFilingPeriod
• NewPass (8-10 characters, alphanumeric, case sensitive)

Document Structure:

<BulkRegistrationDocument>
  <DocumentType>BulkRegistrationNew</DocumentType>
  <BulkRegistrationHeader>
    <FilingType>BulkRegNew</FilingType>
  </BulkRegistrationHeader>
  <BulkRegistrationNew>
    <ActionCode>N</ActionCode>
    ...
  </BulkRegistrationNew>
</BulkRegistrationDocument>

Change Registration (BulkCOU) - Action Code "C"

Used for:

• Start managing an existing registration
• Update business info
• Update state registration info
• Register for additional states
• End managing a registration

Document Structure:

<BulkRegistrationDocument>
  <DocumentType>BulkRegistrationCOU</DocumentType>
  <BulkRegistrationHeader>
    <FilingType>BulkRegCOU</FilingType>
  </BulkRegistrationHeader>
  <BulkRegistrationCOU>
    <ActionCode>C</ActionCode>
    <SSTPID>S########</SSTPID>
    ...
  </BulkRegistrationCOU>
</BulkRegistrationDocument>

Unvolunteer/Unregister (BulkCOU) - Action Code "U"

Ends registration for selected or all states.

Required Fields:

• StateIndicators with LastSaleDate for each state being unregistered
• StateAcctInd (Y to remain registered in individual state, N to close)

Out of Business (BulkCOU) - Action Code "O"

Closes account and flags as out of business for ALL states.

Required Fields:

• StateIndicators with AcctCloseDate for each state (must be same for all)
• AcctCloseDate must be last day of current or prior month

State Indicator Fields

---

Chapter 15: CSP Query, Extract and Fail to Pay Notices

CSP Menu Options

My Account

• Change phone number, email, password
• Set security questions

Query Registrations

Search registrations by:

• SSTID
• FEIN/SSN
• Business Name

Search Results:

• If CSP is current or last CSP: Full registration information displayed
• If exact match but different CSP: Warning displayed
• No match: No listing or warning

Export to Excel

Export provides all account information including:

• Names and addresses
• Contact information
• All state registration indicators

Fail to Pay Notices

CSPs can submit Fail to Pay Notices through SSTRS when a seller fails to pay as required.

Process:

1. Log in to SSTRS
2. Navigate to Fail to Pay section
3. Select account and enter details
4. Submit notice

States designated to receive notices will be notified automatically.

---

Chapter 16: SST2015V01 XML Schema Prints

Available Schemas

• Registration Schema
• Bulk Registration Schema
• Simplified Return Schema
• Financial Transaction Schema
• Receipt Schema
• Acknowledgement Schema

All schemas available at:

• FTA E-Standards: http://www.statemef.com ↗
• SST Website: Technology section
• GitHub: https://github.com/azavar/SST-API ↗

---

Chapter 17: SST Definitions

Key Terms

SSTRS: Streamlined Sales Tax Registration System - Central electronic registration for all member states

SSTPID: SST Participant ID - Unique identifier assigned to each seller (format: S########)

CSP: Certified Service Provider - Third-party provider certified to calculate and remit sales tax for sellers

CAS: Certified Automated System - Software certified to calculate sales tax

SER: Simplified Electronic Return - Uniform return format for all member states

FIPS Code: Federal Information Processing Standards code - Unique jurisdiction identifier

Technology Models:

• Model 1: Seller uses CSP to calculate tax, file returns, and remit tax
• Model 2: Seller uses CAS to calculate tax; seller files and remits
• Model 3: Seller uses CAS and files SER but uses own remittance system
• Model 4: Seller does not use CSP or CAS

Action Codes:

• N: New registration
• C: Change/update
• U: Unregister/Unvolunteer
• O: Out of Business

Registration Indicators:

• R: Registering (new to state)
• A: Already Registered (has existing state registration)
• N: Not Registering

---

Appendix: XML Examples

BulkRegistrationNew Example

<?xml version="1.0" encoding="utf-16"?>
<BulkRegistrationTransmission xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  transmissionVersion="SST2015V01">

  <TransmissionHeader>
    <TransmissionId>CSP00000119178000011</TransmissionId>
    <Transmitter>
      <ETIN>CSP000001</ETIN>
    </Transmitter>
    <ProcessType>T</ProcessType>
    <DocumentCount>1</DocumentCount>
  </TransmissionHeader>

  <BulkRegistrationDocument>
    <DocumentId>CSP00000119178000011</DocumentId>
    <DocumentType>BulkRegistrationNew</DocumentType>

    <BulkRegistrationHeader>
      <ElectronicPostmark CSPID="CSP000001">2019-06-27</ElectronicPostmark>
      <FilingType>BulkRegNew</FilingType>
      <TIN TypeTIN="FEIN">
        <FedTIN>460001085</FedTIN>
      </TIN>
    </BulkRegistrationHeader>

    <BulkRegistrationNew>
      <ActionCode>N</ActionCode>
      <RegistrationEntity>CO</RegistrationEntity>
      <BusinessName>NAME</BusinessName>
      <NAICSCode>666000</NAICSCode>
      <PhysicalAddress>
        <USAddress>
          <AddressLine1Txt>Address 1</AddressLine1Txt>
          <CityNm>Anywhere</CityNm>
          <StateAbbreviationCd>SD</StateAbbreviationCd>
          <ZIPCd>57501</ZIPCd>
        </USAddress>
      </PhysicalAddress>
      <MailingAddress>
        <USAddress>
          <AddressLine1Txt>1 Mail Address</AddressLine1Txt>
          <CityNm>Anywhere</CityNm>
          <StateAbbreviationCd>SD</StateAbbreviationCd>
          <ZIPCd>57501</ZIPCd>
        </USAddress>
      </MailingAddress>
      <SellerPhone>6053550555</SellerPhone>
      <SSTPContact>
        <ContactName>
          <FirstName>Contact Name</FirstName>
          <LastName>Last Name</LastName>
        </ContactName>
        <ContactPhone>6053550555</ContactPhone>
        <ContactEmail>email@sstgb.org</ContactEmail>
      </SSTPContact>
      <StateIncorporated>SD</StateIncorporated>
      <TechnologyModel>
        <ModelOne CSPCode="CSP000001" />
      </TechnologyModel>
      <StateRegistrationIndicator>
        <State>AR</State>
        <RegistrationIndicator>R</RegistrationIndicator>
        <FirstSalesDate>2019-06-27</FirstSalesDate>
        <RemoteSellerID>Y</RemoteSellerID>
        <RemoteEffDate>2019-06-27</RemoteEffDate>
        <SSTPAllowanceIndicator>Y</SSTPAllowanceIndicator>
      </StateRegistrationIndicator>
      <StateRegistrationIndicator>
        <State>GA</State>
        <RegistrationIndicator>R</RegistrationIndicator>
        <FirstSalesDate>2019-07-01</FirstSalesDate>
        <RemoteSellerID>N</RemoteSellerID>
        <SSTPAllowanceIndicator>N</SSTPAllowanceIndicator>
      </StateRegistrationIndicator>
      <EffectiveDate>2019-06-27</EffectiveDate>
      <FirstFilingPeriod>2019-06</FirstFilingPeriod>
      <NewPass>Testing1</NewPass>
    </BulkRegistrationNew>
  </BulkRegistrationDocument>
</BulkRegistrationTransmission>

Acknowledgement Example

<SSTPAcknowledgement xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:noNamespaceSchemaLocation="http://www.sstregister.org/services/SSTP2010V01/SSTPAcknowledgement.xsd"
  acknowledgementVersion="SST2015V01">

  <AcknowledgementHeader>
    <AcknowledgementTimestamp>20xx-mm-ddT00:00:00</AcknowledgementTimestamp>
    <AcknowledgementCount>##</AcknowledgementCount>
  </AcknowledgementHeader>

  <TransmissionAcknowledgement>
    <TransmissionId>###</TransmissionId>
    <TransmissionStatus>A</TransmissionStatus>
  </TransmissionAcknowledgement>

  <DocumentAcknowledgement>
    <DocumentId>###</DocumentId>
    <SSTPID>S########</SSTPID>
    <DocumentType>SSTPRegistration</DocumentType>
    <DocumentStatus>A</DocumentStatus>
    <PaymentIndicator>N</PaymentIndicator>
  </DocumentAcknowledgement>
</SSTPAcknowledgement>

---

Contact Information

SST Testing Central: testingcentral@sstgb.org

SST Website: https://www.streamlinedsalestax.org/ ↗

SST ShareFile: https://sstgb.sharefile.com/ ↗

FTA E-Standards: http://www.statemef.com ↗

SST API (GitHub): https://github.com/azavar/SST-API ↗