Screened payables
Checked before
it reaches your queue.
Bills arrive from a public link or your vendors, and each one goes through screening the moment it lands. Sanctions checks and the rules you set run on every submission, so a bad payable is caught before it enters your workflow and you only weigh the ones that pass.
Incoming bills · screened
Pixel Forge · $3,400
Passed all checks
Blocked · not on your list
1 reached your queue
1 stopped at the door
What you're protected from
The first pass, done for you.
Six checks run on every incoming bill before it reaches your queue.
Sanctions compliance
Senders tied to comprehensively sanctioned jurisdictions are stopped at the door.
Your blocklist
Vendors you've blocked stay blocked. Their submissions are rejected automatically.
Bots and throwaways
Automated abuse and disposable-address spam are filtered out before they reach you.
Bad actors
Reputation signals flag the senders that look like trouble, so you can take a closer look.
New senders
A sender you've never paid is verified before a first payment goes out.
Changed bank details
A changed payout account is flagged for a second look, not quietly paid.
Screening informs, you decide
It does the checking. You make the call.
Screening never quietly pays or blocks a real vendor on its own. It hands you a clear read with the reasons behind it, then waits. You approve, hold, or reject. The only thing settled without you is a hard sanctions failure.
See what we blocked
Proof it's doing something.
Most screening tools block things and never tell you. Wrenbase lists every blocked submission and the reason in plain words. Check it once a week and you'll know exactly what the engine kept out of your workflow.
Submissions · 7d
142
Blocked · 7d
17
What we blocked
- bots and throwaways9
- sanctions4
- not on your list3
- automated abuse1
Projects · The organizing layer
Know what each engagement actually made.
In Wrenbase, every engagement is a project.
Screened bills can link to a project and count against its spend, so job costs stay honest while the incoming side stays protected.
Riverside Brand Shoot · Overview
on trackProfit margin
60%
Outstanding
$1,000
Budget
$14.6k left
Cash timeline, next 6 weeks
Weeks 1-2 run cash-negative before Acme's payment lands in week 3. Consider nudging invoice #4.
Only weigh the bills that pass.
Free to start. Screening is on from the first bill.
Common questions
Quick answers.
- What does 'screened payables' mean?
- Every incoming bill is checked before it reaches your approval queue. Sanctions checks and the rules you set run on each submission, so a bad payable is caught before it lands in your workflow.
- What actually gets checked?
- Sanctions compliance, your own blocklist, bot and throwaway-address filtering, and sender reputation. New senders are verified before a first payment, and a changed bank detail is flagged instead of quietly paid.
- Who is this for?
- Any business that pays vendors and doesn't want to inspect every incoming bill by hand. If bills reach you from a public link, a shared inbox, or many vendors, screening does the first pass so you only weigh the ones that matter.
- Does screening decide who gets paid?
- No. It does the checking and hands you a clear read with the reasons behind it. You approve, hold, or reject. The only thing it settles on its own is a hard sanctions failure, which can't be approved through Wrenbase either way.
- Does this slow down my real vendors?
- No. Screening runs in seconds when a bill arrives. Anything that fails is blocked and logged; everything else reaches you right away.
- Where can I see what was blocked?
- Your dashboard has an activity panel listing every blocked submission and the reason in plain words. Check it once a week and you'll know exactly what the engine kept out.
