The Hook: Use this process to resolve errors on the Import PMS/POS screen caused by multiple Income Journal batches existing for the same date.
Prerequisites:
- Access to Input Journals.
- If your error is caused by an inactive account, you must also have access to Admin > Customize Accounts.
- Note the Account Number and Batch Number from your error message before beginning this workflow.
The Steps:
Troubleshooting Duplicate or Incorrect Batches
- Navigate to Accounting > Input Journals.
- Locate the batches for the date causing the error.
- Identify the duplicate/incorrect batch.
- Click the List icon next to the incorrect batch.
- Click Delete icon for the line that is blank and select Save.
- Return to the Submit Income Journal to submit the batch.
Note: If you need to delete an Income Journal batch, you should review/export the Daily>Manual Adjustments Report because those will also be deleted when the batch is deleted and will need to be re-entered.
Troubleshooting Inactive Account(s) in a Batch
- Navigate to Accounting > Input Journals.
- Locate the date or Batch Number causing the error.
- Click the List icon next to the incorrect batch.
- Locate the specific Account Number or the line that is completely blank.
- Click the Delete icon for the row if there is no data in the Stat and Amount columns.
Click Save.
Activate an Inactive Account
Follow these steps if the account row in the batch has data in the Stat and Amount columns, but the account is currently inactive.
- Navigate to Admin > Customize Accounts.
- Click the Options icon to filter the departments and account types.
- Locate the Account Number that appeared in your error message.
- Check the box in the Is Active? column to activate the account.
- Click Save.
The Result Validation:
- Success: The error message clears, and the import screen loads the single correct batch.
Note: If you need to delete an Income Journal batch, you should review/export the Daily>Manual Adjustments Report because those will also be deleted when the batch is deleted and will need to be re-entered.
Comments
0 comments
Article is closed for comments.