#Grace
1 messages · Page 1 of 1 (latest)
Hi there, sorry for the delay!
No worries!
Been doing more thinking - this customer has a current subscription price of £7140. If I increase that annual cost to £7170, then the amount of all of those returned values comes to £7761.04 - so there's a considerably larger difference there, however, I have just come up with a hypothesis as to why...
When I started testing with prorations on this specific customer, always_invoice wasn't set as a parameter, so possibly there's some old prorations that occurred before that parameter was specified, leading to extra costs build into those return values that haven't yet been accounted for in payments (?)
Either way, going to set up a fresh test customer and see what happens
Since you're already digesting the prorations documentation, I imagine you've looked into the API endpoint for retrieving an upcoming invoice? https://stripe.com/docs/api/invoices/upcoming
Yes, I have the response from that call displaying elsewhere in the billing dashboard inside of our platform
Not gone absent! Starting with a new customer has given me a different set of results so now I'm refactoring things to see if I can get everything to play nice. Might not need any help in the end after all