We are pleased to provide you with a summary of our August, 2009 release.
You can now export draft invoices to .csv and .pdf for any completed bill run. You do not have to post your bill run prior to exporting. Since you can now export your invoices in batch, it is easier to check and validate your invoices all at once prior to posting.
We continue to change processes to be asynchronous. We recently changed the canceling and posting processes to be asynchronous. With this release, batch emailing of invoices and .pdf extracts of invoices are now also asynchronous. We will continue to move additional processes such as the generation of .csv invoices and other exports to be asynchronous in upcoming releases.
The Invoice PDF file naming has changed to include additional information: INVnumber_AccountNumber_AccountName_InvoiceDate_Status.pdf. This additional naming provides relevant details about the invoice.
If you batch email your invoices, the bill run details will now show the status when you are done. You will also now see the date that the last email was sent. To see the date, go to the generated invoices tab within the bill run.
We recognize that it is easier for you to use fraud protection and AVS as well as better process global transactions if we provide additional information (that is optional for you to populate) for your Authorize.net transactions. See below for a complete list of fields that are available to you for your Authorize.net transactions:
The Gateway Transaction Result Number and the Gateway Transaction Result Message are now available via the payment export. This information allows for better tracking of payments at the gateway for either troubleshooting or reconciliation (i.e., tracing declined payments at the gateway).
Currently, you can set a maximum number of login attempts. When users exceed this, they are locked out. Starting with this release, administrators can unlock users that have been locked out. To do so, go to Admin and then Manage Users. Only administrators will be able to see this feature under Admin settings.
The Subscription Created Date field is available to query. This is possible for all versions of a subscription. This allows you to track the creation of new subscriptions and amendments as well as existing subscriptions amendments.
Delete usage is possible from the delete() call. You can now delete usage programmatically. For example, if usage is uploaded incorrectly, usage can be deleted via the delete() call and the correct usage can be uploaded subsequently.