> ## Documentation Index
> Fetch the complete documentation index at: https://support.stuut.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Bill.com

> How Stuut integrates with Bill.com — connection setup, data scope, and sync behavior.

This guide outlines how Stuut integrates with Bill.com, including what's required to connect and how data is synced. The integration provides visibility into key financial workflows using a **read-only** data flow.

|                        |                                           |
| ---------------------- | ----------------------------------------- |
| **Integration method** | Bill.com Connect API (v3)                 |
| **Data cadence**       | Recurring scheduled sync (hourly polling) |
| **Write-back**         | None — read-only                          |

## Part 1: Onboarding & setup

To connect your Bill.com account, retrieve the following from your Bill.com dashboard under **Settings → Sync & Integrations → Tokens**. Stuut uses these to establish a secure session:

1. **Token Name** — AP/AR sync token name
2. **Token Value** — AP/AR sync token secret (masked in Stuut after entry)
3. **Organization ID** — your Bill.com internal organization identifier

### Ownership & responsibilities

| Task               | Owner    | Notes                                               |
| ------------------ | -------- | --------------------------------------------------- |
| Token generation   | Customer | Retrieve name, value, and Org ID from Bill.com      |
| Initial connection | Customer | Enter credentials into the Stuut settings page      |
| Sync verification  | Joint    | Confirm first data payload matches Bill.com records |

### Sync mechanics

Data is synced sequentially to maintain referential integrity. Stuut continuously checks for updates, but only incremental changes are processed after the initial full sync.

<Note>
  **Read-only integration.** Stuut does not write data back to Bill.com. Sync runs automatically on a scheduled basis, and no webhook setup is required.
</Note>

## Part 2: Technical specification

This section describes the specific data points Stuut syncs from Bill.com to power visibility and outreach workflows.

### Data scope

| Object       | Synced data elements                                 |
| ------------ | ---------------------------------------------------- |
| Customers    | Name, contact details, billing address               |
| Invoices     | Amounts, status (open, paid, void), line items, PDFs |
| Credit Memos | Applied/unapplied amounts, status (open or applied)  |
| Payments     | Payment amounts, dates, allocations to invoices      |

### Sync order

Stuut follows a deterministic sync order to handle data dependencies correctly:

1. **Customers** — identity and billing addresses
2. **Invoices** — header and line-item mappings, plus invoice PDFs
3. **Credit Memos** — applied vs. unapplied capture
4. **Payments** — allocation by invoice ID

### Troubleshooting checklist

If data is missing or out of sync, verify the following before contacting support:

* **Connection issues:** re-check your token name, value, and Organization ID in Bill.com Settings
* **Missing data:** ensure the records exist and are up to date within the Bill.com platform itself
* **Delayed updates:** the sync runs periodically (hourly polling), so expect a short delay between system updates

### Next steps

Once the connection is established, Stuut begins syncing data automatically. You can immediately start using the synced data for visibility, workflows, and financial reporting.

Questions? Contact [support@stuut.co](mailto:support@stuut.co).