Debit Notes
Section: Purchase Management
URL:/admin/purchase/debit_notes
Page title: (2) Corecții
Overview
Debit notes (corrections) adjust a previously received vendor invoice for missing items, returns, or pricing errors.
Business value
Adjusts a previously received vendor invoice — for missing items, returns, or pricing errors. Keeps AP accurate without forcing the vendor to re-issue documents.
- Who uses it: Procurement, accounts payable, finance
- Key benefit: Resolves vendor disputes cleanly and recovers cash on shorts and over-charges.
Typical use cases:
- Short-shipment debit note
- Pricing-correction debit note after audit
At a glance
Accessing this module
From the admin sidebar, navigate to Debit Notes, or open the URL directly:
/admin/purchase/debit_notes
List view
The list view shows existing debit notes records. Use it to search, filter, sort, and bulk-act on items.
Common actions
- View existing records — open Debit Notes from the sidebar to see the list view.
- Search and filter — use the search box and column filters to find records.
- Create a new record — click the Add / New button (or follow the "Create" URL above) and fill in the required fields.
- Edit a record — click a row to open the detail view, then use the edit action.
- Delete a record — use the row's delete action; deletion may be soft or hard depending on the module.
- Bulk operations — select multiple rows via the checkboxes and apply a bulk action from the toolbar (export, delete, status change, etc., where supported).
Create a debit note directly from the original vendor invoice — open the invoice and use the Create Debit Note action. This pre-fills vendor, currency, and line items so you only need to adjust the quantity or price being disputed.
A debit note adjusts the accounts-payable balance only — it does not affect stock levels. If goods were physically returned, raise a Purchase Return in Warehouse first, then issue the debit note for the financial adjustment.
API
This module is available via the REST API.
Authentication. All API requests require the header authtoken: <token> (generate one at /admin/api/api_management).
Base URL. https://your-domain.tld/api/
Key endpoints:
| Method | Path | Purpose |
|---|---|---|
GET |
{{base_url}}purchase/items?page=1&per_page=50 |
List |
GET |
{{base_url}}purchase/items/{{purchase_record_id}} |
Get one |
GET |
{{base_url}}purchase/items/search/{{search_key}} |
Search |
POST |
{{base_url}}purchase/items |
Create |
PUT |
{{base_url}}purchase/items/{{purchase_record_id}} |
Update |
DELETE |
{{base_url}}purchase/items/{{purchase_record_id}} |
Delete |
GET |
{{base_url}}purchase/vendors?page=1&per_page=50 |
List |
GET |
{{base_url}}purchase/vendors/{{purchase_record_id}} |
Get one |
GET |
{{base_url}}purchase/vendors/search/{{search_key}} |
Search |
POST |
{{base_url}}purchase/vendors |
Create |
PUT |
{{base_url}}purchase/vendors/{{purchase_record_id}} |
Update |
DELETE |
{{base_url}}purchase/vendors/{{purchase_record_id}} |
Delete |
GET |
{{base_url}}purchase/vendor_items?page=1&per_page=50 |
List |
GET |
{{base_url}}purchase/vendor_items/{{purchase_record_id}} |
Get one |
POST |
{{base_url}}purchase/vendor_items |
Create |
PUT |
{{base_url}}purchase/vendor_items/{{purchase_record_id}} |
Update |
DELETE |
{{base_url}}purchase/vendor_items/{{purchase_record_id}} |
Delete |
GET |
{{base_url}}purchase/purchase_request?page=1&per_page=50 |
List |
GET |
{{base_url}}purchase/purchase_request/{{purchase_record_id}} |
Get one |
POST |
{{base_url}}purchase/purchase_request |
Create |
See the full payload schemas, query parameters, and example responses in the API reference (`Purchase`).
Captured: 2026-05-10T09:51:26.776Z · Source: demo.crmconnect.io/admin/purchase/debit_notes