Registry AP Journal (sys-viewer-vapjrnl)

Purpose:

Testing Your Registry Entries
The system does not verify the validity of registry entries. Be sure to test your registry entries after completing them to verify that they are functioning correctly.

Setting Values are Uppercase-Lowercase Sensitive:
The Setting Value is case-sensitive: be sure that you enter the value exactly as specified in the documentation. If the documentation specifies a value of true, do NOT enter True or TRUE.

Related Registries:

Disable Warning when Journal Entry has been Replaced

Default Balance Sheet Entity for Journals for Intercompany Installations.

Important Fields:

 Id:       sys-viewer-vapjrnl

See the Standard Registry section in Registry Viewer for additional Registry Id formats to allow entries for specific Users, Branches, Security, or User Groups to override the main entry.

Display Error or Warning if AP Journal Effective Date Precedes Last PO Receipt

This registry may be enabled to prevent or warn the user if the PO's Voucher Effective dates would precede it's PO Receipt date. This registry impact AP Journal entries for Purchase Orders with Inventory or General lines.  Credit PO's and dollar-based PO's (with detail added on the Subcontractor tab) are not impacted.

Id: sys-viewer-vapjrnl

Setting Key:  EvaluatePOReceiptDates   Setting Value: warning or error

If this registry is not present, the user will not be notified if the Last PO Receipt Date precedes the AP Journal's Effective Date.

If a Setting Value of warning is specified, the user will be Warned on adding/saving the entry if the AP Journal's Effective Date precedes the Last PO Receipt date. If the entry is in Add mode, the user will be given the opportunity to change the Effective Date before adding the entry:

WARNING: Effective Date should not precede PO Last Receipt Date
Select YES to use the date or
Select No to correct the date before saving.

If a Setting Value of error is specified, the user will be not be allowed to add the entry until the Effective Date is corrected. If the entry was previously saved, the user will be allowed to edit it as long as the Effective Date is not changed to a value preceding the Last PO Receipt.

Note: AP Journal's Last PO Receipt Date
This display field displays the most recent receipt date of the selected PO.

If the AP Journal is in Add mode and the User has selected from a list of IRJ transactions, this field displays the IRJ's Date Received. NOTE: this refinement ONLY applies during ADD mode because the selected IRJ is not saved with the APJ entry. For edits of existing transactions, the overall last Date Received of all Inventory Receipts will be used.

If items were received on the PO itself, the PO's Release Date will be displayed.

Registry to Use Default Service Job in the Equipment record for all but PM WO’s

Registry Id: sys-viewer-vapjrnl

Setting Key: DefaultJobByEquipmentId Setting Value: true

By default, the system uses the Job in the Work Order header as the default job for entering WO-related detail in the AP Journal. This release supports the above registry setting to alter this behavior. If this registry entry is enabled (and the referenced WO is NOT preventative maintenance), the system will check to see if there is a default service job in the Equipment header. If so, the Job, Cost Code and Billing item to the from the Equipment will be defaulted instead of from the WO header. If the job info is blank in the equipment record, the system uses the job info in the work order header.

For Preventive Maintenance Work Orders, Job information defaults from the WO header, regardless of whether or not this registry entry is enabled.

Note: registry options to provide this functionality are also available in the Work Order, AP Journal and Purchase Order registries. .

Allow Vendor Billings to Exceed Earnings on Sub PO's

When implemented, this registry allows AP Journal entries to be recorded for Subcontractor PO's when the sub amount vouchered exceeds the amount earned/approved. The user will be warned if the vouchered amount exceeds the approved/earned amount, but will be allowed to created the AP Journal entry.

Id: sys-viewer-vapjrnl

Setting Key: AllowSUBAmountToExceedAmountEarned   Setting Value: true     (default false)

Enable Reset Tax on Lines Button

The Reset Tax On Lines button automates the process of changing the Tax Group on all of the Inventory, General and Subcontractor lines, and automatically adjusting the necessary tax amount on such lines. This eliminates the need to touch every line on the AP Journal. Lines with Copied For Edit checked will be skipped.

A registry is required to enable usage of the Reset Tax On Lines button.  This setting should be discussed with your support representative before it is enabled.

Note that this functionality does NOT pertain to the AP Journal Taxes tab; entries on this tab must be deleted priority to clicked the Reset Tax On Lines button. The user will be alerted if any lines appear on the Taxes tab when the button is clicked; these lines must be deleted before proceeding.

Registry Id: sys-viewer-vapjrnl
Setting Key: AllowResetTaxOnLines  Setting Value: true (default false)

