AI Summary: This article explains how to connect a Gmail or Outlook mailbox to the Cash Application Manager (CAM) for NetSuite integration app so it can create customer payments directly from remittance emails, not just from bank files. Use it if your AR team receives remittance advice by email and you want those payments applied automatically. It's for CAM administrators who already have the integration app installed. After completing these steps, CAM reads your labeled remittance emails, extracts the payment details with AI, and posts matching payments using the same logic it applies to bank file remittances.
Overview
Email Remittance lets the Cash Application Manager for NetSuite integration app create customer payments directly from remittance advice that arrives by email, instead of only from bank files on your FTP server. The integration app connects to a Gmail or Microsoft Outlook mailbox you choose, reads the emails you've labeled as remittances, and uses AI to extract the payer, invoice numbers, and payment amount from the email body or a PDF attachment. When a remittance references an early-payment discount, a deduction, or a short pay, CAM extracts that adjustment too and applies it along with the payment. The extracted data goes through the same matching, exception, and posting logic as a bank file.
Use this article to connect a mailbox, configure what CAM reads from it, and enable the Email Remittance flows. It's for CAM administrators who already have the integration app installed. If you haven't installed CAM yet, see Install Cash Application Manager for NetSuite first.
Prerequisites
- Email Remittance doesn't require a separate license or add-on. It's available as a bank on every CAM for NetSuite integration app tile, alongside your other banks in the All Banks dropdown. If you already have other banks installed, see "Add the Email Remittance bank" below for the order to install it in.
- Each mailbox you connect uses one integrator.io endpoint and two flows: Bank File to NetSuite and Bank Transactions to NetSuite. Gmail and Outlook together use two endpoints and four flows. On an Endpoint (2022) license, the new flows do not count, but each mailbox connection does. On a Platform (2024) license, you need that many open flows and open endpoints before you enable the mailbox. Every Cash Application Manager for NetSuite integration app tile gets an Email Remittance bank with this update.
- Intelligent Document Processing is turned on for your account if you want the integration app to extract data from PDF attachments. Body-only remittance emails don't require it.
- You know which Gmail label or Outlook category you'll use to mark remittance emails, and you're able to set up a Gmail filter or Outlook inbox rule to apply it automatically (see Label remittance emails automatically).
- 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 is no separate step.
For existing installs where every licensed bank is already installed, Email Remittance is added at the end of the bank list. No action is needed.
For existing installs that still have licensed banks to add: Email Remittance is added after the first bank. You can leave it there and continue with the installation of the remaining banks.
Note: If you want Email Remittance at the end of the All Banks list, uninstall it, and install the remaining banks in the order of your license documentation. Email Remittance is added after all the banks in the license are added. Select Add Bank once no licensed bank remains and complete adding Email Remittance. If Email Remittance is missing after the update, use the same step.
Once Email Remittance appears in your bank list, select Email Remittance from the All Banks dropdown at the top right of your integration app tile, next to Add Bank. Adding the bank creates its two mailbox connections and four flows: Bank File to NetSuite [EMAIL - ACH - Gmail], Bank Transactions to NetSuite [EMAIL - ACH - Gmail], and the matching [EMAIL - ACH - Outlook] pair, all disabled and unauthenticated until you complete the steps below. If you're adding Email Remittance back after removing it, the integration app reuses your original connection names, so you'll need to sign in again.
Connect a mailbox
You can connect Gmail, Outlook, or both. Connect only the mailbox or mailboxes your team actually uses to receive remittance emails. Make sure Email Remittance is still selected in the All Banks dropdown at the top right of your integration app tile. If you land on this page with a different bank selected, you'll see that bank's connections instead.
- With Email Remittance selected in the All Banks dropdown, go to Connections. By default, the connections are offline.
- Select the connection named 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, openid, offline_access, User.Read, and Mail.Read for Outlook). It doesn't write back to your mailbox; it never removes or changes the label or category you apply.
An unauthenticated mailbox connection doesn't show as Connection down on your tile. That status only appears once integrator.io has tried to use the connection and failed, so a connection you haven't signed in to yet looks the same as a healthy one until you enable its flow.
Label remittance emails automatically
CAM only reads emails that carry the Gmail label or Outlook category you configure in the next section. Set up a Gmail filter or an Outlook inbox rule to apply that label or category automatically when a remittance email arrives, rather than labeling messages by hand.
Applying the label after the fact can cause the integration app to miss the email on its regular schedule: the Gmail and Outlook flows check for new mail using each message's received time, not the time you applied the label. An email labeled after that time window has already passed isn't picked up automatically. If this happens, select Run now on the flow and set an earlier start date. CAM's duplicate detection makes it safe to re-check a wider date range without creating duplicate payments for remittances it already posted.
Configure the file import settings
Each mailbox has its own Bank File to NetSuite [EMAIL - ACH - Gmail] or [EMAIL - ACH - Outlook] flow. Configure its settings before you enable it.
- With Email Remittance selected in the All Banks dropdown, go to Flows.
- In the left panel, select EMAIL. (The General list next to it holds the matching and posting flows CAM uses for every channel, bank file, and email alike; you don't need to change anything there.)
- Next to the Gmail or Outlook Bank File to NetSuite flow, select Settings.
- Configure the fields described in the Field reference below.
- Select Save & close.
Field reference
Fields appear on the File Import tab in the order listed below. This table reflects the Gmail flow's File Import tab; the Outlook flow mirrors it except for the label field, flagged below.
| Field | Description |
| Gmail label to read | The Gmail label applied to remittance emails. Defaults to CAM-Remittance. A space or slash is searched as a hyphen, so AR Remit and AR/Remit are both read as AR-Remit. |
| Outlook category to read | The Outlook flow's equivalent field. |
| Minimum confidence to auto-apply | The AI confidence score, from 0 to 1, below which CAM won't post a payment automatically. Default: 0.9. Payments extracted below this score are staged as Unidentified for you to review instead of being applied automatically. |
| Allowed senders | A list of sender email addresses or domains, one per line or comma-separated. When set, CAM processes only messages from these senders and rejects everything else with the error EMAIL_SENDER_NOT_ALLOWED before any AI extraction runs (so a blocked message doesn't use AI credits). Leave blank to accept every sender in the labeled or categorized mail. See "Restrict which senders CAM reads" below. |
| Use Credit Memos | Select to have CAM apply credit memos referenced in a remittance email, the same way it does for bank files. Credit memo detection depends on the AI model identifying a memo reference in the email that matches your configured prefix; it doesn't have a dedicated extraction field, so review flagged remittances that mention a credit or discount. |
| Credit memo prefix | The prefix your NetSuite credit memos use, for example CM or MEM. Enter multiple prefixes as a comma-separated list, in priority order. |
| Ignore following Customers | A comma-separated list of NetSuite customer names whose payments you don't want CAM to import, for example ACME Inc., S Industries. Matching remittances aren't imported and can't be retrieved later. |
| NetSuite Invoice Prefix | A comma-separated list of the invoice number prefixes used in your NetSuite account, for example INV, IV, in priority order. CAM tries each prefix in turn to match the invoice number the AI extracted to a NetSuite invoice. |
| NetSuite Invoice Identifier | NetSuite fields used to match the extracted invoice number. Defaults to Invoice #. You can select up to three. |
Restrict which senders CAM reads
A shared mailbox isn't a bank feed: any email that lands in the labeled folder is a candidate for AI extraction. Set Allowed senders to the domains or addresses your AP platforms actually send from (for example, your Paymerang, Bill.com, or Ramp sending addresses) so CAM ignores everything else before it reaches the AI step. This is the primary control against someone forwarding or spoofing a fake remittance into the labeled folder. CAM also checks the receiving mail server's SPF and DKIM authentication result where your mailbox provider exposes it. On Gmail, an SPF or DKIM result of fail, softfail, or permerror is held for review. Missing headers are not held. Outlook does not provide these headers.
Enable the flows
- With Email Remittance selected in the All Banks dropdown, go to Flows > EMAIL.
- Turn on Enabled for both flows on the mailbox you configured: the Bank File to NetSuite [EMAIL - ACH - Gmail] (or [EMAIL - ACH - Outlook]) flow you just set up, and its paired Bank Transactions to NetSuite [EMAIL - ACH - Gmail] (or [EMAIL - ACH - Outlook]) flow.
You can run either flow on demand with Run now, or leave it on its configured schedule, the same options as your other CAM flows.
Running a flow manually with Run now, or testing it from the flow debugger, reads your live mailbox and uses AI credits the same as a scheduled run. There's no separate test mode for Email Remittance.
Avoid duplicate payments across channels
CAM's duplicate detection prevents the same email from creating two payments if you retry or rerun a flow. It doesn't prevent two different channels from creating two payments for the same underlying remittance; for example, a customer emails you a remittance and also includes it in that day's bank file, or the same PDF is forwarded to both your Gmail and Outlook mailboxes with different message IDs. In either case, CAM has no way to know the two records represent the same payment, so it creates a second, unapplied customer payment for the invoice rather than double-applying it.
Route each remittance source through one channel only to avoid this. If you use both a bank file and email, or both Gmail and Outlook, agree with your bank or your customers on a single channel per relationship, and check for and remove any unapplied duplicate payments your AR team encounters. See Avoid creating duplicate transactions in NetSuite for how CAM's duplicate detection works for retries within a single channel.
Uninstall Email Remittance
Uninstalling the Email Remittance bank removes it from your bank list and removes both mailbox connections. It doesn't affect your other banks. To remove it, follow Uninstall an integration app account, store, bank, or tile and select Email Remittance as the bank to uninstall. To bring it back later, see "Add the Email Remittance bank" above.
Limitations
- CAM reads only a PDF attachment. If the email has more than one attachment, it sends one PDF to AI, preferring a file whose name looks like a remittance. Invoice, W-9, and statement names are ranked last. Other file types are ignored. If the remittance detail is only in a non-PDF attachment, CAM holds the email for review instead of posting it.
- There's no dedicated Celigo inbound address for remittance emails. Email Remittance only reads a Gmail or Outlook mailbox you connect directly; you can't forward remittances to a separate Celigo-hosted address.
- A credit-only or net-zero remittance isn't staged in NetSuite at all. CAM rejects the email with the EMAIL_NO_PAYMENT_AMOUNT error instead of applying it.
- CAM's duplicate detection is scoped to a single channel: it prevents the same email from creating two payments on retry, but it can't recognize that a bank-file record and an email record represent the same real-world remittance. See "Avoid duplicate payments across channels" above.