11 code 070 no usable address

© 2019 - State of Utah - Department of Technology Services
Jump to navigation Jump to search

No Usable Address - Code 070

This is a BLS combination edit. It is intended to group the results of several edits together into a common linkage. A number of edit exceptions deal with errors in address format, whether that is a physical location address, a mailing/other address, or a U-I tax address. This edit is enacted when none of the three addresses is “usable.” That means each address block is either blank or unable to pass through the edits successfully.

Note: Federal government (ownership ‘10’) accounts are exempt from this edit.

The philosophy of the edit is that any account that possesses a usable address in any of the three address blocks should not need to appear on the edit exception report. A hierarchy has been established to denote the relative significance of an address. The most pertinent is the physical location address, followed by the Mailing/Other Address, and finally the U-I address. The reasoning behind this hierarchy is that a worksite physical address provides the most specific information about an address, whereas a mailing address is more valuable than the unverified and non-updateable U-I address. When one of the addresses is usable, those lower in the hierarchy need not be identified in the edit exception listings; however, those accounts with an address higher in the “pecking order” should still be noted. MOA and physical address errors will always appear in the Micro Edit File. If no other usable address exists, the U-I address edits will also be conducted and stored in the Micro Edit File.


An index is used in the edits to identify the availability of usable addresses. It is a composite value, summing values of:

  • 1 = U-I address (UIA) available and not flagged,
  • 2 = mailing/other address (MOA) available and not flagged, and
  • 4 = physical location address (PLA) available and not flagged.


This numbering scheme maintains the hierarchy of address relevance. The index is initially set to 7 (assuming that all addresses are available and error-free). Then the value is diminished as addresses show their non-usability. If the physical address block is blank, 4 is subtracted from the index, leaving a value of 3. If there is no associated MOA File record for the account, 2 is subtracted from the sum. A blank U-I address drops the sum by 1. This first round of subtractions is necessary to find out which address blocks are not blank. Since a blank address will not be flagged with any of the format errors (Codes 101 through 111), it could easily be interpreted that an account has a usable address if it is not able to be flagged. But then an establishment with no address information at all would never be identified as needing location data.


In order to flag this condition, the standard address edits must first be run. Although that places the Code 070 error after other higher-numbered (and hence, less significant) edit codes, it is necessary due to the nature of the edit. Another out-of-sync coding problem is the fact that address errors don’t follow the address hierarchy scheme. For instance, Code 106 deals with the lower-priority U-I address, while Code 109 relates to the mid-level mailing/other address. To process these in hierarchical sequence, the exception codes will not always be numerically sorted.


For each of the non-blank addresses, the associated format edits are run. When one of these is found to have a problem, not only is the edit code added to the list for the establishment, but the address availability index is also diminished. When all of the address edits have been completed, the usable address index is examined. If the index is set to zero, no usable address exists. That causes this edit code to be attached to the record in the Micro Edit record, assuming the current employment exceeds the PK069 cutoff. Since this has a default value of zero, any non-zero-employment establishment is eligible to be flagged.


The presence of a valid address is important. Therefore, this is classified as a crucial condition, which will keep appearing until it is remedied. This is also a “gross” error condition, provided the employment or total wage value for the employer meets or exceeds the PK067 or PK068 (respectively) cutoff parameter. BLS classification: A.1.4 or B.1.5, based on employer size. EXPO “G” code: A070 or B070.


Related Links