01
The problem
Cash arrives on different rails with different remittance formats: an ACH with a reference number, a wire with a note, a check with a stub, a card batch. Matching each receipt to the right open invoice by hand is hours of daily work, and the harder the match, the more likely it is applied to the wrong account.
02
How it is built
- 1Webhook trigger starts the run on a new payment or remittance advice.
- 2Agent block reads the remittance detail from the email or attached file, whatever format it arrives in.
- 3NetSuite or Sage Intacct block pulls the open invoices for the customer so the match runs against live receivables.
- 4Code block matches the payment to those invoices on amount, reference, and customer.
- 5Condition block routes partial payments and unmatched receipts to a review path.
- 6NetSuite or Sage Intacct block applies the cash to the matched invoices.
- 7Slack block summarizes what was applied and what needs a human.
03
The payoff
One matching engine handles every rail, and the reason a payment matched a given invoice is recorded. The AI reads the messy remittance; the coded match decides where the cash lands. In a typical run, the bulk of receipts apply automatically and only the genuine exceptions reach a person.
Want this workflow built and maintained for your finance stack?
Book a demo