AR – Allow Payment Plan in Cash Collection

A/R – Payment Plan

Overview

Citizens when presented with a bill may not be able to settle the amount in full. The Govern system allows the administration of a payment plan that has been agreed to with the citizen. The A/R Inquiry Payment Plan is used for entering payment plan information on a selected account.

The Payment Plan consists of the following:

  • Delinquent Payment Plan Entry Form (101-ar-fea-008-delinquentPayment)
  • Payment Plan Information Function (101-ar-fea-008-paymentPlanInfo)
  • ACH Prenotification Batch Process (101-ar-bp-060)
  • ACH Data Preparation Batch Process (101-ar-bp-061)
  • ACH File Generation Batch Process (101-ar-bp-062)
  • Payment Plan Information – rel. 6.0 (101-ar-fea-008-paymentPlanInfo60)

Accounts Receivable (AR) – Allow Payment Plan in Cash Collection

Version 6.0 | Version 6.1

A/R – Delinquent Payment Plan

Overview

The Delinquent Payment Plan Entry form is used to define a plan for payment for all delinquent year(s).

Functionality

General Information

  • AR_PAYMENT_PLAN: Allow to setup the payment plan for delinquent year(s)

    • Payment Plan ID
      • Unique key of the payment plan.
      • Primary key of the payment plan.
      • Auto-generated with dynamic key plan_id from usr_key_dynamic.
      • Cannot edit field.
      • The field is required.
    • Year ID
      • Allow to know the payment plan is created in which year.
        • Show only the delinquent years before the year ID with A/R balance or the sub system doesn’t have a year if the balance is higher than zero.
        • Show only the current year equal to the year ID with selected installment.
      • Auto-generated with the fiscal year on creation.
      • Not visible to user.
      • Cannot edit field.
      • The field is required.
    • Reference ID
      • Auto-populated with the key id from the profile.
        • Default key id is set with the parcel ID.
      • Cannot edit field.
      • The field is required.
    • Reference Type
      • Auto-populated with the key type of the profile.
        • Related to the reference ID.
        • Default key type is set as “P_ID” for parcel ID.
      • Cannot edit field.
      • The field is required.
    • Plan Number
      • Formatted with the plan_id with leading zero.
        • {0:00000000}
      • Cannot edit field.
      • The field is required.
    • Plan Status
      • The status of the payment plan.
      • Lookup VT system: PMTPLSTAT.
      • The field is required.
    • Plan Type
      • Lookup VT system: PMTPLTYPE.
      • The field is required.
    • Begin Date
      • The value is copy to the payment plan info once finalized.
      • Auto-populated with the govern date on new.
    • Resolution No
      • Can be change anytime (even after finalizing the payment plan).
    • Authorized By
      • Can be change anytime (even after finalizing the payment plan).
    • Payment Period
      • Lookup VT system: PMTPER
      • The field is required.
      • The value is copy to the payment plan info once finalized.
    • Number of Period
      • The field is required.
      • The value is copy to the payment plan info once finalized.
    • First Payment Date
      • The value is copy to the payment plan info once finalized.
    • Final Payment Date
      • The value is copy to the payment plan info once finalized.
    • Finalized
      • The field is required.
      • Default value is set as false.
      • Once the value is set to true and saved in the database, all the fields from the payment plan are disable except:
        • Plan Status
        • Resolution Number
        • Authorized By
        • Notes & Comments
      • Once finalized, the value cannot be changed from the UI.
    • ACH Suspended
      • Payment Plan ACH state.
      • The field is required.
      • Default value is set as false.
      • The value is copy to the payment plan info once finalized.
    • Classification Code
      • The value is copy to the payment plan info once finalized.
    • Payment Option
      • The value is copy to the payment plan info once finalized.
    • Initial Payment
      • The payment that needs to be paid before the first payment date.
    • Status Override
      • In the batch process Update Payment Plan Status, skip specific Plan IDs with this flag set on the contract to exclude from defaulting it.
      • It is always enabled.
    • Amount Period
      • The value of the payment period (if edited). If the value is null, it means it uses the default value based on the number of installments, otherwise it is imputed by the user.
    • Amount
      • The value of the delinquent balance after the plan is finalized.
      • Until the plan is finalized, the value is null.
      • It is a hidden field, when it has a value, it overwrites the value of the delinquent balance.
    • Name ID
      • Key for the NA_NAMES table, serving as link between the plan and the name linked to
    • First Payment Date Override
      • To be able to override fist payment date.
    • Notes
      • Set the notes and comments on the payment plan.
      • Allow multi line.
    • Ach Seq
      • Contract Holder ACH
      • Using Name ID, link to ACH Info
      • Optional: can be used by ACH batch processes for Real Estate when Use Payment Plan Name ID is checked (See detail)
  • AR_PAYMENT_PLAN_INFO: Allow to setup the payment plan for an account receivable

    • Payment Plan ID
      • Primary key of the payment plan.
      • The ID is in the GovernIds.
      • Auto-generated with key dynamic plan_id from usr_key_dynamic.
      • Cannot edit field.
      • The field is required.
    • Account Receivable ID
      • Primary key of the payment plan.
      • The ID is in the GovernIds.
      • Cannot edit field.
      • The field is required.
    • Is Active
      • Check if the plan is on or off.
      • The field is required.
      • Default value is set as false.
    • ACH Suspended
      • Payment Plan ACH state.
      • The field is required.
      • Default value is set as false.
    • Begin Date
      • The begin date of the payment plan.
    • Resolution No
      • The resolution number of the payment plan.
    • Authorized By
    • Payment Period
      • Lookup VT system: PMTPER.
      • The field is required.
    • Number of Period
      • Number of period for the payment plan.
      • The field is required.
      • Only numeric
    • First Payment Date
      • First payment date of the payment plan.
    • Next Payment Date
      • Next payment date of the payment plan.
    • Last Payment Date
      • Last payment date of the payment plan.
    • Last Payment Amount
      • The last payment amount.
    • Reason Code
      • Lookup VT system: ARREASON.
    • Amount
      • Amount Due of the payment plan.
    • Amount Period
      • Payment amount per period.
    • Number of Total Paid
      • Number of period paid.
    • Notes
      • Set the notes and comments on the payment plan.
      • Allow multi line.
    • Final Payment Date
      • Final payment date of the payment plan.
    • Original Late Charge
      • The original late charge amount.
    • Classification Code
      • Lookup VT system: PAPCLASS.
    • Payment Option
      • Lookup VT system: PAPOPT.
    • Penalty/Interest no charge
      • Set the penalty/interest no charge (true/false).
    • No Charges Effective From
      • The penalty/interest no charge effective from date of the payment plan.
    • No Charges Effective To
      • The penalty/interest no charge effective to date of the payment plan.
    • Expiration Date
      • The expiration date of the payment plan.
    • Initial Payment
      • The payment that needs to be paid before the first payment date.
    • First Payment Date Override
      • To be able to Override the first payment date.
  • AR_PAYMENT_PLAN_PERIOD: Allow to setup the detail on the payment plan period.
    • Payment Plan ID
      • Unique key of the payment plan.
      • Primary key of the payment plan.
      • The ID is in the GovernIds.
      • Auto-generated with key dynamic plan_id from usr_key_dynamic.
      • Cannot edit field.
      • The field is required.
    • Account Receivable ID
      • Primary key of the payment plan.
      • The ID is in the GovernIds.
      • Cannot edit field.
      • The field is required.
    • Sequence
      • Primary key of the payment plan.
      • The sequence of the period.
    • Periodic Amount
      • The amount for the period.
    • Due Date
      • The due date of the period.
    • Payment Option Period
      • Lookup VT system: PAPOPT.
    • Amount Paid
      • The amount of the payment if paid.

