Bill AR | Customer transactions
Browse all Bill APIs72
AI ReadinessAI-Aware (A-)72/100
Agent-ready OpenAPI document · curated by JenticFinanceAccountingapiKey40 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Issue customer invoices, run recurring billing, charge authorised customers, and record received payments inside BILL's AR workflow.
Use for: I need to create an invoice for a customer in BILL, I want to set up a recurring invoice that bills weekly, Send an invoice to a customer by email, Charge an authorised customer for an outstanding invoice
Not supported: Does not handle vendor bills, AP payments, or organisation-level user and bank-account management - 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 Accounts Receivable API automates how an organisation invoices and collects payments from its customers. 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. The API also surfaces invoice credits, received payments, processing fees, and an AR summary so agents can reconcile cash-flow positions against accounting records.
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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbill.com%2Fcustomer-transactions" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbill.com%2Fcustomer-transactions" | 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 and update invoices and recurring invoice schedules for individual customers or in bulk batches
Send invoices to customers by email or postal mail and capture customer authorisation for charges
Charge authorised customers and record received AR payments against open invoices
Issue and manage credit memos and look up invoice credits applied to customer balances
Read received payments, processing fees, and an aggregate AR summary for cash-flow reporting
Use Cases
Patterns agents use AR | Customer transactions API for, with concrete tasks.
★ Recurring SaaS invoicing
Generate and send recurring invoices to subscription customers on a fixed schedule and reconcile collected funds back to the accounting ledger. The customer-transactions API provisions RecurringInvoice records, issues each cycle's Invoice via SendInvoice or MailInvoice, and writes the matching ReceivedPay record once the customer pays. A small finance team can run a multi-hundred customer book without manual invoice creation each month.
Create a RecurringInvoice for customer ID 0cu01AAAAA with monthly frequency, $499 USD line item, and email delivery enabled, then verify the next-run date is set
Customer charge and AR reconciliation
Charge authorised customers' stored payment methods and record the resulting funds against the originating invoice. Agents call SetCustomerAuthorization to capture mandate, ChargeCustomer to debit the account, and RecordARPayment to mark the invoice paid. This lets professional services and B2B firms close their AR loop without touching the BILL web UI.
Call ChargeCustomer for invoice ID 00n01AAAAA against the customer's authorised bank account, then call RecordARPayment with the returned transaction reference
Credit memo and dispute handling
Apply credit memos to customer accounts when invoices are disputed, partially refunded, or adjusted. The API exposes Crud/Create/CreditMemo for issuing the memo and Crud/Read/InvoiceCredit plus List/InvoiceCredit so agents can audit which credits have been applied. Useful for AR teams handling chargebacks, returns, or pricing corrections.
Create a CreditMemo for $120.00 against customer ID 0cu01AAAAA referencing invoice 00n01AAAAA, then list InvoiceCredit records to confirm it posted
AR summary reporting for finance agents
Pull the consolidated AR position for a BILL organisation on demand. GetARSummary returns aggregate open balances, aging buckets, and received payment totals so a finance agent can answer cash-flow questions or feed a weekly board pack. Combined with List/ReceivedPay it gives a complete view of inflows over a window without the user opening BILL.
Call GetARSummary for the connected organisation and return total outstanding balance plus current-period received payments
Agent-driven invoice operations via Jentic
An AI agent uses Jentic to discover customer-transaction operations from a natural-language intent like 'send an invoice to a customer'. Jentic returns the matching BILL operation, loads its input schema, and executes the call with credentials held in your Jentic One instance. The agent can chain Create + Send + RecordARPayment without ever handling the BILL session token directly.
Search Jentic for 'send an invoice to a customer', load the SendInvoice schema, and execute it for invoice ID 00n01AAAAA with the customer's email address
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
/MailInvoice.json
Send an invoice by postal mail
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
/MailInvoice.json
Send an invoice by postal mail
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
AR | Customer transactions
- AI-Aware (A-)72/100
99
Foundational Compliance56
Developer Experience & Jentic Compatibility57
AI-Readiness & Agent Experience94
Agent Usability100
Security67
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
99
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
96%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
57
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
77%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
67
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: B+Signals: 1
67%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the BILL customer-transactions API by hand means logging in for a session id, pairing it with your developer key on every RPC-style POST, and shaping each invoice and payment body yourself. Through Jentic you install once, import BILL customer-transactions from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
This API carries the invoice and customer ids in the request body of RPC-style operations rather than the URL path, so limit the agent to the operations it needs, such as creating or sending a customer invoice. You choose that set, so charging a customer or recording a payment is not reachable unless you include them.
Credential isolation
Your BILL developer key and session token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a customer invoice in BILL' or 'record an AR payment', and Jentic returns the matching customer-transactions operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Stripe handles card-based subscription invoicing where BILL handles ACH-led B2B AR.
Choose Stripe when the customer base pays primarily by card and needs Stripe Checkout or hosted invoices; choose BILL for ACH-heavy B2B receivables with 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 with Jentic One, the self-hosted execution layer.
What authentication does the AR | Customer transactions API use?
BILL uses an API key plus session token model. Agents authenticate to bill.com once and pass the session token with each request alongside the developer key. Through Jentic these credentials are held encrypted in the vault, so the agent receives a scoped handle and never sees the raw key.
Can I create a recurring invoice with this API?
Yes. Call POST /Crud/Create/RecurringInvoice.json with the customer ID, frequency, and line items. Use POST /Crud/Update/RecurringInvoice.json to change a schedule, and POST /List/RecurringInvoice.json to enumerate active schedules for an organisation.
How do I charge an authorised 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. Follow with POST /RecordARPayment.json to post the receipt against the invoice.
What rate limits apply to the AR | Customer transactions API?
BILL applies per-organisation throttling on its v2 API. Specific quotas are not exposed in the spec; in practice agents should batch via the Bulk/Crud endpoints (for example POST /Bulk/Crud/Create/Invoice.json) when issuing more than a handful of records to stay within limits.
Is the BILL AR API free to use?
BILL bundles API access with paid plans rather than offering a separate free tier. You need an active BILL organisation and a developer key. Jentic does not add usage charges on top of the underlying BILL plan.
Can I limit what my agent is allowed to do with the BILL Customer Transactions API?
Yes. Because Jentic One is self-hosted, you decide which of the RPC-style operations your agent may call, so you can allow it to create or send a customer invoice while leaving charging a customer or recording an AR payment out of reach. Since these operations carry the invoice and customer ids in the request body rather than the URL path, the agent can only act on the operations you have granted. Your BILL developer key and session token stay with your own instance and are injected at execution time, so the agent works inside the boundary you set.
GET STARTED