> ## Documentation Index > Fetch the complete documentation index at: https://docs.erp.arukz.com/llms.txt > Use this file to discover all available pages before exploring further. # Update receipt > Update an existing receipt Also accepts `PATCH` with the same body. ## OpenAPI ````yaml /api-reference/openapi.json put /admin/api/v1/inventories/receipts/{id} openapi: 3.0.3 info: title: ARUKZ ERP API version: v1 description: >- The REST API of ARUKZ ERP: sales, purchases, inventory, products, partners, accounts, projects and reference data. Every call acts as the user whose token it carries and sees only that user's company. servers: - url: https://erp.arukz.com description: ARUKZ ERP (hosted) security: - bearerAuth: [] tags: - name: Authentication description: Sign in for a token and sign out. - name: Sales description: Quotations, sales orders and their lines, deliveries and invoices. - name: Purchases description: Purchase orders, receipts, bills, agreements and vendor price lists. - name: Inventory description: >- Warehouses, locations, lots, stock quantities, receipts, deliveries, transfers and scrap. - name: Products description: 'The product catalogue: categories, attributes, variants and packaging.' - name: Partners description: Customers, vendors, contacts, addresses and bank accounts. - name: Accounts description: >- Invoices, bills, credit notes, refunds, taxes, journals and the chart of accounts. - name: Projects description: Projects, tasks, stages and milestones. - name: Reference data description: Currencies and rates, banks, countries, states and units of measure. paths: /admin/api/v1/inventories/receipts/{id}: put: tags: - Inventory summary: Update receipt description: |- Update an existing receipt Also accepts `PATCH` with the same body. operationId: inventory-receipts-update-receipt parameters: - name: id in: path required: true schema: type: integer description: The receipt ID example: 1 description: The receipt ID requestBody: required: false content: application/json: schema: type: object properties: partner_id: type: integer description: >- Partner ID (receive from, contact, or delivery address based on operation type). The `id` of an existing record in the partners_partners table. nullable: true example: 1 operation_type_id: type: integer description: >- Operation type ID. If omitted, the API resolves the default operation type for the resource. The `id` of an existing record in the inventories_operation_types table. nullable: true example: 1 source_location_id: type: integer description: >- Source location ID. The `id` of an existing record in the inventories_locations table. nullable: true example: 1 destination_location_id: type: integer description: >- Destination location ID. The `id` of an existing record in the inventories_locations table. nullable: true example: 2 user_id: type: integer description: >- Responsible user ID. The `id` of an existing record in the users table. nullable: true example: 1 move_type: type: string description: Shipping policy. enum: - direct - one nullable: true example: direct scheduled_at: type: string description: Scheduled datetime. Must be a valid date. nullable: true example: '2026-02-25 10:00:00' origin: type: string description: >- Source document reference. Must not be greater than 255 characters. nullable: true example: SO/00001 description: type: string description: Operation note. nullable: true example: Handle with care. moves: type: array items: type: object properties: id: type: integer description: >- The `id` of an existing record in the inventories_moves table. nullable: true example: 16 product_id: type: integer description: >- The `id` of an existing record in the products_products table. example: 16 product_uom_qty: type: number description: >- Must be at least 0. Must not be greater than 99999999999. example: 22 uom_id: type: integer description: >- The `id` of an existing record in the unit_of_measures table. nullable: true example: 16 final_location_id: type: integer description: >- The `id` of an existing record in the inventories_locations table. nullable: true example: 16 description_picking: type: string description: Must not be greater than 255 characters. nullable: true example: 'n' scheduled_at: type: string description: Must be a valid date. nullable: true example: '2026-03-03T04:25:42' deadline: type: string description: Must be a valid date. nullable: true example: '2026-03-03T04:25:42' product_packaging_id: type: integer description: >- The `id` of an existing record in the products_packagings table. nullable: true example: 16 quantity: type: number description: >- Must be at least 0. Must not be greater than 99999999999. nullable: true example: 22 is_picked: type: boolean nullable: true example: false description: Optional operation moves payload. nullable: true example: - product_id: 1 product_uom_qty: 5 uom_id: 1 quantity: 0 is_picked: false responses: '200': description: Success content: application/json: example: data: id: 1 name: WH/INT/1 origin: null move_type: direct state: draft is_favorite: false description: null has_deadline_issue: false is_printed: false is_locked: false deadline: null scheduled_at: '2025-04-10T12:10:18.000000Z' closed_at: null created_at: '2025-04-10T12:11:32.000000Z' updated_at: '2025-04-10T12:11:32.000000Z' message: Receipt updated successfully. '401': description: Unauthenticated content: application/json: example: message: Unauthenticated. '404': description: Receipt not found '422': description: Validation error content: application/json: example: message: The given data was invalid. errors: moves.0.product_id: - The moves.0.product id field is required. components: securitySchemes: bearerAuth: type: http scheme: bearer description: >- An API token from [Sign in](/api-reference/authentication), sent as `Authorization: Bearer `. Tokens last 30 days. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.