AvaTax for Communications user manual SAU (Legacy)

Mapping

Prior to performing tax calculations, client transactions and services must be matched, or “mapped,” to the Valid Transaction and Service Pairings defined in AFC. Refer to Section 2 Mapping for the full explanation of how this is accomplished.

Transactions

Once the transactions and services have been mapped, transaction records can be passed to AFC.  Section 3 Transactions explains what AFC expects for each part (or field) contained in a transaction record and provides the definitions and reasons for selecting one of the valid options to use.

Tax Calculations

The AFC Engine accepts the transaction record(s) and performs the tax calculations based upon the information within the record.

Utilities

Once the taxation has been performed, Utilities can be used to provide the tax information in selected formats that meet specific requirements and perform file management functions. The many options available are detailed in the Utilities section of this document.

The Advantage of Using Functions

Section 7 provides specific details of the expanded capabilities provided to users that integrate AFC to the billing system using functions. Refer to the figure shown below. The billing system passes information to AFC, as calls are being rated for billing. AFC calculates all required taxes and returns the tax information to the billing system per transaction. In addition, AFC stores all tax data generated in its databases and provides reports that facilitate tax filing and provide insight to the rating, billing and taxing processes.

Figure 1-1 AFC Operation Diagram

Adjustment information is returned to the billing system and is utilized to update tax data for report generation and compliance filing. AFC also provides facilities that allow users to insert tax overrides and exempt a transaction from taxes at federal, state, county and local authority levels. AFC also provides the capability to limit exemptions to a specific jurisdiction and to exempt specific taxes.

Using the AFC API is the most efficient method available for interfacing with the AFC system. Due to the superior performance of AFC, there is very little performance difference between a system running without taxation and one running with taxation generation by AFC.

General Product Information

Enhanced Flexibility for Users

User reporting and organizational activities have been enhanced with the addition of user defined fields. This empowers the user to include additional user specific information within transaction records, thereby enhancing reports and data files once processed by the AFC Engine. Note that the Batch Processing utility takes full advantage of the additional transaction fields.

Enhanced Capabilities for Processing Specialized Taxes

AFC maintains tax rate histories and applies them according to the transaction date. This allows for tax calculations to process transactions that require dated tax information.

• Billable Flag – Allows for the identification of a compliance only tax or fee that is used for filing and not passed on to the user. It is noted as a non-billable item in the tax log.
• Compliance Flag – Allows for the identification of a tax or fee that is a tax compliant item and that the tax or fee should be sent to the log. The reporting utilities can identify and generate compliance and billing reports. All existing taxes currently in AFC are compliance taxes or fees. A charge with the compliance set to false in logic is billable but the charge would not be place into the log for compliance or reported in compliance reports.
• Rate at Final - Allows for a specialized application of tax brackets. Each bracket specifies the tax rate for the “Total Tax” range that it spans. The culmination of all of the brackets results in a tax rate “look-up” table for total transaction amounts.
• Tier At Transaction - This logic flag indicates that tax will be calculated using graduated tax brackets on a transaction basis instead of a customer invoice basis.
• Tax On Tax Until No Effect - Configuration settings in EZTax.cfg determine one of two methods to calculate Tax on Tax. If the configuration setting is left unchanged, AFC will perform a single iteration of the tax on tax calculation.

Additional Functions to Support New Capabilities

• The Get Rates function has been added to retrieve all possible taxes when given a location by PCode. The structure of the returned tax information is compatible with the new override structure, so that specific changes can be applied to the existing tax data to create override entries.

New Version Tracking

A version number has been embedded into the AFC database to ensure database compatibility between the AFC software and the AFC database. The AFC Engine compares version numbers on session initialization. If incompatible version numbers are detected, a message is written to the status file and AFC system will not return a valid session handle.

Additional Tax Types

AFC now supports over 450 Tax Types to allow for highly specific tax type designation.

Increased Accuracy

The Tax Amount calculations have been modified to increase accuracy and further reduce rounding errors.

File transervdescsau.txt

A file named transervdescsau.txt is present in the database directory in each month’s update. This file contains all of the valid transaction type/service type pairs, with the description of those types and of the pairing. It is a fixed format file, though there are spaces and commas between some of the fields for readability. It is described in the table below.

transervdescsau.txt File Format Key

Customer Number

The Customer Number is a 20-character null terminated string field stored in the tax log and used as the Primary Output Key for the AFC billing reports.

Customer Type

This field is used to specify the type of customer involved in the transaction. The customer type is selected from one of the following four Customer Types.

Customer Type

Exemption Levels

The exemption level is the jurisdictional level of the taxing authority that defines the tax. It is used to exempt taxes at specific state, county and/or local taxes.

Incorp

The Incorp field is used to specify whether the customer involved in this transaction is inside or outside of the Local level designated as their location. The tax may or may not be affected by this designator depending upon whether or not the local level has taxes which would apply to the transaction/service type pair.

Invoice Number

The Invoice Number is an optional field used to aid users in uniquely identifying a billing record for a specific customer within their system.

JCode Exemption Levels

The exemption JCode is the JCode associated with the jurisdictional level of the taxing authority that defines the tax. It is used to exempt all federal, state, county and / or local taxes. If the exemption JCode fields are not specified then all taxes are exempt at that level.

To pass an individual tax exemption using the JCode Exemption, use the Tax Exempt structure to specify the tax type, tax level, and the JCode for the jurisdiction. Refer to Section 4.1.1.2.

NOTE: JCodes are an internal intermediate Jurisdiction Code that can change monthly. The JCode can be obtained from a PCode or an address using like functions.

Tax Type Exemptions

Two fields are provided for entering the quantity of tax type exemptions and the pointers to the tax exemption structures.

Optional Fields

Optional Fields are provided to allow clients to enhance reporting and billing utilities with information beyond the scope of that which is generated to support AFC activities.

The Customer Number is a 20-character text field that is not manipulated during processing and stored as part of the log file record.

It can be used as part of the sorting key (see Figure 3-1) when using some utilities, allowing for the combining of records based upon this and other fields. It is useful when it is desired to have like taxes from different transactions combined, to have taxes from each transaction detailed individually in a report or to have each transaction detailed at the customer level.

Figure 3-1 Primary Output Key

Company Identifier

The Company Identifier field is an optional field made available for alpha information, such as the name of a subsidiary company. This information is passed thru to the tax log so that reporting utilities can sort or summarize by this field.

Attribute

The Attribute field refers to ancillary transactions related to the actual sale – freight, discounts, financing, installation, shipping/handling, maintenance and service contracts, and warranties.

Properties

Properties specify the details of the transaction’s Attribute.

Charge

The Charge field specifies the amount of the transaction to be taxed. This amount will be passed through AFC to rate the tax based on the specified transaction/service pair.

Date

The Date field is normally populated with the bill date. Generally accepted accounting principles dictate that liabilities should be recorded when revenues are recorded. In most cases, neither of these is recorded (or even known) until billing occurs.

However, companies with a high call volume that record revenue daily as it occurs should record the tax on the same basis (i.e. the call date should be used).

AFC compares this date to the effective date of each tax that applies to the transaction. Historical rates and effective dates are maintained and updated within the AFC Engine and AFC will return the correct tax information based upon the transaction date. The monthly updates assure that the rates and effective dates are current.

WARNING: All transaction data Date fields must be formatted as CCYYMMDD. Failure to do so will cause incorrect results when the transaction is processed.

Count

Number of items in the sale.

Sale Type

The following options are available as sales type:

Sales Type

Service Type

Refer to Transaction and Service Types for details of this field.

Transaction Type

Refer to Transaction and Service Types for details of this field.

To have exempt taxes available for reporting, Exemption Type 3 (Sales For Resale) should be used in combination with Resale.

The JCode Jurisdiction Identification

Avalara has assigned each jurisdiction with a proprietary “JCode” (Jurisdiction Code) that identifies its specific territorial boundaries. A jurisdiction fairly claiming nexus on a transaction within this boundary will apply taxes accordingly. The AFC Engine uses this “jurisdiction bound” JCode to associate the jurisdiction specific taxes to the transaction as it is processed.

However, any alterations in the jurisdictional boundaries, such as an expansion of a city limit, will be reflected in the JCode of locations that are situated within the expanded jurisdiction area.

The Avalara tax research staff monitors jurisdiction taxation activity to maintain current and accurate taxation information. The results of this research is applied to the Monthly updates which are provided to ensure the most accurate taxation is applied to the records processed by the AFC Engine. The JCodes will be changed at this time. It is the user’s responsibility to re-populate their database tables with the new JCodes every time an AFC update is provided. If this task is not performed, the AFC Engine will return incorrect tax calculations for jurisdictions that have been updated.

However, when a transaction is submitted with the stable and location sensitive PCode, the AFC Engine can use internal functions to obtain the correct jurisdiction. Since the AFC Engine is updated with the re- mapped jurisdiction information monthly, tax calculations are always performed with the most current jurisdiction taxation information that applies to the address defined by the PCode.

Figure 3-2 JCode and PCode Changes During Annexation

All that is required to make use of this recommended option is to cross reference or “map” the customer locations with its correct PCode. The time invested in incorporating PCodes into your database records will be quickly offset by the reduced processing time and the increased accuracy and reliability of your tax reporting will be evident.

Zip Codes

This method of providing jurisdiction information is the least efficient method provided. A record submitted using this method will compromise the accuracy of correct jurisdiction identification, the degree of which would depend upon the amount of data provided for the address and the user’s ability to select the correct taxing jurisdiction zip code and address. AFC databases necessarily contain numerous duplicate zip codes that cross taxing jurisdiction and locality boundaries. Providing a complete address with zip code will provide the best possible match. If the address information is not provided, AFC will return taxes based upon the first match of the input record information.

If the jurisdiction is positively identified by the billing system it would be appropriate to use the zip code for transactions. For instance, this would apply if the transaction is the sale of a product at a business that has just one location or in the case of internet usage from a residence.

