---
title: "Get Gl Capitalization Rescan Status"
method: GET
path: "/companies/{company_id}/gl/capitalization-rescan"
tags: ["gl-fixed-assets"]
---

# Get Gl Capitalization Rescan Status

`GET /companies/{company_id}/gl/capitalization-rescan`

## Request

- Base URL: `https://app.zeno-works.ch` (the document declares no server; this is the origin it was published from)
- URL: `https://app.zeno-works.ch/companies/{company_id}/gl/capitalization-rescan`
- Auth: none declared

What a retroactive capital-good rescan would touch — member read.

Counts the analyzed items whose cached extraction predates the
`extract.invoice@1.11.0` capital-good signal (`pre_signal`), the re-analyses
already in flight, and the re-analyzed coded invoices ready for the
deterministic evaluate pass. `skipped_no_document` is different in kind:
capitalization detection only evaluates entries coded from an ingested
document (the capital-good signal is doculyse's extraction), so this counts
the posted journal entries authored directly — over the journal-entry
API/MCP tools or the AI accountant's chat — that carry no coded document and
are permanently out of scope. It is a standing count, not a backlog:
rescanning never reduces it. To have a purchase evaluated, ingest it as a
document (`upload_document`) and let the pipeline code it, then rescan.

`skipped_no_signal` is the second standing count (ZET-269): analyzed items
whose extraction answered *nothing* — the tri-state key is present but null,
which reads as "looked, unsure". Those are neither queueable (the key is
there, so they are not `pre_signal`) nor evaluable (the signal is not
positive), so no phase touches them. A nonzero value beside zeros everywhere
else means the capital-good question was never answered for those documents —
re-analyse them (`POST /items/{id}/analyze`) rather than rescanning.

## Path parameters

- `company_id` string, required

## Headers

- `authorization` string, nullable

## Cookies

- `access_token` string, nullable

## Response `200`

Successful Response

- CapitalizationRescanStatusOut: ``GET …/gl/capitalization-rescan`` — what a rescan run would touch.
  - `pre_signal` integer
  - `in_flight` integer
  - `ready_to_evaluate` integer
  - `skipped_no_document` integer
  - `skipped_no_signal` integer

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/zeno-works/apis/zeno-api.md) · [All operations](https://skmtc.dev/zeno-works/apis/zeno-api/llms.txt) · [OpenAPI document](https://skmtc.dev/zeno-works/apis/zeno-api/revisions/1eb93dde146c?raw)