Mass Billable Charge Creation CSV Format

The following table lists and describes the columns that should be available in the CSV file while creating multiple billable charges for the financial services business at once through an upload request:

Sr. No. Column Name Description Mandatory (Yes or No)
1 Account Identifier Type Used to specify the account identifier type.
Note: You must specify an account identifier type which is already defined in the system.
 Yes (Conditional)
Note: This data is required when the account ID and contract ID are not specified in the record.
2 Account Identifier Used to specify the account identifier.
Note: The system derives the account using the given account identifier type and account identifier combination when the account ID is either not specified or is invalid in the record.
 Yes (Conditional)
Note: This data is required when the account ID and contract ID are not specified in the record.
3 Account ID Used to indicate the account for which you want to create the billable charge. Yes (Conditional)
Note: This data is required when the following conditions are met:

  • Account identifier type and account identifier are not specified in the record.

  • Contract ID is not specified in the record.
4 Contract ID Used to indicate the contract against which you want to create the billable charge.
Note:

If you do not specify the contract ID in the record, the system creates the billable charge against the account’s contract which is created using the contract type where:

  • The payment priority is set to highest.

  • The Eligible for Billing option is selected.

In addition, the contract type considered for billing should match the contract type specified in the price item.

 Yes (Conditional)
Note: This data is required when you want to create the billable charge against a specific contract of the account.
5 Start Date Used to specify the start date of billable charge.
Note:

You must specify the date in the YYYY-MM-DD format.

The start date cannot be later than the end date.

 Yes
6 End Date Used to specify the end date of billable charge.
Note:

You must specify the date in the YYYY-MM-DD format.

The end date cannot be earlier than the start date.

 Yes
7 Charge Type Used to indicate the type of billable charge.
Note: You must specify a charge type which is already defined in the system.
 No
8 Description On Bill Used to specify the summarized information about the charge that you want to print on the bill. Yes
9 Recurring Flag Used to indicate whether you want to create recurring bill segments for the charge. The valid values are:

  • BP - Used when you want to create recurring bill segments at the intervals defined in the bill period.

  • FR - Used when you want to create recurring bill segments at the set invoice frequency.

 No
10 Frequency Used to indicate the invoice frequency using which the system determines the intervals at which the recurring bill segments should be created for the billable charge.
Note: You must specify an invoice frequency which is already defined in the system.
 Yes (Conditional)
Note: This data is required when the recurring flag is set to FR.
11 Bill Period Used to indicate the bill period using which the system determines the intervals at which the recurring bill segments should be created for the billable charge.
Note: You must specify a bill period which is already defined in the system.
 Yes (Conditional)
Note: This data is required when the recurring flag is set to BP.
12 Bill After Used to specify the date after which the charge can be billed to the account.
Note: You must specify the date in the YYYY-MM-DD format.
 No
13 Adhoc Bill Used to indicate whether the billable charge should be considered during adhoc or regular billing. The valid values are:

  • Y - Used when you want to consider the billable charge during adhoc billing.

  • N - Used when you want to consider the billable charge during regular billing.

 No
14 Description on Bill1, Description on Bill2, ....., Description on Bill5 Used to specify the description for the pass-through charge line.
Note: You can specify maximum 5 pass-through charge lines in the record.
 Yes (Conditional)
Note: This data is required while creating a pass-through billable charge.
15 Amount1, Amount2, ....., Amount5 Used to specify the charge amount.
Note: You must specify a number with decimal positions less than or equal to the decimal positions defined for the respective currency.
 Yes (Conditional)
Note: This data is required while creating a pass-through billable charge.
16 Currency1, Currency2, ....., Currency5 Used to specify the currency in which the amount is charged.
Note:

You must specify a currency which is already defined in the system.

If you specify a currency other than the account's invoice currency, the system will do the currency conversion if the appropriate exchange rate is available in the system.

 Yes (Conditional)
Note: This data is required while creating a pass-through billable charge.
17 Show On Bill1, Show on Bill2, ....., Show On Bill5 Used to indicate whether the charge should appear on the person's printed bill. The valid values are:

  • Y

  • N

Note: If you do not specify this column value, by default, it is set to Y.
 No
18 Memo Only1, Memo Only2, ....., Memo Only5 Used to indicate whether the charge should not be included in the bill amount. The valid values are:

  • Y

  • N

Note: If you do not specify this column value, by default, it is set to N.
 No