Create A/R Payment Plan

  • On creation, the following fields will be auto-set:

    • Year Id : with the current fiscal year (invisible to user, not on UI)
    • Reference ID: with the current parcel ID, selected parcel on the treeview (invisible to user, not on UI)
    • Reference Type: with “P_ID” (invisible to user, not on UI)
    • Plan Number: User can enter the plan number. Otherwise, plan number will be populated from PLAN_ID
    • Finalized: False
    • ACH Suspended: False
    • Begin Date: with the current govern default date
    • Installment (Current Year Only) : Based on the current govern default date

Save A/R Payment Plan

  • Can create new payment plan or save an existing payment plan only if the reference ID doesn’t have an active payment plan with the same plan type for the same year.

    SELECT COUNT(*)
    FROM ar_payment_plan WITH (NOLOCK)
    WHERE ar_payment_plan.ref_id=@ref_id
    AND ar_payment_plan.year_id = @year_id
    AND ar_payment_plan.plan_type = @plan_type
    AND plan_status=’A’ AND plan_id<>@plan_id
  • The first payment date is calculated by the begin date, the payment period and the number of payments.
    • monthly: starts next month from begin date
    • bi-monthly: starts next two month from begin date
    • annual: start next year from begin date
    • semi-annual: starts next 6 months from begin date
    • weekly: starts next week from begin date
  • When the payment period is set as ‘Other’ and the begin date, first payment date or final payment is nothing an error message will show up:
  • When the payment plan is set as ‘Other’ and the begin date is greater than the first payment date or the first payment date is greater than the final payment date an error message will show up:
  • If the payment plan in the DB is not finalized yet and the user decide to finalize the payment plan:
    • Cannot finalize if the delinquent amount is NULL or 0.
      • This can happen when changing the installment for the year and linked accounts were not delinquent for it or no accounts were linked yet.
    • A confirmation message will show up to make sure the user want to finalize the payment
    • Once finalized, the following fields from AR_PAYMENT_PLAN will be updated in the payment plan AR_PAYMENT_PLAN_INFO:
      • Begin Date
      • Start Date
      • Payment Period
      • Number of Period
      • Initial Payment
      • First Payment Date
      • Final Payment Date
      • Classification Code
      • Payment Option
      • ACH Suspended
      • Total Amount Finalized
      • All the amounts in AR_PAYMENT_PLAN_INFO will be calculated
    • Once finalized, we cannot delete the payment plan anymore.
    • Once finalized, we cannot edit the payment plan anymore, in exception of a few fields:

      • Plan Status
      • Resolution Number
      • Authorized By
      • Notes & Comments
      • ACH Suspended
      • Payment Classification
      • Status Override
    • Once finalized, if the plan status is changed:
      • Plan Status is set to Active
        • Set the AR_PAYMENT_PLAN_INFO.IS_PLAN_ACTIVE = True
        • Set the AR_MASTER.NO_CHARGES = True
      • Otherwise if the Plan Status is not set to Active
        •  Set the AR_PAYMENT_PLAN_INFO.IS_PLAN_ACTIVE = False
        • Set the AR_MASTER.NO_CHARGES = False
    • Once finalized, if the ACH suspended is changed:
      • Update AR_PAYMENT_PLAN_INFO.IS_ACH_SUSPEND with the ACH suspended value
      • Update AR_MASTER.ACH_ACTIVE_FLAG depending on the ACH suspended value
        • If True, the value = 3 (Manual Deactivate), otherwise value = 2
    • Once finalized, the payment plan period(s) are created.