AFC currently has Zip Code information for U.S. and Canadian jurisdictions. Use the Zip Code Plus 4 Interface to use the 6 character Canadian postal codes.

Zip Plus 4

Just as with the Zip Code method (see Section 3.4.2), AFC’s jurisdiction determination will depend on the address information provided. However, it is useful (and more accurate than the 5-digit zip code) because this 9-digit zip code uniquely identifies a location, which can then be used to determine the tax jurisdiction. There is no need to supply the additional city and county information and information in these fields are ignored.

NOTE: Supplying ZIP Code Plus 4 information where the plus 4 is all zeros will function like the ZIP Code Interface since the United States Postal Service has no valid plus 4 code assigned with all zeros. The default will retrieve the first jurisdiction with the supplied 5-digit zip code.

Canadian Postal Codes

Canadian postal codes need to be specified using the ZIP Plus 4 to retrieve a tax jurisdiction code. Place the first three characters go in the zip code field and the last three characters go in the plus 4 field. In addition, the country ISO field must be set to the Canadian ISO Code.

FIPS Codes

AFC has functions allowing the use of FIPS codes to retrieve tax jurisdiction codes. The US Census Bureau provides the following description of the FIPS Codes and associated reference tables.

“The Federal Information Processing Standards codes (FIPS codes) are a standardized set of numeric or alphabetic codes issued by the National Institute of Standards and Technology (NIST) to ensure uniform identification of geographic entities through all federal government agencies. The entities covered include: states and statistically equivalent entities, counties and statistically equivalent entities, named populated and related location entities (such as, places and county subdivisions), and American Indian and Alaska Native areas”.

A FIPS Code is a 10-digit numeric code with the following format:

Table 3-3 FIPS CODE FORMAT

Figure 3-3 FIPS State Codes for the States and the District of Columbia

Figure 3-4 FIPS State Codes for the Outlying Areas of the United States, the Freely Associated States and Trust Territory

Support for India

Processing tax calculations in the the country of India includes support for all the states. Please reference the table below for the appropriate IDs, abbreviations and PCodes for each state.

Note: This only applies to telecom support for India; however, it is visible to SAU clients.

States in India

Determining the Correct Taxing Jurisdiction for Wireline Long Distance

AFC applies taxes to transactions based on the statutes that dictate specific taxes per jurisdiction.

Each jurisdiction from the state level down to the local level establishes jurisdiction rules to determine if their tax will apply to a specific call transaction. These jurisdiction rules (also known as sourcing rules) for determining the correct jurisdiction arose from a United States Supreme Court ruling that established the minimum requirements necessary for a taxing jurisdiction to claim “nexus”.

Tax Type Exemptions

Tax type exemptions are used to specify a specific Tax Type at a specific Tax Level to be exempted for the current transaction. The exemption jurisdiction code specifies the jurisdiction for the tax exemption. If the jurisdiction code is not specified (i.e. set to zero), then all taxes of the Tax Type and Tax Level specified are considered exempt regardless of the jurisdiction they are calculated for. Typically the JCode should be specified as specific tax exemptions are normally only effective for specific jurisdictions.

Another option allows the tax type to be set to zero, to indicate that all taxes of a specific tax level are exempt in the specific jurisdiction.

Tax Adjustments

Tax adjustment functions provide for adjustment activities such as refunds, changing a customer’s bill or writing off un-collectable accounts. The AFC engine allows adjustments to be passed by the user. Note that these adjustments must be accounted for to provide an audit trail.

Tax adjustments are made using the Adjustment functions. The tax amount entered should be a positive number for credit adjustments as the adjustment functions will appropriately sign the charges, lines or locations for computation purposes. The adjustments are logged in the EZTax.log along with the rest of the tax and transaction data associated with the tax run. The information is returned to the billing system and is utilized to update tax data for report generation and compliance filing.

Adjustments may be declared as ‘default’ in which case they are processed exactly like a similar charge transaction with negative tax results. They may be declared as least or most favorable. This declaration is only useful for taxes which have multiple tiers or brackets and should be used with caution. The rate will be determined separately for each tax returned within the tax table. AFC software will search the tiers or brackets and select the tier which has either the highest rate (for most favorable) or lowest rate (for least favorable) and apply that rate to the number of lines or charge amount as appropriate.

NOTE: Debit and credit transactions will generate different taxes if otherwise identical transactions are processed with the same least/most favorable flag. To reverse a most favorable credit adjustment the exact transaction should be sent as a debit adjustment with a least favorable flag.

Tax Overrides

Overrides allow the client to change the rate of a tax in the AFC Engine. Avalara markets the AFC Manager - Rate and Logic Modifier (a Graphic User Interface based Windows program that is sold separately) to support this activity. It steps the user through the process of creating an EZTax.ovr file. Alternatively, overrides can be achieved using the Override functions (such as APIs).

WARNING: An override to exempt taxes OVERRIDES the tax information in Avalara’s tax research database. This is not recommended for those that do not possess a full understanding of the tax ramifications and liabilities when doing so.

Although all clients can use Tax Overrides, the method to make use of them depends upon the client type.

1. AFC SaaS Standard clients must use the AFC Manager - Rate and Logic Modifier to create an EZTax.ovr file that contains the overrides to insert. The file is then uploaded to the service bureau inside the FTP.zip file that carries the CDS file for processing. The overrides are then used during that processing and for subsequent processing until a new or empty override file is uploaded.
2. Avalara clients that submit records in Batch fashion must use the AFC Manager - Rate and Logic Modifier to create an EZTax.ovr file that contains the overrides to insert. Filelocs.txt is then modified to point to this file. When the data file is processed, the overrides are inserted automatically.
3. Avalara clients that integrate with the AFC Engine using functions (such as APIs) can use the Override utility as an easy way to create overrides in the same manner that batch mode and online clients do, modify filelocs.txt to point to the EZTax.ovr file or use the file path to point to the EZTax.ovr file.

The following functions use a session and a tax override record to override the tax rates used by AFC to calculate taxes.

Table 4-4 Tax Override Names and Descriptions

EZTaxGroupResults(session, GROUP_ST_CO_LOCAL | GROUP_SALES_CATEGORY);

Sales and Use

The AFC Sales and Use feature allows API users access to an expanded set of Transaction and Service Type pairs. A Sales and Use transaction requires not only the valid Transaction and Service Type pair but must also include one or more attribute(s). The attributes are used to further specify details of a transaction, such as the freight costs or the purchase of an extended warranty.

Sales and Use contains a comprehensive list of transactions to handle your taxation needs. In addition to the products/services, other items such as Shipping, Discounts, Installation, etc. may or may not be taxable depending on the underlying transaction. AFC Sales and Use provides the ability to pass these items with each transaction. The system automatically determines the taxability of these items based upon the jurisdiction.

AFC Sales and Use contains sourcing tables to determine where the taxable event took place based upon the order entry information entered into the API. The tables contain sourcing information for both SSTP and non-SSTP states. The transactions are designed with a one-to-one relationship with SSTP definitions and also include definitions for non-SSTP states.

Tax Types

When a transaction is processed through the AFC Engine, a Tax Type is assigned based on the results. The Tax Type is determined by the transaction location and transaction/service pairs provided in the transaction record and is used to accurately describe the exact nature of the tax applied.

With over 450 Tax Types available, highly detailed and specific tax descriptions are provided for use in taxation disclosure. This is useful in billing and customer service, and simplifies tax compliance filing.

AFC allows for a change, referred to as an override (see section 4.1.3), of the rate for a specific tax type and tax level in a specific jurisdiction. When overriding a tax type, the tax type must exist in the jurisdiction where for the override is to be made.

See AFC Tax Types for a complete list of supported tax types or refer to the EZTaxTaxType.h file located on the most recent Distribution/Update. For .NET users, the tax types are also available in EZTaxConstants.cs. For Java users, the tax types are also available in TaxType.java.

Nexus

AFC allows a client application to set the nexus information in multiple methods.

• Set the appropriate nexus option in the configuration file (see TM_00548_AFC Configuration Guide). The option specified in the configuration file will automatically be applied to every AFC session as it is initialized. However, this option may be overridden by calling the EZTaxSetNexus API function.
• By EZTaxSetNexus API function.
• By using a nexus_table at the transaction level.
• By EZTaxSetStateNexus API function.

General Usage

When the engine determines there is no nexus for the taxing jurisdiction of the transaction, no taxes will be returned.

If the nexus information has been set by either configuration file or by API call, the transaction level nexus will take precedence.

EZTaxSetNexus allows one call to set all nexus information whereas EZTaxSetStateNexus allows the client application to set each state individually.

By using EZTaxSetNexus with a null pointer and a nexus count of zero, it will reset the AFC engine to default value of nexus in every state.

Nexus is only used within the United States.

Exclusions

AFC allows a client application to exclude states or countries (and all lower level jurisdictions) from taxation. By using the exclusion option, the client is informing AFC that the specified state or country and all lower jurisdictions are to return no taxes. An excluded state will exempt all state and lower level jurisdiction taxes; however, it will continue to return federal level taxes. An excluded country will exempt all federal and lower level jurisdiction taxes. Exclusions may be accomplished using several methods, such as those listed below:

• Set the appropriate exclusion option in the configuration file (see TM_00548_AFC Configuration Guide). The option specified in the configuration file will automatically be applied to every AFC session as it is initialized. However, this option may be overridden with other API functions.
• Use the EZTaxSetStateExclusion API function.
• Use the EZTaxClearExclusion API function.

General Usage

When the engine determines that taxes are excluded at the state level for a transaction, only federal level taxes are returned. When the engine determines that taxes are excluded at the federal level, no taxes are returned.

EZTaxClearExclusion will clear all exclusion information and return taxes at every level.

US Territories

