AR – Transaction Types

Accounts Receivable (A/R) – Transaction Types

Overview

The following table provides a description and abbreviation for each A/ R transaction type. The transaction types are saved to VT_SY_ ARTRTYPE in the Govern database. They are used to populate the Transaction Type fields, on the A/R Class Parameters form on the A/R Transaction forms.

Click here for the pdf version.

The Transaction Type Codes are recorded in the AR Detail records.

 

Code Transaction Type Description
ab Abatement/Exemption A reduction of a payment or release from a payment.
adj Adjustment A modification made on an account or bill.
ajb Adjusted Bill A modification made to a Partial Billing record.
chg Charge An amount applied on an account or bill.
dct Discount A reduction on the total value or gross amount.
dep Deposit An amount of money placed in a bank.
dmd Demand A special charge applied to delinquent bills. This is used in the Motor Vehicle Excise Tax subsystem
dup Duplicate Payment A second payment made to cover an amount already paid.
fee Fee An amount charged for a service or product.
int Interest A charge, usually a percentage, applied on delinquent bills or borrowed money.
inv Billed (Invoice) A list of itemized amounts for goods and services.
mcr Misc. Cash Receipt An amount charged for an item not covered by other categories.
och Open Cash Credit A credit generated from a cash payment.
ocr Open Credit A credit generated from an adjustment.
ovr Overpayment

An adjustment generated from an overpayment on an installment. This is used in the Real Estate Tax module only.

Note: The Over, Short & Duplicate Method option must be selected on the Accounts Receivable General Parameters form in Govern Admin.

pdt Postdated Payment A payment dated later than the current date.
pen Penalty A charge applied on delinquent accounts.
pmt Payment Money given in exchange for goods or services.
rev Payment Reversal A correction made when an payment error has been entered and posted or a Not Sufficient Funds (NSF) check has been processed.
rf Refund An amount of money returned when an overpayment has been made.
sht Over & Short An amount generated from the Automatic Generation of Over & Short batch process.
td Tax Deferral A postponed tax payment.
tri Transferred To Tax (I/P) Interest and penalty charges transferred from the Special Assessment subsystem
tt Tax Title Lien A charge applied on property for the fulfillment of a debt or duty.
tti Tax Title Lien Interest The interest generated from the tax title.
tto Transferred Principal The amount of principal transferred to tax.
ttp Transferred (Interest and Penalty) The amount of interest and penalty transferred to tax.
ttx Transferred To Tax The total amount transferred, including principal and interest.
tx1 Sales Tax 1 A Sales Tax calculation method in which the first and second taxes are added together; then, applied to the bill.
tx2 Sales Tax 2 A Sales Tax calculation method in which the first tax is added to the bill; then, the second tax is calculated on this amount.
vp Voluntary (Advanced) Payment

An amount that is paid before the bill is received; for example, a taxpayer may forward a payment to cover bills during a predicted absence.

Note: If you select Voluntary Payment, as the transaction type, on a Govern user form, an AR_ID is required for the NA_ID or P_ID associated with the record.

 

NOTE: The Deposit, Postdated Payment, Payment, and Voluntary Payment transaction types are not distributed to Govern’s G/L

 

 

101-ar-ref-TransactionType

 

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

Standard AR Controller – Create AR Payment Action Button (101-ar-fea-024)

Standard AR Controller – Create A/R Payment Action Button

Overview

NOTE: The following specifications will change due to enhancements, and as such may change.

This standard controller can be setup on different Account Forms (Real Property, Misc. Billing, Self-Reported Tax…) in order to provide the user with an Action Button to create an A/R payment for the users to enter payments, deposits or voluntary payments against this Account.

  • The Create A/R Payment button can be used for all Sub-Systems (Real Property, Self-Reported Tax, Personal Property, Miscellaneous Billing, etc.)
  • The AR Record to pay is determined by the action button controller setup….
  • This action button can be secured by profile user and role.

Functionality

This controller is used in different standard Forms distributed with the system. It can also be added and configured on a customized form.

NEW! The action button will open a Cash Collection Form in a modal window. When the form is opened, the focus will be on the Cash Collection tab. Next, a new Data Payment Entry record is created. The Subsystem and Transaction Type will be set to the ones specified in the action button properties. Note that these fields will be disabled in the Cash Collection form. If there are any ID’s, or a payer name is specified, they will be auto-loaded and set. When the payment is saved, the AR Detail links will be added if needed. At the end of the process, if required, the Cash Collection is closed.

Configuration

To add or configure this controller on a a form see below:

 

Read More...

 

Govern New Administration (GNA)

To configure in GNA…

  1. On the GNA ribbon select Editors (tab) > Editors (group) > Profile Editor.
  2. In the Profile Editor, ensure that you have linked the cash collection form that will be opened by the AR Create Payment action button.

OpenForms Designer (OFD)

In the OFD, follow these steps…

  1. Select the action for action button, i.e., the Ar_CreatePayment_Action.

