Profile Visual Queries

Profile Visual Queries

Overview

The Govern Visual Query is a visualization of query results. This visual representation can be in the form of Pie Charts, Graphs of Data, or Data grids. When a dataset is retrieved, the impact upon the end user is increased significantly when the data is presented in a format that is easy for the viewer to visualize. The visual query is presented as icons that are displayed on the Govern Release 6.0 ribbon. When the user clicks the icon that is used to represent the Visual Query, the query result is displayed. Optionally after the data is displayed, the resulting chart may also be configured to display a report when the user clicks on the image of the chart.

Display of Data Query Controls

Query data, when compatible, can be presented in any of the following supported controls:

Control Name Description
Label Displays a user-defined text label in
the Govern ribbon.
Large Label Unlike the text label, a large text label
icon is displayed in the Govern ribbon.
Picture This is a picture icon that will display
a thumbnail representation of the
selected image.
Pie Chart Displays a Pie Chart graphical
representation of the data.
Column Chart Data will be displayed as a column chart.
Line Chart A Line Chart representation of the data
is displayed.

 

What’s New!

Export to Excel Option

NEW! The functionality that has been added to this feature is the ability to conveniently export the View Query result as a Microsoft Excel file. This is export is carried out from the result grid. See below to review the details of this feature.
View_Query_Export_to_Excel_Option.pdf

Configuring the Visual Query

Prior to configuring the control in the OpenForms Designer (OFD), it will be necessary to design queries to retrieve the data that will then be presented. In addition users must approach this process with the understanding that units that are being retrieved must also be formatted for use in the control.

Queries Tab

The parameters under the Queries tab are used to configure the profiles with queries.

Profile Editor – Queries tab command buttons

  • Add a New Query: Click this button to add a new Query to the current profile.
  • Remove Selected Query: To remove the currently selected query from the profile, click Remove Selected Query.
NOTE: You are able to make multiple or extended selections using the Ctrl or Shift keys in this list.

Profile Editor – Queries tab parameters

Control Type

Select one of the control types for your query from the drop down menu.

Query

This list will display the English Long Name of the available queries. When the Open icon is clicked , the SQL Query editor is launched to create a new query; when a query is already configured in the parameter, it will be displayed. Refer to SQL Query Editor on page 245 for information about creating queries with the Govern SQL Query Editor.

Tool Tip

Enter the text for a Tool Tip that is displayed when the user pointer is hovered over the ribbon icon. This parameter has 3 possible states that can be selected.

  • Fix – Select this option to display the current text string as a fixed text description, i.e. tool tip.
  • Query – When selected, the parameter will change to a drop down list of queries. The result of the queries can then be used to determine whether the tool tip is displayed.
  • Logical Expression – Select this option to display a list of Logical Expressions that can be used to determine whether the tool tip is displayed.

Visibility

This is a flag that is set to indicate that the icon will be displayed in the Govern Ribbon.

  • Fix – Select this option to display the icon as a fixed image.
  • Query – When selected, the parameter will change to a drop down list of queries. The result of the queries can then be used to determine whether the icon is displayed. Refer to SQL Query Editor on page 245 for information about creating queries with the Govern SQL Query Editor.
  • Logical Expression – Select this option to display a list of Logical Expressions; the visibility of the controls icon will be based upon the result of the expression. Refer to Logical Expression Editor on page 186 for information about creating Logical Expressions with the Govern Logical Expression Editor.

On Click group

The options in the On Click group when selected will determine what action occurs when the selected query item is clicked in the ribbon. The options are as follows:

None

Selecting None is an indication that no action will be performed when the query item is clicked

Open Form

When selected, you will have the option to indicate which is to be opened when the user clicks on the query.

Open Report

Click to select the option to choose a report that will be displayed.

Open View Query

Select the Open View Query option to open a selected View Query.

Execute Command

To execute a command, click this option; available commands can be selected from the list.

Open GIS

When selected, this option will open a window with an embedded GIS output screen.

Open Query Tool

Selecting this option will open the Govern Query Tool (QT).

Open Batch Process

