Undo Receiving Discrepancy
POST/api/purchase-orders/:purchase_order/receiving-discrepancy/undo
Reverse a previous "close with receiving discrepancy" on a purchase order. No request body.
purchase-orders:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
What it does (all in one transaction, synchronous):
- deletes the discrepancy accounting entry and its lines
- reopens the purchase order (
order_status: open) and recomputes its receipt status from actual received quantities (it may land onpartially_received,unreceived, or auto-close again asreceivedif everything was in fact received)
Errors:
- 404 — the purchase order has no receiving discrepancy to undo
- 400 — the discrepancy has already been posted to your accounting provider; it cannot be undone and a reversing entry must be made manually
Requires the purchase-orders:write token scope and receiving permission on purchase orders.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Bad Request
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.
Not Found
Response Headers
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.