These release notes describe the enhancements included in version 2026.11.1 of the Cash Application Manager - NetSuite integration app.
What's enhanced
Email Remittance matches remittance emails to bank file payments
Email Remittance now uses a customer's remittance email to find the invoices for a payment that's already in your bank file, instead of creating a payment from the email. Your bank file is the only source of cash. Cash Application Manager (CAM) saves each remittance email in NetSuite, finds the open bank payment that matches the email, adds the email's invoices to it, and applies it. The result is one customer payment, created from the bank payment.
Previously, Email Remittance created a customer payment directly from each email. When the same payment also arrived in your bank file, NetSuite could end up with a second, unapplied customer payment for the same remittance. Automated clearing house (ACH) and wire payments that arrived without invoice numbers stayed Unidentified or Unapplied until someone found the customer's email and applied them manually.
Who it's for: Accounts receivable teams that receive ACH or wire payments in a bank file without invoice details, and whose customers send the invoice list by email.
What changed:
- Remittance emails no longer create customer payments or Cash Application Manager transactions. Each remittance email from an allowed sender creates one Celigo Cash App Email Remittance record in NetSuite, under Cash Application Manager > Records > Celigo Cash App Email Remittance. CAM reads each email once and skips emails that aren't remittances. If the same remittance arrives again, for example forwarded or in another mailbox, CAM saves it as Duplicate, names the original email, and doesn't match it.
- CAM matches each email to an open bank payment that has no invoice details in the bank file. CAM considers a bank payment once it has processed the bank file, up to 15 minutes after import. Bank payments that are already applied or partially applied are never matched. The bank payment must have the same currency, an amount within Amount tolerance, and a bank date within Match window (days) of the email's payment date. When more than one bank payment fits, the tie-breakers you turn on choose between them. If more than one still fits, CAM doesn't guess, and the email needs review.
- Bank payments that already include invoice numbers in the bank file apply as before. A remittance email never changes them.
- The email and the bank file can arrive in either order. CAM checks for a match when it reads the email and again every 15 minutes. After a match, CAM creates the customer payment on its next scheduled run, up to about 15 minutes later. If no bank payment matches by the end of the match window plus 3 days, the email is listed as Unmatched.
- A customer can pay less than an invoice. CAM applies what the email says was paid and leaves the rest of the invoice open. If the bank amount differs from the email amount by no more than Amount tolerance, CAM still matches them; the difference stays unapplied on the customer payment, and the email is listed as Partially applied.
- A new Email remittances tab on the Cash Application Manager dashboard in NetSuite lists emails to review, with the reason for each. From there, you can approve a suggested match, link an email to the right bank payment, retry matching, or ignore an email. See Review email remittances on the Cash Application Manager dashboard.
- The settings for the Bank File to NetSuite [EMAIL - ACH - Gmail] and Bank File to NetSuite [EMAIL - ACH - Outlook] flows are grouped into Mailbox and Matching sections. For each setting, see Set up Email Remittance in CAM for NetSuite.
- Matching is new, with Amount tolerance, Match window (days), Bank flows to match against, four tie-breaker settings, When the bank payment's customer differs from the invoices' customer, and Apply automatically when one bank payment matches. If you leave Bank flows to match against empty, CAM searches all of the integration's bank flows.
- Minimum confidence to auto-apply is renamed Minimum confidence to match. Emails below it are listed as Low confidence instead of being matched.
- Gmail label to read and Outlook category to read are optional. Leaving them empty checks every email in the run's date range and uses more AI credits.
- Use Credit Memos, Credit memo prefix, Ignore following Customers, NetSuite Invoice Prefix, and NetSuite Invoice Identifier are removed, and you don't need to re-enter them. Invoice and customer matching uses the settings on the bank flow that brought in the payment. If you used an invoice prefix or identifier on an email flow, set it on that bank flow.
- The Bank Transactions to NetSuite [EMAIL - ACH - Gmail] and Bank Transactions to NetSuite [EMAIL - ACH - Outlook] flows are removed. Each mailbox you connect uses one flow instead of two.
Some remittances always go to a person, such as an email with credits or deductions. See the limitations in Set up Email Remittance in CAM for NetSuite.
Action required: Your Email Remittance setup switches to the new behavior when your integration app updates to this version. Celigo updates the Cash Application Manager bundle in NetSuite production accounts. In NetSuite sandbox accounts, your NetSuite administrator updates it in Customization > SuiteBundler > Search & Install Bundles > List. A sandbox refresh removes the bundle, so install it again after each refresh.
If the bundle is missing or the integration role isn't authorized, the update stops and the integration app tile shows CAM_EMAIL_BUNDLE_REQUIRED. Nothing changes, and Email Remittance keeps working as before. Install the bundle, authorize the integration role, and run the update again.
Your mailbox label or category, Minimum confidence to match, and Allowed senders carry over. Check that Gmail label to read or Outlook category to read is set; if it's empty, CAM reads every email in the run's date range and uses more AI credits. Review the Matching settings for each mailbox you use. By default, Apply automatically when one bank payment matches is on, When the bank payment's customer differs from the invoices' customer is set to Send the email to review, and every tie-breaker except Use payer name to break ties is on. See Set up Email Remittance in CAM for NetSuite.
Customer payments that Email Remittance created before this update don't change. If an invoice has two payments for the same remittance, one from the email and one from the bank file, unapply or delete the duplicate, or contact Celigo Support.