Delete A/R Payment Plan

  • Can always delete a payment plan which is not finalized.
  • Delete the record(s) with the associated plan_id from:
    • AR_PAYMENT_PLAN
    • AR_PAYMENT_PLAN_INFO
    • AR_PAYMENT_PLAN_PERIOD
  • When the payment plan is finalized, the delete button is disable.

Add/Remove Delinquent Year(s)

  • Allow to add/remove a delinquent year(s) if the payment plan is not finalized.
    • The button is enable if not finalized.
    • The button is disable if finalized.
  • A popup window show up to choose all the delinquent year(s)

    • If the year existed in the DB and the user uncheck the year, the payment plan info for this year will be deleted.
    • If the year doesn’t existed in the DB and the user select the year, the payment plan info will be created.
    • Only when at less 1 year is selected, the OK button will be enable. Otherwise the button is disable.
    • The Cancel button will only close the window.
    • The X button will only close the window.
    • The checkbox on the header will select all the year(s) or unselect all the year(s).
    • Can sort the grid using the header on the grid.
    • By default the records are sorted as:
      • Year desc
      • Sub System
      • AR ID
  • The year is consider delinquent when:
    • The year is NULL in ar_master or the year is small than the payment plan year
    • The A/R must have a balance
    • Get all the transaction type not as adjusted bill if the plan type is regular or get all the transaction type as adjusted bill if the plan type is omitted
