Bill AR | Customer transactions
Browse all Bill APIs★ Only Publicly Available OpenAPI DocumentFinanceAccountingapiKey40 EndpointsREST
For Agents
Send customer invoices, run recurring billing, charge authorised customers, and reconcile received payments through BILL's AR API.
Use for: I need to invoice a customer through BILL, I want to set up recurring monthly billing for a customer, Send a pending invoice to the customer's email, Charge an authorised customer for an outstanding amount
Not supported: Does not handle vendor bills, AP payment runs, or organisation-level user and bank-account administration — use for accounts receivable customer invoicing and collections only.
Jentic publishes the only available OpenAPI specification for AR | Customer transactions, keeping it validated and agent-ready. The BILL main bundle exposes the Accounts Receivable surface that automates how an organisation invoices customers and collects what is owed. Agents can create one-off and recurring invoices, issue credit memos, send invoices by email or postal mail, charge authorised customers, and record received payments back into the BILL ledger. Invoice credits, received payments, conversion fees, and a top-line AR summary are also exposed for reconciliation.
Install Jentic One Beta
Connect the AR | Customer transactions to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AR | Customer transactions, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AR | Customer transactions API.
Create, update, and bulk-modify customer invoices and recurring invoice schedules
Send invoices to customers by email or postal mail and capture customer charge authorisations
Charge authorised customers and record AR payments against the originating invoice
Issue credit memos and read invoice credits applied to customer accounts
Inspect received payment records, processing fees, and an aggregate AR summary
Use Cases
Patterns agents use AR | Customer transactions API for, with concrete tasks.
★ Automated subscription invoicing
Generate and dispatch recurring invoices for subscription customers and post received payments back to the ledger. The API creates RecurringInvoice schedules, sends each cycle's Invoice via SendInvoice or MailInvoice, and writes a ReceivedPay record once funds clear. A small finance team can manage hundreds of recurring customers without hand-keying invoices.
Create a RecurringInvoice for customer ID 0cu01AAAAA at $299/month with email delivery, then verify the next-run date populated correctly
AR collection on authorised customers
Charge authorised customers' bank accounts and reconcile inflows against open invoices. The agent calls SetCustomerAuthorization to capture mandate, ChargeCustomer to debit, and RecordARPayment to mark the invoice settled. This closes the AR loop end-to-end through one API surface.
Call ChargeCustomer for invoice 00n01AAAAA against the authorised bank mandate, then call RecordARPayment with the returned reference
Credit memo and adjustment workflow
Apply credit memos for disputed, returned, or partially refunded services, and audit the resulting credits. The API exposes Crud/Create/CreditMemo plus Read and List operations on InvoiceCredit so an agent can reverse charges and confirm the credit posted, useful for AR teams managing chargebacks or pricing corrections.
Create a $75 CreditMemo against invoice 00n01AAAAA, then call List/InvoiceCredit to confirm the credit posted to the customer record
Cash-flow reporting for finance agents
Pull a consolidated AR position on demand. GetARSummary returns aggregate balances and aging while List/ReceivedPay enumerates inflows over a window. A finance agent can answer 'how much is outstanding?' or feed a weekly cash-flow brief without the user opening BILL.
Call GetARSummary for the connected organisation and return total outstanding balance plus current-period received payment total
Agent-driven AR operations via Jentic
An AI agent uses Jentic to discover BILL operations from a natural-language intent like 'send a customer invoice'. Jentic returns the matching SendInvoice operation, loads its input schema, and executes the call with credentials held in the Jentic vault. The agent can chain Create + Send + RecordARPayment with no direct exposure to BILL session tokens.
Search Jentic for 'send a customer invoice', load the SendInvoice schema, and execute it for invoice 00n01AAAAA
Key Endpoints
40 endpoints — jentic publishes the only available openapi specification for ar | customer transactions, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/Crud/Create/Invoice.json
Create a customer invoice
POST
/Crud/Create/RecurringInvoice.json
Create a recurring invoice schedule
POST
/SendInvoice.json
Email an invoice to the customer
POST
/ChargeCustomer.json
Charge an authorised customer
POST
/RecordARPayment.json
Record a payment received against an invoice
POST
/Crud/Create/CreditMemo.json
Issue a credit memo
POST
/GetARSummary.json
Retrieve consolidated AR summary
POST
/Crud/Create/Invoice.json
Create a customer invoice
POST
/Crud/Create/RecurringInvoice.json
Create a recurring invoice schedule
POST
/SendInvoice.json
Email an invoice to the customer
POST
/ChargeCustomer.json
Charge an authorised customer
POST
/RecordARPayment.json
Record a payment received against an invoice
POST
/Crud/Create/CreditMemo.json
Issue a credit memo
POST
/GetARSummary.json
Retrieve consolidated AR summary
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
BILL developer keys and session tokens are encrypted in the Jentic vault. Agents receive a scoped reference and never see the raw key, so a leaked context cannot replay AR charges.
Intent-based discovery
Agents search Jentic with intents like 'send a customer invoice' and Jentic returns the matching BILL operation with its input schema, removing the need to read BILL's developer portal.
Time to first call
Direct BILL integration: 3-5 days to handle session login, error mapping, and bulk batching. Through Jentic: under 1 hour to the first invoice send.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Stripe handles card-led subscription invoicing where BILL handles ACH-led B2B AR.
Choose Stripe when customers pay primarily by card and need hosted Checkout; choose BILL for ACH-heavy B2B receivables tied to accounting sync.
FAQs
Specific to using AR | Customer transactions API through Jentic.
Why is there no official OpenAPI spec for AR | Customer transactions?
BILL does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AR | Customer transactions via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the BILL main API use?
BILL uses an API key plus session token model. Agents log in once to obtain a session token and pass it with each call alongside the developer key. Through Jentic these credentials sit encrypted in the vault and the agent only ever holds a scoped reference.
Can I create recurring invoices through the BILL main API?
Yes. Call POST /Crud/Create/RecurringInvoice.json with the customer ID, frequency, and line items. POST /Crud/Update/RecurringInvoice.json adjusts an existing schedule and POST /List/RecurringInvoice.json enumerates active schedules.
How do I charge a customer through Jentic?
Search Jentic for 'charge a customer in bill.com'. Jentic returns the ChargeCustomer operation, loads its schema, and your agent calls POST /ChargeCustomer.json with the customer ID and amount, then posts the receipt with POST /RecordARPayment.json.
What rate limits apply to the BILL main API?
BILL applies per-organisation throttling on the v2 API. Specific quotas are not exposed in the spec. For higher throughput use the Bulk/Crud endpoints (for example POST /Bulk/Crud/Create/Invoice.json) rather than looping single creates.
Is the BILL main API free?
API access is bundled with paid BILL plans rather than a separate free tier. You need an active BILL organisation plus a developer key. Jentic does not add usage charges on top of the underlying plan.
GET STARTED