When enabled, when the AP Journal parent Tax Group Id is changed the user will be alerted that the Reset Tax On Lines button should be pressed to go thru the Inventory, General and Subcontractor lines that have a Tax Group Id and emulate changing that field and updating the tax amount. If any errors occurs during the changing of the tax lines an Error Log will display at the end of the process to tell the user what to fix.

Default Balance Sheet GL Entity (Intercompany Installations)

See Default Balance Sheet Entity for Journals  for details on implementing the Setting Keys DefaultBalanceSheetEntity and UseDefaultBalanceSheetEntity.

Registry to Retain Date and Period from Initial Entry

When entering in invoices in the AP Journal, if the Effective Date and the Period ID are changed, they remain the same for the next journal if there is no PO entered. But if you do enter a PO ID, then the period goes back to the default. The effective date does not change. With the following registry enabled, the Accounting Period and Date will not change from the first journal entry in the session, even if a PO Id is specified.

Registry Id: sys-viewer-vapjrnl        

Setting Key: retainDateAndPeriodWhileInSession   Setting Value: true (default false)

Warn / Error if Vendor Tax Does not Match Job Cost Tax

If the calculated tax does NOT match the vendor invoice,  the user may adjust the tax amount on the taxes tab and add the AP journal. However, Job Cost would be incorrect, and the D/C Pass-thru not equal to zero.  (Debit Expense 106.00, Credit Use Tax Payable 6.00, Debit Use Tax Payable 6.50, Credit A/P 106.50)

The following registry may be enabled to either warn the user that job cost tax does match the calculated Vendor Invoice tax (but allow the journal to be saved), or error and not allow the save until the calculated and job cost tax totals match.

Id: sys-viewer-vapjrnl

Setting Key: ValidateTaxCost    Setting Values: Warning or Error (default is neither)

If Warning is selected, a message will display the Tax Cost Amount on the Tax Tab, and the Tax Cost Amount in the purchase items. When the user clicks OK, the journal entry will be saved / added.

If Error is selected, a message will display the Tax Cost Amount on the Tax Tab, and the Tax Cost Amount in the purchase items, and instruct the user to adjust the tax cost stored in the line items to reflect the correct tax. After clicking OK, the user must adjust these values before the journal entry can be saved / added.

Validate GL Entity Group

SAM Pro has the capability to validate the consistency of the GL Entities entered in the parent and children of the AP Journal.  The validation can take the form of either an error or a warning based on the content of this following registry entry.

Id: sys-viewer-vapjrnl

Setting Key: ValidateGLEntityGroups Setting Value: option

where option is replaced by either error or warning. Note that two entities are considered 'compatible' if they share at least one common GL Entity Group.

Execute ‘New Record’ on Adding and or Changing Record

Id: sys-viewer-vapjrnl

Setting Key: NewRecordAfterAdd Setting Value: true
Setting Value:
NewRecordAfterChange Setting Value: true

These options will execute the ‘new record’ function each time this journal entry is added (NewRecordAfterAdd=true) and/or an journal entry is saved (NewRecordAfterChange=true).

WO Billing / PWP Arrangements

This registry option concerns Service Invoicing where a firm has PWP arrangements with their subs. During Vendor Invoice entry, the user may specify an AR Invoice Id to attach to the Job History entries, making it appear as though the charges have already been billed.  In cases where the sub PO was issued for a single WO and that WO has appeared on an AR Invoice, the AR Invoice will be recorded by default when the AP Entry is made. Specifically:  

1. If a WO Id appears on the Purchase Order’s Main tab, Job History is queried to determine if the WO has been invoiced.
2. If the WO has been invoiced, the AR Invoice logic is activated.

Conversely, if the APJ entry has no PO or the PO has no WO or the WO hasn't been invoiced, then the AR Invoice logic is not activated.

Important Usage Note: This feature only attaches an AR INVOICE ID for the VARIANCE AMOUNTS entered in AP. PO Cost lines  (those with Source Jrnl = 'Purchase' or 'Receipt') are NOT updated with an AR INVOICE id, as it is assumed the PO was received PRIOR to the AR Invoice being created so these Transactions already have an AR Invoice Id linked to them.

This registry allows the user to adjust the default behavior to either prompt the user to determine if the AR Invoice Id should be attach, or to never attach the AR Invoice Id.  You may want to adjust the default behavior if  your firm creates an AR invoice before the costs are received; you would still have to use the PWP Billed function to link ALL Costs.

Id: sys-viewer-vapjrnl

Setting Key: AttachCostsToARInvoiceForWO Setting Value: always or never or prompt

The attachment (whether manual or automatic) is not made to reversed AR Invoices.

The default behavior is 'always'.  This means that, whenever possible, the A/R Invoice Id should be set automatically. This behavior will occur if no registry entry is made.

