BV Intake

The finance request desk in Slack, with the controls auditors ask for

Type /bv in Slack, react to any message with :receipt:, or forward an email. Intake turns it into a tracked request with a category, an owner and an SLA, keeps the requester updated in their thread, and enforces approvals and segregation of duties on the server, not just in the UI.

The problem

Finance requests arrive everywhere and get controlled nowhere

Sales, employees and vendors all need something from finance. Most of it arrives as a message, and some of it is the kind of message fraud starts with.

DMs and threads

Requests get buried

A refund request in #sales, a missing invoice in a DM, a vendor change by email. Each one depends on someone remembering it.

Bank details in chat

Sensitive numbers everywhere

Account numbers, IBANs and card numbers get pasted into Slack, and a "please update our bank details" message is the classic payment-fraud opener.

No record

Nothing to show an auditor

Who approved that refund, who called the vendor back, and was it the same person who asked? Usually nobody can say.

How it works

From a message to a closed, auditable request

  1. 01 · You

    Ask

    Type /bv and your request, or /bv alone to open a form (type, amount, vendor or customer, invoice or PO number, due date). Or react with :receipt: or use the "Create finance request" shortcut on any message.

  2. 02 · Agent

    Triage

    Bank, card, SSN and EIN numbers are masked first. Then the request is categorized and the amount, vendor, invoice or PO number and due date are pulled out; keyword rules take over if AI is off or over budget.

  3. 03 · Rule

    Route and approve

    Your rules pick the owner (by category, channel, keyword or amount, or round-robin). Refunds, reimbursements, POs and card requests get an approval chain from your amount thresholds.

  4. 04 · You

    Resolve

    The owner replies from BillVerge or the thread; replies reach the requester, internal notes never do. On resolve, the requester rates the help from 1 to 5.

BillVerge APP · 10:02 AM

@dana used /bv: refund for Acme Retail, $1,250.00, order 1182.

Request#TK-1730 · Refund
Amount$1,250.00
OwnerPriya · AR
ApprovalManager (over $1,000)
First response dueToday 2:30 PM
Assign to meChange categoryPriorityResolve
Example message. Example data.
In Slack

Every request gets a card, an owner and a business-hours clock

New requests post to your triage channel with Assign to me, Change category, Priority and Resolve. Approvers get Approve and Reject buttons in the same thread, and Slack users are matched to BillVerge users by email before any button does anything.

Requests in confidential categories post as a redacted summary and their replies go by direct message.

What Intake handles

Built around the requests finance actually gets, and the controls they need

15 finance categories

  • Payment status and invoice status
  • Missing invoice; invoice or fee dispute
  • Refund; duplicate payment; credit memo
  • Vendor bank or remit-to change; vendor onboarding and W-9s
  • Statement, PO, expense reimbursement, card and budget requests

Segregation of duties, enforced

  • The requester can never approve, resolve or close their own request
  • Refunds and reimbursements: the approver must differ from the owner who handled it (on by default)
  • One person cannot approve two steps of the same chain
  • Checked on every path: the API, Slack buttons and the ticket screens

Approvals by amount

  • Sequential steps from your thresholds, e.g. over $1,000 a manager, over $10,000 a controller
  • Approve or reject from Slack or the app; rejections need a reason
  • Change the amount and approval starts again
  • Missing amount or another currency: every step is required

Vendor bank-change protocol

  • Intake never accepts or applies bank details from a message
  • Account, routing and IBAN numbers are masked and the requester is asked not to post them
  • A Payables exception blocks pay runs to that vendor until verified
  • Call-back on a number from records on file, with its source, the caller, time and outcome recorded
  • A second admin or manager, not the caller and not the requester, approves

PII redaction everywhere

  • Bank account and routing numbers, IBANs (checksum-verified), card numbers (Luhn-checked), SSNs and EINs
  • Masked to the last 4 before anything is stored or sent to AI
  • Applies to requests, replies, notes and CSAT comments
  • Invoice and PO numbers, amounts, dates and phone numbers are left alone

SLAs in business hours

  • First-response and resolution targets per priority and per category
  • Your timezone and working hours; weekends and your holidays skipped
  • Warning at 80%, breach alerts in the triage channel, escalation to managers
  • The resolution clock pauses while waiting on the requester

Answers from your ledger

  • Payment and invoice status questions are matched to bills and invoices synced from QuickBooks or Xero, and to the bank payment that references them
  • The draft cites what it found; when nothing matches, there is no draft
  • A person approves each draft, unless you allow auto-posting above a confidence level

Two-way threads, reminders, CSAT

  • Replies post to the requester’s Slack thread, or by email for emailed requests
  • Internal notes stay in BillVerge; triage-thread chatter is saved as internal notes
  • Nudges after 2 business days waiting on the requester, then auto-close with a notice
  • A 1 to 5 rating in Slack or from a signed email link, with an optional comment

Audit, access and retention

  • Every create, category, priority, owner and status change, approval, redaction, confidential view, SLA breach and verification step is in an append-only audit log
  • Confidential categories visible only to the owner, approvers, the requester and finance admins
  • Optional retention: anonymize requester details and text a set number of days after close; metadata and audit stay
  • Possible duplicates (same requester, near-identical text, 7 days) are flagged and linked, never merged
Pricing

Free for up to 3 users

Founding-customer pricingFreeUp to 3 usersGrowth: $29/mo for unlimited users

For bigger teams, $29 a month with unlimited users. Exceptions is included.

See all pricing
Questions

Common questions

Is Intake available now?

Yes. Intake is live. Recon, Exceptions, Payables Guard, Collect and Close are in early access.

How do people send a request?

In Slack, type /bv followed by the request, or /bv on its own to open a short form. You can also react to any message with :receipt: (the emoji is configurable) or use the "Create finance request" message shortcut. Email that arrives in your connected Gmail inbox becomes a request too.

Does Intake change vendor bank details?

No. Intake never accepts or applies bank details. It masks them, blocks payments to that vendor in Payables Guard and walks your team through a call-back and a second approval. Your AP team then updates the vendor record in your accounting system.

What does the AI see?

Only the masked text. Account, card, SSN and EIN numbers are replaced with their last 4 digits before anything is stored or sent to the model, and AI spend is capped per organization each month.

What reports are included?

Volume by category, source and week, median first response and resolution time, SLA compliance, backlog aging, approval turnaround and average CSAT.

See it on your own data

Book a 30-minute walkthrough, or run the free Payout Reconciler on one of last month’s Stripe payouts first.