On this page
createReceipt
mutation · in the family Inventory operations
What it does
Create a new goods receipt — stock arriving from a purchase order at your organization.
CREATE a Receipt: the parent PO RECEIVABLE (issued/acknowledged/partially_received); the receiving LF tenant-scoped + ACTIVE + named by ≥1 PO line; every line addresses a PO line destined to THIS LF (one line per PO-line × disposition; a hold is reason-coded — the law, strict both ways); estimate components ≤8 in the PO currency; up to 90 lines per call (a receipt holds up to 1000 — add more with addReceiptLines).
Who may call it
Capability area: Inventory operations — Receiving, counting, transferring and moving stock.
- Owner
- Manager
- Associate Manager
- Warehouse Associate
- An API key whose scope allows
api:createReceipt
Arguments
| Name | Type | Required | Notes |
|---|---|---|---|
input | CreateReceiptInput CreateReceiptInput! | yes | No further notes. |
Returns
Receipt Receipt! — Over-receipt refuses CONFLICT/THREE_WAY_MATCH (the PO declared receive.match_flag form; tolerance ZERO until); under-receipt is partial, first-class — the next receipt is a NEW doc. posted is the immutable NON-doomed fact (corrections are compensating movements, never edits); cancelled is the doomed terminal (lists filter it). Re-running post RESUMES a stalled walk; on a healthy in-flight receipt it refuses CONFLICT/IN_PROGRESS naming the progress; one receipt posts against a purchase order at a time (its receivingReceiptId).
Example request
mutation ExampleCreateReceipt($input: CreateReceiptInput!) {
createReceipt(input: $input) {
id
sysId
type
caption
status
parentId
rootId
createdAt
updatedAt
revisionNum
revision
logicalFacilityId
organizationId
lineCount
nextLineNo
}
}
Variables:
{
"input": {
"caption": "Blue jeans",
"purchaseOrderId": "01900000-0000-7000-8000-54a5b8570000",
"logicalFacilityId": "01900000-0000-7000-8000-8026f71c0000",
"lines": [
{
"poLineNo": 1,
"quantityReceived": "<quantity received>",
"disposition": "accept"
}
]
}
}
Send it with the envelope naming the version: "extensions": {"at": {"version": {"name":"genesis","number":0}}}.
Example response
{
"data": {
"createReceipt": {
"id": "01900000-0000-7000-8000-37386ae00000",
"sysId": "RC-EXMP-0000-000F",
"type": "Receipt",
"caption": "Blue jeans",
"status": "draft",
"parentId": "01900000-0000-7000-8000-065235280000",
"rootId": "01900000-0000-7000-8000-a093dd800000",
"createdAt": "2027-01-31T00:00:00.000Z",
"updatedAt": "2027-01-31T00:00:00.000Z",
"revisionNum": 1,
"revision": "01900000-0000-7000-8000-b7960e180000",
"logicalFacilityId": "01900000-0000-7000-8000-8026f71c0000",
"organizationId": "01900000-0000-7000-8000-44b781470000",
"lineCount": 1,
"nextLineNo": 1
}
},
"extensions": {
"at": {
"callId": "01EXAMPLE-CALL-ID",
"version": {
"requested": {
"name": "genesis",
"number": 0
},
"serviced": {
"name": "genesis",
"number": 0
}
}
}
}
}
Errors this call can answer
VALIDATION/INVALID— Something in the request is not valid. (VALIDATION)AUTHN/REQUIRED— Sign in to do this. (AUTHN)AUTHZ/FORBIDDEN— Your role does not allow this action. (AUTHZ)RATE_LIMIT/THROTTLED— Too many requests in a short time. (RATE_LIMIT)NOT_FOUND/*— That record could not be found. (NOT_FOUND)CONFLICT/*— The record’s state, or a change made in the meantime, does not allow this; the codes are on the CONFLICT page. (CONFLICT)VALIDATION/VERSION_REQUIRED— The request did not say which app version it came from. (VALIDATION)