US Territory exclusions function like state exclusions and are set and cleared when the federal level USA country code is used without a state or territory. When specified as a state jurisdiction using the two letter state code, ex. ‘USA,VI’, the exclusion behaves like any other state jurisdiction.

Country codes for US Territories are deprecated.

Reporting Utilities

The reporting utilities are used for customer billing and compliance reporting. They extract specific data from the content rich binary AFC Log file, commonly sorting the data into a logical and orderly format. The resulting output is a flat file containing just the information required for the specific report, compatible with common software such as spreadsheets and databases.

The most common use of this information is to file tax returns. However, other uses may include audit trails, internal tracking and projections.

File Management Utilities

File management utilities are provided for maintenance purposes, such as combining one or more archived AFC log files or appending one log file to another.

Note that AFC provides the asciilog.exe utility for maintenance of AFC log files. It allows the user to view the unsorted log file as readable ASCII text without deleting the file.

asciilog.exe

COMMAND LINE

asciilog logfilename.log <+p> <+tc> <+a> <+h> <-csv> <-?>

DESCRIPTION

The asciilog.exe command dumps the contents of the logfilename.log to an ASCII version of the log file. It does not sort or combine records. It produces a file named logfilename.txt which is a legible version of the logfilename.log data.

INPUT

Log file: logfilename.log file as defined in the command line and is NOT deleted at end of job.

OUTPUT

Comma delimited logfilename.txt or logfilename.csv file.

FILE FORMAT KEY

The contents of the file are highly dependent upon the command line arguments. Use the +h argument to prepend the output with a header row that defines each column.

ARGUMENTS (in any order)

+p option adds the P-Code to the output, located before the Country for each record

+tc option adds the tax category description to the end of each record

+a option outputs all available fields

+h option prepends the output with a header record

-csv option uses .csv as the extension for easier import to other applications

-? option displays usage screen and exits

NOTES:

• AFC log is NOT deleted.
• Also, to have valid values for transaction type and service type, the AFC session that generated the log must have logtransserv=true.

batch_sau.exe

batch_sau is a Processing Utility used to pass Sales and Use transaction records through the AFC Engine in Batch fashion. Refer to batch file processing for details on the Batch processing method.

commerge.exe

COMMAND LINE

commerge

DESCRIPTION

The commerge.exe command reads the log file specified in filelocs.txt, combines the log file with the log.sum (if present) then sorts and combines the data.

INPUT

Reads the log file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run

OUTPUT

No output file is produced as this is a log manipulation utility.

FILE FORMAT KEY

The output file produced is a log file with no format key as this is a log manipulation utility.

ARGUMENTS

None.

NOTES:

• The log.sum file is created
•  WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

No output file is produced as this is a log manipulation utility.

comptnum.exe

COMMAND LINE

comptnum [-z <pkzip executable>] outputfilename <extralogfilename> [-cl]

DESCRIPTION

The comptnum.exe command reads the log file specified in filelocs.txt and produces comma delimited text files outputfilename.ssf, outputfilename.nca, and outputfilename.nba (or a unified file outputfilename.scl) for tax compliance filing.

INPUT

Reads the logfilename.log file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run.

OUTPUT

Comma Delimited outputfilename.ssf (nca, nba, scl) file for tax compliance filing. Sorted and condensed by PCode, Tax Type, Tax Level, Tax Rate

FILE FORMAT KEY

Country, State, County, Locality, PCode, Tax type, Tax Type Description, Tax level, Tax Level Description, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes

Figure 5-3 comptnum SSF File Format Key

ARGUMENTS

-z <pkzip executable> - path to zip executable file*

<output filename>

extra log file name – use instead of log.sum

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

*The pkzip executable option is only available with the windows platform.

NOTES:

• The Tax Rate field is sensitive to positive and negative values
• The log.sum file is NOT created
• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

USA, , , , 0, 6, Federal Excise Tax, 0, Federal, 0.030000, 63.946941, 2131.564739, 0.000000, 0.000000, 2131.564739, 2376516.0, 1

USA, CA, , , 253500, 9, P.U.C. Fee, 1, State, 0.001100, 0.072776, 66.159998, 0.000000, 0.000000, 66.159998, 155916.0, 0000000000000002

USA, CA, , , 253500, 10, E911 Tax, 1, State, 0.006500, 0.450252, 69.269518, 0.000000, 0.000000, 69.269518, 155916.0, 0000000000004302

USA, CA, , , 253500, 19, State High Cost Fund, 1, State, 0.024300, 1.607688, 66.159998, 0.000000, 0.000000, 66.159998, 155916.0, 0000000000999999

U, 1SA, CA, , , 253500, 21, CA Teleconnect Fund, 1, State, 0.001600, 0.105856, 66.159998, 0.000000, 0.000000, 66.159998, 155916.0, Customer Number 2

USA, CA, , , 253500, , 160, CA High Cost Fund A, 1, State, 0.001500, 0.099240, 66.159998, 0.000000, 0.000000, 66.159998, 155916.0, User value here

USA, CO, , , 427200, 13, State Universal Service Fund, 1, State, 0.029000, 0.026172, 0.902500, 0.000000, 0.000000, 0.902500, 1920.0, xxxxxxxxxxxxxxxx2

USA, CO, DENVER, , 442100, 4, District Tax, 2, County, 0.001000, 0.000211, 0.210945, 0.000000, 0.000000, 0.210945, 246.0, 00000000000000000000

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

comrpt.exe

COMMAND LINE

comrpt [-cl]

DESCRIPTION

The comrpt.exe command reads the log.sum. The data is then formatted to produce a customer information file called compliance.ssf.

INPUT

Reads the log.sum file.

log.sum – optional input from previous run

OUTPUT

Fixed Length compliance.ssf file.

FILE FORMAT KEY

Figure 5-4 comrpt File Format Key

ARGUMENTS

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

NOTES:

None.

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

csf20.exe

COMMAND LINE

csf20 [-z <pkzip executable>] outputfilename [-cl]

DESCRIPTION

The csf20.exe command is a processing utility that reads the log file specified in filelocs.txt. It produces a fixed length file outputfilename.CSF. The command line argument determines the output file name.

INPUT

Reads the log file as defined by filelocs.txt.

OUTPUT

Fixed Length outputfilename.csf file.

FILE FORMAT KEY

Table 5-3 csf20.exe File Format Key

ARGUMENTS

outputfilename

-z <pkzip executable> - path to zip executable file*

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

*The pkzip executable option is only available with the windows platform.

NOTES:

• EZTax.log is not deleted.
• filelocs.txt MUST be in the working directory.

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

customsort.exe

COMMAND LINE

customsort -cfg customsort.cfg [-log logfile] [-data datapath] [-work workpath] [-ext extension] [-?]

DESCRIPTION

The custom sort utility is designed to allow clients to produce taxation reports which are sorted and summarized using client-specified fields and/or options. The utility is restricted to fields available in the AFC transaction log, which can be affected by configuration settings in the EZTax.cfg.

INPUT

Reads the log file as defined by filelocs.txt.

OUTPUT

User defined.

ARGUMENTS (in any order)

-cfg customsort.cfg : Required. Custom sort configuration to be used.

-log logfile : EZTax log file to be processed (DEF: EZTax.log).

-data <path> : Data directory; overrides config file value.

-work <path> : Working directory; overrides config file value.

-ext <ext> : Result file extension without ‘.’; overrides reserved config file extension.

-summarize <sumfile> : Log file is summarized into sumfile. On large log files, this option can substantially speed up the sorting process.

-out <fname> : Output base filename; overrides config file. This option can be used when there is a need to set the output files from a script so that different sorts can share the same configuration file.

-? : Display usage and exit

Refer to the AFC Custom Sort Utility User Manual for more information on this utility.

ezcomprep.exe

COMMAND LINE

ezcomprep [-cl]

DESCRIPTION

The ezcomprep.exe command reads the log file specified in filelocs.txt and produces a comma- delimited file for compliance filing. It does not include adjustments as part of Gross Sale. Sorting and combining is performed at the jurisdictional level. It combines the contents of log.sum if it exists.

INPUT

Reads the log file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run

OUTPUT

log.sum – sorted and condensed log file as optional input for next run

Comma delimited outputfilename.rpt file.

Sorted and condensed by PCode, Tax Type, Tax Level, Tax Rate

FILE FORMAT KEY

Country, State, County, Locality, Tax type, Tax level, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes

Figure 5-5 ezcomprep File Format Key

ARGUMENTS

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

NOTES:

• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

USA,,,, 6, 0, 0.030000, 29881.866905, 996062.252444, 0.000000, 0.000000, 996062.252444, 14859213.000000

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

ezlog_ns.exe

COMMAND LINE

ezlog_ns outputfilename [-cl]

DESCRIPTION

The ezlog_ns.exe command reads the log file specified in filelocs.txt and produces a comma- delimited file for compliance filing.

INPUT

Reads the log file name from filelocs.txt.

log.sum – optional input from previous run

OUTPUT

log.sum – sorted and condensed log file as optional input for next run

Comma delimited outputfilename.ssf file.

Sorted and condensed by PCode, Tax Type, Tax Level, Tax Rate

FILE FORMAT KEY

Country, State, County, Locality, Tax type, Tax level, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes

Figure 5-6 ezlog_ns File Format Key

ARGUMENTS

outputfilename

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

NOTES:

• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

USA,,,, 6, 0, 0.030000, 29881.866905, 996062.252444, 0.000000, 0.000000, 996062.252444, 14859213.000000

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

ezlogcust.exe

COMMAND LINE

ezlogcust [-cl]

DESCRIPTION

The ezlogcust.exe command reads the log file specified in filelocs.txt and produces a comma- delimited file for customer billing. Sorting and reporting is done at the customer level.

INPUT

Reads the log file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run

OUTPUT

log.sum – sorted and condensed log file as optional input for next run

Comma delimited log.rpt file.

Sorted and condensed by Customer Number, PCode, Tax Type, Tax Level, Tax Rate, Calculation Type.

