Why Does My Monthly Bill Change?

Understand the common reasons your Oracle Integration bill may change and learn how changes to service packs and usage affect your costs.

Reasons for billing changes

Review the following reasons why your billing amount may change between billing periods.

  • Service pack change

    An administrator might have selected a different number of message packs for an instance. See How Do I View the Message Packs for an Instance?.

  • Usage change

    If the number of consumed messages exceeds the number of subscribed messages during a one-hour period, the excess messages are considered overage. For billing purposes, overage messages are converted into consumed message packs. Billing is based on the greater of the following values:

    • Subscribed message packs

    • Consumed messages

Note:

Billing for Oracle Integration changed on July 1, 2025. As of that date, several new features, including disaster recovery, robotic process automation, and extended data retention result in extra message usage. These updates are included in the Service Description, which is part of your agreement with Oracle.

Factors to consider when reviewing billing

Consider the following factors when reviewing your billing and deciding whether to adjust your message pack subscription.

  • Overages are pay-as-you-go

    When an instance uses more messages than it is subscribed to, an overage occurs. However, keep in mind that there isn't a penalty for overages. You're simply paying for the messages that an instance has used.

  • Message packs determine concurrency

    The number of message packs that an instance subscribes to directly affects the concurrent synchronous and asynchronous request limit. If asynchronous integrations experience slowness, or synchronous integrations experience timeouts, your instance would benefit from the higher concurrency that comes with more message packs. See When to Increase Message Packs.

  • Billing can be consistent

    Some organizations prioritize consistent monthly bills over cost savings. In such cases, subscribing to a higher number of message packs is worth considering.

  • Integration cleanup reduces costs

    When organizations review their billing data, they often discover older integrations that are still running but are no longer needed. Deactivating unused integrations can help reduce both usage and costs.

Options for managing your bills

Use the following guidance to determine the best way to manage your message pack subscription and billing.

  • Do nothing

    If your throughput is acceptable AND your organization is comfortable with monthly bills that vary based on usage, do nothing. You'll continue paying for your usage, including the subscribed message packs and any usage above them.

  • Increase your message packs

    If you need improved concurrency OR your organization requires consistent monthly bills, increase your message packs to match your peak usage.

    If you require improved concurrency during peak periods, you can also increase your message packs before the peak periods and then reduce the message packs afterward.

    For more guidance, see When to Increase Message Packs and Edit the Number of Message Packs.

Learn more

To learn more about your usage, review all the billing FAQs. See FAQs for Billing.