To configure the query to load a batch process, select this option.

NOTE: Multiple or extended selections using the Ctrl or Shift keys are not allowed in this list.

Security

For more information, see 102-Govern Security Manager (GSM) OpenForms System Suite.

Best Practices

As a Best Practice, users should ensure that their queries have been optimized, as they will be executed at the time Govern is loaded.

How to Set up a Visual Query

Click for detailed steps to setup Profile Queries.

 

 

101-std-fea-003

 

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...

 

System Architecture (Dataset Treeview)

System Architecture (Dataset Treeview)

[In Development]

Overview

The following table describes the rules that the Dataset Treeview is adheres to. For flexibility, Views (queries) are used to define the content to be displayed. To improve the user experience, a Standard Iconology provides visual information to identify the type and status of records listed in the treeview.

Database Views

Naming Standard
V_TREEVIEW_(name) Standard system Govern views that are distributed.
VW_TREEVIEW_(name) Custom views to include in the list of Treeview that can be selected for a profile
Database
Security Access No special security required for the view
SQL View Syntax
Primary Govern ID LINE 1
The first field matching a Governs ID name must match the Profile Dataset Type (brule)
Secondary Govern ID LINE 1
Sequential, i.e. Line 1, Line 2, and so on…
Information Displayed LINE 1
The attributes and their order to be displayed are defined in. Formatting is made in the SQL query view…
Mouse-Over (Tool Tip) LINE 1 to Line X (Need to verify)
Each line will be displayed on the mouse-over
Sort Order Primary Sort
Not relevant…
–
Security
Database Access Set up in Profile Editor
Setup
Profile Editor For each profile, a treeview is selected that matches the correct dataset type access

Supported Views

Standard Views
For name dataset profiles (NA_ID) The following views are supported:

  • V_TREEVIEW_ADDRESS (Name and Address)
  • V_TREEVIEW_BTAX (Name and Business Tax Info)
  • V_TREEVIEW_PP (Name and Personal Property Tax Info)
  • V_TREEVIEW_MB (Name and Misc. Billing Info)
For parcel dataset profiles
(P_ID)		 The following views are supported:

  • V_TREEVIEW_LOCATION (Property Location)
  • V_TREEVIEW_PARCEL_INFO (Property General Info)
For A/R dataset profiles
(NA_ID)		 For Accounts Receivable Profiles (NA_ID)

Distribution Methods (Govern Techno)

Views are created, updated, included in …

SYSTEM AREA ITEM DESCRIPTION
Database Verification
Create The standard views are created automatically on a Database Verification execution when the view does not exists
Update The standard views are replaced when there is a deletion. They are recreated;
Verify The standard views are executed for errors … errors are thrown
EMT (Import / Export)
Exported When a profile is exported Views are also transferred
Imported No Views are imported
Database Extraction
Extracted with The standard/custom views in use for all Views and Functions and are extracted and copied. >00b050
Mobile
Copied Standard and Custom views are copied.

Standard Iconography

SYSTEM AREA ITEM DESCRIPTION
Standard Icons
Govern IDs Profile Dataset Govern ID Icons that are displayed in front of each record when by:
Parcels = HOUSE icon (p_id)
Names = PERSON icon (na_id)ALL OTHER ITEMS
Accounts = FOLDER icon (ST_ID, PP_ID, MB_ID, UB_ID, RE_ID…)
None or Undefined = Govern ID only
Edit mode turned on = Padlock icon
Record Selected Regular – These use the same icons as the selected identifier
When Edit Mode
The Lock icon is displayed when Edit Mode is Activated. On selecting a record, the EDIT icon is displayed and must be pressed to access record in modification mode
Inactive Records Same Govern ID icon but greyed out

Dynamic Search (eSearch), Saved Datasets and Treeview

The Dynamic Search (AKA e-search) and saved dataset search is highly integrated with the treeview. Users can use the results of searches to append to, or remove records from the treeview.

Dynamic Queries