If Plan Type = Regular

SELECT ar_master.ar_id, ar_master.year_id, ar_master.sub_system, SUM(balance) as TotalBalance
FROM ar_master WITH (NOLOCK), ar_detail WITH (NOLOCK)
WHERE ar_master.ar_id = ar_detail.ar_id
AND ar_master.P_ID = @fieldValue
AND (ar_master.year_id IS NULL OR ar_master.year_id < @year_id)
AND ar_detail.trans_type <> ‘ajb’
GROUP BY ar_master.ar_id, ar_master.year_id, ar_master.sub_system
HAVING SUM(balance) > 0
ORDER BY ar_master.year_id DESC, ar_master.sub_system, ar_master.ar_id

If Plan Type = Omitted

SELECT ar_master.ar_id, ar_master.year_id, ar_master.sub_system, SUM(balance) as TotalBalance
FROM ar_master WITH (NOLOCK), ar_detail WITH (NOLOCK)
WHERE ar_master.ar_id = ar_detail.ar_id
AND ar_master.P_ID = @fieldValue
AND (ar_master.year_id IS NULL OR ar_master.year_id < @year_id)
AND ar_detail.trans_type = ‘ajb’
GROUP BY ar_master.ar_id, ar_master.year_id, ar_master.sub_system
HAVING SUM(balance) > 0
ORDER BY ar_master.year_id DESC, ar_master.sub_system, ar_master.ar_id

Periodic Budget and Delinquent Balance

  • After adding at least one delinquent year, the delinquent balance and Periodic Budget will be calculated.

  • There are two modes for the periodic budget:
    • Based on the installment (default)
    • Based on the user’s input
  • The default one will calculate the periodic budget with the formula → Periodic Budget = (Total Amount – Initial Payment) / Number of Installments. The value is displayed on a read-only field Periodic Budget Display.
  • The second mode, based on the user’s input, will instead update the numbers of installments if the value differs from the one entered previously.
  • The final payment is calculated after either the number of installments or periodic budget are updated.
  • After that the balance and budget get populated, editing either the periodic budget override, the installments or the initial payment will trigger the calculation used to either obtain a new value for the periodic budget or the number of installments.
  • When a plan is finalized, if the periodic budget was entered by the user, the periodic plan amount will use this value, otherwise it will calculate the value as the one in display.
  • Also, when the plan is finalized, the Delinquent Balance is saved in the Amount field and this value will be used to display the Delinquent Balance, instead of calculating it every time the form opens, and won’t be updated if the Delinquent Balance is modified.
  • To enable the Periodic Budget and the Periodic Balance, the user must first enable the Controller property “Display field with payment per period calculation”

