NetSuite Automated Cash Application for Emailed Remittances

Try it now: extract email data to Excel, CSV, or JSON

Convert your email files
No install

Connect a Gmail or IMAP mailbox to parse new mail automatically, or paste an email below to test the converter now.

or paste an email to test
Output format
Columns to extract
Extract your own custom fields
Popular:

Create a free account to download. No credit card required.

NetSuite Automated Cash Application turns imported bank lines into customer payments and applies them to open invoices, and it works best when one bank credit pays one invoice or an exact total. It does not read the remittance advice your customer emails you, so a lump ACH that covers seven invoices, a credit memo and a short pay still needs someone to read that email and tell NetSuite where the money goes. The practical options are to key it by hand, add an enterprise cash application suite, or parse the remittance emails into a file and let NetSuite or your AR clerk apply from it.

This comparison is for the AR lead or controller on NetSuite who is deciding whether to buy something for that gap and what. If you already know you want the parsing route, the remittance processing software page shows how MailParse handles it. The rest of this article explains when another option is the better buy.

What the native feature handles well

Oracle describes the feature in its help center: once bank data is imported (see Automating Imports for Bank Reconciliation), the Automated Cash Application page lets you generate a batch of customer payments and apply them to open invoices, and the generated payments are then matched and cleared. You can save a customer mapping rule when you pick the customer for a bank line, so the next credit from the same payer lands on the right account without help.

That covers a lot of easy cash. A customer that pays invoice 20871 for exactly 4,210.00, with the invoice number in the bank memo, goes through with almost no touch. Card and portal payments that settle one invoice at a time behave the same way. If most of your receipts look like that, the native feature plus good mapping rules may be all you need, and you should not buy anything.

Where it runs out: the remittance lives in an email

The hard payments are the ones where the bank line carries a total and a reference and nothing else. The customer's AP system sends the detail separately, usually as an email titled "Remittance advice" or "Payment notification" with a table of invoices, or a PDF advice attached. NetSuite sees 18,420.50 from Harlow Building Supply. The email says that 18,420.50 is:

  • six invoices paid in full,
  • one invoice paid 61.20 short with the note "pricing variance",
  • a credit memo of 512.00 taken against the total.

No bank feed contains that list. NetSuite can suggest invoices that add up to the amount, but when the sum does not land on a clean combination, or when the customer took a deduction, the suggestion is a guess. So the AR clerk opens the email, reads the table, finds each invoice and applies amounts by hand. ACH payments that do carry remittance in the bank file use addenda records defined by the Nacha Operating Rules, but many payers send the detail by email instead, and that is the part this article is about.

Distributors that sell to farms and ranches see the worst version of this: a landowner settles a season of feed, fence and seed invoices in one wire, often after a lease payment or a parcel sale comes through. (Owners in that position are usually also checking what a US parcel is worth before they sell, which is why those payments come in lumps.) The remittance arrives as a forwarded email or a photo of a handwritten list, and someone has to make sense of it.

Four ways to handle emailed remittances in NetSuite

Decision point Native feature, remittances keyed by hand Enterprise cash application suite No-code flow on the AR inbox Remittance parser plus native feature
Reads remittance emailsNo, a person doesYes, often with OCR for scans and lockbox imagesOnly layouts you build a flow forYes, body, tables and digital PDF or CSV advices
Applies payments in NetSuiteYes, from bank linesYes, with its own matching rulesOnly if someone scripts itNetSuite applies, from a file or the parsed list
Deductions and short paysFound by readingCaptured and often coded by reasonRarelyOwn column, next to the invoice
SetupTurn on the feature and bank importsDemo, contract and implementationA flow per customer layoutName the fields once, same day
PricingIncluded, plus staff timeQuote based, usually annualAutomation plan plus maintenance timePublished monthly plan
Best forMostly one invoice per paymentHundreds of payments a day, lockbox, many deductionsOne or two payers with a fixed layoutTeams of one to five with many emailed remittances

Enterprise suites are described in general terms from their public pages, so check the specific vendor. MailParse reads digital text only, has no OCR and does not post into NetSuite on its own.

A worked example with real numbers

Take a building products distributor on NetSuite that receives about 40 ACH payments a week from contractors and dealers. Roughly half pay one invoice and clear on the Automated Cash Application page with no work. The other 20 cover between 3 and 12 invoices each, about 6 on average, and each comes with an emailed remittance.

