# Invoicing & receivables

Keep your billing product and your customer’s receivables in step.

For vertical SaaS, billing, and revenue operations teams.

[API endpoints](https://developers.apideck.com/apis/accounting/reference?useCase=accounts-receivable) · [Build this workflow](https://developers.apideck.com/guides/accounts-receivable-automation)

## What you can build

Create customers and invoices, allocate payments, and read back outstanding balances.

Workflow: Resolve the customer → Create the invoice → Allocate payments

## Where your product takes over

Accounting payment records do not collect funds. Your billing and payment systems own charging, settlement, and dunning policies.

## From connection to a working integration

### 1. Establish customer identity

Connect the accounting company through Vault, then match or create a customer using a stable mapping scoped to that connection.

[Explore this step](https://developers.apideck.com/guides/vault)

### 2. Create consistent invoices

Resolve ledger and tax references before writing invoice lines. Keep the downstream invoice ID and check the returned currency and totals.

[Explore this step](https://developers.apideck.com/guides/accounts-receivable-automation)

### 3. Reconcile outstanding balances

Record supported payment allocations and read back the invoice. Account for partial payments and credit adjustments in your reconciliation process.

[Explore this step](https://developers.apideck.com/apis/accounting/reference?useCase=accounts-receivable)

## The API behind the workflow

Support, fields, and permissions vary by connector. Verify operation coverage and setup before implementation.

- [Customers](https://developers.apideck.com/apis/accounting/reference/customers?useCase=accounts-receivable)
- [Invoices](https://developers.apideck.com/apis/accounting/reference/invoices?useCase=accounts-receivable)
- [Payments](https://developers.apideck.com/apis/accounting/reference/payments?useCase=accounts-receivable)

[Select a connector and plan implementation](https://developers.apideck.com/integration-plan?useCase=accounts-receivable)

## Know when it works

- Customer IDs never leak across tenants or accounting companies.
- Invoice line totals, taxes, and currency agree with the source billing record.
- Partial payments and credits produce the expected outstanding balance.

## Start building

- [Implementation guide](https://developers.apideck.com/guides/accounts-receivable-automation)
- [API endpoints](https://developers.apideck.com/apis/accounting/reference?useCase=accounts-receivable)
- [Workflow context for your agent](https://developers.apideck.com/api/context/accounting/accounts-receivable.md)
- [Explore the demo](https://vertical-saas.apideck.dev/)

The demo illustrates a product flow. Its data and connection setup depend on the demo; verify your target connector before implementation.