This FAQ answers common questions about Email Remittance in Cash Application Manager (CAM) for NetSuite, which reads customers' remittance emails and uses them to find the invoices for payments that are already in your bank file. It's for CAM administrators who set up Email Remittance and accounts receivable teams who review email remittances. For setup steps, see Set up Email Remittance in CAM for NetSuite. To resolve emails that need a person, see Review email remittances on the Cash Application Manager dashboard.
What is Email Remittance?
Email Remittance reads remittance emails from a Gmail or Outlook mailbox and uses them to apply the payments in your bank file. CAM uses AI to read the payer, payment amount, payment date, reference, and invoice numbers from the email body or an attachment. It saves the email in NetSuite, finds the open bank payment that matches it, adds the email's invoices to that bank payment, and applies it. The email never creates a payment; your bank file is the only source of cash.
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 and enable its flow. 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 accounts receivable 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.
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 Email Remittance read every email in my inbox?
CAM reads the emails that carry the Gmail label or Outlook category set in the email flow's settings. An Outlook category must match exactly; in a Gmail label, a space or slash is read as a hyphen. If you leave Gmail label to read or Outlook category to read empty, CAM checks every email in the run's date range, which uses more AI credits. Either way, CAM reads each email once and skips emails that aren't remittances. Apply the label or category with a filter or inbox rule when mail arrives, so scheduled runs don't miss late-labeled mail.
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 customers' and AP platforms' 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. A domain covers every address at that domain, and entries aren't case-sensitive. CAM doesn't read emails from other senders, and no record is created for them. See Set up Email Remittance in CAM for NetSuite.
Which attachments does CAM read?
CAM reads remittance details from PDF, PNG, JPG, TIFF, XLSX, XLS, and CSV attachments, including scanned PDFs, when Intelligent Document Processing is turned on for your account. Word documents (DOCX) aren't read; CAM uses the email body instead. An image with a transparent background can't be read, and the email is listed as Needs review, so ask customers to send opaque scans. A picture pasted into the email body isn't treated as an attachment. An email whose remittance details are in the body doesn't need an attachment.
Does CAM read every attachment on a remittance email?
No. CAM reads one attachment. When several are attached, it picks a file whose name looks like a remittance first. Invoice, W-9, and statement names are ranked last.
What happens if CAM can't confidently read a remittance email?
CAM doesn't guess. It saves the email and lists it under Email remittances on the Cash Application Manager dashboard with a reason, instead of matching it:
- Low confidence: CAM read the email with a confidence below Minimum confidence to match (0.9 by default). Very short emails, such as a single line, can score below 0.9.
- Needs review: the email has no payment amount or invoice numbers, or its details are only in an attachment CAM couldn't read.
On Gmail, an email with an SPF or DKIM result of fail, softfail, or permerror is also held for review. Missing authentication headers aren't held, and Outlook doesn't send those headers. See Review email remittances on the Cash Application Manager dashboard.
What if the same remittance email arrives more than once?
If the same remittance is forwarded or arrives in a second mailbox, CAM saves the copy as Duplicate, names the original email in Reason, and doesn't match it. Ignore the duplicate on the dashboard to remove it from Needs attention.
What happens if the same remittance arrives by both bank file and email?
CAM creates one customer payment. The bank file brings in the payment, and the email supplies its invoices, so the payment isn't counted twice. If an invoice has two payments for the same remittance from earlier, one created from the email and one from the bank file, unapply or delete the duplicate, or contact Celigo Support.
What happens if the email arrives before the bank file?
CAM saves the email as New and checks it again every 15 minutes. A bank payment can be matched only after CAM processes the bank file, up to 15 minutes after import. When the bank payment fits, CAM matches and applies it, with nothing for you to run. If no bank payment matches by the end of Match window (days) plus 3 days, the email is listed as Unmatched.
Why wasn't an email matched to a bank payment that's already in NetSuite?
CAM matches an email only to an open bank payment that has no invoice details, from the bank flows in Bank flows to match against. Bank payments that are already applied or partially applied are never matched. For example, if your bank flow applies payments to a customer's open invoices when CAM identifies the customer, that bank payment is applied before the email arrives, and the email is later listed as Unmatched. Check the email's Reason on the dashboard, then link it to another bank payment or ignore it.
What happens when a customer pays less, or the amounts differ?
CAM applies what the email says was paid, and the rest of the invoice stays 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.
Can one remittance email cover several invoices?
Yes. CAM applies the bank payment across all the invoices in the email. One email that covers several bank payments, or one bank payment that several emails describe, isn't matched automatically; the email is listed for review.
Which remittance emails always need a person?
CAM doesn't apply a remittance automatically when the email includes credits or deductions, its invoices total more than the payment, the bank payment's customer differs from the invoices' customer, or more than one bank payment still fits. These emails are listed on the dashboard with a reason. For what to do with each status, see Review email remittances on the Cash Application Manager dashboard.
Does CAM match payments in currencies other than US dollars?
Yes. The bank payment must have the same currency as the email.
Do changes to the Matching settings apply to emails CAM already read?
No. CAM matches each email with the settings in place when it read the email, including when you select Retry matching. Changes apply to emails CAM reads afterward.
What does Celigo do with my email content?
The email body (with signature banners stripped, capped at 60,000 characters) and the 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 the extracted payment details, the email subject, and the sender in a Celigo Cash App Email Remittance record for each email.
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.
Does uninstalling Email Remittance affect my other banks?
No. Uninstalling the Email Remittance bank removes the Email Remittance bank and its mailbox connections only; your other banks are unaffected. Celigo Cash App Email Remittance records stay in NetSuite. See Uninstall an integration app account, store, bank, or tile.