# What does each Confluent Cloud invoice line\_type actually bill for? Sanity-checking my mapping

**URL:** <https://forum.confluent.io/t/what-does-each-confluent-cloud-invoice-line-type-actually-bill-for-sanity-checking-my-mapping/38509>\
**Category:** Confluent Cloud\
**Created:** [3 September 2026 22:00 UTC](https://forum.confluent.io/t/what-does-each-confluent-cloud-invoice-line-type-actually-bill-for-sanity-checking-my-mapping/38509 "2026-09-03T22:00:37Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mithrandirr](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@mithrandirr](https://forum.confluent.io/u/mithrandirr)\
**Post date:** [3 September 2026 22:00 UTC](https://forum.confluent.io/t/what-does-each-confluent-cloud-invoice-line-type-actually-bill-for-sanity-checking-my-mapping/38509/1 "2026-09-03T22:00:37Z")

</div>

I’ve been reconciling Confluent Cloud invoices line by line, mapping every `line_type` in the billing CSV to what it actually meters. I’d like to check my understanding before relying on it.

| line\_type | I think it bills | Unit |
| --- | --- | --- |
| `KAFKA_NUM_CKUS` / `KAFKA_NUM_ECKUS` | Whole-cluster capacity | CKU-hour |
| `KAFKA_STORAGE` | Retained bytes; replication already included | GB-hour |
| `KAFKA_NETWORK_READ` / `_WRITE` | Network egress / ingress | GB |
| `KAFKA_PARTITION` | Partitions beyond the free allowance (Basic/Standard only?) | partition-hour |
| `CONNECT_NUM_TASKS` | Connector tasks, whether moving data or not | task-hour |
| `CONNECT_THROUGHPUT` | Bytes processed by the connector | GB |
| `FLINK_NUM_CFU` | Flink compute | CFU-hour |
| `GOVERNANCE_BASE` | Schema Registry / Stream Governance | hour |

A few things I’m unsure about:

1. **Storage and replication:** Is `KAFKA_STORAGE` measured as logical retained bytes, with RF3 already reflected in the price? My assumption is that replication-factor changes cannot reduce this cost in Confluent Cloud because RF is fixed at 3.
2. **Dedicated partitions:** I don’t see `KAFKA_PARTITION` for Dedicated clusters. Does that mean partitions are covered by CKU capacity rather than billed separately?
3. **Connector tasks:** Does `CONNECT_NUM_TASKS` bill for provisioned connector tasks regardless of whether the connector is actually moving bytes? In other words, would a paused—but not deleted—connector still incur task-hour charges?
4. **Negative lines / credits:** Do credits or adjustments ever appear as negative lines in the CSV, or are they handled elsewhere?

If you’ve reconciled an invoice against these fields, I’d appreciate any confirmation or corrections.

---

<div class="post-metadata">

**Author:** ![mmuehlbeyer](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/mmuehlbeyer/32/1088_2.png) [@mmuehlbeyer](https://forum.confluent.io/u/mmuehlbeyer)\
**Post date:** [7 September 2026 12:01 UTC](https://forum.confluent.io/t/what-does-each-confluent-cloud-invoice-line-type-actually-bill-for-sanity-checking-my-mapping/38509/2 "2026-09-07T12:01:24Z")

</div>

hey @mithrandirr

not sure if you already did but in case you didn’t 😉

did you check

> **[unallocated - Cost Allocation in Confluent Cloud | Confluent Documentation](https://docs.confluent.io/cloud/current/billing/cost-allocation.html#how-cost-allocation-works)**
>
> Cost allocation itemizes a Confluent Cloud bill by the service account, user, identity pool, or resource that drove each charge. Use it to feed your internal chargeback or showback process, split a shared cluster across the teams that use it,...

best,

michael

---

<div class="post-metadata">

**Author:** ![mithrandirr](https://avatars.discourse-cdn.com/v4/letter/m/e495f1/32.png) [@mithrandirr](https://forum.confluent.io/u/mithrandirr)\
**Post date:** [7 September 2026 18:27 UTC](https://forum.confluent.io/t/what-does-each-confluent-cloud-invoice-line-type-actually-bill-for-sanity-checking-my-mapping/38509/3 "2026-09-07T18:27:22Z")

</div>

Michael — thank you. That was the page I needed, and I clearly hadn’t read it closely enough.

One thing I’m still unsure about: does the invoice CSV from Billing & Payment use the same vocabulary as the cost-allocation export? Cost allocation documents `billing_metric` in CamelCase (for example, `KafkaNumCKUs`) and `product_type` in lowercase hyphenated form (for example, `stream-governance`). I don’t know whether the invoice export uses those same strings or maintains its own set. If anyone has a recent invoice CSV and can paste just the header row—column names only, no values—that would settle it.