Keyed by hand, one of those 20 takes about 3 minutes to open and read, plus about a minute per invoice to find it, apply the amount and note any short pay. That is around 9 minutes per payment, 3 hours a week, or about 13 hours a month, and the deductions end up in a notes field where nobody totals them.

With a parser on the remittance mailbox, the same Harlow email becomes these rows (four of eight shown):

payer payment_ref payment_total invoice_number amount_paid deduction
Harlow Building Supply773104218420.50INV-208714210.000.00
Harlow Building Supply773104218420.50INV-208742984.300.00
Harlow Building Supply773104218420.50INV-209023105.7561.20
Harlow Building Supply773104218420.50CM-1188-512.000.00

The clerk now checks that the rows sum to the bank credit and applies them, which takes about 2 minutes per payment. Twenty payments a week at 2 minutes instead of 9 gives back roughly 2.3 hours a week, about 10 hours a month. At a loaded cost of 30 dollars an hour that is around 300 dollars of AR time a month, and the 61.20 deduction is already sitting in a column you can total by customer at month end. These figures are an illustration built from the stated assumptions; time your own desk for a week and swap in your numbers.

How the parsed file meets NetSuite

There are two common ways to use the rows. The simple one keeps the native feature in charge: the clerk works the Automated Cash Application page with the parsed sheet open beside it, so picking invoices for a lump payment is a copy of a list rather than a reading exercise. The fuller one uses NetSuite's CSV Import Assistant, which accepts customer payments with the invoices to apply, so the parsed file (payment reference as the external ID, customer from the sender, one line per invoice) can be imported as payments and then matched to the bank lines. Test the field mapping in a sandbox first, because invoice numbers must match NetSuite's exactly and customers must already exist.

If you would rather skip files, send each parsed remittance as JSON to a webhook of your own and let a small SuiteScript or middleware job create the payment. The same parser can sit on the payables side too: the NetSuite vendor bill import from email page covers bills arriving in the AP inbox.

Which option fits your AR desk

Stay with the native feature alone when most payments settle one invoice and the few lump payments are easy to read. Spend the effort on customer mapping rules instead.

Choose an enterprise cash application suite when you receive hundreds of payments a day, run a lockbox with scanned checks, and deductions are a department of their own. OCR, reason codes and direct posting earn their contract at that size.

Choose a no-code flow when one or two large payers send the same remittance layout every time and someone on the team will maintain it. It breaks quietly when a customer changes AP systems.

Choose a remittance parser when remittances come by email from dozens of customers in their own formats, the AR team is small, and you want the fix this week. Connect the AR mailbox over IMAP or upload a .zip of last month's remittance emails to see the result on real data. PDF advices are read on Plus and higher; the email attachment extractor page lists exactly which attachment types are read.

Questions AR teams ask before buying

Does NetSuite have automated cash application?

Yes. NetSuite includes an Automated Cash Application page that generates customer payments from imported bank lines and applies them to open invoices, with customer mapping rules for repeat payers. It relies on bank data, so remittance detail that arrives by email still has to be read by a person or a separate tool before a lump payment can be applied correctly.

Can NetSuite read remittance advice emails?

Not on its own. NetSuite works from bank imports and the records you give it; it does not open the AR mailbox and read the invoice list in a customer's remittance email or PDF advice. Teams either key that detail, buy a cash application suite that captures it, or parse the emails into a file NetSuite can use.

How do I handle short payments in NetSuite cash application?

Apply the amount actually paid to the invoice and record the difference as a deduction you can follow up, rather than leaving the invoice partly open without a note. Capturing the deduction amount from the remittance in its own column first makes this a review step, and lets you total short pays by customer each month.

What to check before you buy any of them

  • Your ten hardest remittances. A portal notice, a pasted table, a PDF advice and the customer who always short pays. Vendor samples prove nothing.
  • Totals that tie out. Every remittance should sum back to its bank credit, so check that the output repeats the payment reference and total on each line.
  • Deductions. Ask where a short pay ends up. If it is buried in a memo, the saving on keying is lost in collections.
  • Attachments and scans. Confirm which formats are read. MailParse reads digital PDF and CSV advice text and does not OCR scans, so check stubs stay a manual step.
  • Cost at your volume. Price the tool against the hours you measured, not against a vendor's case study.

If your order desk faces the same problem with incoming POs, the order entry automation software comparison covers that side of the business.

Turn remittance emails into rows you can apply

Connect the AR mailbox or upload saved remittances, name the payment fields once, and download CSV, Excel or JSON. See the remittance processing software.