View Payment Plan Info

  • View AR payment plan info detail.
  • Show the detail on the payment plan info only if the plan is finalized

    • Year
    • Subsystem
      • Show long description of the sub system from VT System: SUBSYS
    • Barcode
      • Link which allow to Open the form AR008 – A/R Inquiry, positioning on the tab item A/R Payment Plan.
    • Begin Date
    • First Payment Date
    • Final Payment Date
    • Plan Amount
    • Period Amount
    • Number of Total Paid
    • Next Payment Date
    • Last Payment Date
    • Last Payment Amount
  • No record if the payment plan is not finalized.

    SELECT
    ar_master.year_id ‘Year’,
    CASE WHEN vt_system.long_desc_en IS NOT NULL THEN vt_system.long_desc_en
    WHEN vt_system.short_desc_en IS NOT NULL THEN vt_system.short_desc_en
    ELSE vt_system.code END ‘Subsystem’,
    ‘Form=AR008:AR_PaymentPlanInfo;PLAN_ID=’ + CAST(ar_payment_plan_info.plan_id AS varchar) + ‘;AR_ID=’ + CAST(ar_payment_plan_info.ar_id AS varchar) ‘<LINK>’,
    ar_payment_plan_info.ar_id ‘Barcode’,
    ar_payment_plan_info.begin_date ‘Begin Date’,
    ar_payment_plan_info.first_payment_date ‘First Payment Date’,
    ar_payment_plan_info.final_payment_date ‘Final Payment Date’,
    Format(ar_payment_plan_info.amount, ‘C’) ‘Plan Amount ($)’,
    Format(ar_payment_plan_info.amount_period, ‘C’) ‘Period Amount ($)’,
    ar_payment_plan_info.number_total_paid ‘Number of Total Paid’,
    ar_payment_plan_info.next_payment_date ‘Next Payment Date’,
    ar_payment_plan_info.last_payment_date ‘Last Payment Date’,
    Format(ar_payment_plan_info.last_payment_amount, ‘C’) ‘Last Payment Amount ($)’
    FROM ar_payment_plan_info
    INNER JOIN ar_master
    ON ar_master.ar_id=ar_payment_plan_info.ar_id
    INNER JOIN vt_system
    ON vt_system.code = ar_master.sub_system
    INNER JOIN ar_payment_plan
    ON ar_payment_plan_info.plan_id=ar_payment_plan.plan_id
    WHERE ar_payment_plan_info.plan_id=@attrPLAN_ID
    AND ar_payment_plan.is_finalized = -1
    AND vt_system.table_name = ‘SUBSYS’
    ORDER BY ar_master.year_id DESC, ar_master.sub_system, ar_payment_plan_info.ar_id

Use Payment Plan Name ID

Option to use ACH Account from this Payment Plan for ACH batch processes:

  • A/R – ACH Batch Process – Prenotification
  • A/R – ACH Batch Process – Data Preparation
    • If active, those parameter will be hidden: Include Payment Plan, For Installment and For Fixed Amount
  • A/R – ACH Batch Process – File Generation
    • If active, those parameter will be hidden: All Pending Records, Fixed Amount Only and By Installment Only

instead of to use primary name index. Right now only available for RE sub system.

GNA General settings:

Classes

N/A

Database

Configuration

BED

Attribute
Properties
PLAN_ID

FIRST_PAYMENT_DATE_OV

IS_ACH_SUSPEND

IS_FINALIZED

NUMBER_OF_PERIOD

PAYMENT_PERIOD

PLAN_STATUS

PLAN_TYPE

REF_ID

REF_TYPE

STATUS_OVERRIDE

YEAR_ID

AMOUNT

AMOUNT_PERIOD

AUTHORIZED_BY

BEGIN_DATE

CLASSIFICATION_CODE

FINAL_PAYMENT_DATE

FIRST_PAYMENT_DATE

INITIAL_PAYMENT

INSTALL_CURRENT_YEAR

LAST_MODIF_DATE

LAST_MODIF_UID

LEGACY_ID

LEGACY_ID_DEFINED

NA_ID

NOTES

PAYMENT_OPTION

PLAN_NUMBER

RESOLUTION_NO

AMOUNT_DISPLAY

IS_PERIODIC_BUDGET_OVERRIDDEN

LAST_PAYMENT_AMOUNT

PERIODIC_BUDGET_DISPLAY

ACH_SEQ

GNA

