---
title: "Whether QuickBooks invoices and bills can post for a customer (#2642)"
method: GET
path: "/accountant/companies/{customerId}/integrations/quickbooks/arap-enablement"
tags: ["Accountants"]
---

# Whether QuickBooks invoices and bills can post for a customer (#2642)

`GET /accountant/companies/{customerId}/integrations/quickbooks/arap-enablement`

## Request

- Base URL: `https://api.medianfi.com/api/v1`
- URL: `https://api.medianfi.com/api/v1/accountant/companies/{customerId}/integrations/quickbooks/arap-enablement`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Invoices, bills, customer and bill payments, credit memos and vendor credits post through the AR/AP items subledger, which is off until the company's subledger conversion has run and passed its integrity check. Read-only.

## Response `200`

Enablement status

- object
  - `success` true, required
  - `data` QuickBooksArApEnablementStatus, required
    - `state` 'off' | 'dual_read' | 'single_write' | 'rolled_back', required: The company's subledger conversion state
    - `arApItemsEnabled` boolean, required: True when invoices and bills can post
    - `converted` boolean, required: A conversion run completed in the current cycle
    - `validated` boolean, required: That run passed INV-1..9 and is stamped
    - `quickBooksConnected` boolean, required
    - `canEnable` boolean, required
    - `reason` string, nullable, required: Why canEnable is false

## Other responses

- `401`: Authentication required
- `403`: Insufficient permissions or not a company member

---

[API](https://skmtc.dev/medianfi/apis/median-api.md) · [All operations](https://skmtc.dev/medianfi/apis/median-api/llms.txt) · [OpenAPI document](https://skmtc.dev/medianfi/apis/median-api/revisions/20090ea32b0d?raw)