A $4,200 ACH lands in your client's checking account on Tuesday. The bank description says ACH CREDIT VENDOR PAY 847293847. You open QBO, look at the open invoices for that customer, and see three: $1,800, $1,500, and $2,400. None of them match. None of them sum to $4,200 either. You're guessing.
A remittance advice would tell you exactly which invoices the customer paid and what they took as a discount or short-pay. Without it, you're either calling the customer, leaving the deposit in Undeposited Funds, or applying it across the wrong invoices and hoping nobody notices at year-end.
This is what remittance advice actually does in a bookkeeping seat. Not the textbook definition. The practitioner version, including what to do when the remittance arrives three days after the deposit and what to do when it never arrives at all.
What is remittance advice?
Remittance advice is a notification that tells the recipient what a payment is for. It lists the invoice numbers being paid, the amount applied to each, any discounts taken, and the payment method. Customers send it to vendors when they pay. Vendors use it to apply the payment to the right open invoices. On the AR side, you receive it. On the AP side, you send it. It's not legally required, but missing remittance advice is one of the top three reasons bookkeepers run out of time at month-end. A clean remittance advice posts in under a minute. A missing one can cost 20 minutes per deposit while you chase down what the customer paid.
Payment reconciliation starts here. If you can't tell what a deposit covers, you can't reconcile it.
A remittance advice is the customer's way of saying "here's what this payment covers." Nothing more. It's a notice, not a payment. The money moves through ACH, wire, check, or card. The remittance advice rides alongside, telling you how to apply it.
Five fields show up on almost every remittance advice you'll handle:
That's the universe. If the document has those five fields, it's a remittance advice, regardless of what it's called or how it arrived. Some companies call it a "payment advice." Others call it a "remittance slip" or "EFT advice." Same document.
An invoice is a bill. A receipt is proof of payment. Remittance advice is the bridge. The vendor invoices the customer. The customer pays. The customer sends remittance advice telling the vendor which invoices the payment covers. The vendor then issues a receipt back.
Bookkeepers confuse remittance advice with payment confirmation. They're not the same. A payment confirmation says "we paid you $4,200." Remittance advice says "we paid you $4,200 against invoices INV-1042, INV-1043, and INV-1051 minus a $50 return credit."
On the receivables side, remittance advice arrives with or shortly after the deposit. You match the remittance to the deposit, apply the payment to the right invoices in QBO or your AR system, and the customer's balance goes down.
On the payables side, your client cuts a check or sends ACH to a vendor. Your client (or your bill-pay tool) sends remittance advice to the vendor so the vendor knows which bills the payment closes. Without it, the vendor's AR clerk does the same guessing dance you do on your side.
The job changes depending on which side of the transaction you're on. Most bookkeepers handle both within the same client.
You're the vendor's bookkeeper. Your client sells consulting, software, or product. Customers pay. Remittance advice arrives by email, paper stub, or ACH addenda. Your job:
Standard time on a clean remittance: 30 to 60 seconds per deposit. On a missing or unclear remittance, 10 to 20 minutes if you have to email the customer, plus another 5 minutes when they reply.
Your client pays vendors. You're cutting checks or scheduling ACH through Bill.com, Melio, QBO Bill Pay, or direct from the bank. Your job on the send side:
Most modern bill-pay tools generate remittance advice automatically. The problem isn't generating it. It's making sure it actually reaches the vendor. Bill.com and Melio email remittance to whatever address the vendor entered when they accepted the first payment. If that address is wrong or the vendor's AR clerk doesn't check it, the vendor doesn't see the remittance.
Stripe, PayPal, and Square don't send remittance advice in the traditional sense. They send payout reports. The payout combines hundreds or thousands of charges, fees, refunds, and disputes into one deposit. The payout report is the remittance, but the format is dense and the matching work is different. See the payment reconciliation guide and gross vs net accounting for payment processors for that workflow.
Three uses dominate. The textbook version skips two of them.
Every payment posted to the books needs documentation behind it. The bank statement shows the deposit hit. The invoice shows the sale. Remittance advice connects them. If a customer later disputes the application or a refund comes through, the remittance advice is what proves how the payment was originally applied.
Most firms retain remittance advice for seven years alongside the deposit slip. Cloud bill-pay tools handle this automatically. Paper-stub clients require a scanner workflow or an "attach to deposit" habit in QBO.
When you pay a vendor, the remittance advice tells the vendor what bills to close. On your own books, the remittance is the record of which bills your client closed. This matters at month-end when you're reconciling AP aging.
If the AP aging shows a bill still open after the payment, one of three things happened:
Remittance advice resolves all three. You match what you sent against what the vendor applied. Mismatches surface immediately instead of three months later when the vendor sends a past-due notice.
A clean remittance advice tells your categorization tool which GL accounts to hit. A $4,200 payment against three invoices, where one invoice was for consulting and two were for software licenses, splits across two accounts. Without remittance, the entire $4,200 lands in one bucket and you fix it later.
Growthy categorizes automatically and you review and approve. On payments with attached remittance advice, the categorization is straightforward because the invoice references are right there. On payments without remittance, the tool flags it for review instead of guessing. That's the difference between 85% accurate on first import and the 50% accuracy QBO suggestions hover at.
Five patterns surface across hundreds of client books. Each one has a fix, but only if you know to look.
The customer's payment hits the bank Tuesday. The remittance advice email arrives Friday. By then you've already applied the deposit somewhere because month-end is in three days. When the remittance shows up, the application is wrong.
Fix: use an Undeposited Funds or Unapplied Cash clearing account. Deposits without matching remittance sit there until the remittance arrives, even if it takes a week. The dollar-amount risk of holding $4,200 in clearing for three days is zero. The dollar-amount risk of misapplying $4,200 to the wrong customer is much higher.
This one bites firms running bi-monthly bill pay. The first payment run goes out. The remittance advice doesn't make it to the vendor (wrong email, attached PDF stripped by spam filter). The vendor calls past-due. Someone on the AP team approves a second payment for the same invoice. The vendor cashes both checks.
Fix: never approve a vendor payment without checking the vendor's statement against your AP aging. If the bill shows paid on your side but the vendor says past-due, the remittance didn't land. Re-send remittance and confirm receipt before cutting a second check.
A customer pays $4,150 against a $4,200 invoice. The remittance advice says "less $50 return credit." If you book the short-pay as bad debt, your bad-debt expense overstates and your customer's payment history looks worse than it is.
Fix: book short-pays per the remittance reason. Return credits go to Sales Returns. Early-pay discounts go to Sales Discounts. Disputes go to a Disputed Receivables account until resolved. Bad debt is reserved for actual non-payment, not customer-initiated adjustments.
ACH payments can carry remittance data inside the transaction itself, in fields called addenda records. Most bank feeds strip this data before it reaches QBO. The remittance was technically delivered with the payment, but your bookkeeping tool never showed it to you.
Fix: ask the bank for the full ACH detail report (usually called "EDI 820" or "CTX detail"). On high-volume B2B clients, this single report can resolve 80% of unidentified ACH deposits per month. Most banks include it free if you ask; some charge $25 monthly for it.
Bill.com sends remittance to the vendor's email of record. If the vendor's AR clerk leaves and nobody updates the address, remittance disappears for months. Your client's books show bills paid. The vendor's books show past-due. Eventually the vendor calls.
Fix: quarterly, pull a Bill.com vendor list and confirm at least one remittance was successfully delivered to each active vendor in the prior 90 days. Stale email addresses surface fast.
If your client pays vendors and your bill-pay tool doesn't auto-generate remittance, send it manually. Three scenarios:
The remittance should include: payment date, payment method, total amount, list of invoice numbers and amounts paid against each, and any discounts taken. That's all. No marketing, no signature lines, no formatting that breaks in Outlook preview panes.
Growthy categorizes deposits and payments automatically. You review and approve. When remittance advice is attached to a payment (Bill.com PDF, ACH addenda data, or a parsed bank-feed memo), Growthy reads the invoice references and applies the payment correctly on the first pass.
When remittance is missing, Growthy flags the deposit instead of guessing. The triage dashboard shows "13 of 247 need you" rather than 247 of 247 needing review. That's the difference between a 30-minute morning and a three-hour one.
Built by a CPA firm partner who still reconciles books for real clients. 85% accurate on first import. Climbs to 90%+ as Growthy learns each client's vendor and customer patterns.
No. Remittance advice is a best practice, not a legal requirement. The Uniform Commercial Code governs payment obligations, but it doesn't mandate that a payor notify a payee of payment application. That said, sending remittance reduces disputes and speeds vendor cash application. Most B2B accounting policies require it for payments over a threshold (often $1,000 or $5,000).
Seven years aligns with most state statutes of limitations for contract disputes and matches IRS retention guidance for supporting documentation under IRC §6001. Some industries require longer. Healthcare and government contracts often require ten years. Bank statements and remittance documentation share the same retention rule.
A payment confirmation says "we paid you." A remittance advice says "we paid you, and here's exactly which invoices the payment covers." Payment confirmations are common in B2C and consumer banking. Remittance advice is standard in B2B and accounts payable.
Bill.com emails remittance to the vendor of record, not back into QBO. To see remittance on payments your client sent, you have to log into Bill.com itself and pull the bill payment record. If you reconcile from QBO only, you'll miss the remittance documentation. Add Bill.com bill-payment reports to your month-end checklist.
Park it in Undeposited Funds or an Unapplied Cash clearing account. Email the customer the same day asking which invoices the payment covers. Don't apply it to invoices on a best-guess basis, especially if the customer has multiple open invoices that sum to similar amounts. Misapplication takes longer to fix than a one-day delay.
Not in the traditional sense. Stripe sends payout reports that bundle hundreds of charges, fees, refunds, and disputes into a single deposit. The payout report acts as the remittance, but the format is dense. See the payment reconciliation guide and the automated vs manual payment reconciliation walkthrough for handling payment-processor deposits.
Bill.com, Melio, and QBO Bill Pay all generate AP-side remittance automatically. On the AR side, options are thinner. Cash application tools like HighRadius, Versapay, and Billtrust read remittance from email and ACH addenda, but they're priced for mid-market firms ($30K+ annual). Most small bookkeeping firms handle AR-side remittance manually and use a clearing account discipline to catch mismatches.
You'll handle remittance advice at three points in a typical close cycle. When deposits hit during the month, you match remittance to apply payments correctly. When you cut bill payments, you send remittance to vendors. When you reconcile AP and AR aging at month-end, you use remittance documentation to resolve open balances.
Done well, this is a 30-second decision per deposit. Done poorly (or skipped entirely), it's the silent reason close takes an extra two days every month. The fix isn't complicated. It's a clearing account, a habit of checking remittance before applying cash, and a tool that flags missing remittance instead of guessing.
If you're tired of guessing what a deposit covers, start with Growthy free. Built by a CPA firm partner who still reconciles books for real clients. Categorizes automatically. You review and approve. Done before lunch.
Free during alpha. Read-only access. You review every sync.
CPA firm partner who got tired of watching bookkeepers click categorize 500 times a day. Built Growthy to fix it.
View all articles →Growthy is dedicated to helping businesses of all sizes make informed decisions. We adhere to strict editorial guidelines to ensure that our content meets and maintains our high standards.
Stop chasing W-9s in January. Collect them before the first payment, track receipt, and handle the messy cases (refusal, foreign vendors, single-member LLCs).
Stripe sends one deposit for 47 transactions. Learn the clearing account method to reconcile lump-sum payment processor deposits with step-by-step journal entries.