FILE FORMAT KEY

Country, State, County, Locality, Tax type, Tax level, Tax rate, Calculation Type, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes, Lines, Customer Number

Figure 5-7 ezlogcust File Format Key

ARGUMENTS

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

NOTES:

• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

USA, , , , 6, 0, 0.030000, RATE, 0.892576, 29.752527, 0.000000, 0.000000, 29.752527, 0.000000, 1, 1, 2143278889

USA, TX, , , 9, 1, 0.001670, RATE, 0.049687, 29.752527, 0.000000, 0.000000, 29.752527, 0.000000, 1, 0, 2143278889

USA, TX, , , 13, 1, 0.036000, RATE, 1.035438, 28.762179, 0.000000, 0.000000, 28.762179, 0.000000, 1, 0, 2143278889

USA, TX, , , 26, 1, 0.012500, RATE, 0.367089, 29.367090, 0.000000, 0.000000, 29.367090, 0.000000, 1, 0, 2143278889

USA, TX, DALLAS, DALLAS, 1, 1, 0.062500, RATE, 1.863693, 29.819089, 0.000000, 0.000000, 29.819089, 0.000000, 1, 0, 2143278889

USA, TX, DALLAS, DALLAS, 1, 3, 0.010000, RATE, 0.298022, 29.802214, 0.000000, 0.000000, 29.802214, 0.000000, 1, 0, 2143278889

USA, TX, DALLAS, DALLAS, 4, 3, 0.010000, RATE, 0.283838, 28.383766, 0.000000, 0.000000, 28.383766, 0.000000, 0, 0, 2143278889

USA, TX, DALLAS, DALLAS, 10, 3, 0.620000, PER_LINE, 0.620000, 0.000000, 0.000000, 0.000000, 0.000000, 0.000000, 1, 0, 2143278889

USA, TX, DALLAS, DALLAS, 51, 3, 1.350000, PER_LINE, 1.350000, 0.000000, 0.000000, 0.000000, 0.000000, 0.000000, 1, 0, 2143278889

USA, , , , 6, 0, 0.030000, RATE, 0.210216, 7.007192, 0.000000, 0.000000, 7.007192, 5.100000, 0, 0, 2143278889B

USA, , , , 18, 0, 0.072805, RATE, 0.009967, 0.136896, 0.000000, 0.000000, 0.136896, 0.100000, 0, 0, 2143278889B

USA, , , , 31, 0, 0.000730, RATE, 0.000099, 0.135089, 0.000000, 0.000000, 0.135089, 0.100000, 0, 0, 2143278889B

USA, TX, , , 9, 1, 0.001670, RATE, 0.011392, 6.821736, 0.000000, 0.000000, 6.821736, 5.000000, 0, 0, 2143278889B

USA, TX, , , 10, 1, 0.006000, RATE, 0.039000, 6.500000, 0.000000, 0.000000, 6.500000, 5.000000, 0, 0, 2143278889B

USA, TX, , , 13, 1, 0.036000, RATE, 0.242515, 6.736532, 0.000000, 0.000000, 6.736532, 5.100000, 0, 0, 2143278889B

USA, TX, , , 26, 1, 0.012500, RATE, 0.086118, 6.889438, 0.000000, 0.000000, 6.889438, 5.100000, 0, 0, 2143278889B

USA, TX, DALLAS, DALLAS, 1, 1, 0.062500, RATE, 0.436224, 6.979585, 0.000000, 0.000000, 6.979585, 5.100000, 0, 0, 2143278889B

USA, TX, DALLAS, DALLAS, 1, 3, 0.010000, RATE, 0.068331, 6.833129, 0.000000, 0.000000, 6.833129, 5.000000, 0, 0, 2143278889B

USA, TX, DALLAS, DALLAS, 4, 3, 0.010000, RATE, 0.068331, 6.833129, 0.000000, 0.000000, 6.833129, 5.000000, 0, 0, 2143278889B

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

ezlogcustios.exe

COMMAND LINE

ezlogcustios [-cl]

DESCRIPTION

The ezlogcustios.exe command reads the log file specified in filelocs.txt and produces a comma- delimited file for customer billing. Sorting and reporting is done at the customer level.

INPUT

Reads the reads the log file specified in filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run

OUTPUT

log.sum – sorted and condensed log file as optional input for next run

Comma delimited log.rpt file.

Sorted and condensed by Customer Number, PCode, Invoice Number, Optional, Service Level Number, Tax Type, Tax Level, Tax Rate

FILE FORMAT KEY

Invoice Number, Optional, Service Level Number, Country, State, County, Locality, Tax type, Tax level, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes, Customer Number

Figure 5-8 ezlogcustios File Format Key

ARGUMENTS

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

NOTES:

• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

6, 8, 7, USA, AL, AUTAUGA, AUTAUGAVILLE, 1, 1, 0.040000, RATE, 0.720000, 18.000000, 0.000000, 0.000000, 18.000000, 275.940002, 54, 18, BillSoft Inc.

6, 8, 7, USA, AL, AUTAUGA, JONES, 1, 2, 0.020000, RATE, 0.320000, 16.000000, 0.000000, 0.000000, 16.000000, 245.280014, 48, 16, BillSoft Inc.

6, 8, 7, USA, AL, AUTAUGA, PRATTVILLE, 1, 3, 0.025000, RATE, 0.050000, 2.000000, 0.000000, 0.000000, 2.000000, 30.660000, 6, 2, BillSoft Inc.

6, 8, 7, USA, AL, AUTAUGA, AUTAUGAVILLE, 1, 3, 0.030000, RATE, 0.060000, 2.000000, 0.000000, 0.000000, 2.000000, 30.660000, 6, 2, BillSoft Inc.

6, 8, 7, USA, , , , 6, 0, 0.030000, RATE, 14.312928, 477.097605, 0.000000, 0.000000, 477.097605, 5825.416504, 1140, 380, BillSoft Inc.

6, 8, 7, USA, AL, , , 8, 1, 0.060000, RATE, 2.200486, 36.674766, 0.000000, 0.000000, 36.674766, 551.879822, 108, 36, BillSoft Inc.

6, 8, 7, USA, AL, BALDWIN, , 10, 2, 0.690000, PER_LINE, 4.140000, 2.000000, 0.000000, 0.000000, 2.000000, 30.660000, 6, 2, BillSoft Inc.

6, 8, 7, USA, AL, AUTAUGA, , 10, 2, 0.850000, PER_LINE, 35.700001, 14.000000, 0.000000, 0.000000, 14.000000, 214.620010, 42, 14, BillSoft Inc.

6, 8, 7, USA, AL, , , 16, 1, 0.060000, RATE, 7.759929, 129.332160, 0.000000, 0.000000, 129.332160, 1931.577759, 378, 126, BillSoft Inc.

6, 8, 7, USA, , , , 18, 0, 0.089000, RATE, 5.340000, 60.000000, 0.000000, 0.000000, 60.000000, 919.800232, 180, 60, BillSoft Inc.

6, 8, 7, USA, AL, , , 23, 1, 0.150000, PER_LINE, 16.200001, 36.000000, 0.000000, 0.000000, 36.000000, 551.879822, 108, 36, BillSoft Inc.

6, 8, 7, USA, , , , 31, 0, 0.003560, RATE, 0.213600, 60.000000, 0.000000, 0.000000, 60.000000, 919.800232, 180, 60, BillSoft Inc.

6, 8, 7, USA, AL, BALDWIN, , 35, 2, 1.950000, PER_LINE, 11.700000, 2.000000, 0.000000, 0.000000, 2.000000, 30.660000, 6, 2, BillSoft Inc.

6, 8, 7, USA, AL, AUTAUGA, , 35, 2, 2.400000, PER_LINE, 100.800004, 14.000000, 0.000000, 0.000000, 14.000000, 214.620010, 42, 14, BillSoft Inc.

6, 8, 7, USA, AL, , , 44, 1, 0.700000, FIXED, 12.600000, 18.474840, 0.000000, 0.000000, 18.474840, 275.940002, 54, 18, BillSoft Inc.

6, 8, 7, USA, , , , 55, 0, 0.025365, RATE, 1.014600, 40.000000, 0.000000, 0.000000, 40.000000, 613.199890, 120, 40, BillSoft Inc.

6, 8, 7, USA, , , , 56, 0, 0.010680, RATE, 0.213600, 20.000000, 0.000000, 0.000000, 20.000000, 306.599976, 60, 20, BillSoft Inc.

6, 8, 7, USA, , , , 62, 0, 0.001015, RATE, 0.040600, 40.000000, 0.000000, 0.000000, 40.000000, 613.199890, 120, 40, BillSoft Inc.

6, 8, 7, USA, , , , 63, 0, 0.000427, RATE, 0.008540, 20.000000, 0.000000, 0.000000, 20.000000, 306.599976, 60, 20, BillSoft Inc.

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

ezlogcustpts.exe

COMMAND LINE

ezlogcustpts [-cl]

DESCRIPTION

The ezlogcustpts.exe command reads the log file specified in filelocs.txt and produces a comma- delimited file for customer billing. Sorting and reporting is done at the customer level. The sort key also contains PCode, optional, and Service Level Number fields.

INPUT

Reads the log file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run

OUTPUT

log.sum – sorted and condensed log file as optional input for next run

Comma delimited log.rpt file.

Sorted and condensed by Customer Number, PCode, Optional, Service Level Number, Tax Type, Tax Level, Tax Rate

FILE FORMAT KEY

PCode, Transaction type, Service Type, Country, State, County, Locality, Tax type, Tax level, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes, Customer Number.

Figure 5-9 ezlogcustpts File Format Key

ARGUMENTS

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

NOTES:

• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

0, 1, 1, USA,,,, 6, 0, 0.030000, 0.128824, 4.294140, 0.000000, 0.000000, 4.294140, 61.320000, BillSoft, Inc.

