Organization | Accounts tracking

Name: Organization | Accounts tracking API
Brand: Organization | Accounts tracking
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceAccountingapiKey74 EndpointsREST

For Agents

Manage the chart of accounts, classes, departments, items, jobs, locations, and payment terms used to code BILL transactions to the ledger.

Connect the Organization | Accounts tracking to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Organization | Accounts tracking, 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 Organization | Accounts tracking API.

Create, update, and list chart-of-accounts entries with bulk operations for backfills

Manage accounting classes, departments, locations, and jobs as transaction tracking dimensions

Maintain item and employee records used as line-level references on invoices and bills

Configure payment terms used on customer invoices and vendor bills

GET STARTED

Start building with Organization | Accounts tracking API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Organization | Accounts tracking, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Organization | Accounts tracking, keeping it validated and agent-ready. This BILL surface manages the accounting dimensions an organisation uses to classify every transaction: chart of accounts, accounting classes, departments, employees, items, jobs, locations, and payment terms. Agents create, update, and bulk-load these tracking entities so that invoices, bills, and payments downstream can be coded against the correct ledger, cost centre, and project. Without this layer, AR and AP records cannot be reconciled to the underlying accounting system.

Use Cases

Patterns agents use Organization | Accounts tracking API for, with concrete tasks.

★ Initial chart of accounts setup

Bulk-load an organisation's chart of accounts, classes, departments, and locations from an accounting source of truth into BILL. The API exposes Bulk/Crud/Create endpoints on each tracking entity so an agent can mirror QuickBooks or Xero structures into BILL in one batch instead of clicking through the UI. Useful for onboarding a new BILL organisation or migrating between accounting systems.

Call Bulk/Crud/Create/ChartOfAccount.json with 50 GL account records exported from the source ledger and verify all returned successfully

Cost coding dimension management

Keep BILL's accounting classes, departments, jobs, and locations in sync with the operational hierarchy as the business grows. The API provides full CRUD plus undelete on each dimension so an agent can add a new department, retire an old class, or restore a deleted job without losing audit trail. This keeps line-level coding accurate on every downstream invoice and bill.

Create a new Department record named 'EMEA Sales' and a new Location record named 'Dublin Office', then list both to confirm IDs

Item and payment-term governance

Maintain the item catalog and payment-term records that drive invoice and bill line items. Crud/Create/Item lets an agent register a new product or service, while Crud/Create/PaymentTerm and Crud/Update/PaymentTerm govern net-30, net-45, and custom terms. Useful when finance ops needs to roll out a pricing or terms change without manual UI work.

Update an existing PaymentTerm record from net-30 to net-45 and verify the change persisted via Crud/Read/PaymentTerm

Accounting reconciliation prep

Pull the active tracking lists before exporting a period close. Calling List/ChartOfAccount, List/ActgClass, List/Department, and List/Location gives a finance agent the dimension lookups needed to map BILL transactions back to the GL during reconciliation. This avoids stale dimension references when the books close.

Call List/ChartOfAccount, List/ActgClass, and List/Department, then return the count and IDs of all active records

Agent-driven dimension setup via Jentic

An AI agent uses Jentic to discover BILL tracking operations from intents like 'add a new department' or 'create a GL account'. Jentic returns the matching Crud/Create operation, loads its schema, and executes with credentials from the vault. The agent can stand up a full tracking taxonomy without reading BILL's developer docs.

Search Jentic for 'add a department in bill.com', load the Crud/Create/Department schema, and execute it with name 'Customer Success'

Key Endpoints

74 endpoints — jentic publishes the only available openapi specification for organization | accounts tracking, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/Crud/Create/ChartOfAccount.json

Create a GL account

POST

/Bulk/Crud/Create/ChartOfAccount.json

Bulk create GL accounts

POST

/Crud/Create/Department.json

Create a department

POST

/Crud/Create/ActgClass.json

Create an accounting class

POST

/Crud/Create/Location.json

Create a location

POST

/Crud/Create/Item.json

Create a catalog item

POST

/Crud/Create/Job.json

Create a job for cost coding

POST

/Crud/Create/PaymentTerm.json

Create a payment term

POST

/Crud/Create/ChartOfAccount.json

Create a GL account

POST

/Bulk/Crud/Create/ChartOfAccount.json

Bulk create GL accounts

POST

/Crud/Create/Department.json

Create a department

POST

/Crud/Create/ActgClass.json

Create an accounting class

POST

/Crud/Create/Location.json

Create a location

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

BILL developer keys and session tokens are stored encrypted in the Jentic vault. The agent receives a scoped reference and the raw key never enters the agent context, which matters when bulk-creating GL records on behalf of a finance team.

Intent-based discovery

Agents search intents like 'create a GL account' or 'add a department' and Jentic returns the matching Crud/Create operation with its input schema, so the agent does not need to map BILL's tracking taxonomy by hand.

Time to first call

Direct BILL integration: 2-4 days to model the eight tracking entities and their bulk variants. Through Jentic: under 30 minutes to the first dimension created.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Xero Accounting

Xero exposes the same chart-of-accounts and tracking categories at the ledger level.

Choose Xero when the books live in Xero and BILL is downstream; choose BILL tracking when BILL is the system of record for AP/AR coding.

Complementary

BILL AP Vendor Transactions

Vendor transactions consume the tracking dimensions defined here.

Use vendor-transactions to record bills and pay vendors after the chart-of-accounts and departments are in place.

Complementary

BILL AR Customer Transactions

Customer transactions reference these tracking dimensions on invoices.

Use customer-transactions to issue invoices that are coded against the GL accounts and classes managed here.

FAQs

Specific to using Organization | Accounts tracking API through Jentic.

Why is there no official OpenAPI spec for Organization | Accounts tracking?

BILL does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Organization | Accounts tracking 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 Organization Accounts Tracking API use?

BILL uses an API key plus session token model. Agents authenticate once to obtain a session token and pass it on each request alongside the developer key. Jentic stores both in the encrypted vault and exposes only a scoped reference to the agent.

Can I bulk-load my chart of accounts via this API?

Yes. POST /Bulk/Crud/Create/ChartOfAccount.json accepts a batch of GL account records in one call. The same Bulk/Crud pattern is available for Department, ActgClass, Item, Job, Location, and Employee records to support full chart migrations.

How do I add a department through Jentic?

Search Jentic for 'add a department in bill.com'. Jentic returns the Crud/Create/Department operation, loads its schema, and your agent calls POST /Crud/Create/Department.json with the department name and parent location.

What rate limits apply to the tracking API?

BILL applies per-organisation throttling. Specific quotas are not exposed in the spec, so prefer the Bulk/Crud endpoints (for example POST /Bulk/Crud/Create/Item.json) when loading more than a few records to avoid serial-call throttling.

Is the Organization Accounts Tracking API free?

API access is bundled with paid BILL plans rather than a separate free tier. You need an active BILL organisation and a developer key. Jentic does not add usage charges on top.