ST Late Filing Penalty Method

Business Tax (ST) Late Filing Penalty Method

Overview

This is a new computation method for the Late Filing Levies and the Late Payment feature of Self-Reported Business Tax (ST). This new method was introduced for the current 6.0.1706 and 6.1.1706, 6.1.1707 and greater releases. See below for details about this new method.

Functionalities

The following system and UI changes can be associated with this feature implementation.

System Registry – OpenForms General Settings

There is a new entry under the Self-Reported Tax Registry Filter in the OpenForms General Settings (System registry Registry) form. There is a Force Late Filing Levies Method Date. While the default date of 1/1/0001 is present in the parameter, the Late Filing Levy Method will not be enforced. When any another date is entered, the late filing method will be enforced.

NOTE: Within Govern some settings that appear in the OpenForms General Settings form (SY_REGISTRY), may have other locations that can override the system registry settings form. This location is the only point in which the Force Late Filing Levies Method Date parameter can be overridden.

User Interface (UI)

Category tab – General sub tab

Previously, the Late Filing Penalty and Late Payment Penalty group boxes were hidden conditionally. Entries were required in the A/R Class and Late Payment parameters in order to display the Late Filing group and Late Payment Penalty group boxes respectively. Both groups are now visible.

System Registry – OpenForms General Settings

There is a new entry under the Self-Reported Tax Registry Filter in the OpenForms General Settings (System registry Registry) form. There is a Force Late Filing Levies Method Date. While the default date of 1/1/0001 is present in parameter, the Late Filing Levy Method will not be enforced. When another date is entered, the late filing method will be enforced.

NOTE: Within Govern some settings that appear in the OpenForms General Settings form (SY_REGISTRY), may have other locations that can override the system registry settings form. This location is the only point in which the Force Late Filing Levies Method Date parameter can be overridden.

Late Payment Penalty group

For the Late Payment Penalty group, when there is no A/R Class selected in the combo, the penalty is broken down by A/R Class, i.e. associated with each levy’s A/R class, and the Minimum/Maximum Amount does not apply to the total return, rather, it is per A/R record. The amounts are applied to each penalty record created.

Category tab – Levies sub tab

At the bottom of the Levies sub tab form is the Late Filing Levy combo-box. This parameter is used to link a levy to a Late Filing Levy.

Levies sub tab

In the Computation Method group, the Late Filing Levy combo box is available for all radio button options, i.e. Base X Rate, Fixed Amount, etc. The Late Filing Levy can be linked with the currently selected levy code.

Category tab – Levies sub tab – Computation Method group

In the Computation Method group of the Levies sub tab form is a new Late Filing Levy radio button option. The new Computation Method, when selected, noticeably absent are the Rate Type, Computation Information groups, and the Late Filing Levy combo box.

New Computation Method

When the new computation method, Late Filing Levy is selected, A/R Class must be selected. For this option the only two (2) A/R Classes that can be selected in Invoice (INV) or the parameter field is blank; a blank will also default to invoice.

The new Computation Method called Late Filing Levy when selected, noticeably absent are the Rate Type, Computation Information groups, and the Late Filing Levy combo box.

Business Rules

When a Late Filing levy is being used within the system, should a modification be made to one of the parameters, e.g. Computation Method, and a save is attempted, a warning will be triggered. The warning message will read as, “The following Late Filing Levy cannot change its Computation Method: <methodName>”.

Setup

The setup of a Late Filing Levy follows the same methodology of other standard levies. To associate late filing charges with an existing levy…

  1. Select or create the levy that will be configured.
  2. In the Computation Method group, click to select Late Filing Levy
  3. You will note that the Rate Type and the Computation Information groups will be immediately hidden on the form.
  4. Select an A/R Class; click the ellipsis […] button beside the parameter to open the A/R Class form.
  5. In the A/R Class form, create or select an existing class code.
NOTE: There are only two (2) transaction types that can be selected in the Transaction Type parameter; invoice, i.e. Billed, or leave the parameter blank.

