Chase utility rebate claims until the credit lands
Every Monday, WebRun opens Epicor Eclipse, finds utility rebate-eligible orders that haven't been submitted or are still pending, drafts the claim submission in Gmail for your rebate coordinator, checks QuickBooks for credits paid since last week, and posts accounting and sales a Slack tracker of what's submitted, paid, and overdue.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I track utility rebate claims automatically from submission to payout?
WebRun finds utility rebate-eligible orders in Epicor Eclipse every Monday, drafts the claim submission in Gmail for your rebate coordinator to review and submit, then checks QuickBooks for credits paid since the last run and matches them to open claims. It posts accounting and sales a Slack tracker of what's submitted, paid, and overdue past 60 days.
- Rebate claims get submitted the week they're eligible instead of piling up unfiled
- Paid credits are matched to their claim automatically instead of a manual QuickBooks search
- Claims stuck past 60 days surface at the top of the tracker instead of getting forgotten
Built for electrical distributors · rebate program coordinators · accounting and AR teams · outside sales reps
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
www.epicor.com/en-us/products/enterprise-resource-planning-erp/eclipsein a real browser with your saved login - no setup, no API keys. -
1
Epicor Eclipse - find rebate-eligible orders awaiting claim
WebRun opens Epicor Eclipse to find rebate-eligible orders awaiting claim. - Open orders tagged with a utility rebate program such as LED, motors, or controls
- Filter to orders not yet submitted or still pending a decision
- Capture the customer, program, product, and rebate amount for each
Done when Every rebate-eligible order has its submission status listed.
-
2
Gmail - draft the claim submission for review
WebRun opens Gmail to draft the claim submission for review. - Draft the claim submission to the utility program administrator with the order and product details
- Reference the program name and rebate amount in the draft
- Leave it unsent in Gmail for your rebate coordinator to attach paperwork and submit
Done when A ready-to-submit draft is waiting in Gmail for every unsubmitted rebate claim.
-
3
QuickBooks - reconcile the credit once it's paid
- Check for rebate credits or checks received since the last run
- Match each credit against its open claim by program and amount
- Mark matched claims paid and note any claim still outstanding past 60 days
Done when Every paid rebate is matched, and claims outstanding past 60 days are flagged.
-
4
Slack - post the week's claim tracker
WebRun opens Slack to post the week's claim tracker. - Post the week's rebate tracker to the accounting and sales channel
- Break it into submitted, pending, paid, and stale past 60 days
- Put the oldest outstanding claims at the top
Done when Accounting and sales have this week's rebate status 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
Will it submit rebate claims without me?
No. WebRun drafts every claim submission in Gmail and leaves it unsent, so your rebate coordinator can attach the required paperwork and submit it.
How does it know a rebate credit was paid?
It checks QuickBooks each Monday for credits or checks received since the last run and matches them to an open claim by program and amount.
What happens to a claim that's taking too long?
Any claim still outstanding past 60 days is flagged at the top of the Slack tracker so your team can follow up with the utility.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.