ACTION CONDITION EXPECTED RESULTS
Send to the Treeview From Dynamic Queries The result of a search 101-std-fea-004
On Append Records are added to the treeview
On Deselect and Load Not Applicable (N/A)
On Add and reposition Custom Control action – Determine Custom Control

Saved Datasets

ACTION CONDITION EXPECTED RESULTS
Get Records
From Saved Dataset The content of a saved dataset101-std-fea-006
From Action Button Send to Treeview If the action button sent to the treeview is used (available in the following standard forms: Split Merge, Parcel Linking, Name Linking

Other Treeview Integration

The treeview can be populated from the Dynamic Search Queries (e-search), from the Query Tool, from a Saved Dataset or from special Action Button Controllers (Send to Treeview). Optionally, if they are setup to this effect, the treeview can be populated by the results of the Matix GIS search, the Web Browser and the Application Browser forms.

ACTION CONDITION EXPECTED RESULTS
Get Records
From Action Button Send to Treeview If the action button send to treeview is used (available in the following standard forms: Split Merge, Parcel Linking, Name Linking
From GIS Matix Search 101-std-frm-008
Manual Mode
Automatic Mode
From Web Browser Form 101-std-frm-003
Manual Mode
Automatic Mode
From Application Browser From 101-std-frm-005
Manual Mode
Automatic Mode
From Query Tool Manual refresh to be performed by user. ()
Selected Record
Default First record is selected
User clicks on a record Record is selected
On Select
Refresh Govern IDs Main Govern IDs
Secondary Govern IDS
First Record is Selected
Refresh Forms

Treeview User Interaction

The users can perform the following Treeview Actions

ACTION CONDITION EXPECTED RESULTS
On Mouse Over
Tool Tip Line 2 to x is displayed as a Tool Tip
On Select
User clicks on a record The Govern IDs are refreshed
The icon changes
The forms are refreshed with the selected record Govern ID
On Remove
X The user can remove records from the Treeview
On Move
Previous F6 Go Up
Next F7 Go Down
On Expand
Form Expand Icon The Forms are displayed below the treeview entry.
The same forms as the Forms Explorer are displayed. Displays the forms that the user/role has access to in GSM
Double Click
On Collapse
Form Expand Icon The Forms are no longer displayed
Double Click

Inactive Business Rules

The users can perform the following Treeview Actions

ACTION CONDITION EXPECTED RESULTS
Parcel
Inactive and Effective year
Effective date
Name
Buildings
Effective and Inactive date
Links
Effective and Inactive date
Accounts
Jurisdictions
TFS13225
Mobile
Checkout Bypass Checkout

Special Features

The users can perform the following actions:

NOTE: The following actions are the same as on load.

 

ACTION CONDITION EXPECTED RESULTS
Auto Synch
Form Refresh
Govern F5 Used to update the treeview
If profile view is changed
If form is added
If date is changed
Hibernate

 

 

101-std-fea-005-Treeview_Architecture

 

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...

100-ChangesDBStructure

Changes in Database Structure

Version 6.0 and 6.1

Overview

Standard Functions and Features

System and User Validation Tables

Version 6.0 and 6.1

  • Changes to VT_USER and VT_SYSTEM tables. System and User Tables are now validated and compared against the standard structure XML file.

 

Read More...

Userfile

Version 6.0

  • New GLOBAL KEY to allow us to link Workflow and global messages to users.
    • U_ID field added to USR_USERFILE.

User Profiles

Version 6.0.1412

  • Fields removed from USR_PROFILE
    • ORG_NBR
    • GROUP_CODE
    • JURISDICTION_CODE
    • OWNER_MM
    • OWNER_YY
    • NB_REC_WARN
    • NB_MIN_ROLLBACK

Roll Forward Exclusion Tables

Version 6.0

  • New tables added to support the roll forward exclusion of fields.
    • SY_ROLLFORWARD_EXCLUSION
    • SY_ROLLFORWARD_EXCLUSION.TABLE_NAME [PK]
    • SY_ROLLFORWARD_EXCLUSION.COLUMN_NAME [PK]

User Audit Trail New Tables (3)

Version 6.0 – see User Audit for more info [std-fea-017]

  • USR_AUDIT_OPENFORMS
    • AUDIT_ID
    • AUDIT_ACTION
    • ENTITY_ID
    • FORM_CODE
    • USER_ID
    • AUDIT_DATE
    • IP_ADDRESS
    • SOURCE_COMPUTER_NAME
    • REMOTE_COMPUTER_NAME
  • USR_AUDIT_OPENFORMS_CHANGE
    • AUDIT_ID
    • ATTRIBUTE_ID
    • TABLE_NAME
    • COLUMN_NAME
    • OLD_VALUE
    • NEW_VALUE
  • USR_AUDIT_OPENFORMS_KEY
    • AUDIT_ID
    • ATTRIBUTE_ID
    • KEY_NAME
    • KEY_VALUE
    • IS_PRIMARY_KEY
NOTE: The legacy table USR_AUDIT_TRAIL will be kept for modules running in prior releases, but developers should note the new modifications and table structures impact for custom processes.

Property Control (PC)

PC Parcel

Version 6.1

  • NON_PARCEL_FLAG and VIRTUAL_PARCEL cannot be set to null.

PC Sales
Version 6.0

  • PC_SALES is no longer used, only MA SALES

Accounts Receivable & Cash Collection (CC)

Version 6.0

Payer Name

  • PAYER_NAME added to CC_MASTER (name was previously kept in CC_MASTER_NOTES) – 6.0 and 6.1

Mass Appraisal (MA)

For the specification document, click on Appraisal Detail Specification for listing.

Building Changes

Version 6.1

  • Current_P_ID was added to MA_BUILDINGS
  • VT_SY_DRAWCMD is no longer used

Site Changes

Version 6.1
Site changes to support new override methodology

  • These columns were added:
    • LAND_VALUE_OVERRIDE (money)
    • LAND_AG_VALUE_OVERRIDE (money)
    • BLDG_VALUE_OVERRIDE (money)
    • MISC_VALUE_OVERRIDE (money)
    • INCOME_GRM_VALUE_OVERRIDE (money)
    • INCOME_DIR_VALUE_OVERRIDE (money)
    • MRA_VALUE_OVERRIDE (money)
    • PP_VALUE_OVERRIDE (money)
  • These columns were dropped : (No longer used in v6.1)
    • TEMPLATE_CD
    • TEMPLATE_VA
  • A misc. correction script was added to move :
    • LAND_VALUE to LAND_VALUE_OVERRIDE when LAND_OVERRIDE = -1
    • LAND_AG_VALUE to LAND_AG_VALUE_OVERRIDE when LAND_AG_OVERRIDE = -1
    • BLDG_VALUE to BLDG_VALUE_OVERRIDE when BLDG_OVERRIDE = -1
    • MISC_VALUE to MISC_VALUE_OVERRIDE when MISC_OVERRIDE = -1
    • INCOME_GRM to INCOME_GRM_VALUE_OVERRIDE when INC_GRM_OVERRIDE = -1
    • INCOME_DIR_VALUE to INCOME_DIR_VALUE_OVERRIDE when INC_DIR_OVERRIDE
    • MRA_VALUE to MRA_VALUE_OVERRIDE when MRA_OVERRIDE = -1
    • PP_VALUE to PP_VALUE_OVERRIDE when PP_OVERRIDE = -1
  • A misc. correction script was added to move :
    • All XXX_VA values to XXX_OV_VALUE when XXX_OV = -1
    • – XXX_OV_VALUE should be created as well.

Income Changes

Version 6.1
Income changes to support new override methodology

  • These columns were added in MA_Income.
    • Building_Value_Override
    • DIR_Rate_Amount_Override
    • GRM_Rate_Amount_Override
    • Gross_Effective_Override
    • Gross_Rent_PCT_Override
    • Gross_Rent_Value_Override
    • Land_Value_Override
    • Misc_Value_Override
    • Net_Dir_Override
    • Net_GRM_Override
    • Net_Value_Override
    • Rent_Units_Override
    • Vacancy_PCT_Override
    • Overall_ADJ_VAL_Override
  • These columns were added in MA_Income.
    • Ma_Income_Group

Income changes to support new calculation method and configuration

  • Income Fields added
    • Ma_Income_Record_Type
  • Income Table added
    • For Added Fields – to be validated

 

Miscellaneous Billing

Available in GA Release 6.1.1606
To offer more flexibility, the misc. billing parameters are now year base.
As such the YEAR_ID was added to the following tables:

  • MB_INVOICE and MB_INVOICE_DET
  • MB_RECURRING and MB_RECURRING_DET

In prior versions, only the AR Class Code was used for the invoice and invoice detail. To simplify data entry and offer more flexibility, the following tables were added.

  • MB_PARM_CATEGORY (contains a category that will be used to link the detail invoice items)
  • MB_PARM_ITEM

New Database Fields

  • LAST_RECUR_DATE was added to the MB_INVOICE_REC table
  • BATCH_ID was added to the MB_INVOICE table

Self Reported Business Tax (ST)

When the fields for ST forms are created, the following USR_FIELDS_XXXXX tables, are no longer used.

  • USR_FIELDS_DEF
  • USR_FIELDS_LABEL
  • USR_FIELDS_MASK
  • USR_FIELDS_NUMERIC_FORMAT (Added for 6.0 and 6.1)
NOTE:The data in the above have been copied to (Table: ST_PARM_CATEG)

New Field added in ST_MASTER

  • NAICS (Varchar 15) MANDATORY when using Estimated Filings.
NOTE: This field is now a Standard System Field and may need to be converted if it was created as an Added Field.

New Tables added for Estimated Filings

  • ST_ESTIMATE_ID

New Table added for Corporate Account

  • ST_CORP_ACCOUNT

Name and Address (NA)

For ACH processing and field encryption, the following changes have been made:

  • NA_ACH_INFO.ACH_DESC (new field)
  • NA_ACH_INFO.BANK_ACCOUNT_NO (new field length = 44)
  • NA_ACH_INFO.TRANSIT_NO (new field length = 32)

OpenForms Tables

Version 6.0

Tables Removed from versions: 6.0.1411.0106 and 6.1.1411.0106
1. OF_SE_APP_TYPE replaced by an object in memory
2. OF_DE_MODELCONTENT was used only for MOD
3. OF_MD_UPDATER was used only for MOD
4. OF_LK_PROFILE_OF1 was used only for MOD to establish the link with a profile.

Tables Removed from versions: 6.0.1411.0017 and 6.1.1411.0021
The tables defined in MSGDatanaseStructMods.xml (so also in OPENFORMS_REFERENCE_60):

  • 1. OF_BE_MAPEXPR
  • 2. OF_BE_MAPTYPE
  • 3. OF_BE_NAVIGATION
  • 4. OF_BE_SERIALIZATION
  • 5. OF_BE_VALRULE_ATTB
  • 6. OF_BE_VALRULE_PARM
  • 7. OF_CTRL_TO_COLUMN
  • 8. OF_LK_ATT_VALRULE
  • 9. OF_MODEL_PERSONALIZATION
  • 10. OF_SE_ACCESSRIGHTS (notion still useful but the table has been replaced by an enumeration in the code)
  • 11. OF_SE_AUDIT
  • 12. OF_SE_LK_ROLE_USER
  • 13. OF_SE_USER_EXCL
  • 14. OF_UI_MAPTABLE (notion still useful but the table has been replaced by CLR objects in the code)

Release 5.x

Version 5.x

  • PC_LK_PARCEL has been replaced with PM_LK_MASTER

See Prior Database Changes (ref. v6.1.1508)

Related Topics

Govern Database Diagrams – Refer to the List of Changed Tables section

 

 

100-ChangesDBStructure

 

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...

 

Payment Processing

Payment Processing

Overview

The following is a list of the currently Available Payment Processors and Gateways (POS)

NOTE: This list will be modified periodically.

Recommended Payment Provider List

Read More...

FORTE

Jami Hughes (Contact)
Director of Sales
866.290.5400 ext. 721
jami.hughes@forte.net

PAYMENTUS

Nicole Haskins (Contact)
Director of Sales
540-951-6462
nhaskins@paymentus.com

POINT & PAY

Peter Drew (Contact)
Director of Sales
Office: 888-891-6064
Mobile: 334-303-4941
pdrew@pointandpay.com

NELNET (Cryptpay)

Peggy Smith (Contact)
Manager Strategic Partnerships
121 S. 13th STE 201, Lincoln, NE 68508
312-961-8603
PeggySmith@paymentspring.com

Kamil Salus (Contact)
NTS Project Manager
224.420.7277
Kamil.Salus@cryptpay.net

UniPAY

Debbie Mateer (Contact)
UniPay Supervisor
debbie.mateer@unibank.com
Toll Free: 877-227-1157 Ext. 1131
Direct: 508-849-4255

CONSTELLATION PAYMENTS

Angie Clarke
Director of Product Integration
aclarke@csipay.com
Direct: 267-287-1052

iCLOUD

Stephanie Ivie (Contact)
Implementation Manager
Invoice Cloud, Inc.
Office: (901) 737-8686
sivie@invoicecloud.com

Additional Information

Type of Payment Processing

A payment gateway does not process credit cards transactions. They act as an intermediary between a website or software and a merchant account provider.

Payment Service Providers

A payment service provider (PSP’s) offers additional online services for accepting electronic payments by a variety of payment methods including credit card, bank-based payments such as direct debit, bank transfer, and real-time bank transfer based on online banking. Typically, they use a SaaS model and form a single payment gateway for their clients (merchants) to multiple payment methods.

Payment Processor

A payment processor is a company (often a third party) appointed by a merchant to handle transactions from various channels such as credit cards and debit cards for merchant acquiring banks. They are usually broken down into two types: front-end and back-end.

Payment as a Service

Due to the many regulatory requirements levied on businesses, the modern payment processor is usually partnered with merchants through a concept known as software-as-a-service (SaaS).
Transaction Quality

Security

Tokenization

Tokenization, when applied to data security, is the process of substituting a sensitive data element with a non-sensitive equivalent, referred to as a token, which has no related or useful meaning or value to anyone seeking to exploit it.

Point-to-Point

Another method of protecting payment card data is Point to Point Encryption, which encrypts cardholder data so that clear text payment information is not accessible within the merchant’s system in the event of a data breach.

Compatibility Matrix

NOTE: This matrix is subject to periodic updates.

The following grid is available for viewing or download as a PDF file.
File: 100-pos-table-PaymentProcessing.pdf

Point of Sale eGovernment grid

3rd Party Company Product / Service Provider Status Credit Debit POS Release Version Customers eGov Version ePayments ePermits eRenewals eRemittance Customers Platform *Other Options Available Merchant Account(s) Convenience Fees Fee Per Transaction Fee Per Month Notes
Cryptpay (NelNet)- note now owned by PaymentSpring NelNet yes no yes 1609 yes yes yes yes sav (move to paymentus) Nelnet looking to increase functionalities via our AR/CC api solution
Constellation Payment CSI PAY Terminal Cloud yes no yes v6.0 1603 no — Online Cloud Solution yes yes ? ?
Direct Standard API Paymentus yes no yes 6.0 yes no no yes arv, pro, sav API
Paypal yes no yes 6.0 yes yes yes yes shn, addison API
Point & Pay yes no yes 6.0 yes yes yes yes ehn API
JP Morgan yes no yes 6.0 yes no no yes eri Direct to paym. provider + file for returns
Unipay yes no yes 6.0 yes no no yes oxf API
YourPay Not recommended no yes 6.0 none —
First Data Pax yes yes yes vb6, v6.0 1609 wal no — wal File Exchange (custom) — yes yes
FIS File Exchange yes yes v6.0 *1609 ctg ? ? ctg *Virtual Terminal /Custom Batch Process similar to lockbox ?
Forte Payment Gateway yes yes v6.0 1606 mec yes 1609 yes yes yes yes mec All Major processors. *Virtual POS yes
Harris Payment Gateway (HPG) Card Net Deprecated rev yes rev Revere moving to Forte
FIS Deprecated ken yes ken
TWI Deprecated ftc yes ftc Bought out by Paymentus Paymentus bought out TWI
Moneris Moneris vb6 only yes vb cbj- not yet implemented ? vb cbj Bought out by Vantiv- transition March 2017- will no longer be supported
Nelnet Nelnet Legacy Legacy ofa, ply yes shn, ofa, ply Disc. by Nelnet replaced by Cryptpay
PayPal Paypal vb5 only yes v5.0 yes yes
Invoice Cloud e-billing & Payment Systems yes yes yes v5.0+ — wal ? ? wal Payment Services Providers (PSP) SaaS / File Exchange eBilling ++
System Integrators
  • iNovah
 To be discussed — *Cash Collection Revenue/Solution. AR/CC api. Need to discuss conformity
Document Audit Version Date Description

 

Related Topics

System Third Party Integration
e-Government – Public Self Service Portal

1. FORTE
Jami Hughes
Director of Sales
866.290.5400 ext. 721
jami.hughes@forte.net

2. PAYMENTUS
Nicole Haskins
Director of Sales
540-951-6462
nhaskins@paymentus.com

3. POINT & PAY
Peter Drew
Director of Sales
Office: 888-891-6064
Mobile: 334-303-4941
pdrew@pointandpay.com

4. Nelnet (Cryptpay)
Peggy Smith
Manager Strategic Partnerships
121 S. 13th STE 201, Lincoln, NE 68508
312-961-8603
PeggySmith@paymentspring.com
Kamil Salus
NTS Project Manager
224.420.7277
Kamil.Salus@cryptpay.net

5. UniPay
Debbie Mateer
UniPay Supervisor
debbie.mateer@unibank.com
Toll Free: 877-227-1157 Ext. 1131
Direct: 508-849-4255

6. PayPal

7. JP Morgan

Stephanie Ivie
Implementation Manager
Invoice Cloud, Inc.
Office: (901) 737-8686
sivie@invoicecloud.com

 

 

100-pos

 

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...

 

AR General Parameters – Miscellaneous Billing

Accounts Receivable General Parameters – Miscellaneous Billing

Overview

There are administrative options that will control how the Govern System handles charges that are related to Misc. Billing (MB).
The following parameters need to be setup for Miscellaneous Billing:

Bypass MB/LM/SA/ST funds reapplication

There are administrative options that will control how the Govern System handles charges that are related to Misc. Billing (MB), Land Management (LM), Special Assessment (SA), and Self Reported Tax (ST). The Accounts Receivable General Parameters form is used to define settings for all the subsystems that are linked to Govern’s Accounts / Receivable (A/R) subsystem. Open Credit Transactions (OCT) are generated in the system when an amount that is applied to a payment exceeds the payment due. In the Govern system an OCT is in the form of an Open Cash on Hand (OCH), or an Overpayment (OVR). The Bypass MB/LM/SA/ST funds reapplication in the A/R General Parameters form is an option that changes how the system treats the reapplication of OCT’s.

When the Bypass XX funds reapplication option in GovAdmin is selected, the system will now apply the OCT to the account even if an invoice is NOT referenced.
As before, if the invoice is referenced, the OCT amount will be applied to the selected invoice.
When Reapply in the A/R Inquiry form is selected, the No option will apply the OCT to the outstanding balance of an invoice and creates the applicable G/L entries.
Only select the Yes option with the understanding that the OCT will be applied to account, but the OCT reference will be lost; this is consistent with the previous system behavior.

Default Rules of applying OCH

By default, in the A/R Inquiry form, when a payment is made in the system and no invoice number is specified, the Govern system will apply the payment to all outstanding invoices. When an overpayment amount exists as a result of that overpayment, it is recorded in the system as an open credit OCH. When users select the Bypass XX funds reapplication option in GovAdmin, where XX is a related subsystem. When Reapply is selected in the Govern A/R Inquiry form, unless an invoice number is specified, payments will be recorded as an OCH record, and will remain in the system.

NOTE: Invoices must be referenced by their number otherwise the system will not apply the payment.

During Reapply, if the Yes option is selected for Bypass MB funds reapplication, the OCH will be cleared. Any reference to the OCH will be lost and no adjustment will be made to the GL transactions.

A/R Master by Fiscal Year

This can be selected to create a new AR_ID each year for each MB_ID when an Invoice posting occurs. Otherwise, all invoices for each MB_ID will post to the same AR_ID.

Allow payments < Late Charges Due

 

 

103-ar-parm-MB

 

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...

AR Module Priorities

Accounts Receivables Module Priorities

Overview

The A/R Subsystem Priorities form is used to define the order that payments, entered through the Lockbox utiliy and Centralized Cash, are distributed.
To set up the subsystem priorities:

  • Launch GNA; select from the ribbon, Application Configurations > Accounts Receivable > Subsystem Priorities

Priority:

Enter a number in the Priority field next to each subsystem to define the order in which bills are paid.
The higher the number, the higher the priority and the sooner the bill is paid.
Note: If a collection year is entered on the Accounts Receivable General Parameters form, no payments will be made on bills dated prior to this year.

Ignore Year:

Select Ignore Year to use only the subsystem priority when making payments.
Bills from the subsystem with the highest priority are paid first.
Otherwise, if this option is deselected, payments are made on all outstanding bills according to year; i.e., all bills from 2012 are paid before the bills from 2013.

Payments application order:

  • Payments are made first to the subsystems with the Ignore Year option selected, according to Priority Number. The subsystem with the highest priority number is paid first.
  • Payments are then made to subsystems with the Ignore Year option deselected, according to Priority Number. The subsystem with the highest priority number is paid first.
  • If two subsystems have the same priority number, payments are made in alphabetical order.
  • See payment application business rules

Related Topics

 

 

103-ar-parm-Priorities

 

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...

AR – Payment Application Priorities Business Rules

Accounts Receivable (A/R) Payment Application Priorities Business Rules

Version 6.1

Overview

The following explains the payment application and priority business rules.
[under construction]

Parameters

Mainly, the following parameters impact the payment priority order:

A/R Sub-System Priorities
Enter a number in the Priority field next to each subsystem to define the order in which bills are paid.
The higher the number, the higher the priority and the sooner the bill is paid.
Note: If a collection year is entered on the Accounts Receivable General Parameters form, no payments will be made on bills dated prior to this year.

Ignore Year:

Select Ignore Year to use only the subsystem priority when making payments.
Bills from the subsystem with the highest priority are paid first.
Otherwise, if this option is deselected, payments are made on all outstanding bills according to year; i.e., all bills from 2012 are paid before the bills from 2013.

Application Order

Payments application order:

Sub-System

  • Payments are made first to the subsystems with the Ignore Year option selected, according to Priority Number. The subsystem with the highest priority number is paid first.
  • Payments are then made to subsystems with the Ignore Year option deselected, according to Priority Number. The subsystem with the highest priority number is paid first.
    • Note: If a collection year is entered on the Accounts Receivable General Parameters form, no payments will be made on bills dated prior to this year.
  • If two subsystems have the same priority number, payments are made in alphabetical order.

A/R Class Code

Priority can be setup by Class code
Priority (Highest Number = Highest Priority)
The Class Code with the highest number is processed first; i.e., the class code assigned priority number 2 is processed before that with priority number 1.

Apply Before Installment/Apply Before Date
If two class codes have the same priority number, they are processed according to these 2 fields.
The following table defines the four possible combinations that can be set for these options:

Process Order Priority Number Apply Before Installment Apply Before Date
1 x x x
2 x x
3 x x
4 x

History / Inactive Account

(To be validated if used for Cash Collection)
An account can be inactivated. This option is set in the Accounts Receivable A/R Inquiry Notes tab.
When turned on, no further Accounts Receivable transactions can be performed on the account.

 

 

101-ar-brules-payment

 

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...