---
title: "Read companies reports general ledger entries"
method: GET
path: "/accountant/companies/{customerId}/reports/general-ledger/{glAccountId}/entries"
tags: ["Accountant Portal"]
---

# Read companies reports general ledger entries

`GET /accountant/companies/{customerId}/reports/general-ledger/{glAccountId}/entries`

## Request

- Base URL: `https://api.medianfi.com/api/v1`
- URL: `https://api.medianfi.com/api/v1/accountant/companies/{customerId}/reports/general-ledger/{glAccountId}/entries`
- Auth: one of:
  - HTTP bearer
  - API key in header `X-API-Key`

Generated minimal contract (#1940): parameters, auth, and status codes are authoritative; see the route handler for the exact body/response shape. Enrichment tracked by the x-median-spec-stage marker.

## Query parameters

- `basis` 'accrual' | 'cash'

## Response `200`

Success envelope; see the route handler for the payload shape

- object
  - `data` object
    - `items` object[]
      - `cashBasisSource` CashBasisLineProvenance: Present on a drill-down row of a cash-basis read when the row is a receivable or payable settlement moved onto the income or expense accounts of the invoice or bill it settles. The row keeps the settlement's own date and amount; this names where it came from.
        - `originEntryId` string, required: The invoice or bill entry.
        - `originEntryDate` string, date, required
        - `controlAccountId` string, required: The receivable or payable account the settlement line was posted to.
        - `cumulativeSettledCents` integer, required: Settled on the item up to and including this settlement, in ledger cents.
        - `itemTotalCents` integer, required: The invoice's or bill's receivable or payable total, in ledger cents.
    - `ledgerRevision` string, nullable: Opaque token of the posted ledger state the report was read under (#1166). It changes whenever any journal entry or line of the company (with `entityId`, of that entity and of entries with no entity) is inserted, updated, voided or deleted, backdated or not. Two reads with equal tokens saw the same ledger. Null when the ledger moved on both attempts of the read, so a client combining pages or statements must treat the result as unproven and retry. Not a credential; not ordered.

## Other responses

- `401`: Authentication required
- `403`: Insufficient permissions or not a company member
- `404`: Resource not found
- `422`: `basis` is not `accrual` or `cash` (a validation error naming the field), or `basis=cash` was asked and the cash-basis view cannot be produced for this request (`CASH_BASIS_UNAVAILABLE`, with the reasons at `error.extensions.cashBasis`). No rows are returned in either case. Other business-rule refusals of the read use the same envelope.

---

[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)