...
This Import will allow the User to add or update Charges on Services for Billing. In order to add a charge to a Service, the '"Billable'" flag of the Service must already be set.
By default, this import will always Add new charges, not Update existing charges. Care should be taken, as this can create duplicate charges. There is an optional UPDATE Flag that can be set to force the import to do Updates instead of Adds.
The import cannot delete existing charges, but it can set an existing MRC charge Stop Date to end the charge.
...
Datatype is String.
Default value is ' blank'.
The Charge Catalog Name expects just the name, and will only work if the name is unique in the whole catalog.
...
Conditionally Required (unless Charge Catalog Name is provided instead)
Datatype is Hierarchical String.
Default value is ' blank'.
This is the full hierarchical path of the Charge Catalog.
...
Allowed values are from the SERVICE_TYPE List Values.
All Service Types are valid for Service Charge Imports.
...
This will override the Charge Catalog Description for Billing.
Expense GLA
Datatype is Hierarchical String.
Override Amount
Datatype is Number.
...
Datatype is Date.
Default value is ' blank'.
Used for MRCs only.
NRCs ignore this field.
...
Datatype is Number.
Default value is ' blank'.
If you map the New Override Amount and provide a blank value, then any existing Override Amount on the charge will be removed.
...
Datatype is Number
Default value is ' blank'.
Used for UPDATE only.
RECID
Datatype is Number.
Default value is ' blank'.
This is used only as a lookup key for Charge Updates.
...
Datatype is Number.
Default value is ' blank'.
This is used to specify the Service Record for Services that have a blank Service ID. If this is provided, the provided value must be a valid existing service RECID. If it is not, it will cause an error. The only Service Type permitted to have blank Service IDs is Other Services .
...
Datatype is String
Default value is ' blank'.
This flag is only needed if there are multiple Charges with the same Names that have different types.
If this is set, it must be set to the code of one of the CHARGE_TYPE List Values from the List Values grid.
Allowed values are the System Use Values: MONTHLY_RECURRING, NONRECURRING, QUARTERLY, SEMI_ANNUAL, and ANNUAL_RECURRING.
...
The provided Service ID value might match a Service ID, and also match an Alias value of a different Service ID. This flag tells the import which result to use. You can set the flag to one of these 3 values:
'"First' " The Alias value will be used first.
'"Last' " The Alias value will be used last.
'"None' " The Alias value will not be used at all.
...
Alternate Recurring Charges (Quarterly, Semi-Annual, and Annual), when updated, will always use BACKDATE as the Effective Date.
...
If an existing Monthly Recurring Charge has been billed, then Updating the GLA, Amount, Quantity, or Prorate Flag, will stop the existing Charge and create a new Charge with the appropriate changes. The date of this stop and start is determined by the Effective Date flag. If this is set to '"TODAY'", then it will stop the existing charge with yesterday's date, and start the new charge with today's date. If it is set to '"BACKDATE'", then it will use the date that the existing charge has been billed through.
...