SELECT
ar_master.year_id ‘Year’,
CASE WHEN vt_system.long_desc_en IS NOT NULL THEN vt_system.long_desc_en
WHEN vt_system.short_desc_en IS NOT NULL THEN vt_system.short_desc_en
ELSE vt_system.code END ‘Subsystem’,
‘Form=AR008:AR_PaymentPlanInfo;PLAN_ID=’ + CAST(ar_payment_plan_info.plan_id AS varchar) + ‘;AR_ID=’ + CAST(ar_payment_plan_info.ar_id AS varchar) ‘<LINK>’,
ar_payment_plan_info.ar_id ‘Barcode’,
ar_payment_plan_info.begin_date ‘Begin Date’,
ar_payment_plan_info.first_payment_date ‘First Payment Date’,
ar_payment_plan_info.final_payment_date ‘Final Payment Date’,
Format(ar_payment_plan_info.amount, ‘C’) ‘Plan Amount ($)’,
Format(ar_payment_plan_info.amount_period, ‘C’) ‘Period Amount ($)’,
ar_payment_plan_info.number_total_paid ‘Number of Total Paid’,
ar_payment_plan_info.next_payment_date ‘Next Payment Date’,
ar_payment_plan_info.last_payment_date ‘Last Payment Date’,
Format(ar_payment_plan_info.last_payment_amount, ‘C’) ‘Last Payment Amount ($)’
FROM ar_payment_plan_info
INNER JOIN ar_master
ON ar_master.ar_id=ar_payment_plan_info.ar_id
INNER JOIN vt_system
ON vt_system.code = ar_master.sub_system
INNER JOIN ar_payment_plan
ON ar_payment_plan_info.plan_id=ar_payment_plan.plan_id
WHERE ar_payment_plan_info.plan_id=@attrPLAN_ID
AND ar_payment_plan.is_finalized = -1
AND vt_system.table_name = ‘SUBSYS’
ORDER BY ar_master.year_id DESC, ar_master.sub_system, ar_payment_plan_info.ar_id

OFD

Attribute
Properties
Plan Number

Plan Status

Plan Type

Resolution Number

Authorized By

Installment Current Year

Is Finalized

Status Override

Contract Holder

Begin Date

Payment Period

Delinquent Balance

Display Periodic Budget

Periodic Budget

Override (Periodic Budget)

Last Payment

Number of Payments/Period

Initial Payment

First Payment Date

Final Payment Date

Payment Classification

Payment Option

ACH Suspended

Notes & Comments

Calculation of payment periods

The calculation of payment period is a formula = (Total balance due of all years in a plan – initial payment ) / number of payments

If the Periodic Budget Override is filled, it uses that value as the payment period instead

The due date for each period is calculated by the payment period

The period 0 is reserved for the initial payment and the due date for period 0 is started on Begin date

The initial payment will be applied from the oldest year to the most recent year until the balance due for a year. The remaining initial payment will be applied on the next year and so on.

Govern is generated the periods for all years in a plan from the oldest year to the most recent year until the balance due for a year. The remaining period amount will be applied on the next year and so on

Example: Payment plan

 

 

Related Topics

Standard A/R Controller Configuration (101-ar-fea-022-ofr)

Accounts Receivable Parameters (103-ar-parm-General)

 

 

101-ar-fea-022

 

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

 

 

101-ar-fea-008

 

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 – Security by Area Form

Accounts Receivable (A/R) Security by Area Form

Version 6.0 | Version 6.1

Overview

In Govern for Windows, the A/R Security by Area form in Govern Admin is used for defining security permissions by property area. This form does not exist in Govern OpenForms. For Govern for OpenForms, all security is managed through the Govern Security Manager (GSM) and the OpenForms Designer (OFD).

 

 

101-ar-fea-009

 

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 – Manage Credited Interest on Refunds

Managing Credited Interest on Refunds

Overview

The following setup can be performed in order to credit the interest, This can be useful if a client was refunded the amount of an overpayment but was not given the interest.
Credited Interest is available for Open Cash Credit (OCH) transactions only.

Documentation

To view or download this information in pdf format, click on the following link:
101-ar-fea-010-CreditedInterest.pdf

Prerequisites

