/
Cashiering Batches Coming Into Enterprise ERP At Step 10

Cashiering Batches Coming Into Enterprise ERP At Step 10

Description of Issue

Error releasing batch number XXXXX

One or more Tenders in this Batch needs a deposit number prior to release.

Context
  • Tyler Cashiering

  • Enterprise ERP

  • Payment Entry

  • General Billing

  • Miscellaneous Cash

  • Accounts Receivable

Cause

The WSUSER role (or similar webservice user role) has Account Receivable permission Deposit numbers on payment batches set to Always Required.

Resolution

Tyler Cashiering users will need to include tender deposits on batches and transactions processed in Tyler Cashiering. If desired, the restriction can also be removed entirely from the webservice role:

System Administration > Security > Roles

  1. Click Search

  2. Enter the Role ID

  3. Click Accept

  4. Click the Accounts Receivable folder

  5. Click Update

  6. Set Deposit numbers on payment batches to Not Required

  7. Click Accept

Additional Information










Related content

Cashiering Batches Pending Approval
Cashiering Batches Pending Approval
More like this
Cashiering Requiring Some Users to Have Deposit Numbers, but Not Others
Cashiering Requiring Some Users to Have Deposit Numbers, but Not Others
More like this
An error occurred while releasing the Batch Message In Hub Approvals
An error occurred while releasing the Batch Message In Hub Approvals
More like this
Payments Batches not Closing Automatically - One or more Tenders in this Batch needs a deposit number prior to release
Payments Batches not Closing Automatically - One or more Tenders in this Batch needs a deposit number prior to release
More like this
Modify the requirement to have a Deposit Reference in Tyler Cashiering
Modify the requirement to have a Deposit Reference in Tyler Cashiering
More like this
The user permissions for user.name require that the payment have a deposit number
The user permissions for user.name require that the payment have a deposit number
More like this