The following are the available properties with their associated descriptions.

  1. AutoCloseAfterSave : When checked, the modal window in which the cash collection form was opened will be closed after the completion of the payment.
  2. AutoSearchDatasetTypeCode : Chose the Dataset Type code that defines the ids that you want to auto load (e.g ar_id, p_id)
    • If this is not set the Auto load will not function properly
  3. AutoSearchIds : An expression that returns a list of ids seperated by “;” that you want to load in the cash collection form automatically
    • E.g of a the output of a the expression = “10;30;100” or “20”
    • If this is not set the Auto load will not function properly
  4. CashCollectionForm : The form that you want to open for the payment.
    • This must be a form that is linked to the current profile
  5. CashCollectionPayorNameId : An expression that returns a na_id that you want to set as the default payor for the payment
  6. CashCollectionSubSystem : The subsystem for the payment transaction.
  7. CashCollectionTransactionType : The transaction type for the payment transaction (Note: The transaction field on the cash collection form will be disabled so you should use this property to set the correct transactiontype)
  8. DetailLinkCreation : If checked, a detail link will be created for all the Ar Details that are created for the payment transaction.
  9. DetailLinkId : An expression that returns the link id that will be inserted for the new ar details links (AR_DETAIL_LINK.LINK_ID)
    • If this is not set, no detail link will be created even if the DetailLinkCreation property was set to true.
  10. DetailLInkType : The type for the new detail links (AR_DETAIL_LINK.LINK_TYPE)
    • If this is not set, no detail link will be created even if the DetailLinkCreation property was set to true.

 

 

 

 

Contact your System Administrator or Business Analyst for more information on this feature implementation in OpenForms.

 

Related Topics

 

 

101-ar-fea-024

 

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 – Inquiry ACH Information

Accounts Receivable (AR) Inquiry ACH Information

Overview

The A/R Information tab of the A/R Inquiry form includes a section for ACH Information.

This is updated automatically when you run the Prepare Data for ACH and the ACH Generate File batch process. For details, see
ACH Batch Processes

 

 

101-ar-frm-004

 

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

Payment Data Entry

Overview

The Payment Data Entry form is used for accepting payments at the counter, by cash, check, credit card, debit card, or by any other user-defined method. The current property owner associated with the account is automatically defined as the payer.

Documentation

For the complete reference guide, see Govern Accounts Receivable.
For the A/R Transaction Rules, see A/R Transaction Rules.

Transaction Types

The following transaction types can be accepted and processed through the Payment Data Entry form.
Payment: Money given in exchange for goods or services.
Deposit An amount of money placed in a bank.
Postdated Payment: A payment dated later than the current date. Note: For a posted payment, you can create a payment transfer. A payment transfer is similar to a payment reversal.
Voluntary Payment / Advance Payment: An amount that is paid before the bill is received; for example, a taxpayer may forward a payment to cover bills during a predicted absence. Note: If you select Voluntary Payment, as the transaction type, for a Payment Data Entry, an AR_ID must already exist for the person or property associated with the payment.

For details on the A/R Transaction Types, see A/R Transaction Rules.

User Form

The Payment Data Entry form is divided into four sections:

  • General Information displaying the subsystem, year, bar code, and cashier ID
  • Summary for the transaction type, deposit information, and notes
  • Detail: for the transaction information including the effective date, A/R balance, interest, penalties, fees, etc.
  • Payer Information: for the name and address of the taxpayer

General Information

Subsystem: This field displays the subsystem for the record selected on the A/R Inquiry form.
Year: This field displays the fiscal year of the transaction.
Bar Code: This field displays the bar code or A/R ID in the Bar Code field.
Cashier ID: This field displays the Cashier ID defined on the Cash Collection Parameters form in GNA.

Summary

Select one of the following transaction types from the Transaction Type drop-down list:

  • Payment: Money given in exchange for goods or services.
  • Deposit: An amount of money placed in a bank.
  • Postdated Payment: For this transaction type, an AR_ID must be set up previously for the NA_ID or P_ID associated with the payment.
  • Voluntary Payment / Advance Payment: An amount that is paid before the bill is received; for example, a taxpayer may forward a payment to cover bills during a predicted absence.

Deposit Information: These fields display the current Deposit Number and the total amount of the deposit.
Notes: Enter any notes or comments that are applicable to the payment.
The data entry field for the Deposit transaction type are different from the fields for the Payment transaction Type.

Detail for Payment Transaction Types

