Skip to main content
Aria Knowledge Central

void_invoice_m Guide

Voids a given invoice object and all its associated transactions. Voiding an invoice is permanent and cannot be undone.

API Specification: void_invoice_m
Required Fields:
  • <client_no>
  • <auth_key>
  • <acct_no> or <client_acct_id>
  • <invoice_no>
  • <reason_code>

Error Codes

Error Code/Description Associated Inputs

1001: unexpected error


1004: authentication error

Associated Inputs: auth_key, client_id, client_no

<client_no>, <auth_key>

1009: account does not exist, Account not found: AriaNo (acct_no), Account not found: Userid (userid), or Account not found: ClientId (client_acct_id)

Associated Inputs: acct_no, account_no, client_acct_id, user_id, userid, parent_acct_no

<acct_no>, <client_acct_id>

2003: transaction already voided


2005: Combine invoices can not be voided. Please contact customer support.

Associated Inputs: invoice_no


3004: Invoice does not exist

Associated Input: invoice_no


3024: Invalid reason code

Associated Input: reason_code


3095: The invoice cannot be voided because one or more credit memos have been applied to it.

Associated Input: invoice_no


3096: The invoice cannot be voided because it has been rebilled.

Associated Input: invoice_no


Additional Guidance

Input Fields
Field Name Notes

Allowable Values

Values Description
1 Duplicate check posting
2 Transfer in wrong direction
3 Returned payment
4 Account responsibility incorrect
5 Invoice created in error
6 Error in processor integration
7 Test data
8 Erroneous entry
9 Collection on order failed
10 Payment voided before settlement
11 Voided by 3rd party
12 Collection Failed


  • Was this article helpful?