> ## Documentation Index
> Fetch the complete documentation index at: https://agents.nanonets.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Sage Intacct Get Bills

> Reads AP bills from Sage Intacct.

Reads AP bills from Sage Intacct. Display name follows the registry name. Off by default.

Bill numbers can duplicate in Intacct — always send `vendor_id` together with `bill_number` when both are known.

## Authentication and enablement

Requires a workspace Sage Intacct integration. `company_id`, `user_id`, and `user_password` are injected and not shown as a per-run input. Enable the tool and bind the integration.

## Inputs

LLM-visible filters (all optional; combine as needed):

* `bill_number` — RECORDID / invoice number.
* `vendor_id`
* `amount` — typically combined with a date.
* `entity_id` — see Entity scoping below.
* Additional status / posted-date filters as declared on the schema.

## Entity scoping

In a multi-entity company, Sage Intacct decides scope from the entity the API session logs
into, not from the query. Set `entity_id` to the Intacct entity/location ID to read within
that entity; leave it empty to read at the top level with shared visibility.

`entity_id` is not a search criterion — it narrows where the other filters are applied, so
still pass at least one of `bill_number`, `vendor_id`, `amount`, `date`, or `filters`.

Entity IDs are whatever the company named them, not necessarily numbers — a real
multi-entity company may use names like `Charlwell` or `Park Ave`. A wrong or inaccessible
`entity_id` fails at login with an explicit "the entity may not exist or the Web Services
user may lack access to it" error rather than silently falling back to top level.

The same `entity_id` input is available on `sage_intacct_get_payments`,
`sage_intacct_get_po`, `sage_intacct_get_vendor`, `sage_intacct_get_receipts_by_po`,
`sage_intacct_create_bill`, and `sage_intacct_create_bill_by_po`. On the two create tools
it decides which entity the bill is posted into, and line items without an explicit
`location_id` inherit it.

## Output

Matching AP bills (structured).

## Limits and side effects

* Read-only. Does not post or edit bills.
* Duplicate bill numbers without `vendor_id` can return the wrong bill.

## Expected errors

* Integration credentials missing.
* Intacct API error / no match.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.