Email Remittance connects a Gmail or Microsoft Outlook mailbox to the Cash Application Manager (CAM) for NetSuite integration app, so CAM can use your customers' remittance emails to find the invoices for payments that are already in your bank file. Use this article to add the Email Remittance bank, connect a mailbox, configure the email flow's Mailbox and Matching settings, and enable the flow. It's for CAM administrators who already have the integration app installed. If you haven't installed CAM, see Install Cash Application Manager for NetSuite first.
How Email Remittance works with your bank file
Your bank file is the only source of cash. A remittance email never creates a payment; it supplies the invoices for a bank payment that arrived without them.
- CAM uses AI to read the payer, payment amount, payment date, payment reference, and invoice numbers from the email body or one attachment. It saves each remittance email as a Celigo Cash App Email Remittance record in NetSuite and skips emails that aren't remittances.
- CAM looks for an open bank payment from the bank flows in Bank flows to match against. The bank payment must be Unapplied, Unidentified, or in Errors, with no invoices or credit memos yet. It must also have the same currency as the email, an amount within Amount tolerance, and a bank date within Match window (days) of the email's payment date. Applied and Partially applied bank payments are never matched.
- 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 is listed as Ambiguous.
- When one bank payment matches, CAM adds the email's invoices to it. With Apply automatically when one bank payment matches selected, CAM's next processing run creates the customer payment and applies it. Otherwise, the match waits for your approval as a Suggested match.
- The email and the bank file can arrive in either order. A bank payment can be matched only after CAM processes the bank file. CAM checks for matches every 15 minutes by default; see Summary of scheduled Cash Management Application scripts in NetSuite. If no bank payment matches by the end of the match window plus 3 days, the email is listed as Unmatched.
- If the same remittance arrives again, for example forwarded or in your other mailbox, CAM saves the copy as Duplicate and doesn't match it. A remittance that arrives in both your bank file and an email produces one customer payment.
Emails CAM can't match or apply are listed under Email remittances on the Cash Application Manager dashboard, with the reason. See Review email remittances on the Cash Application Manager dashboard.
Prerequisites
- Email Remittance doesn't require a separate license or a bank license. Every CAM for NetSuite integration app tile has an Email Remittance bank in the All Banks list.
- Each mailbox you connect uses one mailbox connection and one flow.
- A bank flow in this integration imports the payments your customers send remittance emails for.
- Intelligent Document Processing is turned on for your account if you want CAM to read attachments. Remittance emails with the details in the body don't need it.
- If your organization restricts third-party app access in Google Workspace or Microsoft Entra, ask your Workspace or Entra admin to allow Celigo's OAuth apps before you connect a mailbox.
Add the Email Remittance bank
New installs: Email Remittance is added to your All Banks list automatically when you install your first bank. There's no separate step.
Existing installs where every licensed bank is already installed: Email Remittance is added at the end of the bank list. No action is needed.
Existing installs that still have licensed banks to add: Email Remittance is added after the first bank. You can leave it there and continue installing the remaining banks.
Note: To have Email Remittance at the end of the All Banks list, uninstall it, and then install the remaining banks in the order of your license documentation. Once no licensed bank remains, select Add Bank and add Email Remittance. If Email Remittance is missing from All Banks, use the same step.
Once Email Remittance is in your bank list, select Email Remittance in All Banks at the top right of your integration app tile. Adding the bank creates two mailbox connections and two flows, Bank File to NetSuite [EMAIL - ACH - Gmail] and Bank File to NetSuite [EMAIL - ACH - Outlook]. The connections aren't authorized and the flows are disabled until you complete the steps below. If you add Email Remittance back after removing it, the integration app reuses your original connection names, and you sign in again.
Connect a mailbox
Connect Gmail, Outlook, or both. Connect only the mailbox or mailboxes your accounts receivable team uses to receive remittance emails.
- With Email Remittance selected in All Banks, go to Connections.
- Select Gmail Mailbox Connection (Cash Application Manager for NetSuite) [Email Remittance] or Outlook Mailbox Connection (Cash Application Manager for NetSuite) [Email Remittance].
- Select Save & authorize, then sign in with the Google or Microsoft account for the mailbox that receives remittance emails and grant the requested read-only permissions.
CAM requests read-only access: gmail.readonly for Gmail, and openid, offline_access, User.Read, and Mail.Read for Outlook. It never writes to your mailbox, and it never removes or changes the label or category you apply.
A mailbox connection you haven't signed in to doesn't show as Connection down on your tile. That status appears only after integrator.io tries to use the connection and fails, so an unauthorized connection looks healthy until you enable its flow.
Label remittance emails automatically
CAM reads the emails that carry the Gmail label or Outlook category you set in the email flow's Mailbox settings. Set up a Gmail filter or an Outlook inbox rule to apply it when a remittance email arrives, rather than labeling messages by hand.
- Gmail: a space or slash in a label is read as a hyphen, so CAM-Remittance also matches the labels CAM Remittance and CAM/Remittance.
- Outlook: the category must match exactly.
- If you leave the label or category empty, CAM checks every email in the run's date range and skips the ones that aren't remittances. Checking more emails uses more AI credits.
The flow checks for new mail by each message's received time, not the time the label was applied. An email labeled after its time window has passed isn't picked up on the regular schedule. To pick it up, select Run now on the flow and set an earlier start date. CAM reads each email once, so checking a wider date range doesn't create duplicate records.
Configure the email flow settings
Each mailbox has its own Bank File to NetSuite [EMAIL - ACH - Gmail] or Bank File to NetSuite [EMAIL - ACH - Outlook] flow. Configure its settings before you enable it.
- With Email Remittance selected in All Banks, go to Flows > EMAIL.
- Next to the Gmail or Outlook flow, select Settings.
- Set the Mailbox and Matching settings described below.
- Select Save.
Mailbox settings
| Setting | Description | Default |
|---|---|---|
| Gmail label to read (Gmail flow) or Outlook category to read (Outlook flow) | The label or category that marks remittance emails. Leave it empty to check every email in the run's date range, which uses more AI credits. See Label remittance emails automatically. | — |
| Minimum confidence to match | A value from 0 to 1. An email CAM reads with a lower confidence isn't matched automatically; it's listed as Low confidence under Email remittances. Very short emails, such as a single line, can score below 0.9. | 0.9 |
| Allowed senders | The email addresses or domains allowed to send remittance emails, separated by commas or new lines. A domain also covers its subdomains, and entries aren't case-sensitive. Emails from other senders aren't read and don't use AI credits. Leave it empty to accept every sender. See Restrict which senders CAM reads. | Empty |
Matching settings
| Setting | Description | Default |
|---|---|---|
| Amount tolerance | The largest difference, in the payment currency, allowed between the amount in the email and the bank payment, for example 5 to cover wire fees. The difference stays unapplied on the customer payment, and the email is listed as Partially applied. | 0 (exact amount) |
| Match window (days) | How many days before or after the email's payment date the bank payment can be dated, from 0 to 60. | 10 |
| Bank flows to match against | The bank file flows whose payments these emails can be matched to. Leave it empty to match against every bank file flow in this integration, including ones you add later. | Empty |
| Use payment reference to break ties | When more than one bank payment fits, picks the one whose bank reference or memo contains the payment reference from the email, such as a check number, ACH trace number, or wire reference. | Selected |
| Use invoice numbers in the bank memo to break ties | When more than one bank payment still fits, picks the one whose bank reference or memo contains an invoice number from the email. | Selected |
| Use the bank payment's customer to break ties | When more than one bank payment still fits, picks the one CAM identified as belonging to the customer of the email's invoices. | Selected |
| Use payer name to break ties | When more than one bank payment still fits, picks the one whose payer or customer name matches the payer in the email, ignoring punctuation and suffixes such as LLC or Inc. A name alone never matches an email to a payment. | Cleared |
| When the bank payment's customer differs from the invoices' customer | What happens when CAM already identified a customer for the bank payment and the email's invoices belong to a different customer. Send the email to review lists the email as Needs review. Use the email's invoices anyway adds the invoices to the bank payment. Placeholder customers set up for unidentified payments aren't compared. | Send the email to review |
| Apply automatically when one bank payment matches | Adds the email's invoices to the matched bank payment so CAM's next processing run applies it. Clear it to list each match as Suggested match under Email remittances, where you approve it first. | Selected |
Invoice and customer matching use the settings on the bank flow that brought in the payment, such as NetSuite Invoice Prefix and NetSuite Invoice Identifier. See File import settings in Cash Application Manager.
Restrict which senders CAM reads
A labeled mailbox folder isn't a bank feed: any email that lands in it is a candidate for AI extraction, including a forwarded or spoofed message. Set Allowed senders to the domains or addresses your customers and their AP platforms send from, for example your customers' Paymerang, Bill.com, or Ramp sending addresses. CAM then skips every other sender before the AI step.
CAM also checks the receiving mail server's SPF and DKIM results where the mailbox provider exposes them. On Gmail, an email with an SPF or DKIM result of fail, softfail, or permerror is listed as Needs review. Missing authentication headers don't hold an email, and Outlook doesn't provide these headers.
A remittance email doesn't always come from your customer. Some banks offer a payables service: when your customer pays through their bank's payables portal, the bank emails the payment advice to you on the customer's behalf. This is more common with large corporate payers using banks such as JPMorgan or HSBC. If your customers pay this way, add the bank's sending domain to Allowed senders alongside your customers' addresses and AP platforms.
Enable the flow
- With Email Remittance selected in All Banks, go to Flows > EMAIL.
- Turn on Enabled for the flow of each mailbox you configured.
The flow runs on its schedule, the same as your other CAM flows. A run you start with Run now reads your live mailbox and uses AI credits the same as a scheduled run; there's no separate test mode.
Uninstall Email Remittance
Uninstalling the Email Remittance bank removes it from your bank list, along with its mailbox connections and flows. Your other banks aren't affected, and the Celigo Cash App Email Remittance records stay in NetSuite. Follow Uninstall an integration app account, store, bank, or tile and select Email Remittance as the bank to uninstall. To add it back later, see Add the Email Remittance bank.
Limitations
- CAM reads one attachment per email: a PDF, PNG, JPG, TIFF, XLSX, XLS, or CSV file, including scanned PDFs. When an email has more than one attachment, CAM reads a file whose name looks like a remittance first; invoice, W-9, and statement names are ranked last.
- Word (DOCX) attachments aren't read; CAM uses the email body instead. An image with a transparent background can't be read, and a picture pasted into the email body isn't treated as an attachment. If the remittance details are only in an attachment CAM can't read, the email is listed as Needs review.
- There's no Celigo inbound address for remittance emails. Email Remittance reads only a Gmail or Outlook mailbox you connect.
- An email with credits or deductions, invoices that total more than the payment, no payment amount, or no invoice numbers isn't applied automatically. It's listed as Needs review, and you apply the payment manually.
- When two emails match the same bank payment, neither is applied automatically; both are listed as Ambiguous.
- Applied and Partially applied bank payments are never matched, and neither is a bank payment that already has invoices or credit memos. This includes a payment your bank flow applied to a customer's open invoices before the email arrived.
- A difference within Amount tolerance stays unapplied on the customer payment. CAM doesn't write it off.
Related articles
- Review email remittances on the Cash Application Manager dashboard
- Email Remittance FAQ
- Troubleshoot Email Remittance errors
- Add a Bank in Cash Application Manager
- File import settings in Cash Application Manager
- Uninstall an integration app account, store, bank, or tile
- Cash Application Manager – NetSuite Integration App overview