This section describes the data entry fields for the Payment, Postdated Payment and Voluntary or Advance Payment Transaction Types.
The fields at the top of the Detail section are automatically populated. You can modify them only if you have full access rights to the function. The Reference, Type, Amount, and Money fields are available for user input.
Effective Date: This field displays the date of the payment. By default, this is the current date. To change the date, click the calendar beside the field and select a new date.
Installment: For payments by installment, this field displays the installment number: 1st, 2nd, 3rd, 4th, or Total.
A/R Balance: This field displays the amount to apply to the bill. By default, this is the balance due and the field is read-only.
Interest: This field displays the current Interest owing on the account.
Penalty: This field displays the current Penalty owing on the record.
Fee: This field displays the current fee.
Discount: This field displays the current discount if applicable.
Charge: This field displays the current charge.
Demand: This field displays the current value of the Demand to apply on the A/R Balance amount.
Note: Changes to values are displayed when the record is saved.

Total to Pay: This field displays the total amount due on the bill. This total includes the amounts from all fields in this section.
For example, interest charges, penalties, fees, and discounts are added to the value in the Total to Pay field.
You can modify the value in the Total to Pay field. Your modification is applied to the A/R Balance.

Detail for the Deposit Transaction Type

This section describes the parameters for the Deposit Transaction Type.
Effective Date: This field displays the date of the payment. By default, this is the current date. To change the date, click the calendar beside the field and select a new date.
Installment: For payments by installment, this field displays the installment number: 1st, 2nd, 3rd, 4th, or Total.
Total to Pay: This field displays the total amount due on the bill. This total includes the amounts from all fields in this section.

Payer Information

By default, the Payer information fields display the name of the taxpayer and a code that identifies the type of letter to be issued with the bill.
To modify the payer information:
1. Click C beside the Payer information field to change the name. This displays the Search screen with the following options:

  • By Name ID: By Tax Payer Account Number
  • By Name: By Phone Number
  • From NA_External

2. Enter the required information on the search screen. Then, select the applicable record.
3. Select a code from the Letter Code field to identify the type of letter the payer receives, such as, duplicate payment, over payment or payment reversal (Table: VT_USR_LETER_C).
4. Click Save.

Payment Transfer

For a posted payment, you can create a payment transfer. A payment transfer is similar to a payment reversal.

 

 

101-ar-frm-020

 

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

Accounts Receivable (A/R) Frequently Asked Questions (FAQ)

Overview

When the AR_DETAIL.BK_RETURNED_CODE is populated with a value, when that field is populated, it will show up in the AR Inquiry with the Label of “Bank Returned Code”. When it is required to change the labels, see the following.

Resources File

Changing Labels in the Inquiry

To change the labels, see

  1. In the Resource File Editor, added a new Entry with the Key = ‘LBLBK_RETURNED_CODE_TX”.
  2. Fill in the Text for both English and French.

Example:

>key:AR,ARINQUIRY,BANK_PROCESSING_CODE
>>en:Bank Returned Code
>>fr:Code Ret Banq

>key:AR,ARINQUIRY,BANK_PROCESSING_DATE
>>en:Bank Returned Date
>>fr:Date Ret Banq

 

101-ar-faq

 

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 – Using Protest Flags

Accounts Receivable (AR) – Using Protest Flags

Version 6.0 [In Development]

Overview

You can add a protest flag to a record listed in A/R Inquiry Detail in order to indicate that the bill has been contested by the recipient.

NOTE: When the recipient makes a payment, only the non-protested amount is paid. Any amount over this creates an open cash credit and interest continues to accrue on the unpaid entries.

This is illustrated in the following scenario:

Real Estate Tax Levies Under Protest

In this scenario, a taxpayer is billed for two levies, but protests the amount billed on the first.

Real Estate Levy 1 (RE1): 1,000. (Protested Entry)

Real Estate Levy 2 (RE2): 500.

The taxpayer protests RE1 but makes a payment of $800.00. This amount is used to pay RE2 and to create an open cash credit for $300.00. Interest continues to accrue on the $1,000. owed on RE1.

Adding a Protest Flag to a Record

To add a protest flag to a record:

  1. Open the A/R Inquiry form in Govern.
  2. Perform a search to retrieve the required record.
  3. Open the record in A/R Inquiry.
  4. Display the record in the Details grid.
  5. Select the Applied Records option.
  6. Right click on the transaction that is under protest. The following confirmation message is displayed:
    Set the protest flag for the select rows with the following Protest?
  7. Click OK
    The protested record is displayed in red and the Protest Code column is added to the A/R Inquiry Detail tab.
  8. Select the reason for the protest from the Protest Code drop-down list.

Removing a Protest Flag

To remove a protest flag from a record:

  1. Open the A/R Inquiry form in Govern.
  2. Perform a search to retrieve the required record and load it to tree view.
  3. Open the record in A/R Inquiry.
  4. Select a transaction in the Summary section to display it in the Details grid.
  5. Select the Applied Records option.
  6. Right click on the transaction that is under protest. Protested records are displayed in red.
    The following message appears if there is a due date in the database for the selected record.
    Do you want to remove the protest flag for the selected row?
  7. Click the calendar to select the new due date for the transaction.
    NOTE: The new date affects the interest calculation.
  8. Click OK to confirm.

 

 

101-ar-fea-002

 

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