AR | Customer transactions

Name: AR | Customer transactions API
Brand: AR | Customer transactions
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingapiKey40 EndpointsREST

For Agents

Issue customer invoices, run recurring billing, charge authorised customers, and record received payments inside BILL's AR workflow.

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.

Install Jentic One Beta (Self-Hosted)

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 | sh

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 instance

Jentic 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

GET STARTED

Start building with AR | Customer transactions API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for AR | Customer transactions, keeping it validated and agent-ready.

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.

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 the Jentic vault. 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

Why though 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 agent context cannot replay AR charges.

Intent-based discovery

Agents search Jentic with intents like 'create a customer invoice in BILL' and Jentic returns the matching customer-transactions 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 for the first invoice send.

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.

Complementary

Xero Accounting

Xero is the accounting ledger BILL invoices typically sync to.

Use Xero when you need to post journal entries or reconcile bank feeds after BILL has issued the invoice and recorded the payment.

Alternative

Recurly

Recurly is a dedicated subscription billing engine.

Choose Recurly when you need dunning, plan changes, and revenue recognition for a SaaS subscription book; choose BILL when AR sits inside a broader AP/AR/accounting workflow.

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 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.