The first step is to create the required A/R Class Codes for Credited Interest or to ensure that they are created. A/R Class Codes for the following transaction types are required:

  • ICR – Interest Credited: The interest on the refund is automatically transferred to this A/R Class Code.
  • OCH – Open Cash Credit: The overpayment is automatically transferred to this A/R Class Code. An A/R Penalty Interest Method is required for this class code.

Creating an A/R Class Code for Credited Interest

You need to create an A/R Class Code for Credited Interest. The transaction type is Interest Credited. No Interest or Penalty method is associated with this A/R Class Code.

To create an A/R Class for Credited Interest:

  1. Launch GNA.
  2. Select Application Configurations > Accounts Receivable > A/R Class.
  3. Click New to create a new A/R Class Code.
  4. Enter a unique set of characters to identify the A/R Class Code in the Code parameter.
  5. Enter descriptions in the Short and Long Description fields.
  6. Select the subsystem from the Subsystem drop-down list.
  7. Select a cycle code from the Cycle drop-down list.
  8. Complete additional parameters as required.
  9. Click Save.

Creating an A/R Class Code for Open Cash Credit

Because Credited Interest is available for Open Cash Credit (OCH) an A/R Class Code for OCH transaction with interest must be created.

Note:Only the standard interest methods can be used. Credited Interest is not available for the custom interest methods.

To create an A/R Class for Credited Interest:

  1. Launch GNA.
  2. Select Application Configurations > Accounts Receivable > A/R Class.
  3. Click New to create a new A/R Class Code.
  4. Enter a unique set of characters to identify the A/R Class Code in the Code parameter.
  5. Enter descriptions in the Short and Long Description fields.
  6. Select the subsystem from the Subsystem drop-down list.
  7. Select a cycle code from the Cycle drop-down list.
  8. Select an interest and penalty method from the Interest / Penalty drop-down list.
  9. Select the A/R Method button to complete the Penalty / Interest parameters.
  10. Enter the amount of interest and the Due Date Method.
    Fields vary according to the method selected.
  11. Click Save on the Interest Penalty window.
  12. Click Save on the A/R Class window.

Creating a Transaction with Credited Interest

Credited Interest is created for over-payments.

The amount of the overpayment is displayed as an Open Cash Credit in Govern Accounts Receivable.
In the following screen shot an example of an overpayment of $113.97 on a Real Estate bill is shown.
To view the Open Cash Credit:

  1. Launch Govern.
  2. Open a Profile that contains Accounts Receivable.
  3. Open the Accounts Receivable form.
  4. Perform a search to retrieve the applicable record.
    The Payment and Open Cash Credit must be posted before you can create a Refund.
  5. Right click on the payment to open the Refund form.
  6. The interest accrued on the overpayment is displayed in the Interest field on the Refund form.
  7. Enter the deposit number for the refund in the Deposit Number field.
  8. Click Save.

The Credited Interested is displayed in A/R Inquiry.

 

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

AR – Payment Data Entry Rules

Accounts Receivable Payment Data Entry Rules

Overview

In addition to the security setup in OFD, different business rules apply when a payment is entered in Govern and the behavior of the form may vary.
The following rules apply whether the payment is entered from the A/R Inquiry Payment or from the Cash Collection form unless identified as such.
Furthermore, other Cash Collection business rules and validation can apply.

Parameters

The following parameters impact payment data entry.

Parameters – Accounts Receivable General Parameters

Use Proportional Distribution (Deprecated in 6.0)

  • Select this option to enable Proportional Distribution for cash collection. With Proportional Distribution, payments are distributed according to the amount owed on each account.
  • For example, if the client pays $100.00 but owes $150.00 for electricity and $50.00 for water, $75.00 is paid towards the electric bill and the remaining $25.00 towards the water bill.

Minimum Percent or Amount to Collect

