Revenue reports are showing aggregated percentages for revenue share leading to incorrect share calculations. See below dummy data used for testing:
| Monetization Package | Package ID | Rate Plan | Plan ID | API Product | Product ID | Developer Name |
| ISVA-Bundle | isva-bundle-fayx | ISVA-Rate | isva-bundle-fayx_fortellis-scenario-2 | ISVA-Product | isva-product | ISVC |
| Developer ID | Application Name | Application ID | Currency | Transaction Type | Provider Status |
| isvc | ISVC-App | 090ec643-d182-4da3-a030-63f1f0aa7c18 | USD | PURCHASE | OK |
| Net Price |
Provider Rev Share |
% Provider Rev Share |
Developer Rev Share |
% Dev Rev Share |
Transaction ID |
Payment Reference |
| 5.0000 |
288.0000 |
720.00 |
32.0000 |
80.00 |
5610d71a-ef41-4782-8f4a-b0165463d878 |
5610d71a-ef41-4782-8f4a-b0165463d878 |
| Transaction Start Time |
Transaction End Time |
Batch Size |
| 2020-09-02 14:03:27 |
2020-09-02 14:03:28 |
8 |
In the above figures %Provider Rev Share is shown as 720 which is 90% times the batch size of 8. This 720% is then used to calculate the Provider Rev Share. It seems to me that the % Provider rev share should always be 90% so that even in batched requests the resulting calculation is Charged Rate x %Provider Rev Share. 40 x .90 = 36 vs 40 x 7.20 = 288
Wondering how to stop % Provider Rev Share from being aggregated. For reference, my rate plan type is rate card and revenue share, it is set to Net, also set to a Fixed sharing model, and lastly 10% revenue share. In my proxy I've configured the netPrice to be 5.
LinkedIn
Twitter