0, 1, 1, USA,,,, 18, 0, 0.072805, 0.291220, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

0, 1, 1, USA,,,, 31, 0, 0.000730, 0.002920, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

0, 1, 2, USA,,,, 6, 0, 0.030000, 0.128824, 4.294140, 0.000000, 0.000000, 4.294140, 61.320000, BillSoft, Inc.

0, 1, 2, USA,,,, 18, 0, 0.072805, 0.291220, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

0, 1, 2, USA,,,, 31, 0, 0.000730, 0.002920, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

0, 1, 3, USA,,,, 6, 0, 0.030000, 0.128824, 4.294140, 0.000000, 0.000000, 4.294140, 61.320000, BillSoft, Inc.

0, 1, 3, USA,,,, 18, 0, 0.072805, 0.291220, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

0, 1, 3, USA,,,, 31, 0, 0.000730, 0.002920, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

0, 1, 4, USA,,,, 18, 0, 0.072805, 0.291220, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

0, 1, 4, USA,,,, 31, 0, 0.000730, 0.002920, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

0, 2, 1, USA,,,, 6, 0, 0.030000, 0.120000, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

0, 2, 2, USA,,,, 6, 0, 0.030000, 0.120000, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

0, 2, 3, USA,,,, 6, 0, 0.030000, 0.120000, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

0, 2, 5, USA,,,, 6, 0, 0.030000, 0.120000, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

0, 3, 6, USA,,,, 6, 0, 0.030000, 0.360000, 12.000000, 0.000000, 0.000000, 12.000000, 183.960007, BillSoft, Inc.

0, 3, 9, USA,,,, 6, 0, 0.030000, 0.120000, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

100, 1, 1, USA, AL, , , 16, 1, 0.060000, 0.257648, 4.294140, 0.000000, 0.000000, 4.294140, 61.320000, BillSoft, Inc.

100, 1, 2, USA, AL, , , 16, 1, 0.060000, 0.257648, 4.294140, 0.000000, 0.000000, 4.294140, 61.320000, BillSoft, Inc.

100, 1, 3, USA, AL, , , 16, 1, 0.060000, 0.257648, 4.294140, 0.000000, 0.000000, 4.294140, 61.320000, BillSoft, Inc.

100, 1, 4, USA, AL, , , 16, 1, 0.060000, 0.257648, 4.294140, 0.000000, 0.000000, 4.294140, 61.320000, BillSoft, Inc.

100, 2, 1, USA, AL, , , 16, 1, 0.060000, 0.240000, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

100, 2, 2, USA, AL, , , 16, 1, 0.060000, 0.240000, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

100, 2, 3, USA, AL, , , 16, 1, 0.060000, 0.240000, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

100, 2, 4, USA, AL, , , 16, 1, 0.060000, 0.240000, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

100, 2, 5, USA, AL, , , 16, 1, 0.060000, 0.240000, 4.000000, 0.000000, 0.000000, 4.000000, 61.320000, BillSoft, Inc.

100, 3, 6, USA, AL, , , 16, 1, 0.060000, 0.720000, 12.000000, 0.000000, 0.000000, 12.000000, 183.960007, BillSoft, Inc.

200, 2, 5, USA, AL, AUTAUGA, , 10, 2, 0.050000, 0.100000, 2.000000, 0.000000, 0.000000, 2.000000, 30.660000, BillSoft, Inc.

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

ezlogcustptslnl.exe

COMMAND LINE

ezlogcustptslnl [-cl]

DESCRIPTION

The ezlogcustptslnl.exe command reads the log file specified in filelocs.txt and produces a comma-delimited file for customer billing. Sorting and reporting is done at the customer level. In addition to the PCode, optional, and Service Level Number fields and the number of lines are also included.

INPUT

Reads the log file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run

OUTPUT

log.sum – sorted and condensed log file as optional input for next run

Comma delimited log.rpt file.

Sorted and condensed by Customer Number, PCode, Optional, Service Level Number, Tax Type, Tax Level, Tax Rate

FILE FORMAT KEY

PCode, Transaction type, Service Type, Country, State, County, Locality, Tax type, Tax level, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes, Customer Number, Lines

Figure 5-10 ezlogcustptslnl File Format Key

ARGUMENTS

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

NOTES:

• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

0, 0, 0, USA, , , , 6, 0, 0.030000, 2.462930, 82.097663, 0.000000, 0.000000, 82.097663, 0.000000, BillSoft, Inc. , 6, 2

0, 0, 0, USA, , , , 18, 0, 0.089000, 1.157000, 13.000000, 0.000000, 0.000000, 13.000000, 0.000000, BillSoft, Inc. , 0, 0

0, 0, 0, USA, , , , 31, 0, 0.000000, 0.000000, 13.000000, 13.000000, 0.000000, 0.000000, 0.000000, BillSoft, Inc. , 0, 0

1210800, 0, 0, USA, KS, , , 13, 1, 0.048700, 1.458565, 29.949999, 0.000000, 0.000000, 29.949999, 0.000000, BillSoft, Inc. , 0, 0

1284800, 0, 0, USA, KS, SALINE, , 10, 2, 0.750000, 2.250000, 0.000000, 0.000000, 0.000000, 0.000000, 0.000000, BillSoft, Inc. , 3, 0

1284900, 0, 0, USA, KS, SALINE, SALINA, 1, 1, 0.053000, 2.039814, 38.487064, 0.000000, 0.000000, 38.487064, 0.000000, BillSoft, Inc. , 0, 0

1284900, 0, 0, USA, KS, SALINE, SALINA, 1, 2, 0.010000, 0.384871, 38.487064, 0.000000, 0.000000, 38.487064, 0.000000, BillSoft, Inc. , 0, 0

1284900, 0, 0, USA, KS, SALINE, SALINA, 1, 3, 0.007500, 0.288653, 38.487064, 0.000000, 0.000000, 38.487064, 0.000000, BillSoft, Inc. , 0, 0

2502500, 0, 0, USA, NY, , , 5, 1, 0.025000, 0.925712, 37.028499, 0.000000, 0.000000, 37.028499, 0.000000, BillSoft, Inc. , 0, 0

2502500, 0, 0, USA, NY, , , 45, 1, 0.003750, 0.138857, 37.028499, 0.000000, 0.000000, 37.028499, 0.000000, BillSoft, Inc. , 0, 0

2604000, 0, 0, USA, NY, NEW YORK, , 10, 2, 1.000000, 3.000000, 0.000000, 0.000000, 0.000000, 0.000000, 0.000000, BillSoft, Inc. , 3, 0

2604000, 0, 0, USA, NY, NEW YORK, , 27, 2, 0.005950, 0.220320, 37.028499, 0.000000, 0.000000, 37.028499, 0.000000, BillSoft, Inc. , 0, 0

2604000, 0, 0, USA, NY, NEW YORK, , 28, 2, 0.001275, 0.047211, 37.028499, 0.000000, 0.000000, 37.028499, 0.000000, BillSoft, Inc. , 0, 0

2604100, 0, 0, USA, NY, NEW YORK, NEW YORK, 1, 1, 0.042500, 1.630325, 38.360599, 0.000000, 0.000000, 38.360599, 0.000000, BillSoft, Inc., 0, 0

2604100, 0, 0, USA, NY, NEW YORK, NEW YORK, 1, 3, 0.043750, 1.678276, 38.360599, 0.000000, 0.000000, 38.360599, 0.000000, BillSoft, Inc., 0, 0

2604100, 0, 0, USA, NY, NEW YORK, NEW YORK, 29, 3, 0.023500, 0.870170, 37.028499, 0.000000, 0.000000, 37.028499, 0.000000, BillSoft, Inc., 0, 0

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

EZTaxappend.exe

COMMAND LINE

EZTaxappend logfilename1.log logfilename2.log

DESCRIPTION

The EZTaxappend.exe command is used to combine two logfilename.log files. It appends logfilename1.log to logfilename2.log, leaving logfilename1.log intact.

INPUT

logfilename1.log

OUTPUT

logfilename2.log

FILE FORMAT KEY

The output file produced is a log file with no format key as this is a log manipulation utility.

ARGUMENTS

logfilename1.log – the name of the EZTaxlog file to be appended

logfilename2.log – the name of the EZTaxlog file to be appended to.

NOTES:

• log.sum is NOT created.
• EZTax.log is NOT deleted.
• logfilename1.log and logfilename2.log must be actual filenames.
• Filelocs.txt is not used.

EZTaxappendf.exe

COMMAND LINE

EZTaxappendf filelist.txt extaxlogfilename.log

DESCRIPTION

The EZTaxappendf.exe command is used to combine the logfilename.log files listed in the filelist.txt text file containing the paths and logfilename.log names to combine.

INPUT

Filelist.txt

OUTPUT

logfilename.log

FILE FORMAT KEY

The output file produced is a log file with no format key as this is a log manipulation utility.

ARGUMENTS

Filelist.txt – the text file supplied by the user with the names of the logfilename.log files.

logfilename.log – the name of the new logfilename.log to be created.

NOTES:

• logfilename.log will be created if it does not exist. Otherwise it will append to the existing
• logfilename.log file.
• All log files defined in Filelist.txt are concatenated to logfilename.log
• log.sum is NOT created.
• EZTax.log is NOT deleted.
• Filelocs.txt is not used.
• Filelist.txt entries can be space or line delimited.

log no tax transactions

DESCRIPTION

LOGNOTAXTRANS=OFF

LOGNOTAXTRANS=ON

The Log No Tax Transaction option is used to allow writing zero tax amount transactions to the EZTax.ntl log file. The default setting of “OFF” disables this logging function. When set to “ON,” AFC will write zero tax amount transactions to the EZTax.ntl log file.

The no tax transaction log is used to track transactions that do not return any tax types and therefore do not perform tax calculations. This allows for the distinction from a transaction that logs zero tax when a calculation has occurred and resulted in a value of zero which is then placed in EZTax.log.

