Evenbead docs
Contents

Pay bills

Pay many bills at once: tick them, set what you pay on each, preview it in words, record it. Each vendor gets one payment for all of its bills, recorded the same way as paying one bill (the payment, its entry, the bills it pays), and the whole run is recorded all or nothing. (Dated 2026-10-16.)

On the Pay bills page

Open Bills, then Pay bills (the dashboard links it from "You owe vendors" too).

  1. Choose which bills to see. Every open bill is listed, oldest due first, with its vendor, due date, open amount and how many days overdue it is. Narrow it to bills due by a date, one vendor, or overdue only.
  2. Pay from, date and how. Choose the bank, cash or card account the money leaves, the payment date, and how you pay: check, bank transfer (ACH), card, cash or other. For checks give the first check number: each vendor's check takes the next number (vendors in name order) and the number is kept on the payment. For other methods you can add a reference.
  3. Tick the bills and set the amounts. The amount starts at what is open; lower it for a part payment (the rest stays open). The running total says how many bills, vendors and payments, and names any bill given more than it has open.
  4. Vendor credits. A vendor's credits with something left are listed: choose the bill one pays and how much. A bill can be paid by a credit alone (amount 0.00).
  5. Earlier payments. Money you already paid a vendor that is not applied to a bill yet (a prepayment or deposit, or an overpayment) is listed under Earlier payments you can apply. Choose the bill it pays and how much, as with a credit. No money moves for it, and it can never be applied for more than is left on it or open on the bill.
  6. Preview shows the run in words, vendor by vendor: the bills, what each gets, the credits applied, and what that vendor still has open afterwards. Nothing is recorded yet. If a payment is already on the bank, the preview offers the bank lines that could be it: pick one to tie it to the payment. It also says which vendors get a remittance advice by email (below); untick a vendor to skip its email.
  7. Record. One payment per vendor is posted, with its entry. If any bill cannot be paid (more than is open, a locked month, a check number already used), nothing is recorded and the message names the bill and why.

The result page lists each payment with its number, check number, bills, entry and bank line. To undo a payment, Void it there (or on the payment's page): its bills open again, and its bank line goes back to Unmatched. Bills paid earlier lists past runs.

Remittance advice to vendors

When a run is recorded, each vendor you paid (money moved, not credits alone) gets an email from your company saying what the payment covers, if the vendor has an email address on file and you left it ticked in the preview. It shows the payment number and date, how you paid (with the check number), the account it came from by its name and last four digits only, each invoice paid (by the vendor's own invoice number when the bill has one), the credits and earlier payments applied, and the total. It carries your company's name, colour and contact details, and a PDF with your logo is attached. Replies go to your Reply-To address.

The result page's Remittance advice section shows each vendor's emails (queued, sent, not delivered) and has Send again. A vendor with no address on file gets none: add one on the vendor's page, then Send it from the run. Nothing is sent to an address that unsubscribed or bounced, or while email is switched off; the run is recorded anyway. In the demo, the email is recorded as delivered and never really sent.

Which bank lines are suggested

On a bill's Pay this bill and in the preview, Evenbead suggests bank lines that could be the payment. A line is suggested only when it is money out on the account paying, not categorized yet, dated on or after the bill and within 45 days of the payment, and either

  • exactly the amount being paid (the bill's open balance, or the vendor's total in a run), or
  • a part payment: less than the amount but at least half of it, and the bank's text names the vendor or shows the check number.

A larger line, or one much smaller than the bill (a $355.00 charge for a $1,850.00 bill), is never suggested. The exact amount comes first, then the vendor's name on the line, the check number, and the closest date; each suggestion says why.

Agents

An AI agent can prepare a run (pay_bills_batch over MCP, POST /v1/bill-payment-batches over REST) but never records one: it waits in Approvals, said in words. Open it and Review the amounts and approve: change amounts or leave bills out, then approve. It is recorded as you, by the same path, and the audit log names the agent and its proposal. Which vendors get a remittance advice is part of the agent's proposal and is shown on the review page; nothing is emailed until you approve, and you can untick any vendor first.

API

GET /v1/payable-bills, POST /v1/bill-payment-batches (with dry_run for the preview), GET /v1/bill-payment-batches and /{id}, GET /v1/bill-payment-line-suggestions, GET /v1/proposals/{id}/bill-payments, POST /v1/proposals/{id}/approve-bill-payments, POST /v1/bill-payment-batches/{id}/remittances (send a remittance again). A run takes prepayments (earlier payments applied) and, per vendor, email_remittance; the batch's page and the API return each vendor's remittances. Each is also an MCP tool. Not yet: printing checks and stubs.