Submit/Next
This button will only be enabled when the Summary > Payment Method does not have a Type of System Check.
The Submit/Next button will initiate similar functionality and validations that the Save button performs (and more) and then it will leave the user on a new customer payment Summary screen as if the user had clicked add customer payment. This may be desired if the current user is entering a series of Customer Payments. The Legal Entity, Document Date, Post Date, Fiscal period and Bank Account fields on the new customer payment will all be defaulted to values from the current saved customer payment.
Customer Payments can be submitted and posted without having any Paid Documents or Details grid entries.
Upon success, the status of this customer payment will be updated to SUBMITTED (and who and when the submit occurred will be saved to the system).
Roles
This button is only available to users having the Administrator, AR Poster or AR User role.
Validations
While you can save a financial document violating certain rules, you will not be permitted to submit or post the document until they are resolved. If any of the validations fail for any row on the document, the entire document cannot be posted.
- Standard financial document validations:
-
- Only System Administrators can post into closed Fiscal Periods / Years
- When posting a recurring document and the document is not the last in the series, the post process will attempt to automatically create the next occurrence into the next fiscal period. The post will be prevented if the next fiscal period does not exist
- Standard financial document validations for Summary level information:
- Legal Entity must be a financial organization
- Legal Entity must still be defined as Legal Entity at time of posting
Standard financial document validations for each Detail row:
- The row's Account must be active
- Transaction Entry must be allowed for the Account
- Document's Post Date must be within the allowed transaction date range for Account
- Account must still be valid for the Organization
- Organization must be active
- Organization must belong to this document's Legal Entity
- Transaction entry must be allowed for Organization
- Document's Post Date must be within the allowed transaction date range for Organization
- Project must be provided if Account requires project
- Project must not be provided if Account does not require project
- Project provided must be active
- Project's Owning Organization must belong to this document's Legal Entity
- Task must be provided if project is defined as "requires tasks for expense reporting"
- Task provided must be active
- When Project provided, Project Type must be provided
- When Project provided, Expense Type must be provided
- Expense Type must be valid for the Account
- Expense Type must be valid for the project
- Item must be valid for the project
- Customer Payment financial document validations for Summary level
- Customer must be valid for the Legal Entity
- Customer Payment financial document validations for - Paid Document & Detail level
-
- The sum of Payment, Discount and Write Off cannot exceed the Balance on a Paid Documents row
- Additional Submit/Post time validations:
-
- The sum of the amounts applied in the Paid Documents and Details grid are not:
-
- greater than a positive Summary --- Payment Amount
- less than a negative Summary --- Payment Amount