Update Invoice record (partial)
Changed onChange only the fields you send. Other fields stay as they are. Period locks, payments, and approval rules match the full update.
A posted invoice writes general ledger entries. Those entries debit accounts receivable and credit income or a deferral account. Tax and discounts write their own entries. A draft does not post those entries.
When you send contract_id or sales_order_id, DualEntry links that contract or sales order.
The tax on each line stays as you send it. Set auto_calculate_tax to required and DualEntry calculates the tax and replaces it before saving the invoice.
The calculation covers native US sales tax using DualEntry's tax engine. It also covers Avalara US sales tax, VAT, and GST. If the result is DualEntry's own VAT or GST, the request fails with 422. A calculation that cannot finish also fails with 422.
DualEntry reads shipping_address, then billing_address, then the address saved on the customer. If you send neither address, DualEntry copies the customer's saved address to billing_address and shipping_address.
To email the invoice, call the send endpoint.
Side effects
- If an approval workflow matches this request, DualEntry can set record_status back to draft.
- If this request posts the invoice and the company files e-invoices in its country, DualEntry checks the e-invoice with the authority and queues the filing. The check can take up to 10 seconds.
Additional validations
- Fails with 422 if the e-invoice filing of the invoice runs or the authority cleared it. An archive gets the same answer. The e_invoicing key holds the reason. Correct a cleared invoice with a customer credit.
- Fails with 422 if the e-invoice of the posted record has data that the authority refuses. The e_invoicing key lists the reasons.
Request
- Base URL: https://api.dualentry.com
- URL: https://api.dualentry.com/public/v2/invoices/{record_number}/
- Auth: none declared
Path parameters
The number attribute of the record.
Headers
Optional. A unique value (a UUID works well) identifying this operation. If the request is repeated with the same key, the original response is replayed instead of the operation running again, so a retry cannot create a duplicate record. Results are replayable for 48 hours. Reusing a key with a different request body returns 422.
Request body
Response
OK
Changes
- info
added the optional property
/////to the response with the status
- info
- warning
added the new
kintsugienum value to the/////response property for the response status - warning
added the new
kintsugienum value to the/////response property for the response status - info
added the new optional request property
- info
added the optional property
to the response with the status
- warning