Get a demo

Cash reconciliation

Match remittances to invoices, reconcile bank deposits to NetSuite, and surface in-transit transactions that never closed out. The accounting team owns the flow, no engineering required.

Get a demo

The prompt

I want to automate cash reconciliation. Build me a flow that pulls bank deposits, matches them against open invoices in NetSuite or my ERP, applies the payment to the right invoice, and flags any deposit that doesn't have a clean match for the accounting team to work.

Just copy and paste the prompt into a new Parabola flow to get started.

What Parabola builds

A workflow with six steps you can edit:

1. Pull bank deposits. From your bank feed, statement, or treasury workstation. Date, amount, originator, reference field.

2. Pull open invoices. Every unpaid invoice in NetSuite or your ERP, with customer, invoice number, amount, and reference.

3. Match payment to invoice. Exact match on reference first, then customer-plus-amount, then fuzzy on customer name. Each match gets a confidence score.

4. Apply the payment. Write the payment application back to NetSuite. Mark the invoice paid, partial paid, or short pay.

5. Flag the exceptions. Deposits that didn't match, partial payments, duplicates, deposits applied to multiple invoices. Each lands in a queue with the reason.

6. Output the work queue. Exception list for accounting to work, plus a reconciliation summary tying the bank deposit total to applied AR.

Why teams stop doing this manually

Cash rec is the report that holds up close. Bank deposits land in one system. Open invoices live in another. The accountant exports both, drops them into a workbook, and runs VLOOKUPs against the reference field until the deposits and the invoices line up.

The problem is the reference field. A wire from a major retailer has the customer name, sometimes the invoice number, sometimes a remittance reference that points to a PDF detail file the retailer emailed separately. Each retailer formats it differently. Each new retailer takes weeks to set up.

What ends up sitting in the in-transit account is the residue. Payments that almost matched. Duplicates that one team applied and another team reapplied. Short pays that nobody flagged. The clearing account grows every period until someone runs a scan.

A reconciliation flow handles the first 80 percent automatically: clean references match, customer-plus-amount matches resolve. The remaining 20 percent lands in an exception queue accounting works one at a time. That is the right division of labor.

How it works

Step 1. Paste the prompt.

Open Parabola, paste the prompt in section 2, and let it ask follow-up questions about your bank feed, your customer master, and how aggressive to be with fuzzy matching.

Step 2. Connect your data.

API connections to NetSuite or your ERP, your bank feed, and any remittance PDF inbox that needs parsing. Plus the customer master.

Step 3. Run it daily.

The flow runs against fresh deposits each morning. Matches apply automatically. Exceptions land in a queue. New retailer with a weird reference format? Add a parsing rule to the flow.

Related prompts

FAQ

Can the flow handle wholesale retailer remittances with PDF detail?

Yes. Add a PDF parsing step to extract line items from the retailer's remittance email. The flow matches each line against the corresponding invoice.

What about short payments and chargebacks?

Short pays auto-apply with a deduction code if the variance is within tolerance. Outside tolerance, they land in the exception queue. Chargebacks get tagged for the wholesale ops team to dispute.

Can the flow write the payment application back to NetSuite?

Yes. The output is a payment-application file in the format NetSuite expects, or a direct API write if your NetSuite has the right scripts in place.

How does it handle deposits that don't match anything?

They land in an unmatched queue with the deposit detail. Accounting works them one at a time, applies them manually, and the resolution can train the flow for next time.

How is this different from a treasury workstation?

Treasury workstations are great at the bank side. The flow connects the bank side to AR. It is the join that most teams build in Excel today.
Apply 80 percent of cash on autopilot.
Paste the prompt, point it at your bank feed and your ERP, and let the matching run on its own.
Start for free