19 Appears in Summary1, Appears in Summary2, ....., Appears in Summary5 Used to indicate whether the charge should be included in the summary line. The valid values are:

  • Y

  • N

Note: If you do not specify this column value, by default, it is set to N.
 No
20 Distribution Code1, Distribution Code2, ....., Distribution Code5 Used to specify the distribution code that indicates the GL account where the pass-through charge should be posted.
Note: You must specify a distribution code which is already defined in the system.
 Yes (Conditional)
Note: This data is required when the memo only flag of the pass-through charge line is set to N.
49 Price Item Used to indicate the price item for which you want to create the billable charge.
Note: You must specify a price item which is already defined in the system.
 Yes
50 Variance Parameter Variance parameter (i.e., TOU) based pricing is deprecated and no longer supported in ORMB. Therefore, you should keep this column blank in the CSV file. Not applicable
51 Price Item Parameter1, Price Item Parameter2, ....., Price Item Parameter15 Used to indicate the price item parameter that you want to use along with the price item for determining the price item pricing.
Note:

This column value should not contain the Equal To (=) or Tilde (~) symbol.

You must specify the mandatory parameters of the price item when the billable charge start and end dates fall within the respective price item parameter date range.

You must specify a parameter which is associated with the price item in the given date range.

You can specify maximum 15 price item parameters in the record.

 Yes (Conditional)
Note: This data is required when the price item parameter value is specified in the record.
52 Price Item Parameter ValueSQI1, Price Item Parameter Value2, ....., Price Item Parameter Value15 Used to specify the parameter value.
Note: This column value should not contain the Equal To (=) or Tilde (~) symbol.
 Yes (Conditional)
Note: This data is required when the price item parameter is specified in the record.
81 SQI1, SQI2, ....., SQI5 Used to indicate the service quantity identifier (SQI) using which you want to calculate the price item charge.
Note:

You must specify an SQI which is already defined in the system.

You can specify maximum 5 SQIs in the record.

 Yes (Conditional)
Note: This data is required while creating an SQI based billable charge.
82 SQI Value1, SQI Value2, ....., SQI Value5 Used to specify the service quantity for which you want to create the charge.
Note: You can specify a number with a maximum precision 36 and maximum scale 18 (i.e., Number(36, 18)).
 Yes (Conditional)
Note: This data is required while creating an SQI based billable charge.
91 Effective Date1, Effective Date2, ....., Effective Date20 Used to specify the date from when the characteristic is effective for the billable charge.
Note: You must specify the date in the YYYY-MM-DD format.
 Yes (Conditional)
Note: This data is required when the characteristic type is specified in the record.
92 Char Type1, Char Type2, ....., Char Type20 Used to specify the characteristic type.
Note:

You must specify a characteristic type where the characteristic entity is set to Billable Charge.

You can specify maximum 20 characteristics in the record.

 No
93 Char Value1, Char Value2, ....., Char Value20 Used to specify the value for the characteristic type. Yes (Conditional)
Note: This data is required when the characteristic type is specified in the record.
Note:
The CSV file should contain the columns in the above mentioned sequence. You can add five pass-through charge lines — each set containing Description on Bill, Amount, Currency, Show on Bill, Memo Only, Appears in Summary, and Distribution Code followed by the subsequent set (i.e., Description on Bill1, Amount1, Currency1, Show on Bill1, Memo Only1, Appears in Summary1, Distribution Code1, Description on Bill2, Amount2, Currency2, Show on Bill2, Memo Only2, Appears in Summary2, Distribution Code2, and so on). Similarly, you can add the following:

  • 15 sets of pricing parameters — each set containing Price Item Parameter and Price Item Parameter Value followed by the subsequent set (i.e., Price Item Parameter1, Price Item Parameter Value1, Price Item Parameter2, Price Item Parameter Value2, and so on).

  • 5 sets of SQ details — each set containing SQI and SQI Value followed by the subsequent set (i.e., SQI1, SQI Value1, SQI2, SQI Value2, and so on).

  • 20 sets of characteristics — each set containing Effective Date, Char Type and Char Value followed by the subsequent set (i.e., Effective Date1, Char Type1, Char Val1, Effective Date2, Char Type2, Char Val2, and so on).

You must specify either pass-through charge lines or SQI details in the record.

Before uploading the file, ensure that the column headers specified in the CSV file are mapped to the schema of the respective upload request business object through data mapping in the upload request type. Otherwise, erroneous results might occur. For more information, see Mapping Data and Configuring Filters for an Upload Request Type.