Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Description: In this topic, the user will learn the workflow for processing vendor payments. This function allows payments to be submitted to approved vendors, per a client’s authorization.

Role Required: Super User

Permission Required: Vendor Admin

Mode: FI

Step 1: Allow Vendor Payments on Service Codes

A service code must allow payments or a new service code must be set up for the vendor.

Vendor payments can only be created for dollar-based hourly service codes that allow them, or as a separate vendor account type service code. The vendor service code would be used in situations where the authorization is separate from another service. If a vendor service code is created, users must create a vendor funding account and authorization rather than utilize an hourly funding account and authorization.

Step 2: Create and Manage Vendor Profiles

Vendor profiles are created to process invoices for vendors. They do not have the ability to log in and are not sent a confirmation email when the profile is created.

Step 3: Create and Manage Vendor Service Accounts

After a profile is created, a service code must be created to link the client to the vendor. The system automatically creates a vendor service account when a vendor payment entry is created. This allows employers to create an entry when needed, even if an admin user has not created the service account.

Step 4: Create Vendor Payment Entries

Vendor payment entries are created by a super user or employee with vendor admin permission and must have a copy of the invoice attached to the entry. These entries must be approved by the employer, supervisor, or super user.

Step 5: Vendor Entries are Processed through Payroll and Billing

Approved vendor entries are processed through payroll and billing batches.

Preconditions:

  • Service Code exists that allows Vendor Payments
  • Client has an active funding account and authorization for the above service code
  • FI Employee is given Vendor Admin Permission
  • New Vendor Request Message Template is active
  • Optional: Client has Vendor Payments enabled on Client Profile (this allows the Client ability to submit New Vendor Requests and New Vendor Payment Entries in addition to the Employer)

Process:

  • Employer or Client submits New Vendor Request
  • Vendor Admin Permission receives notification
  • Vendor Admin Permission creates new vendor profile
  • Vendor Admin Permission replies to DCI message to notify Employer that Vendor Profile has been created
  • Employer or Client creates new vendor payment entry
    • System checks if a Vendor Service Account exists for vendor/client/service code combo
      • If one does not exist, the system will create one
    • System creates parent vendor payment entry in canceled status and child vendor payment entries for each date of service in pending status
  • Vendor Admin Permission reviews (approve/reject) pending vendor payment entries
  • Payroll Processor processes approved vendor payment entries in payroll batch
  • Billing Processor process approved vendor payment entries in billing batch

Notes:

...

Content by Label
showLabelsfalse
max5
spacesDCI
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel in ("payroll","vendor") and type = "page" and space = "DCI"
labelsvendor payroll

...

Page properties
hiddentrue
Related issues