Reporting API - Invoice Custom Charges

Introduction

This article provides an overview of Invoice Custom Charges in the Reporting API. It explains how to access key details about corrections made to invoices within the platform.

Affected endpoints

The following endpoints are used to retrieve information related to Invoice Custom Charges:

1. GET invoice-headers
https://api.telemetry.appxite.com:8449/api/v1/reporting/invoices/invoice-headers/requesterId?sasKey=sasKey

2. GET invoice-headers/preview

https://api.telemetry.appxite.com:8449/api/v1/reporting/invoices/invoice-headers/requesterId/preview?sasKey=sasKey

3. GET invoice-rows

https://api.telemetry.appxite.com:8449/api/v1/reporting/invoices/invoice-rows/requesterId?sasKey=sasKey

4. GET invoice-rows/preview

https://api.telemetry.appxite.com:8449/api/v1/reporting/invoices/invoice-headers/requesterId/preview?sasKey=sasKey

The Custom Charges related fields are available in both Reporting API collections:

  1. Appxite Reporting API v1
  2. Appxite Reporting API v2
NOTE! AX Reporting API v2 does not provide Preview endpoints. However, these can be accessed by defining the isPreview parameter (boolean type), which defaults to false.

Custom Charges related fields

The visibility of Custom Charges details depends on the status of the related invoice:

1. New Corrected Status
When an invoice is in the "New Corrected" status, the details will only be visible via the GET invoice-headers/preview endpoint.

If Custom Charges are applied, the response will display the following fields:

  • StatusId = 6
  • Status = New Corrected
  • InvoiceSourceId = 4
  • InvoiceSource = Custom

2. Verified Status
Once the invoice with Custom Charges is in the "Verified" status, the following fields will be visible in the GET invoice-headers endpoint:

  • StatusId = 1
  • Status = Verified
  • InvoiceSourceId =4
  • InvoiceSource = Custom

Each invoice header generates multiple invoice rows. The GET invoice-rows and GET invoice-rows/preview endpoints will display details of these rows, including the following fields related to Custom Charges:

  • CustomChargeDetails
  • ChargeType = UserCorrection

NOTE! Custom Charges may or may not be tied to a specific subscription. If Custom Charges are applied at the general customer level (rather than to a specific subscription), the information will appear with the hardcoded value subscriptionName = Default Subscription.


Related Content

Was this article helpful?

0 out of 0 found this helpful

Add comment

Please sign in to leave a comment.