Remittance Processing Software for ACH Remittance Emails and Cash Application
Remittance emails in, invoice level payment rows out
Point MailParse at the AR or remittance mailbox and get payer, payment date, payment reference, payment total, invoice number, amount paid and deduction for every remittance in one sheet. Upload .eml or .msg files or a .zip, or connect the mailbox over IMAP. Export Excel, CSV or JSON, or post each remittance to your own system by webhook.
Connect a Gmail or IMAP mailbox to parse new mail automatically, or paste an email below to test the converter now.
Create a free account to download. No credit card required.
Remittance processing software reads the remittance advice your customers send with a payment (which invoices it covers, how much was paid on each, and any deduction) and turns it into data you can apply against open invoices. MailParse does that for remittances that arrive by email: it reads ACH remittance emails, payment portal notices, pasted tables and digital PDF or CSV advices, and gives you one CSV or Excel row per invoice paid, ready for the cash application step in QuickBooks, NetSuite or your ERP.
- 1 row
- Per invoice a payment covers
- 5,000
- Rows per downloaded file
- 10,000
- Emails in one .zip upload
- 3 parses
- On your own remittances before you sign up
Cash application is slow for one reason: the money and the explanation arrive separately. The bank shows a single ACH credit of 18,420.50 from a customer. The detail of what that credit pays for arrives somewhere else, usually as an email from the customer's AP system or payment portal that says "Remittance advice, payment 7731042" and lists seven invoices and a credit memo, with one invoice paid short for a pricing deduction. Someone in AR opens that email, finds each invoice, keys the amounts and works out why the total is 61.20 short of the open balance.
Here is what MailParse gives you from that one email when you name the fields payer, payment_date, payment_ref, payment_total, invoice_number, amount_paid and deduction:
| payer | payment_ref | payment_total | invoice_number | amount_paid | deduction |
|---|---|---|---|---|---|
| Harlow Building Supply | 7731042 | 18420.50 | INV-20871 | 4210.00 | 0.00 |
| Harlow Building Supply | 7731042 | 18420.50 | INV-20874 | 2984.30 | 0.00 |
| Harlow Building Supply | 7731042 | 18420.50 | INV-20902 | 3105.75 | 61.20 |
| Harlow Building Supply | 7731042 | 18420.50 | CM-1188 | -512.00 | 0.00 |
Four of the eight rows are shown. The payment reference and total repeat on every line, so the file sums back to the bank credit and each line can be applied to an invoice. The 61.20 deduction sits in its own column instead of hiding in a sentence at the bottom of the email. That is the part of cash application a person used to type, and it is the part MailParse removes.
Enterprise cash application suites go further: they also read bank files, match payments to invoices with their own rules and post the result into the ERP, sold through a demo and an annual contract. MailParse is the smaller first step for AR teams of one to five people who already have an import screen. If remittances come as PDF attachments, see the email attachment extractor for what is read and what is not, and if your AR mailbox also receives vendor bills, the invoice data extraction page covers the payables side. NetSuite users can read how this fits NetSuite automated cash application for emailed remittances.
What the converter does
Everything you need to turn the email your team receives into a spreadsheet it can actually use.
Remittance fields you define
Save fields such as payer, payment_date, payment_ref, payment_total, invoice_number, amount_paid, discount and deduction. Common labels ("Invoice #", "Amount Paid", "Payment Number") are found without setup, and your saved fields win when a customer's AP system words things its own way.
ACH notices, portal emails and PDF advices
Values come from the subject, the plain text body, HTML tables and, on Plus and higher, the text inside digital PDF and CSV attachments up to 8 MB. Scanned check stubs and photographed remittances are not read, because there is no OCR.
One row per invoice paid
When a remittance lists invoices in a table, each invoice keeps its own amount and deduction, and the payer, payment reference and total repeat on every row, so the lines add back to the bank credit.
Sender and time on every remittance
The sender address and received time sit beside each row, which helps map a customer's AP mailbox to the right account and spot a remittance that arrived days after the money.
The whole AR mailbox
Connect ar@ or remittance@ over IMAP, forward remittances to your MailParse address so each is parsed within minutes, or upload a .zip of saved messages to clear a month of unapplied cash.
Hand-off to your ERP or a script
Download CSV for a customer payment import, open it in Excel next to the aging report, or send each parsed remittance as JSON to your webhook. MailParse does not post or apply the payment in your ERP for you.
How to automate remittance processing from email
Four steps from an AR inbox full of remittance advices to a file you can apply.
Bring the remittances in
Upload saved .eml or .msg files, a folder or a .zip of up to 10,000 messages, or connect the remittance mailbox over IMAP.
Name the remittance fields
Save the payment fields (payer, date, reference, total) and the invoice fields (invoice number, amount paid, deduction) once, in the column order your import or worksheet uses.
Check the first batch
Compare the parsed rows with ten real remittances from your largest payers. Fix a field that missed one customer's wording once and the correction applies to every later email.
Apply the cash
Load the CSV through your customer payment import, match it against open invoices in Excel, or post each remittance as JSON to your webhook so a script applies it.
Who processes remittances this way
AR desks where the same remittance details are retyped from email every day.
Distributors paid by contractors and retailers
Customers pay dozens of invoices in one ACH and email the list from their AP system. A parsed sheet turns the list into applied lines instead of a morning of lookups.
Manufacturers with retail deductions
Big box and grocery customers short pay for promotions, freight and damages. The deduction column collects every short pay with its invoice so disputes start from a list, not a hunt.
Staffing and service firms
Clients pay weekly invoices through payment portals that send a notice per payment. Pull invoice number and amount from each notice and clear the aging in one pass.
Bookkeepers handling AR for clients
Several clients forward their remittance emails to you. Keep the client, payer and invoice on every row and post each client's cash from one file.
Why automate the remittance step first
Cash applied the day it lands
When the remittance is already in columns, AR checks and applies instead of typing, so the aging report and credit holds reflect real balances sooner.
Short pays caught early
Deductions sit in their own column with the invoice they belong to, which makes a weekly deduction review a filter instead of an inbox search.
A searchable record of every remittance
Each row keeps its sender and time, so "which invoices did that 18,420 payment cover" is answered in seconds months later.
No ERP project
MailParse sits in front of the system you already run. It prepares the remittance data and your existing import, worksheet or script applies it.
Ways to process emailed remittances compared
The right choice depends on payment volume, how many remittance formats you receive and whether you want an ERP integration project.
| Decision point | MailParse | Enterprise cash application suites | Keying remittances by hand |
|---|---|---|---|
| What it does | Turns remittance emails into CSV, Excel or JSON rows, one per invoice paid | Captures remittances, matches payments to invoices and posts them to the ERP | A person reads each remittance and applies it invoice by invoice |
| PDF and scanned remittances | Digital PDF text on Plus and higher, no OCR for scans or check stubs | Usually yes, including lockbox images through OCR | Yes, slowly |
| Matching to open invoices | Your import, worksheet or script does the matching | Built in, with rules and suggested matches | Manual |
| Setup | Upload files or connect the mailbox the same day | Demo, quote and implementation project | None |
| Pricing | Published monthly plans | Quote based, typically annual contracts | Staff time |
| Best for | AR teams of one to five people with an import screen or a developer | High volume AR on enterprise ERPs with lockbox and bank feeds | A handful of payments a week |
Enterprise suites described in general terms from their public pages; capabilities, connectors and pricing vary by vendor, so test with a sample of your own remittances. MailParse reads digital text only and does not apply payments in an ERP directly. Payment formats such as ACH addenda are set by the <a href="https://www.nacha.org/rules" rel="noopener" target="_blank">Nacha Operating Rules</a>; MailParse reads the emailed remittance, not the bank file.
Frequently asked questions
What is the best remittance processing software for a small AR team?
For a small AR team the best fit is usually a tool that turns remittance emails into invoice level rows the same day, without an ERP project. MailParse reads payer, payment reference, invoice numbers, amounts and deductions from the email, tables and digital PDF advices and gives you CSV or Excel. Enterprise suites suit high volume AR with lockbox.
Can I automate cash application from remittance emails?
You can automate the reading part. Connect the remittance mailbox over IMAP or forward advices to your MailParse address, name the fields once, and each remittance becomes one row per invoice paid. Your customer payment import, worksheet or a script then applies those rows to open invoices.
Does it read ACH remittance emails from payment portals?
Yes, when the remittance detail is in the email. Portal and AP system notices usually list the payment number, date, total and each invoice with its amount in the body or an HTML table, which MailParse reads. A notice that only links to a portal login has no detail to read until you download it.
Does it read PDF remittance advices attached to emails?
On Plus and higher MailParse reads the text inside digital PDF and CSV attachments up to 8 MB, which covers advices generated by a customer's AP system. Scanned check stubs and photographed remittances are not read, because MailParse has no OCR.
Will it apply payments in QuickBooks or NetSuite?
No, it prepares the data. You get a CSV in the column order your customer payment import or worksheet expects, or JSON posted to your webhook. The application of each payment to its invoice still happens in your accounting system, with the remittance lines already typed for you.
How does it handle deductions and short payments?
Name a deduction field and MailParse fills it wherever the remittance shows a deduction, discount or adjustment next to an invoice. Each short pay then sits on the row of the invoice it belongs to, so you can total deductions by customer and reason before chasing them.
Can I test it on my own remittances first?
Yes. You can parse 3 of your own emails before creating an account to see which fields it finds. Paid plans add bulk upload, mailbox connection, attachment text, webhooks and larger files.
Turn this week's remittance emails into applied cash
Upload the remittance emails or connect the AR mailbox, name the payment fields once, and download CSV, Excel or JSON.