Acumatica – Gotchas
The latest enterprise resource planning solution release from Acumatica is designed to help customers like you innovate. Get the full story in this Mint Jutras report.
5 gotchas across 3 resources
These are connector-specific behaviors and limitations to be aware of when integrating.
Invoice Items2 gotchas
invoiceItemsAllThe Apideck service type is used for Acumatica non-stock items, and inventory is used for stock items.
invoiceItemsAddFor `sales_details.tax_rate.id`, you must provide the Tax Category ID from the Acumatica not from our tax rates resource.
Invoices1 gotcha
invoicesAddWhen filling line items, you can either link an existing item by providing the item code or create a new item by filling in the item details. Using both options at the same time is not supported.
Journal Entries2 gotchas
journalEntriesAddAcumatica requires a separate Release action to transition a journal entry from Balanced to Posted. When `status: "posted"` is sent, Unify automatically calls the ReleaseJournalTransaction action after creating or updating the entry. Only `status: "posted"` is supported for state transitions. Other values (`draft`, `voided`, etc.) are not supported — the entry will be created or updated but will remain in Balanced state. Once a journal entry is Posted, it cannot be edited. Any attempt to update a Posted entry will be rejected by Acumatica with an error. If the release step fails after a successful create or update, the entry will exist in Acumatica in Balanced state and the API will return an error. The entry is not rolled back.
journalEntriesUpdateAcumatica requires a separate Release action to transition a journal entry from Balanced to Posted. When `status: "posted"` is sent, Unify automatically calls the ReleaseJournalTransaction action after updating the entry. Only `status: "posted"` is supported for state transitions. Other values (`draft`, `voided`, etc.) are not supported — the entry will be updated but will remain in Balanced state. Once a journal entry is Posted, it cannot be edited. Any attempt to update a Posted entry will be rejected by Acumatica with an error. If the release step fails after a successful update, the entry will exist in Acumatica in Balanced state and the API will return an error. The update is not rolled back.