---
title: "Reconcile the direct method (treasury forecast) against the indirect method (derived from the GL), cell by cell over spine x entity x period"
method: POST
path: "/api/v1/explain_gap"
---

# Reconcile the direct method (treasury forecast) against the indirect method (derived from the GL), cell by cell over spine x entity x period

`POST /api/v1/explain_gap`

## Request

- Base URL: `https://k-phi.com` (the document declares no server; this is the origin it was published from)
- URL: `https://k-phi.com/api/v1/explain_gap`
- Auth: HTTP bearer

Reconcile the direct method (treasury forecast) against the indirect method (derived from the GL), cell by cell over spine x entity x period. This is the thing no ERP or TMS can produce, because neither holds both methods in one grid. It REFUSES to answer when the inputs are not comparable — mixed FX bases, more than one GL version, or only one method present — because a reconciliation whose number cannot be trusted is worse than none. Provable layers are peeled deterministically; narrate only the residual.

## Request body

- object
  - `tolerance` number: Absolute amount within which a cell is considered to tie. Default 1.
  - `layers` object: Optional spine -> layer name map. An explained difference becomes a named layer instead of counting as a failure to reconcile.

## Response `200`

OK

- object
  - `data` object
  - `meta` object
    - `api` string
    - `capability` string
    - `at` string

## Other responses

- `401`: No or invalid credential
- `403`: Scope, extension or Builder Mode refused
- `422`: The capability refused the input
- `429`: Rate or daily quota reached

---

[API](https://skmtc.dev/k-phi/apis/k-api.md) · [All operations](https://skmtc.dev/k-phi/apis/k-api/llms.txt) · [OpenAPI document](https://skmtc.dev/k-phi/apis/k-api/revisions/60b28690ec35?raw)