Actions35
- Adjustments Actions
- Assemblies Actions
- Batches Actions
- Companies Actions
- Contacts Actions
- Custom Fields Actions
- File Attachments Actions
- Inventory Actions
- Invoices Actions
- Locations Actions
- Orders Actions
- Packages Actions
- Payment Methods Actions
- Product POS Mappings Actions
- Products Actions
- Purchases Actions
- Strains Actions
- Test Results Actions
- Users Actions
Purchases → Post Payment
AI-generatedOverview
This node operation posts a payment to a specific purchase in the Distru system. It is useful for recording payments made against purchase orders, helping businesses keep track of their financial transactions related to purchases. For example, a user can specify the purchase ID, payment method, amount, payment date, and description to log a payment.
Use Case Examples
- Recording a payment for a purchase order after receiving an invoice.
- Updating the payment status of a purchase with details like payment method and amount.
Properties
| Name | Meaning |
|---|---|
| Resource ID | The unique identifier of the purchase to which the payment is being posted. |
| Payment Method ID | The identifier of the payment method used for the payment. |
| Amount | The amount of money paid towards the purchase. |
| Payment Datetime | The date and time when the payment was made. |
| Description | A description or note about the payment. |
| Additional Fields | Optional extra fields such as Quickbooks deposit account ID and name for integration purposes. |
Output
JSON
json- The response data from the Distru API after posting the payment, typically including details of the payment transaction.
Dependencies
- Requires an API token credential for authenticating with the Distru API.
Troubleshooting
- Ensure the Resource ID (purchase ID) is provided and valid; missing or incorrect IDs will cause errors.
- Verify that the API token credential is set and valid; missing or invalid tokens will prevent API access.
- Check that all required fields (payment method ID, amount, payment datetime, description) are provided; missing required fields will cause the request to fail.
- If using additional fields for Quickbooks integration, ensure the IDs and names are correct to avoid integration issues.