BILL
live · conformance passing
Models BILL's accounts payable surface — vendors, bills with line items and server-computed amounts, the approval policy a bill has to clear, payments that schedule and settle, and payments recorded from outside BILL — along with the receivable side, its chart of accounts, and the 35 minute session window every caller meets.
- Category
- Accounting
- Environment key
- 01…
- Verified against
- https://developer.bill.com/openapi/bill-v3-api.json 1
- Replaces
- A shared BILL sandbox, a payables ledger nobody dares approve against
Scenarios
Start an environment in one of these, or describe the state you want in a sentence and the seeder writes the records it implies.
Busy payables
Vendors, a chart of accounts and bills across several ages and statuses, some approved and some awaiting approval, with more rows than one page holds.
Awaiting approval
Bills sitting in the approval queue under a two-step policy, so an approval agent has work on its first call.
Failed payment
A payment returned with a real reason and its bill owing again, which is the state no sequence of API calls can reach.
Expired session
The session the container starts with is already idle past BILL's 35 minute window, so signing in again is the caller's first step.
Open receivables
Customers and invoices at several ages, some part-paid, for the receivable side of a close.
What it models
Records your code can read, write and edit for the life of the environment. A route the twin does not model returns a provider-shaped refusal rather than a plausible response.
- vendors
- bills
- bill_line_items
- bill_approvals
- payments
- customers
- invoices
- invoice_line_items
- receivable_payments
- chart_of_accounts
- funding_accounts
- users
- sessions
Verified in CI against
- openapihttps://developer.bill.com/openapi/bill-v3-api.json1