CONFLUENCE charge on bank statement: what it means and what to do

If you see CONFLUENCE on your bank or card statement, the charge usually comes from an Atlassian subscription for Confluence Cloud or a broader Atlassian billing account that includes Confluence. Confluence is Atlassian's team workspace and knowledge-base product, used for internal documentation, project notes, runbooks, onboarding guides, engineering specs, and company wikis. Because it is often purchased for work, the cardholder who notices the transaction is not always the same person who created the workspace or controls the billing profile.

That disconnect is the main reason the descriptor can feel unfamiliar. A finance lead might see CONFLUENCE, ATLASSIANCONFLUENCE, ATLASSIANCLOUD, or another shortened billing variation without immediately connecting it to a company wiki subscription. Atlassian also centralizes billing for several products, so a Confluence plan can appear under a parent-brand or cloud-billing label rather than a long product name that clearly says what the team bought.

What this charge usually represents

In most cases, CONFLUENCE is a recurring SaaS subscription charge. Atlassian's public Confluence pricing page shows Free, Standard, Premium, and Enterprise tiers. The page source for the USD pricing data includes Standard monthly pricing at about $6.70 per user for the first pricing tier and Premium monthly pricing at about $13.20 per user. The same pricing data also shows Enterprise annual flat pricing beginning around $2,100 for the smallest published tier. That means a bank statement amount can reflect a single-user or small-team monthly renewal, a seat increase, a larger annual renewal, or a company-wide plan change.

Atlassian's billing documentation also explains that cloud subscriptions are billed based on the app plan, billing frequency, and the number of users with app access at the end of the billing cycle. In plain English, a Confluence charge can change when a team adds users, changes plan level, or lets an annual renewal hit all at once. That is why the amount may not match the number you vaguely remember from the original signup.

Why the descriptor may look unfamiliar

Real-world confusion usually comes from shared ownership. An engineering manager may set up the Confluence site, procurement may add the card, and finance may later see the renewal. Atlassian's support documentation also notes that admins can change plans and manage subscriptions from the Atlassian billing console, so the person who approved the original purchase may not be the only person who can affect the amount over time.

There is also a processor-label problem. Third-party charge references for Atlassian list common statement families such as ATLASSIANCONFLUENCE, ATLASSIANCLOUD, ATLASSIAN CLOUD BILLING, ATLASSIANSUBSCRIPTION, and ATLASSIANRENEWAL. So even when the charge is genuinely tied to Confluence, the statement line may emphasize the parent billing system instead of the exact product that end users know internally.

How to verify the charge quickly

1. Search your work and personal inboxes for Confluence, Atlassian, invoice, billing, renewal, workspace, or admin emails.
2. Log in to the relevant Atlassian organization and review subscriptions, billing accounts, plan level, and user count in admin.atlassian.com.
3. Ask IT, engineering, product, support, or operations teams whether someone created a Confluence site for documentation or internal wiki use.
4. Compare the statement amount against known seat-based pricing patterns, especially Standard or Premium per-user monthly billing.
5. Check whether the card is attached to a broader Atlassian billing account that also covers tools like Jira or Trello.

If the amount, timing, and billing account line up with a real Atlassian workspace, the charge is probably legitimate. If no admin, invoice, or site can explain it, then you should contact Atlassian support and document the outcome.

Pricing clues that help identify it

Pricing often gives the fastest clue. A relatively small recurring amount can suggest one or a few Confluence Standard seats. A higher recurring amount may indicate Premium seats or a larger user count. A much larger one-time charge may reflect annual billing, which often surprises cardholders because it lands as a single renewal instead of a familiar monthly charge. Atlassian's billing help also says charges are tied to the number of users with app access at the end of the billing cycle, so a new department rollout can increase the invoice without any fraud being involved.

If you have seen other digital subscription descriptors before, the pattern is similar to OPENAI CHATGPT, PATREON, or SPOTIFY PREMIUM. Different product, same logic: verify the account, match the amount and billing cadence, and only dispute after the merchant cannot connect the charge to an authorized subscription.

When the charge is probably legitimate

A CONFLUENCE charge is more likely to be legitimate if your company already uses Atlassian software, if coworkers rely on a shared wiki or documentation hub, if the same card has prior Atlassian renewals, or if an administrator can find the subscription in the billing console. It is also common for a free trial or low-usage workspace to become a paid plan later, especially when the team grows beyond free-plan limits or upgrades for permissions, analytics, automation, or admin features.

Another normal explanation is a plan or user-count change. Atlassian's billing docs explicitly say subscriptions are billed according to the plan and user access at the end of the cycle. So if more employees were added to the site, or if a team upgraded from Free to Standard or Premium, the next charge may look unfamiliar even though it is authorized.

How to stop future CONFLUENCE charges

If the charge belongs to a real account but you no longer want it, review the subscription in Atlassian Administration and save screenshots of the current plan, user count, renewal date, and billing owner before making changes. Atlassian's customer agreement says either party may elect not to renew by giving notice before the end of the current subscription term, and that customer notice can be provided through account settings or by contacting Atlassian support. That timing matters, because waiting until after renewal can leave you asking for an exception instead of preventing the next invoice.

It is also smart to remove inactive users, archive abandoned spaces, and confirm whether the workspace is still needed. Many software subscriptions keep billing simply because nobody formally cleaned up ownership after the original project ended. In a business setting, cleanup often solves the problem faster than going straight to a bank dispute.

Refunds and disputes

Atlassian's customer agreement is clearer than many SaaS vendors. It says fees are generally non-refundable, but it also provides a 30-day return policy for an initial order and allows a refund request for that initial product order. For renewals and later billing events, you should not assume a refund is automatic. Start with the merchant. Contact Atlassian support with the statement date, amount, billing entity, and the suspected site URL or organization name if you have it.

If the charge maps to a real Confluence or Atlassian subscription, the best first step is merchant-side cancellation, downgrade, or billing review. If Atlassian cannot match the charge to a real account, no authorized user can explain it, and the card was not intentionally attached to an Atlassian workspace, then treat it as potentially unauthorized. Keep copies of the support contact attempt, the descriptor screenshot, and any evidence that no valid workspace exists before you contact your card issuer.

Bottom line

Most CONFLUENCE charges on a bank statement come from a legitimate Atlassian subscription for a workplace wiki or documentation system. Verify the Atlassian account first, compare the amount against seat-based Confluence pricing, and review whether the workspace is billed monthly or annually. If the subscription is real, cancel or downgrade it through Atlassian. If there is no real account or authorization behind the charge, escalate quickly as a possible unauthorized recurring transaction.