Verify Database Process

As is often the case with a new feature, it is always recommended that administrators run the Verify Database process in the Govern New Administration (GNA). During the process the Verify Database health check will check to see if the SY_REGISTRY default date is being used. When this check has confirmed that the old Late Filing Levies Method is still in use, you will be presented with a warning screen. The screen will link you to the OpenForms General Settings form to change the date in the Force Late Filings Levies Method Date parameter and enable the Late Filing Levy Method.

 

 

101-st-fea-010

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...

 

Self Reported Business Tax Audit Trail

Self Reported Business Tax Audit Trail

Overview

The purpose of the Self Reported Business Tax Audit Trail feature is to view access and modification information related to the ST account.
information for this feature is obtained from (Table: USR_AUDIT_OPENFORMS)
When the Audit Trail is enabled by an administrator through the GSM, the information that is presented in the columns includes the following:

  • Date – The date of the modification. (Table: USR_AUDIT_OPENFORMS.AUDIT_DATE)
  • User – Name of the user that accessed the account. (Table: USR_AUDIT_OPENFORMS.USER_ID)
  • Action – What action was performed on the account, i.e. Viewed, Created, Deleted, and so on. (Table: USR_AUDIT_OPENFORMS.AUDIT_ACTION)
  • Form – The name of the form that was accessed. (Table: USR_AUDIT_OPENFORMS.FORM_CODE)
  • IP Address – The IP address of the computer that accessed the form. (Table: USR_AUDIT_OPENFORMS.IP_ADDRESS)
  • Computer – The Name, Asset or Service tag of the computer that accessed the form. (Table: USR_AUDIT_OPENFORMS.SOURCE_COMPUTER_NAME)
  • Remote Computer – If the access was remote, the name of the Remote Computer. (Table: USR_AUDIT_OPENFORMS.REMOTE_COMPUTER_NAME)

When viewing a form, the Entity Audit feature can be accessed from the Govern ribbon, View (tab) > Entity Audit
Alternatively the keyboard short-cut (Ctrl + H) may also be used.

NOTE: The audit feature is available for the Tax Account, Tax Filing Master, and the Mailing Index OpenForms in the Business Tax module. In addition the feature should only be accessed by users with Administrator level access as sensitive information is readily visible.

 

See Also

101-std-fea-017

 

 

101-st-fea-017

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...

 

BT – Period Validation for AR Deposit in CC Payment Data Entry

Business Tax (BT) Period Validation for AR Deposit in Cash Collection (CC) Payment Data Entry

Overview

This is a new validation in the A/R Payment Data Entry. When a Deposit (DEP) transaction type is attempted in the A/R Self-Reported Tax subsystem without a period, i.e. an ST_ID, one of two things will occur preventing the deposit:

  • The deposit transaction type will NOT BE AVAILABLE FOR SELECTION
  • A validation will be applied (depending on the form)
NOTE: Records from other subsystems, e.g. Land Management (LM), will not create an error state in the form.

Functionality

Depending on the form that the user is making the payment, they will be prevented from making a payment transaction type.

Accounts Receivable

In the Accounts Receivable form, ST records that users try to apply a payment to will be blocked from selecting the Payment option. In the upper Payment grid, the usual right mouse button click on a record displays the floating menu. Selecting the Payment Data Entry menu option will display the Accounts Receivable – Payment Data Entry form. In this form the Payment transaction type will not be available for selection.

Cash Collection

In the Cash Collection Payment Data Entry form, as with the Accounts Receivable form, all record entries from the Self-Reported Tax subsystem, that do not have an ST_ID will be identified. The Accounts grid will be put in an error state, i.e. red border displayed around the grid. When the entry in question is removed, the error state is also removed.

NOTE: Validations will occur when the Transaction Type is changed, or when a record is removed from the grid.

See Also

 

 

101-ar-fea-025

 

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this.Loading...