Duplicate DetectedAlready exported to QuickBooks
View in QBO
Remit Customer—
QBO Customer—
Check / Advice No.—
Credit Memo No.—
Check Date—
Credit Memo Date—
Difference—
Remit Total—
Expected—
Deductions—
Inv. Paid—
Inv. Prepaid—
EPD—
EPD Prepaid—
EPD Settle—
Repayment—
0 / 0 deductions coded
Settings / MappingProfile-scoped — changes only affect the active profile
ProfileActive
RemitParse Company → QBO Customer
Map exactly what RemitParse reads from the remit header to the customer name in QuickBooks. Must match QBO exactly.
⚙ Advanced options are available per customer via the gear icon on each row.
Sub-customer routing — splits one remittance into separate QBO payments per sub-customer (e.g. Walmart + Sam's Club on the same check).
Early Payment Discount % — for distributors that report invoice amounts net of EPD (KeHE, UNFI prepaid rows, WinCo). Enables gross invoice amount imputation. Leave off for all other customers.
Remit capturesQBO Customer Name (exact)
Deduction Type → QBO Product/Service
Map RemitParse deduction types to QBO Product/Service names. Used when exporting Credit Memos. Custom types added here appear in the Type dropdown.
RemitParse TypeQBO Product / Service (exact)
Class Coding
Enable
Class List (one per line — must match QBO exactly)
These values appear in the Class dropdown in the table and are included in Credit Memo exports.
Location Coding
Enable
Location List (one per line — must match QBO exactly)
These values appear in the Location dropdown in the table and are included in Credit Memo exports.
Per-Customer Defaults
Set a default Class and/or Location by QBO customer name. Auto-fills when a remit is uploaded for a matching customer.
When enabled, RemitParse learns from your past exports and pre-fills the Type and Context fields after each upload. Only empty cells are filled — your edits always take priority. History is scoped to this profile and company and never shared.
Auto-Coding is available on Growth and Pro plans. Upgrade to unlock type and context pre-fill from your export history.
How it works
1. Export to build history Every time you export a coded remittance, the deduction types and context values you assigned are saved to your history for that distributor.
2. Upload learns from history On the next upload, RemitParse matches invoice numbers and descriptions against your history and pre-fills matching rows automatically.
3. Review and confirm Pre-filled cells are highlighted so you know which values came from auto-coding. Edit anything that looks wrong — your correction is used going forward.
Cell highlight colors
Green — High confidence (≥ 0.75) Strong match with consistent history. Safe to export without review in most cases.
Yellow — Reasonable confidence (0.50–0.74) Pattern matches history but with lower frequency or partial consistency. Worth a quick check.
Orange — Low confidence (< 0.50) First time seeing this pattern, or conflicting history. Verify before exporting.
Hover any highlighted cell to see the confidence score and what drove the suggestion. Editing clears the highlight.
Works better alongside AI Document Coding. Every deduction you confirm — whether typed by hand, pre-filled here, or matched from a backup document on the AI Document Coding tab — is saved to the same history Auto-Coding learns from. The more of your coding that comes from an actual source document, the more that history reflects real evidence instead of pattern guesses.
When enabled, an optional "Upload Deduction Support" step appears after each remit upload. AI reads any backup you drop in, matches it to the right deduction line, and proposes Type, Context, and Period — anything it isn't confident about is flagged for your review instead of guessed.
AI Document Coding is available on Pro. Upgrade to enable AI-assisted coding from your backup documents.
Flag large deductions for review
Any deduction over this amount gets flagged for a manual look, even if it's fully and confidently coded. Set to $0 to turn this off.
$
How it works
1. Upload your backup documentation After a remit uploads, drop in whatever you already have for a deduction — a chargeback notice, deduction invoice, spreadsheet, even a scanned image. PDF, Excel, Word, and CSV are all supported.
2. AI reads it and matches it to your remit The document is matched to the correct line by reference number and amount, and Type, Context, and Period are proposed based on what the document actually says — not a guess from the invoice number alone.
3. Review what's flagged, confirm the rest A short summary appears once processing finishes, and a guided walkthrough steps you through anything that needs a look — a low-confidence field, a document that couldn't be matched, a line with no document at all, or a deduction over your configured dollar threshold.
Row flags
Green — High confidence (≥ 0.75) The document clearly supports this coding. Safe to export without review in most cases.
Yellow — Reasonable confidence (0.50–0.74) The document supports this coding, but with some ambiguity. Worth a quick check.
Orange — Low confidence, or field not found (< 0.50) Either the document was unclear, or a field (like Period) wasn't found in it at all. Verify before exporting.
📎
No document attached A document batch was processed, but nothing matched this line, and it isn't fully coded yet. Attach a document or code it by hand.
$
Over your review threshold The deduction is larger than the amount configured above. Shown regardless of confidence — even a fully-confident coding on a large line gets a flag, just to be sure.
Hover the flag next to the preview icon on any row to see why it's flagged. Confirming a row in the guided walkthrough clears its flags even if you didn't change anything — it's how you tell RemitParse "I looked, this is fine."
Makes Auto-Coding better over time. Auto-Coding and AI Document Coding don't compete for the same row — Auto-Coding fills first from history, and if you later match a document to that same line, the document's answer takes priority, since it's actual evidence for this specific transaction rather than a pattern guess. Every coding confirmed this way is saved to the same history Auto-Coding draws from, so the more deductions you code from real documents, the more that shared history reflects verified answers instead of inference — which is what Auto-Coding is pre-filling from on your very next upload.
Connect QuickBooks in your Account settings to configure payment posting options.
Deposit Accounts
Select the bank account each customer's ACH payments are deposited into. Must match a Bank or Other Current Asset account in QBO.
Loading accounts from QuickBooks…
No customer mappings found. Add customer mappings in the Customer Mapping tab first.
Payment Search: export a wider window (60+ days) so prior netting charges that offset this period's EFTs are included. Only EFTs within the date range above will be reconstructed — earlier nettings are used silently for linkage only. Invoice Search & Promo Payments: at least 3 months of data recommended.
Type
Ref #
Date
Invoice(s)
Total
Match Invoices to Payment
Match open QBO invoices to this remittance before posting payment.
Loading open invoices from QuickBooks…
Cash Received—
+
New CM (deductions)$0.00
=
Matched Invoices—
+
Repayment Rows$0.00
−
Pre-existing CMs$0.00
+
Rounding Adj
⚠ Not balanced
QuickBooks Period Locked
The remittance date falls in a closed accounting period.
QuickBooks won't accept transactions dated in a locked period. Enter a date in an open period to post this payment — typically the 1st of the following month.
Original remittance date:—
Free Export
Get your CSV
Drop your email and we'll keep you posted on new parsers and features. Your CSV downloads instantly.
🎉
Enjoy the CSV!
But could you imagine doing this for every remittance — with deductions auto-coded and payments posted directly to QuickBooks?
✓Auto-coding deductions from your history
✓1-click payment & credit memo posting to QuickBooks