Build on Wrenbase · Automate
Stop re-keying the same data.
Push purchase orders, vendor records, and bills into Wrenbase straight from your ERP, inbox, or own tooling, and each one is screened on the way in. Pull invoices, payments, and ledger data back out. The systems you already run keep talking to each other, without a person copying rows between them.
The REST API is live today. Webhooks are on the way. For higher-volume automation, talk to us and we'll set it up for your stack.
Automated ingest
liveERP
Inbox
Procurement
Screened on ingest
Your Bills inbox
3 newChapter 1 · The busywork
A PO in one system. Typed again in the next.
The data already exists in your ERP or your inbox. Getting it into your AP workflow means someone re-typing it, which is slow and where the errors creep in. Automation moves the row for you and checks it on arrival, so the same number never gets keyed twice.
Chapter 2 · How it connects
Wire it to what you already run.
Three ways in, whichever fits the system on the other end. No rip-and-replace.
REST API
Push records in and pull data out with direct HTTP calls from your own code.
POST /v1/invoices
File drop
Export a CSV from a system that can't call an API, map the columns once, reuse it.
contacts.csv
Webhooks
Coming soonSubscribe to events and Wrenbase posts to your endpoint the moment they happen. On the roadmap, talk to us if you need them.
invoice.received
Chapter 3 · Checked on arrival
Automation speeds up the work, not the risk.
Every record pushed in through the API goes through the same screening as anything entered by hand. Sanctions checks and your rules run before a bill lands in your workflow, so wiring up a feed never means opening a door that skips the checks.
How screening works →Incoming bill from your ERP
$4,200 · [email protected]
Sanctions compliance
Your rules
Sender reputation
Passed · added to your Bills inbox
Chapter 4 · Two-way · coming soon
Soon, your systems hear back the moment it happens.
Webhooks are on the roadmap. Once they land, you subscribe and Wrenbase posts to your endpoint when an invoice arrives or a submission is held, so your ERP and dashboards react in real time instead of polling. Until then, poll the API for the current state.
{
"event": "invoice.received",
"id": "inv_2211",
"amount": 4200,
"screened": true
}
Planned: your ERP updates the moment it fires.
Wire it up once.
Read the API reference, generate a key, and point your systems at Wrenbase.
Common questions
Quick answers.
- What can I automate with Wrenbase?
- Feed purchase orders, vendor records, and bills into Wrenbase from the systems you already run, and pull invoices, payments, and ledger data back out. Anything that would otherwise be manual data entry can flow over the API instead.
- What systems can I connect?
- Anything that can make an HTTP request or export a file. Common starting points are an ERP, an accounting tool, a procurement system, or a shared inbox. If it can send JSON or drop a CSV, it can talk to Wrenbase.
- Does automated data skip screening?
- No. Records pushed in through the API go through the same screening as anything entered in the app. Sanctions checks and your rules run on the way in, so automation speeds up the busywork without letting an unchecked payable through.
- How will I know when something happens?
- Webhooks are on the way. Once they land, you'll subscribe to events like an invoice arriving and Wrenbase will post to your endpoint so your systems react in real time instead of polling. Today, poll the API for the current state.
- Do I have to replace my current tools?
- No. Automation connects Wrenbase to what you already run, so your ERP and accounting stack stay in place. Data flows between them instead of being re-keyed by hand.
- Is there a fee to automate?
- There's no separate automation fee. You build against the same account and plan you already use. Higher-volume arrangements are worked out with us directly.