Payments to vendors

Security
Built-in filters

The Payment window in Accounts Payable allows you to enter payments manually and to maintain existing payment records. Payments can also be entered manually from the Invoice and Vendor windows. In addition, ActivityHD has a group pay process available from the shortcut menu on the Invoices folder by selecting Select and Pay or from the HD view by selecting invoices to pay and clicking .

×

Payments security

Common accesses available on payments

Access A user with this access can...
Change Use the mass change action on payments.
Custom Fields Create and edit custom fields for payments.
Data Have read-only access to payments from anywhere in the software (e.g., field validations, filters, date expressions).
Delete Delete payments.
Edit Edit payment records.
Export Export payment records from ActivityHD.
New Create new payment records.
Read Have read-only access to payment records.
Report Run reports with payment information (including the ability to include payment drill-down detail on GL reports).
Report Designs Create and edit report designs with payment information. This access enables the Report Designs button on the Output tab of report dialogs.
Shared Answers Create and edit action profiles and report profiles related to payments.
Shared Filters Create and edit shared filters on payments.
Visible View the Payments folder in the Navigation pane.

Special accesses available on payments

Access A user with this access can...
Advice Process remittance advice.
EFT Process EFT payments.
Merge Merge payments.
Print Print checks.
Proof Run proof process to determine if payments are valid for merging.
Reprint Reprint checks.
Update APCodes Run the Update Payment APCodes process.
Void Void payments.

 

×

Payment filters

The following built-in filters are available for payments:

Filter Name Effect
? Amount Range Prompts for a range of amounts and lists the payments with a payment amount in that range.
? Has APCode Prompts for an APCode and lists payments on invoices which reference the APCode.
? Merge # Range Prompts for a range of merge numbers and lists payments with merge numbers in that range.
? Payment Date Range Prompts for a range of dates and lists payments with a payment date in that date range.
? Reference Prompts for a reference and lists payments with a reference that contains the specified search string.
? Vendor Prompts for a vendor name and lists payments to vendors with a name that contains the specified search string.
? Vendor Description Prompts for a vendor description and lists payments to vendors with a description that contains the specified search string.
Merged Payments Lists merged payments only.
New Payments Lists unmerged payments only.
Ready for EFT Lists merged payments that have not been disbursed and have not been voided that have a payment type of "EFT".
Ready for EFT Advice Lists merged payments with a payment type of "EFT" that have been disbursed, have not been voided, have not been sent, and where the payment email address is not blank.
Ready to Print Lists merged payments that have not been disbursed and have not been voided that have a payment type of "Check".

 

×

Entry Totals

Balancing for Payment

Accounts
Displays segment codes for the segments which require balancing. Displays question marks for segments that do not require balancing. If none of the segments requires balancing, the account number shows all question marks.
Unit
Displays the unit associated with the account mask on this row.
Begin Date
This date and the end date are determined by the balance option selected on the ledger for the account mask. The options are:
  • None. If this option was used, the range of dates is 01/01/1950 to 12/31/9999.
  • Period. If this option was used, the range of dates is the period begin and end dates of the period in which the date on the journal entry detail line falls.
  • Daily. If this option was used, the date on the journal entry detail line is used as both the begin date and end date.
End Date
See "Begin Date".
Debit
Displays the amount debited to the account mask on the journal entry. Debits in red indicate an out-of-balance condition.
Credit
Displays the amount credited to the account mask on the journal entry. Credits in red indicate an out-of-balance condition.
Unit Description
Displays the description of the unit associated with the account mask.

 

×

Report Email dialog

From
The email account from which to send the email. Valid options are:
  • Windows user default account. Sends email using the user's Windows default email account. For most users, this is the account configured in Outlook or another email client application.
  • Server personal. Sends email using the email configuration for the system or company server and the email address on the current user's authorized user record. The authorized user record must have a confirmed email address.
  • Server generic. Sends email using the email configuration and "from" address for the system or company server. This option requires "Send generic" access to the Server Email resource.
To
The email address(es) to which to send the email. Separate email addresses with semi-colons.
CC
The email addresses to copy on the email. Separate email addresses with semi-colons.
BCC
The email addresses to blind copy on the email. Separate email addresses with semi-colons.
Subject
The subject line.
Text box
The body of the email.

 

×

AP remittance advice email keywords

The following keywords can be used in the subject and body of the Email Defaults tab in the Generate Remittance Advice wizard:

  • Informational:
    • <REFERENCE>
    • <DATE>
    • <CUSTOMER #>
    • <VENDOR NAME>
    • <VENDOR DESCRIPTION>
    • <ADDRESS NAME LINE 1>
    • <ADDRESS NAME LINE 2>
  • Totals:
    • <AMOUNT>
    • <BALANCE> (before payment)
    • <DISCOUNT>
    • <WITHHELD>

When included, keywords are replaced with their corresponding payment value.

 

×

Validation messages for the Void AP Payments wizard

The following messages may be returned in the void payments process for payments which do not pass validation:

  • Payment is not merged. Only merged payments can be voided.
  • Payment is a reversal payment. The payment is a reversal payment that voided another payment. Reversal payments cannot be voided.
  • Payment is already voided. Since the payment has already been voided, it cannot be voided again.
  • Payment has invoices selected by an unmerged payment.
  • Payment is reconciled to statement (xxxxx).
  • Payment has payroll tax deposit marked "Paid":

    xxxxx