The user cannot enter less than the calculated amount on the Payment Data Entry forms in Govern, unless:

  • The Allow Payments < Late Charges Due option is selected
  • The User has the Security access to the Payment Amount define in OpenForms Designer (OFD) – to be validated in cc
    • For example: If you enter 50%, the minimum payment amount is 50% of the installment due. The user cannot enter less than the calculated amount in the Payment Amount
  • If the previous installment is not completely paid, the remaining amount is added to the current installment. This amount needs to be paid before the minimum amount on the current installment can be collected.
    • For example, a $3,000. Tax bill is divided into three installments of $1,000.
      • The minimum collection amount is 50% ($500. in this example).
      • The client pays $800.00 on the first installment, leaving $200.00 remaining.
      • This is added to the second installment.
      • The minimum amount that can be paid on the second installment is $700.
      • $200.00 (unpaid amount from first installment) +500.00 (minimum collection amount for second installment).
  • The Minimum Percent or Amount to Collect can be the same for ALL sub-systems (General) or vary by module (Sub-System)

Allow Payments < Late Charges Due
Used with the Minimum to Collect option

Collection Year

For Real Property and …..

  • The last year for which you are collecting bills.
    • For example, if you enter 2015, payments cannot be made on bills dated 2014 and before.
  • Typically, this option is used by municipalities that transfer bills to the county, or to another level of government, after a set time has passed.

 

Use Exact Installment

  • Select this option to prevent collection of the second installment through the Payment Data Entry form before the first has been collected. Otherwise, if the second installment is collected while the first remains outstanding, the second installment payment is registered as the total payment in the database.

Security

T/C

 

 

101-ar-brules-payment-entry

 

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

101-ar-brules-validation

Accounts Receivable (A/R) Object – ERROR Messages

Error Messages System Resources

To search the resource file, use key SY, ERROR MESSAGES and Error number -9999

ERROR MESSAGES RETURNED BY A/R OBJECT (ex: Search SY,ERRORMESSAGES, -0015)

 

Key Resources Message
SY ERRORMESSAGES
-1 Invalid ArID property
-2 Save without Append
-3 Invalid ArClassCode Property Case: A/R Class Code has been deleted while unposted entries use it
-4 Invalid Sub-System code in A/R Parameters
-5 Missing required PID property
-6 Missing required NAID property
-7 Missing required Cycle Code
-8 Missing required KeyId or Keytype
-9 Missing required UBID
-10 MoveNext after EOF
-11 Invalid Transaction Type Invalid A/R Transaction Type
Sub-system LM A/R Class is Empty Transaction Type = Int
-12 Detail Object contains existing transactions
-13 Missing required CCID property
-14 Missign required ArId property
-15 Missing SubSystem Property Invalid or missing Sub-System Code
-16 Missing Installment
-22 Class code And Transaction type incompatible See Transaction Type Business Rules
-25 Invalid fiscal year
-26 Invalid Amount
-27 Can’t get a system key index
-28 Invalid G/L Distr. amount
-29 Transaction already posted
-30 Cannot delete because of Subsequent transaction not posted
-32 Invalid or Missing PP_ID
-33 Invalid or Missing MV_ID
-34 Invalid or Missing BT_ID
-35 This A/R record is inactive and unavailable
-36 No Right to Access
-37 Invalid or Missing AC_ID
-38 Invalid or Missing MB_ID
-39 Invalid Date – Period Closed
-40 Invalid PRJ_ID
-41 Invalid Invoice #
-42 Invalid SALE_ID(Deed)
-43 There are subsequent transaction(s) (err = 3146 duplicate key in ar_detail_applied table)
-44 Invalid ST_ID
-45 Amount must be lower than
-47 Missing deposit number
-48 Invalid BR_ID (Bankruptcy)
-49 Invalid ST_ACCT_ID (Self Reported Tax Account)
-50 Shortage is >= Max Shortage allowed ‘added by Ovu, 2012/03/14, Version 10.7
-51 A department is required in order to create the payment.
Verify that a department is configured for the Web or that one is selected.
-52 Invalid DC_ID (Delinquency Collection)
-999 Unhandled exception

 

 

101-ar-brules-validation

 

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