Skip to main content
Wrenbase

The vendor layer

Everyone you pay,
in one place.

Every vendor record builds itself as bills arrive. Their details, every bill they've sent, what you've paid, their block status, and every screening result, all on one record. No separate list to maintain.

P

Pixel Forge

Vendor · 22 bills submitted

Active

Paid

$18,900

Outstanding

$3,400

Blocked

0

Recent bills

BILL-318

$3,400

Screened

BILL-306

$1,200

Paid

BILL-291

$2,800

Paid

No data entry

Bills come in. The record appears.

When a vendor submits through your intake link, their record is created and every bill they send attaches to it. You get a running history for each vendor without ever building a list by hand.

Intake submission

From: Tile Source Inc

Bill: $2,400 · PO-2026-114

Screened, vendor created
T

Tile Source Inc

First bill · screened · just now

Added

Vendor status

Pixel Forge

22 bills · verified

Active

Tile Source Inc

new · verified

Active

Unknown sender

not on your list

Held

[email protected]

changed bank detail

Blocked

Screened and controlled

Every bill checked, every block enforced.

Screening runs on each incoming bill and the result lands on the vendor: a changed bank detail flagged, a new vendor verified before a first payment, blocked attempts logged. Block a vendor and their future submissions are rejected before they reach you.

Know your spend

What you've paid each vendor, without the tally.

Total billed, total paid, what's outstanding, and full submission history sit on every vendor record. It's read from your real bills, so the number is right without you keeping a spreadsheet.

Projects · The organizing layer

Know what each engagement actually made.

In Wrenbase, every engagement is a project.

Vendor bills can link to a project and count against its spend, so a job's costs stay tied to the vendors that drove them.

Riverside Brand Shoot · Overview

on track

Profit 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.

Part of Wrenbase

Vendors connect to the rest of Wrenbase.

Every vendor, one record.

Free to start. Share your intake link and the records begin.

Common questions

Quick answers.

What is a vendor in Wrenbase?
Everyone you pay. A vendor record holds their details, every bill they've sent you, what you've paid, and how they submit. It builds itself as bills come in, so there's no separate list to maintain.
How do vendors get added?
Two ways. Add one yourself, or let it happen automatically: when a vendor submits a bill through your intake link, their record is created and their bills attach to it from then on.
Can I block a vendor?
Yes. Block a vendor and their future submissions are rejected automatically, before they reach your inbox. The block sticks until you lift it, and it shows on the vendor's record.
How does screening tie into vendors?
Every incoming bill is screened before it reaches your queue, and the result attaches to the vendor. A changed bank detail is flagged, a new vendor is verified before a first payment, and blocked attempts are logged on the record.
Can I see how much I've paid a vendor?
Yes. Each vendor shows total billed, total paid, what's outstanding, and their submission history, drawn from your real bills, not a manual tally.
Can I import my existing vendor list?
Yes. Drop in a CSV from a spreadsheet or your accounting tool, map the columns once, and your vendors are ready.