I was looking over the charge models but I didn't see an obvious answer to the type of charge model I was looking for. I'd like to charge users based on my users peek usage for a month. That is I would like to upload the usage each day and charge them based on the day they used the most usage.   i.e.    Every day of the month the user uses 10 units except the 15th where they used 20. I would like to charge them a rate based on the 20 for the month.   Is this possible? If so how?    David ... View more

I'm looking to upload usage records via the Rest API but I unsure what the timezone will be for a given usage record. The format asked for is MM/DD/YY without a timezone. I know Zuora converts dates/times to pacific. If I upload a record in the MM/DD/YY format does Salesforce assume I provided that value in Pacific time? If so how do I provide a timezone? We bill using a different timezone and some of the usage records will be in the wrong window if this not set correctly. ... View more

I'm assuming this isn't supported but I would like to confirm. I"m looking to pass multiple invoice id's to the Invoice and Collect endpoint. I can successfully pass a single invoice Id and it look slike the response can list multiple invoices paid but unless I create a new invoice I seem to have to call invoice-collect for each invoice I wish to pay. Is this correct? If so can you allow users to pass multiple invoice id's?  ... View more

Idea: We would like is a way to tolerate failure and the subsequent replay of the usage data when it is being created.   I would be for you to allow the passing of a unique id within each usage objects (SOAP API). If you have already processed the provided id you can ignore the most recent usage object and report that in the response object.   With this approach we can replay the submission of the same usage object when we are unsure of its success. We can do this without worrying about it being duplicated. This adheres to a stateless RESTful design as each request from any client contains all the information required to service the request and the client holds the session state.   Our Use Case: Currently we process and group large amounts of usage data that can come in at different points in a month. We require a guarantee that each usage object we create in Zuora is unique (Don't want to double bill). That it has only been uploaded once and only once even if upload the same usage object multiple times.   Example:   On Jan 3rd I may submit a usage object: QTY: 5 UOM: Local Start Date: Jan 2nd Submit Date: Jan 3rd   On Jan 30th I may submit a usage object: QTY: 10 UOM: Local Start Date: Jan 2nd Submit Date: Jan 30th   I need to guarantee that the Usage bucket 'Local' gets two usage objects regardless of how many times I upload these two usage objects. I need that guaranteed even if I have to submit these two usage objects multiple times. One reason I may have to submit these usage objects many times is the failure to get the resulting response object in a reasonable amount of time. Additionally the sudden shutdown of the code which submits the data would also leave me in a state in which I would need to resubmit the same usage data in order to ensure it has been received.   Current Workaround Currenlty I use the Description field to hold a unique id. Before I uplaod a batch of record I query the Usage Object for descriptions that match the unique ids which I am about to upload. If I find them then I know the usage has already been processed and I can ignore it. This workaround does the trick but it has its limitations. 1) If I upload in parallel I can still have duplicates as one thread could have uploaded since I last checked (No transacitonal guarantee) 2) I am use up my Read/Query quoat against zuora. (You are getting hit with way more requests then is really needed to solve this issue)     ... View more