topic Re: Tracking variable monthly revenue to invoice partners in 💬 RevOps Discussions

Tracking variable monthly revenue to invoice partners

JCorwin1 — Tue, 28 Oct 2025 16:16:47 GMT

Hello, I have seen a somewhat similar thread from 2023 but it didn't answer exactly our issue so I am hoping someone can help.

We offer a cloud financial management SaaS platfrom that we have partners who whitelabel and offer as a service for their end customers. We bill off of cloud usage costs, which varies month to month. With our partners, we bill monthly, one month in arrears and we want to track and invoice out of Hubspot.

We have been doing this with direct customers for a while now but those were annual contracts with set values. This use case is now monthly with variable dollar amounts every month and we are not sure the best way to do this today. We track everything cost wise in our own platform and can API into Hubspot (if possible), but I'm not sure setting up a deal that then changes is the best way forward or do we need to create a deal per month under the end customer (child) tenant which seems like it would get very noisy, or is there another, better way to do this in Hubspot.

Thanks in advance!

Re: Tracking variable monthly revenue to invoice partners

STierney — Tue, 28 Oct 2025 19:01:34 GMT

Hey @JCorwin1 - thanks so much for posting in the Community!

I managed to find this Community thread, which outlines some approaches you may consider taking in this use case. Feel free to read through and reply with any follow-up questions the Community may be able to continue to answer!

Shane, Senior Community Moderator

Re: Tracking variable monthly revenue to invoice partners

RubenBurdin — Mon, 15 Dec 2025 20:16:40 GMT

Hi @JCorwin1 , this is a very real problem, and you’re right to be cautious about forcing it into a deal model that wasn’t designed for variable monthly usage.

With how HubSpot works now in 2025, the cleanest mental model is to separate commercial structure from billing events. Deals are still best used to represent the partner agreement or commercial relationship, not each monthly invoice. Creating a new deal every month usually looks attractive at first, but it gets noisy fast and makes reporting painful once you have dozens of partners and years of history.

A common pattern I’ve seen work well is:

One active “Partner Agreement” deal per partner, usually long-lived.
A custom object like “Usage Record” or “Monthly Usage,” with one record per partner per month.
Each usage record stores the metered amount, calculated charge, billing period, and invoice status, and is associated to both the partner company and the parent deal.

HubSpot handles this structure well today. Custom objects are first-class, can be reported on cleanly, and can trigger workflows for invoice prep or finance notifications (https://knowledge.hubspot.com/object-settings/create-custom-objects )

You avoid mutating deal amounts every month, and you keep a clear audit trail of what was billed, when, and why. Since your source of truth for usage already lives in your own platform, pushing those monthly usage rows into HubSpot via API is usually the right move, rather than recalculating inside HubSpot. The key is making sure associations and updates are reliable month over month, especially if usage gets corrected after the fact.

One clarifying question that matters here: do partners ever dispute or adjust usage after invoicing, or is usage final once the month closes? That affects whether you allow updates vs. immutable records.

Small disclosure since I’m close to this space: I work at Stacksync. We often see this exact setup where monthly usage data lives in a product database and needs to stay continuously aligned with HubSpot custom objects, without touching deals each month, which is why this pattern tends to hold up operationally over time.

Hope this helps, and happy to dig deeper if you want to sanity-check the object model.