Version 1.20.34
Bug Fixes -
- Added screen field to track the currently approval level the bill payment is on to allow for correct usage of minimum approver functionality
- Updated scripts to account for correct usage of minimum approvers required
Version 1.20.33
Bug Fixes -
- Changed screen fields total to be calculated from the foreign amount field, rather than the amount field
Version 1.20.32
Bug fixes
- Addressing issues for new features in 1.20.31 by record definition change, and adding additional script.
- Fixed an issue for an immediate bank file generation after approval is not populating screen variables.
Version 1.20.31
New Features Introduced
Prevent Approvers from Approving More Than Once
A new option is available to prevent approvers from approving the same payment more than once.
When this option is enabled, if an approver is assigned to multiple approval levels for an individual payment, they may approve the payment only once throughout the entire approval process.
Example:
If Approver A approves a vendor payment at the first approval level, they will not be able to approve the same payment again at the second level, even if second-level approval is required.
Note: This feature requires:
- Advanced Bill Payment Approval to be enabled
- Bypass Lower-Level Approvals to be disabled
BPA Approval Route Enhancement
The BPA Approval Route has been moved to the BPA configuration screen. Additionally, a new field, “Minimum Number of Approvers”, has been added to each approval route record.
❗ Important Notice
In this release, implementation consultants must assist customers with data correction to ensure that existing BPA approval routes are displayed correctly in the configuration screen.
A migration script to automate this process will be provided in a future release.
Version 1.20.30
Fixed an issue on not able to populate extraction date to EP Bank Account record upon a file generation has finished.
Ref#: SC54000
Version 1.20.27
Bundle name changed to Nolan Bill Payment Approvals.
Version 1.20.26
New Features: Update Netsuite Approval Flag upon approve/reject
- This feature enables the bill payment approvals and rejections action to be updated simultaneously to the Netsuite standard approval flag.
The standard accounting feature for transaction "Vendor Payment" must be enabled to use this function. - Remarks: If this feature is used, rejecting the bill payment will not void the bill payment but instead change the approval status to "Rejected".
The operation is still voiding the bill payment if the configuration is disabled
Version 1.20.25
- Resolved an exception on allowing some user defined subsidiary role to view the bill payment other than the assigned subsidiaries.
Version 1.20.24
<Critical fix>
This update is strongly recommended for customers using BPA (v1.20.22+) as it contains a product-wide impact to an issue.
- Resolved an issue that prevents a bill payments to be approved on the scheduled process.
Version 1.20.23
- Bug fixing
- Remove the ability for Users with Cross Viewing permission to see subsidiaries not assigned to them. (They cannot Approve/Reject with that option in place).
Version 1.20.22
This update is strongly recommended for customers using BPA (v1.20.21).
- This is due to the technical changes announced by Oracle NetSuite, coming into effect as of July 30, 2024, deprecating internal calls method to Suitelet.
- No new feature is introduced in this release
Version 1.20.21
Introduce new BPA configuration option "Enforce Subsidiary Restriction by User Role".
When this option is enabled, the bank account listed will be restricted by user subsidiary's role. Support four types of setups:
- All
- All Active
- User Subsidiary
- Selected Subsidiary
This option works for both single selected or multi-selected bank accounts, for both vendor payments approval and customer refund approval.
When the option is unchecked, BPA will work as-is from the previous version.
We recommend to have this option checked if customer would like to segregate their vendor bill reviews by user roles.
IMPORTANT: The enabled option will work for user restricted subsidiary (via user preferences). However due to a Netsuite bug, the functionality will fail (i.e. allow the user to approve / reject vendor payments on a subsidiary outside their user restricted permission) if the following combination is used:
- Role is with "All" or "All Active" subsidiary, with "Allow Subsidiary Viewing" option checked
- Applied User Restriction on some specified subsidiary
Version 1.20.20
BPA-EP enhancement to generate bank files after approval.
Note : To use the BPA enhancement to generate bank files after approval, ensure that the generate Bank File After Approval checkbox is checked on the BPA Configuration record, as well as the products listed below are in the stated version or higher.
Bill Payment Approvals
1.20.20
Nolan Electronic Payments for NetSuite
2.02.18
Background Processing by Nolans
1.00g
Version 1.20.19
Bug fixing
- Usage Limit Error fixing
Version 1.20.18
- Fixed for email remittance not sending out correctly in some scenarios (bundled together with EP release 2.01.08)
Version 1.20.16
Generate Bank File
- Optimisation of search to avoid NetSuite script timeout.
Version 1.20.15
Approve/Reject
- Check for MutliCurrency feature enabled (as well as OneWorld account type) before attempting to set "Consolidation Type" on a search.
