Automated Chargeback Ledger Matching
Every morning, WebRun reads new chargebacks in Chargeflow, finds the matching sales order and revenue transaction in NetSuite by amount, date, and reference, tags each dispute with its original entry, and posts Slack a list of any chargeback it could not tie to a booked sale.
How do I match each chargeback to its original transaction in the ledger?
WebRun ties every chargeback to its source each morning. It reads new disputes in Chargeflow and matches each to the original sales order and revenue entry in NetSuite by amount, date, and reference, tagging the transaction and posting Slack any chargeback it cannot link to a booked sale, so nothing disputed goes untraced in your ledger.
- Every chargeback ties back to the exact sale it came from
- Unmatched disputes are flagged instead of forced
- The ledger is never edited by the automation
Built for finance teams · ecommerce merchants · controllers · revenue accountants
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.chargeflow.ioin a real browser with your saved login - no setup, no API keys. -
1
Chargeflow - read new disputes
chargeflow.io
WebRun opens Chargeflow to read the new disputes. - Open Chargeflow and list chargebacks added since the last run
- Capture the amount, transaction reference, card last four, and date for each
- Prepare each for a lookup against the ledger
Done when Every new chargeback is listed with the fields needed to match it.
-
2
NetSuite - match the original entry
netsuite.com
WebRun opens NetSuite to match the original entry. - Search NetSuite for the sales order and revenue entry behind each dispute
- Match by amount, date, order reference, and customer
- Tag the transaction with the dispute and mark any chargeback with no clear match
Done when Each chargeback is linked to its ledger entry or marked unmatched.
-
3
Slack - flag the unmatched
slack.com
WebRun opens Slack to flag the unmatched disputes. - Post a short list of chargebacks that could not be tied to a sale
- Include the amount, reference, and why the match failed
- Leave it for the team to resolve, WebRun only reports, it does not edit the ledger
Done when Your team has the unmatched chargebacks to resolve in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it change anything in NetSuite?
It only tags each transaction with its matching dispute for traceability and reports the rest. WebRun does not post journal entries or edit amounts, so your ledger balances are never altered by the automation.
Why would a chargeback not match a sale?
A mismatched reference, a partial capture, a duplicate charge, or an amount that differs from the order. WebRun flags each of these in Slack so a person can investigate rather than force a wrong match.
How does it match a dispute to a transaction?
By amount, date, order reference, customer, and card last four. WebRun cross-checks these between Chargeflow and NetSuite so each chargeback ties back to the exact sale it came from.
Related templates
Shopify›Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.