Setting the option to 'prompt' means that the user will be informed that an A/R invoice for the WO and gives them the option of attaching it the AP Journal costs.

Setting the option to 'never' means that the A/R invoice will not be set.

Prevent Use of Completed Job Cost Code or Billing Items

Id: sys-viewer-vapjrnl

Setting Key: CostCodeDateCompletedValidation Setting Value: error

Setting Key: BillingItemDateCompletedValidation Setting Value: error

Currently, the system warns you if you enter a billing item or job cost code whose Date Completed exceeds the effective transaction date. These options change the current warning to an error.

It's also important to note that the validation logic implemented by this registry entry only applies when either a Cost Code Id or a Billing Item Id field's value is explicitly changed by the data entry user.  The Cost Code and Billing Item registry entries are independent from one another.  Note that these options may be specified in Registry Entry Global Settings registry entry for a more far-reaching implementation.

Require a GL Entity for Income / Expense Accounts

Id: sys-viewer-vapjrnl

Setting Key: ValidateGLEntityIE Setting Value: Error or Warning (pick one or the other)

Specify Error if users should be prevented from saving the entry without specifying a GL Entity (if the GL Account is an Income or Expense account) or Warning if the user should simply be warned of the situation.

Deny a GL Entity for Balance Sheet Accounts

Id: sys-viewer-vapjrnl

Setting Key: ValidateGLEntityBS Setting Value: Error or Warning (pick one or the other)

Specify Error if users should be prevented from saving the entry with a GL Entity specified for a Balance Sheet Account, or Warning if the user should simply be warned of the situation.

Prevent Multiple Entry of the same Vendor Invoice Numbers

Id: sys-viewer-vapjrnl

Setting Key: PreventMultipleInvoiceNumberUse Setting Value: true

If implemented, this option will prevent the same Vendor Invoice from being vouchered multiple times.

Disable Account Type Validations on General lines

In version 7.2.476.098, validations were added to the AP Journal to prohibit the entry of AR Control, AP Control & Bank accounts on General lines. Some users find that these validations conflict with their processing procedures: the following registry entry may be implemented turn the default error behavior (that does not allow the account to be selected) into a warning.

WARNING: disabling this validation is NOT recommended unless needed for credit card/eft processing. In particular, entering a bank account on AP General lines may result in Bank Reconciliation issues.

Setting Key: IgnoreCase3193  Setting Value: true

Credit PO’s must be Received

By default, unreceived PO lines for regular PO's may not be vouchered, but credit PO lines can be vouchered even if they aren't received. This registry option prevents unreceived credit PO lines from being vouchered.

Setting Key: CreditPOsMustBeReceived Setting Value: true

Require Approval for Vendor Invoices Exceeding Specified Amount

Id: sys-viewer-vapjrnl

Setting Key: RequiresApprovalInvoiceAmount Setting Value: dollarvalue

For example, to require approval for invoices of $10,000 or above:

Setting Key: RequiresApprovalInvoiceAmount Setting Value: 10000

If a AP Journal Entry would be set to Requires Approval via this registry, the system will display the warning that the A/P invoice will require approval.

The User will be warned if the invoice amount exceeds the registry-set limit. If the user has access to AP Approve Held Invoices (Start AP Payment Approved List), the message will also ask the user "Would you like to approve invoice now?"

If the User clicks Yes, they will be prompted to enter 40 characters of text describing the reason for the approval. This text will be written to the Vendor Invoice record's change log.

If the User clicks No, the AP Journal entry will be saved as Requires Approved; it may be approved for payment via the standard Start AP Payment Approved List.

Require Approval for Vendor Invoices Exceeding Allowed PO Variance

Id: sys-viewer-vapjrnl

Setting Key: RequiresApprovalPOVariance   Setting Value:  percentvalue

This registry enables an invoice be flagged as Requires Approval if the Invoice Total entered in the AP Journal exceeds the PO Total by the specified percent. Note that previous receipts against the PO are taken into account during this calculation. For example, to require approval if the AP Journal amount exceeds the PO total by at least 8 percent:

Setting Key: RequiresApprovalPOVariance   Setting Value: 8

If a AP Journal Entry would be set to Requires Approval via this registry , the system will display the warning that the A/P invoice will require approval. The User will be warned if the invoice amount or PO amount variance exceeds the registry-set limit. If the user has access to AP Approve Held Invoices (Start AP Payment Approved List), the message will also ask the user "Would you like to approve invoice now?"

If the User clicks Yes, they will be prompted to enter 40 characters of text describing the reason for the approval. This text will be written to the Vendor Invoice record's change log.

If the User clicks No, the AP Journal entry will be saved as Requires Approved; it may be approved for payment via the standard Start AP Payment Approved List.