The no tax transaction log will be named [logname].ntl in which logname refers to the name of the AFC transaction log file, minus the extension, and will be output to the same directory as the log file.

Example of Naming Convention:

(Based on the assumption that the billing system has two sessions with log files named SessionA.log and SessionB.log.)

The output from a normal run with no tax transaction logging enabled would be:

SessionA.log

SessionA.sta

SessionA.tsr

SessionA.ntl

SessionB.log

SessionB.sta

SessionB.tsr

SessionB.ntl

NOTE: The lognotaxtrans switch is over-ridden by the overall logging switch. If logging is turned off when the EZTaxInitEx function initializes the AFC session, the no-tax-trans log will not be created.

FILE FORMAT KEY

Short Format:

Company Identifier, Customer Number, Transaction Type, Service Type, P Code, Charge

Figure 5-11 Short EZTax.ntl Log File Format Key

Long Format:

Company Identifier, Customer Number, Optional Alpha Text, Transaction Type, Service Type, P Code, Charge

Figure 5-12 EZTax.ntl Long Log File Format Key

NOTES:

None

SAMPLE DATA

Short Format:

company_identifier, customer_number, transaction_type, service_type, P_Code, charge

--- Sample output begins on the next line ----------

EZtax version 9.0.0.0.5 No-tax Transaction Log

6215687423a, TU98602746, 0001, 0027, 2102300, 1395.00000 

6215687423a, OP97602744, 0001, 0027, 2102300, 630.00000 

6215687423a, 104602742, 0004, 0008, 2102300, 950.00000 

6215687423a, 555602718, 0001, 0027, 2102300, 100.00000 

6215687423a, 16055602716, 0001, 0027, 2102300, 100.00000 

6215687423a, 22602711, 0001, 0027, 2102300, 100.00000 

6215687423a, 19602709, 0003, 0006, 2102300, 266.44000 

6215687423a, 33602707, 0001, 0027, 2102300, 300.00000 

6215687423a, 55602705, 0001, 0027, 2102300, 500.00000 

6215687423a, LD55602703, 0001, 0027, 2102300, 100.00000 

6215687423a, 56602701, 0003, 0006, 2102300, 266.44000 

6215687423a, 57602699, 0001, 0027, 2102300, 300.00000 

6215687423a, 58602697, 0001, 0027, 2102300, 500.00000 

6215687423a, 58587819, 0001, 0027, 2350600, 500.00000 

Long Format:

company_identifier, customer_number, optional alpha text, transaction_type, service_type, P_Code, charge

--- Sample output begins on the next line ----------

EZtax version 9.0.0.0.5 No-tax Transaction Log

6215687423a, TU98602746, Optional Text, 0001, 0027, 2102300, 1395.00000 

6215687423a, OP97602744, Optional Text, 0001, 0027, 2102300, 630.00000 

6215687423a, 104602742, Optional Text, 0004, 0008, 2102300, 950.00000 

6215687423a, 555602718, Optional Text, 0001, 0027, 2102300, 100.00000 

6215687423a, 16055602716, Optional Text, 0001, 0027, 2102300, 100.00000 

6215687423a, 22602711, Optional Text, 0001, 0027, 2102300, 100.00000 

6215687423a, 19602709, Optional Text, 0003, 0006, 2102300, 266.44000 

6215687423a, 33602707, Optional Text, 0001, 0027, 2102300, 300.00000 

6215687423a, 55602705, Optional Text, 0001, 0027, 2102300, 500.00000 

6215687423a, LD55602703, Optional Text, 0001, 0027, 2102300, 100.00000 

6215687423a, 56602701, Optional Text, 0003, 0006, 2102300, 266.44000 

6215687423a, 57602699, Optional Text, 0001, 0027, 2102300, 300.00000 

6215687423a, 58602697, Optional Text, 0001, 0027, 2102300, 500.00000 

6215687423a, 58587819, Optional Text, 0001, 0027, 2350600, 500.00000 

srtcdf20.exe

COMMAND LINE

srtcdf20 [-z <pkzip executable>] outputfilename [-nN] [extralogfilename] [-cl]

DESCRIPTION

The srtcdf20.exe command reads the log file specified in filelocs.txt and produces a fixed length text file outputfilename.ssf for tax compliance filing and a fixed length text file outputfilename.csf for customer billing.

INPUT

Reads the log file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run, or uses the extralogfilename from the command line.

OUTPUT

Fixed Length outputfilename.ssf file for tax compliance filing. Sorted and condensed by PCode, Tax Type, Tax Level, Tax Rate

Fixed Length outputfilename.csf file for customer billing.  Sorted and condensed by Customer Number, Tax Type, Tax Level, Tax Rate

FILE FORMAT KEYS

Figure 5-13 srtcdf20 SSF File Format Key

Figure 5-14 srtcdf20 CSF File Format Key

ARGUMENTS:

-z <pkzip executable> - path to zip executable file*

N or n – CSF file is not sorted

extra log file name – use instead of log.sum

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

*The pkzip executable option is only available with the windows platform.

NOTES:

• The Tax Rate field is sensitive to positive and negative values
• The log.sum file is NOT created
• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

0                1                  2                  3

123456789012345678901234567890123456

------------------------------------------------------------

000000000000006000003000+00098418707

000000000000007000000580+00018387113

000000000000018000003180+00081599822

000000000000031000000039+00001000752

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

srtcdf20p.exe

COMMAND LINE

srtcdf20p [-z <pkzippath>] outputfilename [-nN] [-cl]

DESCRIPTION

The srtcdf20p.exe command reads the log file specified in filelocs.txt and produces a fixed length text file outputfilename.ssf for tax compliance filing and a fixed length text file outputfilename.csf for customer billing.

The .csf file is used for import into the billing system to populate customer bills. Various compliance vendors use the .ssf file. The csf file also contains the PCode.

INPUT

Reads the logfile as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run

OUTPUT

Fixed Length outputfilename.ssf file for tax compliance filing. Sorted and condensed by PCode, Tax Type, Tax Level, Tax Rate

Fixed Length outputfilename.csf file for customer billing.  Sorted and condensed by Customer Number, Tax Type, Tax Level, Tax Rate

FILE FORMAT KEYS

Figure 5-15 srtcdf20p SSF File Format Key

Figure 5-16 srtcdf20p CSF File Format Key

ARGUMENTS:

-z <pkzip executable> - path to zip executable file*

N or n – CSF file is not sorted

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

*The pkzip executable option is only available with the windows platform.

NOTES:

• The Tax Rate field is sensitive to positive and negative values
• The log.sum file is NOT created
• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

srtcomcust20.exe

COMMAND LINE

srtcomcust20 [-z <pkzip executable>] outputfilename [nN] [extra log file name] [-cl]

DESCRIPTION

The srtcomcust20.exe command reads the log file specified in filelocs.txt and produces a comma delimited text file outputfilename.ssf for tax compliance filing and a fixed length text file outputfilename.csf for customer billing.

The .csf file is used for import into the billing system to populate customer bills. The comma- delimited .ssf file is sorted at the customer level.

INPUT

Reads the log file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run or uses the extra log file name from the command line.

OUTPUT

Comma Delimited outputfilename.ssf file for tax compliance filing.  Sorted and condensed by Customer Number, PCode, Tax Type, Tax Level, Tax Rate, Calculation Type.

Fixed Length outputfilename.csf file for customer billing.  Sorted and condensed by Customer Number, Tax Type, Tax Level, Tax Rate

FILE FORMAT KEY

Figure 5-17 srtcomcust20 SSF File Format Key

Figure 5-18 srtcomcust20 CSF File Format Key

ARGUMENTS:

-z <pkzip executable> - path to zip executable file*

N or n – CSF file is not sorted

extra log file name – use instead of log.sum

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

*The pkzip executable option is only available with the windows platform.

NOTES:

• The Tax Rate field is sensitive to positive and negative values
• The log.sum file is NOT created
• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

srtcomma20.exe

COMMAND LINE

Srtcomma20 [-z <pkzip executable>] outputfilename [nN] [extra log file name][-cl]

DESCRIPTION

The srtcomma20.exe command reads the log file specified in filelocs.txt and produces a comma delimited text file outputfilename.ssf for tax compliance filing and a fixed length text file outputfilename.csf for customer billing.

The .csf file is used for import into the billing system to populate customer bills. The comma- delimited .ssf file is sorted at the jurisdictional level.

INPUT

Reads the logfilename.log file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run or uses the extra log file name from the command line.

OUTPUT

log.sum – sorted and condensed log file as optional input for next run

Comma Delimited outputfilename.ssf file for tax compliance filing.  Sorted and condensed by PCode, Tax Type, Tax Level, Tax Rate

Fixed Length outputfilename.csf file for customer billing.  Sorted and condensed by Customer Number, Tax Type, Tax Level, Tax Rate

FILE FORMAT KEY

Country, State, County, Locality, Tax type, Tax level, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes

Figure 5-19 srtcomma20 SSF File Format Key

Figure 5-20 srtcomma20 CSF File Format Key

ARGUMENTS:

-z <pkzip executable> - path to zip executable file*

N or n – CSF file is not sorted

extra log file name – use instead of log.sum

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

*The pkzip executable option is only available with the windows platform.

NOTES:

• The Tax Rate field is sensitive to positive and negative values
• The log.sum file is NOT created
• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

USA,,,, 6, 0, 0.030000, 29881.866905, 996062.252444, 0.000000, 0.000000, 996062.252444, 14859213.000000

USA,,,, 7, 0, 0.007600, 10116.132171, 1331070.000000, 0.000000, 0.000000, 1331070.000000, 20410578.000000

USA,,,, 18, 0, 0.031400, 11145.492379, 354952.000000, 0.000000, 0.000000, 354952.000000, 5446827.000000

