GEP SMART allows vendors to post Credit Memos manually and through Integrations. The memos received by buyers (email/paper) in ERP and from scanning solutions can be posted to GEP SMART for further processing and reporting. The Credit Memo API can be used to post Memos from ERP/scanning solutions to GEP SMART and retrieve Memos from GEP SMART to ERP. The Acknowledgment API allows capturing the ERP processing status in GEP SMART, which is to be displayed to the user along with comments, in case of failures.
Credit Memo
Overview
Actions
| Verb | URL format | Action | Description | |
|---|---|---|---|---|
| POST | api/Invoice/CreditMemoStatusBatch | Create | Create Credit Memo Status | Details |
| POST | api/CreditMemo/SaveCreditMemo | Create | Create Credit Memo details | Details |
| GET | api/CreditMemo/GetCreditMemo | Read | Get Credit Memo details | Details |
| GET | api/CreditMemo/AttachmentByCreditMemoNumber | Read | Get Attachment by Credit Memo Number | Details |
| PUT | api/CreditMemo/CreditMemoStatus | Update | Update processed Credit Memo status | Details |
Authentication
Please refer our user authentication section for more details: Authentication
Response Codes
| Status Code | Status | Description |
|---|---|---|
| 200 | OK | The request was successful. |
| 400 | Bad Request | The request could not be understood or was missing required parameters. |
| 401 | Unauthorized | Authentication failed, or user doesn't have permissions for requested operation. |
| 404 | Not Found | Resource was not found. |
| 415 | Unsupported Media Type | API is not able to process the client's supplied media type, as indicated by the Content-Type request header. |
| 500 | Internal Server Error | The server encountered an unexpected condition which prevented it from fulfilling the request. |