Get GINR Balance
GET/api/reporting/ginr/balance
GINR (Goods Invoiced, Not Received) — also called Accrued Purchases or GRNI — tracks the value of goods that suppliers have invoiced but that have not yet been received into inventory. The balance is calculated as: invoiced − received + discrepancies − adjustments, accumulated from the account's inventory start date (so it behaves like a balance-sheet figure, not a period movement).
reports:readGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Returns the single cumulative GINR balance as of an arbitrary date, broken into its four components (invoiced, received, discrepancy, adjustments) plus the resulting unreceived balance. Figures are computed live from purchasing and receiving records at request time.
Authentication: Requires Bearer token. Scope: reports (read/write).
Ledger tie-out: the response also states whether this figure agrees with the books. ledger_accounts lists the purchase clearing account(s) the report is compared against, as "<code> <name>" labels: Accrued Purchases, plus Goods Received Not Invoiced when that account is mapped (when it is not, receipts and supplier invoices net in Accrued Purchases alone). ledger_balance is the net debit balance of those accounts in SKU.io's ledger as of the same date, in the report's own sign (positive = invoiced ahead of receipts, negative = received ahead of invoices). ledger_difference is unreceived minus ledger_balance; a non-zero difference is clearing-account activity that belongs to no purchase order line (for example a landed-cost bill still awaiting its revaluation, or a manual journal). When no clearing account is mapped, ledger_accounts is an empty array and ledger_balance and ledger_difference are null.
adjustments includes purchase-price true-ups: when a supplier invoice is priced differently from the receipt it covers, the resulting inventory revaluation's posting to the clearing account is counted here, so a purchase order that has already been trued up no longer shows as open.
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.