USA, AL, , , 16, 1, 0.067000, 969.972210, 14477.196802, 0.000000, 0.000000, 14477.196802, 220238.671875

USA, AZ, , , 1, 1, 0.050000, 0.806080, 16.121600, 0.000000, 0.000000, 16.121600, 245.280014

USA, AZ, , , 10, 1, 0.012500, 9.068400, 725.472000, 0.000000, 0.000000, 725.472000, 11037.642578

USA, AZ, , , 12, 1, 0.011000, 7.980192, 725.472000, 0.000000, 0.000000, 725.472000, 11037.642578

USA, AZ, APACHE, , 1, 1, 0.050000, 0.806080, 16.121600, 0.000000, 0.000000, 16.121600, 245.280014

USA, AZ, APACHE, , 1, 2, 0.027000, 0.435283, 16.121600, 0.000000, 0.000000, 16.121600, 245.280014

USA, AZ, APACHE, SPRINGERVILLE, 1, 1, 0.050000, 0.705320, 14.106400, 0.000000, 0.000000, 14.106400, 214.620010

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

srtcomma20l.exe

COMMAND LINE

srtcomma20l [-z <pkzip executable>] outputfilename <nN> <-p> <-s> <pcsf> <extralogfilename> [- cl]

DESCRIPTION

The srtcomma20l.exe command reads the log file specified in filelocs.txt and produces a comma delimited text file outputfilename.ssf for tax compliance filing and a fixed length text file outputfilename.csf for customer billing, separating adjustments.

The .csf file is used for import into the billing system to populate customer bills. The comma- delimited .ssf file is sorted at the jurisdictional level. The .ssf file also contains the number of lines.

INPUT

Reads the logfilename.log file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run or uses the extra log file name from the command line.

OUTPUT

Fixed Length outputfilename.ssf file for tax compliance filing. Sorted and condensed by PCode, Tax Type, Tax Level, Tax Rate.

Fixed Length outputfilename.csf file for customer billing.  Sorted and condensed by Customer Number, Tax Type, Tax Level, Tax Rate, Tax Amount.

FILE FORMAT KEY

Country, State, County, Locality, Tax type, Tax level, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes, Lines

WITH -p OPTION SPECIFIED

PCode, Tax type, Tax level, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes, Lines

Figure 5-21 srtcomma20l SSF File Format Key without –p option

Figure 5-22 srtcomma20l SSF File Format Key with –p option

Figure 5-23 srtcomma20l CSF File Format Key

ARGUMENTS

-z <pkzip executable> - path to zip executable file*

N or n – .csf file is unsorted

-p – add PCode to ssf file. Does not add PCode to csf file

-s – produce only the ssf. The .csf file is not created.

-pcsf – add PCode to csf file.

extra log file name – use instead of log.sum

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

*The pkzip executable option is only available with the windows platform.

NOTES:

• The Tax Rate field is sensitive to positive and negative values
• The log.sum file is NOT created
• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

USA,,,, 6, 0, 0.030000, 29881.866905, 996062.252444, 0.000000, 0.000000, 996062.252444, 14859213.000000, 0

USA,,,, 7, 0, 0.007600, 10116.132171, 1331070.000000, 0.000000, 0.000000, 1331070.000000, 20410578.000000, 0

USA,,,, 18, 0, 0.031400, 11145.492379, 354952.000000, 0.000000, 0.000000, 354952.000000, 5446827.000000, 0

USA, AL, , , 16, 1, 0.067000, 969.972210, 14477.196802, 0.000000, 0.000000, 14477.196802, 220238.671875, 0

USA, AZ, , , 1, 1, 0.050000, 0.806080, 16.121600, 0.000000, 0.000000, 16.121600, 245.280014, 0

USA, AZ, , , 10, 1, 0.012500, 9.068400, 725.472000, 0.000000, 0.000000, 725.472000, 11037.642578, 0

USA, AZ, , , 12, 1, 0.011000, 7.980192, 725.472000, 0.000000, 0.000000, 725.472000, 11037.642578, 0

USA, AZ, APACHE, , 1, 1, 0.050000, 0.806080, 16.121600, 0.000000, 0.000000, 16.121600, 245.280014, 0

USA, AZ, APACHE, , 1, 2, 0.027000, 0.435283, 16.121600, 0.000000, 0.000000, 16.121600, 245.280014, 0

USA, AZ, APACHE, SPRINGERVILLE, 1, 1, 0.050000, 0.705320, 14.106400, 0.000000, 0.000000, 14.106400, 214.620010, 0

SAMPLE DATA WITH -p OPTION

0, 6, 0, 0.030000, 29881.866905, 996062.252444, 0.000000, 0.000000, 996062.252444, 14859213.000000, 0

0, 7, 0, 0.007600, 10116.132171, 1331070.000000, 0.000000, 0.000000, 1331070.000000, 20410578.000000, 0

0, 18, 0, 0.031400, 11145.492379, 354952.000000, 0.000000, 0.000000, 354952.000000, 5446827.000000, 0

100, 16, 1, 0.067000, 969.972210, 14477.196802, 0.000000, 0.000000, 14477.196802, 220238.671875, 0

125300, 1, 1, 0.050000, 0.806080, 16.121600, 0.000000, 0.000000, 16.121600, 245.280014, 0

125300, 10, 1, 0.012500, 9.068400, 725.472000, 0.000000, 0.000000, 725.472000, 11037.642578, 0

125300, 12, 1, 0.011000, 7.980192, 725.472000, 0.000000, 0.000000, 725.472000, 11037.642578, 0

125400, 1, 1, 0.050000, 0.806080, 16.121600, 0.000000, 0.000000, 16.121600, 245.280014, 0

125400, 1, 2, 0.027000, 0.435283, 16.121600, 0.000000, 0.000000, 16.121600, 245.280014, 0

125500, 1, 1, 0.050000, 0.705320, 14.106400, 0.000000, 0.000000, 14.106400, 214.620010, 0

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

srtcomma20ld.exe

COMMAND LINE

srtcomma20ld [-z <pkzip executable>] outputfilename <nN> <-p> <-s> <pcsf> <extralogfilename> [-cl] [-tc]

DESCRIPTION

The srtcomma20ld.exe command reads the log file specified in filelocs.txt and produces a comma delimited text file outputfilename.ssf for tax compliance filing and a fixed length text file outputfilename.csf for customer billing, separating adjustments.

The .csf file is used for import into the billing system to populate customer bills. The comma- delimited .ssf file is sorted at the jurisdictional level. The .ssf file also contains the number of lines.

Note: srtcomma20ld handles adjustments differently than srtcomma20l does by subtracting the adjustment from the Gross Sales before the Net Taxable Amount is calculated.

INPUT

Reads the logfilename.log file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run or uses the extra log file name from the command line.

OUTPUT

Fixed Length outputfilename.ssf file for tax compliance filing. Sorted and condensed by PCode, Tax Type, Tax Level, Tax Rate.

Fixed Length outputfilename.csf file for customer billing.  Sorted and condensed by Customer Number, Tax Type, Tax Level, Tax Rate, Tax Amount.

FILE FORMAT KEY

Country, State, County, Locality, Tax type, Tax level, Discount type, Calculation type, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes, Lines

WITH -p OPTION SPECIFIED

PCode, Tax type, Tax level, Discount type, Calculation type, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes, Lines

Figure 5-24 srtcomma20ld SSF File Format Key without –p option

Figure 5-25 srtcomma20ld SSF File Format Key with –p option

Figure 5-26 srtcomma20l CSF File Format Key

ARGUMENTS

-z <pkzip executable> - path to zip executable file*

N or n – .csf file is unsorted

-p – add PCode to ssf file. Does not add PCode to csf file

-s – produce only the ssf. The .csf file is not created.

-pcsf – add PCode to csf file.

extra log file name – use instead of log.sum

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

-tc adds the tax category description to the end of each line

*The pkzip executable option is only available with the windows platform.

NOTES:

• The Tax Rate field is sensitive to positive and negative values
• The log.sum file is NOT created
• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

USA, NY, NEW YORK, NEW YORK, 1, 1, 0, 1, 0.042500, 50.950600, 1198.837637, 0.000000, 0.000000, 1198.837637, 480.0, 0

USA, NY, NEW YORK, NEW YORK, 1, 3, 0, 1, 0.041250, 49.452053, 1198.837637, 0.000000, 0.000000, 1198.837637, 480.0, 0

USA, PA, BERKS, KEMPTON, 1, 1, 0, 1, 0.060000, 58.370907, 972.848456, 0.000000, 0.000000, 972.848456, 240.0, 0

USA, PA, SCHUYLKILL, NEW PHILADELPHIA, 1, 1, 0, 1, 0.060000, 58.370907, 972.848456, 0.000000, 0.000000, 972.848456, 240.0, 0

SAMPLE DATA WITH -p OPTION

1040600, 1, 1, 0, 1, 0.060000, 34.397387, 573.289778, 0.000000, 0.000000, 573.289778, 240.0, 0

1054600, 1, 1, 0, 1, 0.060000, 34.397387, 573.289778, 0.000000, 0.000000, 573.289778, 240.0, 0

1615500, 1, 1, 0, 1, 0.050000, 25.328978, 506.579556, 0.000000, 0.000000, 506.579556, 480.0, 0

2395900, 1, 1, 0, 1, 0.060000, 111.182681, 1853.044679, 0.000000, 0.000000, 1853.044679, 480.0, 0

2604100, 1, 1, 0, 1, 0.042500, 50.950600, 1198.837637, 0.000000, 0.000000, 1198.837637, 480.0, 0

2604100, 1, 3, 0, 1, 0.041250, 49.452053, 1198.837637, 0.000000, 0.000000, 1198.837637, 480.0, 0

3232600, 1, 1, 0, 1, 0.060000, 58.370907, 972.848456, 0.000000, 0.000000, 972.848456, 240.0, 0

