This FAQ answers common questions about Email Remittance, the feature that lets Cash Application Manager (CAM) for NetSuite create customer payments from remittance emails instead of only from bank files. It's for CAM administrators evaluating or configuring Email Remittance. For setup steps, see Set up Email Remittance in CAM for NetSuite.
What is Email Remittance?
Email Remittance is a way for the CAM for NetSuite integration app to read remittance advice directly from a Gmail or Outlook mailbox, instead of only from bank files on your FTP server. CAM uses AI to extract the payer, invoice numbers, and payment amount from the email body or a PDF attachment, then applies the payment through the same matching and posting logic as a bank-file payment.
Does Email Remittance require a new license or SKU?
No. Every CAM for NetSuite tile gets an Email Remittance bank in the All Banks list, with no separate license or SKU. You still connect the mailbox, label the mail, and enable the flows. See Set up Email Remittance in CAM for NetSuite.
Which mailboxes does Email Remittance support?
Gmail and Microsoft Outlook. You can connect one, both, or neither; connect only the mailbox or mailboxes your AR team actually uses to receive remittance emails.
What mailbox permissions does CAM request?
Read-only access: gmail.readonly for Gmail, openid, offline_access, User.Read, and Mail.Read for Outlook. CAM never writes back to your mailbox; it doesn't remove or change the label or category you apply, and it doesn't mark messages as read.
Does Email Remittance read every email in my inbox?
No. CAM only reads messages that carry the Gmail label or Outlook category you configure in the flow's settings. Apply that label or category with a filter or inbox rule at arrival, rather than labeling messages by hand, so scheduled runs don't miss late-labeled mail.
What happens if CAM can't confidently extract a payment?
CAM stages it in NetSuite as an Unidentified transaction with no customer or invoice attached, and records the reason in the transaction's notes, instead of applying the payment automatically. This happens when the AI extraction confidence is below your configured threshold, the extracted amount doesn't match the invoice total, or the remittance detail is only in a PDF attachment CAM couldn't read, or it is only in a non-PDF attachment. On Gmail, an SPF or DKIM result of fail, softfail, or permerror is also held. Missing authentication headers are not held, and Outlook does not send those headers. See Troubleshoot Email Remittance errors.
Does Email Remittance support PDF attachments?
Yes. CAM reads a PDF attachment, including a scanned PDF, when Intelligent Document Processing is turned on for your account. Excel, CSV, and image attachments are not read. An email whose remittance detail is in the body does not need an attachment.
Does CAM process every attachment on a remittance email?
No. CAM reads only a PDF. When several attachments are present, it sends one PDF, preferring a file whose name looks like a remittance. Invoice, W-9, and statement names are ranked last. Any file that is not a PDF is ignored.
What does Celigo do with my email content?
The email body (with signature banners stripped, capped at 60,000 characters) and the PDF attachment are sent to a Celigo-managed AI agent running under your own integrator.io account, the same data path as any AI agent flow you'd build yourself. The integration app doesn't persist your mailbox data; NetSuite stores only the extracted payment fields and the email subject in the transaction's memo and notes.
Does debug logging expose my email content?
Running a flow in detailed or debug log mode can persist message, attachment, and AI prompt content in that flow's own execution logs. This logging is off by default, and the logs it produces stay in your own account's log storage. Turn debug logging off again once you're done troubleshooting a specific flow run.
Why does CAM ask me to set Allowed senders?
A labeled mailbox folder isn't a bank feed: anyone who can get an email into it is a candidate for AI extraction, including a forwarded or spoofed message. Setting Allowed senders to your AP platforms' actual sending domains or addresses rejects everything else before it reaches the AI extraction step, so CAM doesn't spend AI credits on messages you'd never trust. See "Restrict which senders CAM reads" in Set up Email Remittance in CAM for NetSuite.
What happens if the same remittance arrives by both bank file and email?
CAM creates a second, unapplied customer payment for the invoice rather than double-applying it; it can't recognize that a bank-file record and an email record represent the same real-world payment. Route each remittance source through one channel only to avoid this. See Avoid creating duplicate transactions in NetSuite.
Do I need to forward remittance emails to a special Celigo address?
No. Email Remittance connects directly to your own Gmail or Outlook mailbox; there's no separate Celigo inbound address to forward messages to.
Does uninstalling Email Remittance affect my other banks?
No. Uninstalling the Email Remittance bank removes the Email Remittance bank and both mailbox connections only; your other banks are unaffected. See Uninstall an integration app account, store, bank, or tile.