Upload Usage Records in Salesforce Billing

The following fields are mandatory when uploading Usage records:

• Matching Id
• Start DateTime
• End DateTime
• Either Quantity or both Prerated Quantity and Prerated Amount

The following fields are optional if the target Usage Summary fields are null. They are not used for legacy usage products (when the Order Product Charge Type = Usage). For Usage Based Pricing using Consumption Schedules, if the target Usage Summary fields are populated, they are required and must match their corresponding field values.

• Matching Attribute
• Unit OF Measure

NOTES:

• Matching Id must match the Matching Id on the Usage Summary record.
• If the Order Product that created the Usage Summary has a Consumption Schedule, then the Unit of Measure and Matching Attribute must also match on the Usage record being uploaded. 
• If the Order Product that created the Usage Summary has a Price Schedule and was created with a Charge Type of Usage, then do not add Unit of Measure and/or Matching Attribute to the Usage record or it won't be rated. 
• Quantity can be entered as a decimal and can be entered as a negative value for corrections, if needed.
• DateTime must be correctly formatted for Usage to be loaded and rated properly
  • When using Dataloader, use one of the following formats:
    mm/dd/yyyyThh:mm:ss.sssZ where mm=month, dd=day, yyyy=year, hh=hour, mm=minutes and ss.sss= seconds to 3 decimals. The Z here specifies the GMT time zone. Sample: 07/15/2018T13:13:00.000Z
  • Similar to above, the 'Z' can be replaced by 'GMT-HH:MM' or 'GMT+HH:MM' to specify a specific time zone offset from GMT. Sample: 09/01/2021T02:00:00.000GMT-05:00
  • If using the Data Import Wizard refer to this Knowledge Article for valid formats.
  • Be mindful of time zone conversions for DateTime. Some processes might convert the DateTime to the org DateTime when importing to Salesforce. For example midnight GMT will convert to the previous date if the org GMT offset is positive. The Usage Processing Date field on the Usage record shows what Date the EndDateTime is converted to. This will hold the actual date that is used to compare to the Summary End Date on the Usage Summary.
• End DateTime must be equal to or after Start DateTime
• You can not load usage records into usage summary periods where the Status is 'Processed' or 'Cancelled'. These records will not be loaded.
• If the Start and End DateTime crosses over two or more Usage Summary records, it will be entered in the Summary that contains the End DateTime.
• Usage records should be loaded in a single thread with batch size = 1
• Deleting a Usage Record does not remove its value from the Usage Summary. This must be done by entering an offsetting negative usage record. We advise setting up field tracking for at least the Total Quantity field to make this visible.
• If you use fractional quantities, make sure your Price Schedule on the Order Product has a price tier that starts at 0. This can be updated manually or by setting up a zero percent discount schedule on the Product with a Lower Bound of 0.
• If you are uploading Usage records and using the package setting Usage Rating Process based on: ByProcess, then the Subtotal and Unit Price on individual Usage records will not be updated. The Quantity and Unbilled Subtotal fields are updated on the respective Usage Summary record. This is working as designed.