3415300, 1, 1, 0, 1, 0.060000, 58.370907, 972.848456, 0.000000, 0.000000, 972.848456, 240.0, 0

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

srtcommadetail.exe

COMMAND LINE

srtcommadetail [-z <pkzip executable>] outputfilename [nN] <-nocsf> <extralogfilename> [-cl]

DESCRIPTION

The srtcommadetail.exe command reads the log file specified in filelocs.txt and produces a comma delimited text file outputfilename.ssf for tax compliance filing and a fixed length text file outputfilename.csf for customer billing.

INPUT

Reads the logfilename.log file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run.

OUTPUT

Comma Delimited outputfilename.ssf file for tax compliance filing. Sorted and condensed by PCode, Tax Type, Tax Level, Tax Rate

Fixed Length outputfilename.csf file for customer billing.  Sorted and condensed by Customer Number, Tax Type, Tax Level, Tax Rate

FILE FORMAT KEY

Country, State, County, Locality, PCode, Tax type, Tax Type Description, Tax level, Tax Level Description, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes

Figure 5-27 srtcommadetail SSF File Format Key

Figure 5-28 srtcommadetail CSF File Format Key

ARGUMENTS

-z <pkzip executable> - path to zip executable file*

<output filename>

n or N – csf file is not sorted

-nocsf – csf file is not created

extra log file name – use instead of log.sum

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

*The pkzip executable option is only available with the windows platform.

NOTES:

• The Tax Rate field is sensitive to positive and negative values
• The log.sum file is NOT created
• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

USA, , , , 0, 6, Federal Excise Tax, 0, Federal, 0.030000, 63.946941, 2131.564739, 0.000000, 0.000000, 2131.564739, 2376516.0

USA, CA, , , 253500, 9, P.U.C. Fee, 1, State, 0.001100, 0.072776, 66.159998, 0.000000, 0.000000, 66.159998, 155916.0

USA, CA, , , 253500, 10, E911 Tax, 1, State, 0.006500, 0.450252, 69.269518, 0.000000, 0.000000, 69.269518, 155916.0

USA, CA, , , 253500, 19, State High Cost Fund, 1, State, 0.024300, 1.607688, 66.159998, 0.000000, 0.000000, 66.159998, 155916.0

USA, CA, , , 253500, 21, CA Teleconnect Fund, 1, State, 0.001600, 0.105856, 66.159998, 0.000000, 0.000000, 66.159998, 155916.0

USA, CA, , , 253500, 60, CA High Cost Fund A, 1, State, 0.001500, 0.099240, 66.159998, 0.000000, 0.000000, 66.159998, 155916.0

USA, CO, , , 427200, 13, State Universal Service Fund, 1, State, 0.029000, 0.026172, 0.902500, 0.000000, 0.000000, 0.902500, 1920.0

USA, CO, DENVER, , 442100, 4, District Tax, 2, County, 0.001000, 0.000211, 0.210945, 0.000000, 0.000000, 0.210945, 246.0

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

srtrev20l.exe

COMMAND LINE

srtrev20l [-z <pkzip executable>] outputfilename <nN> <-p> <-s> <pcsf> <extralogfilename> [-cl] [- tc]

DESCRIPTION

The srtrev20l.exe command reads the log file specified in filelocs.txt and produces a comma delimited text file outputfilename.ssf for tax compliance filing and a fixed length text file outputfilename.csf for customer billing, separating adjustments. It is intended for use with log files created using the tax inclusive calculation functionality in AFC.

The .csf file is used for import into the billing system to populate customer bills. The comma- delimited .ssf file is sorted at the jurisdictional level. The .ssf file also contains the number of lines.

INPUT

Reads the logfilename.log file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run or uses the extra log file name from the command line.

OUTPUT

Fixed Length outputfilename.ssf file for tax compliance filing. Sorted and condensed by PCode, Tax Type, Tax Level, Tax Rate.

Fixed Length outputfilename.csf file for customer billing.  Sorted and condensed by Customer Number, Tax Type, Tax Level, Tax Rate, Tax Amount.

FILE FORMAT KEY

Country, State, County, Locality, Tax type, Tax level, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes, Lines, Sale amount

WITH -p OPTION SPECIFIED

PCode, Tax type, Tax level, Tax rate, Tax amount, Gross Sale, Exempt, Adjustments, Taxable measure, Minutes, Lines

Figure 5-29 srtrev20l SSF File Format Key without –p option

Figure 5-30 srtrev20l SSF File Format Key with –p option

Figure 5-31 srtrev20l CSF File Format Key

ARGUMENTS

-z <pkzip executable> - path to zip executable file*

N or n – .csf file is unsorted

-p – add PCode to ssf file. Does not add PCode to csf file

-s – produce only the ssf. The .csf file is not created.

-pcsf – add PCode to csf file.

extra log file name – use instead of log.sum

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

-tc adds the tax category description to the end of each line in the csf

-b adds the base sale amount to the end of each linein the csf

*The pkzip executable option is only available with the windows platform.

NOTES:

• The Tax Rate field is sensitive to positive and negative values
• The log.sum file is NOT created
• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed.

SAMPLE DATA

USA, , , , 55, 0, 0.136000, 2.086860, 41.360000, 26.015440, 0.000000, 15.344560, 3.5, 0, 41.36

USA, , , , 170, 0, 0.015000, 0.015000, 41.360000, 26.015440, 0.000000, 15.344560, 3.5, 0, 41.36

USA, PA, , , 44, 1, 1.000000, 1.000000, 0.000000, 0.000000, 0.000000, 0.000000, 3.5, 0, 41.36

USA, PA, ALLEGHENY, PITTSBURGH, 1, 1, 0.060000, 2.738097, 45.634953, 0.000000, 0.000000, 45.634953, 3.5, 0, 41.36

USA, PA, ALLEGHENY, PITTSBURGH, 1, 2, 0.010000, 0.456350, 45.634953, 0.000000, 0.000000, 45.634953, 3.5, 0, 41.36

USA, PA, ALLEGHENY, PITTSBURGH, 14, 1, 0.050000, 2.173093, 43.461860, 0.000000, 0.000000, 43.461860, 3.5, 0, 41.36

SAMPLE DATA WITH -p OPTION

0, 55, 0, 0.136000, 0.000000, 82.720000, 52.030880, 15.344560, 15.344560, 7.0, 0, 82.72

0, 170, 0, 0.015000, 0.000000, 82.720000, 52.030880, 15.344560, 15.344560, 7.0, 0, 82.72

3198500, 44, 1, 1.000000, 0.000000, 0.000000, 0.000000, 0.000000, 0.000000, 7.0, 0, 82.72

3206100, 1, 1, 0.060000, 0.000000, 91.269906, 0.000000, 45.634953, 45.634953, 7.0, 0, 82.72

3206100, 1, 2, 0.010000, 0.000000, 91.269906, 0.000000, 45.634953, 45.634953, 7.0, 0, 82.72

3206100, 14, 1, 0.050000, 0.000000, 86.923720, 0.000000, 43.461860, 43.461860, 7.0, 0, 82.72

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

strg.exe

COMMAND LINE

strg outputfilename <extralogfilename> [-cl]

DESCRIPTION

The srtg.exe command reads the log file specified in filelocs.txt and produces a fixed length text file outputfilename.ssf for tax compliance filing. If the extralogfilename is specified, it is used for appending instead of the log.sum.

INPUT

Reads the logfilename file as defined by filelocs.txt or AFC Initialization Function.

log.sum – optional input from previous run

<n> - optional input superseding log.sum

OUTPUT

Fixed Length outputfilename.ssf file for tax compliance filing. Sorted and condensed by PCode, Tax Type, Tax Level, Tax Rate

FILE FORMAT KEY

Figure 5-32 strg SSF File Format Key

ARGUMENTS

<outputfilename>

extralogfilename - optional input superseding log.sum

–cl creates a combined compliance log file with a .scl extension, containing both the billable and non-billable amounts instead of a separate log file for each.

NOTES:

• WARNING - EZTax.log is DELETED. Make backups in case reruns are needed. Removes log.sum (or extra log)

SAMPLE DATA

0                1                  2                  3

123456789012345678901234567890123456

------------------------------------------------------------

000000000000006000003000+00098418707

000000000000007000000580+00018387113

000000000000018000003180+00081599822

000000000000031000000039+00001000752

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

upsize_log.exe

COMMAND LINE

upsize_log logfilename1.log logfilename2.log

DESCRIPTION

The upsize_log.exe command converts the short format logfilename1.log to a long format log logfilename2.log.

INPUT

First log file logfileame1.

OUTPUT

The output file produced is a log file with no format key as this is a log manipulation utility.

ARGUMENTS

None.

NOTES:

• log.sum is NOT created.
• EZTax.log is NOT deleted.

See Transactions and AFC Tax Types for descriptions of the data in the generated file.

Taxing Jurisdiction Identification Information

The Ship-From, Ship-From Flag, Ship-To, and Ship-To Flag fields of the record are discussed in this section.

The batch interface method is designed to allow for the transaction ship-from and ship-to points to be entered as PCodes or FIPS Codes in the first fields of the transaction record. (Note that there are advantages to using the PCode as described in Section 3.4.1.1).

• PCodes are proprietary permanent jurisdiction codes created by Avalara that allow AFC software users to populate their databases with proper jurisdiction assignments. When jurisdiction codes change, they are re-mapped by Avalara and the PCode is updated, providing clients with up to date information without making any changes themselves. The PCode is the preferred method of assigning and maintaining jurisdiction identification, and the time invested in including PCodes into your database records will pay off with increased accuracy and reliability.
• FIPS codes are described in section FIPS Codes.

Customer Information

The transaction customer information is supplied using the following fields; Customer Type, Incorporated Flag, Fed Exempt, State Exempt, County Exempt, Local Exempt, Federal Exemption JCode, State Exemption JCode, County Exemption JCode, Locality Exemption JCode, and Customer Number.