In preparing this guide, StoreBuilt checked Shopify’s billing documentation against the questions a merchant needs to answer when a charge looks wrong. The important distinction is between an invoice date, a service period and an approval to spend. Treating those as the same date makes a legitimate delayed charge look like a duplicate and can hide a genuine discrepancy.
Shopify app billing reconciliation is the practical job of connecting each billed amount to an agreed service. This guide is for UK ecommerce teams reviewing their operating costs, rather than choosing a new app stack. Examples are illustrative, with no invented client savings or accounting outcomes.
Contact StoreBuilt if app ownership and billing evidence are difficult to connect.
Table of contents
- Build a charge register
- Separate dates and currencies
- Reconcile usage and plan changes
- Investigate unexpected charges
- Make cancellation verifiable
- Run a monthly review
- StoreBuilt point of view
Build a charge register
Start with the actual invoices, not the installed-app screen. An installed app might be free, a subscription might be billed separately, and an invoice might include activity from an app that has since been removed. Download the relevant statements and ask each department for directly contracted software invoices connected to the store.
Give every entry a store identifier and a named owner. Multi-store businesses can mistake the same app on two stores for duplicate billing. Conversely, a shared brand name can conceal two independently purchased tools performing the same job. Record the business purpose without assuming that apparent overlap means one can be removed safely.
| Field | Evidence to retain | Question it answers |
|---|---|---|
| Store and app | invoice line and store reference | which installation incurred this? |
| Approved plan | approval record and plan details | what did we agree to buy? |
| Service period | provider billing dates | when was the service supplied? |
| Usage basis | metered event definition | what increases the charge? |
| Adjustment | credit or refund reference | where was the correction applied? |
| Owner | responsible team member | who can verify usefulness? |
Do not put customer-level activity into a broadly shared finance spreadsheet when aggregated usage will answer the question. Keep detailed evidence in the appropriate restricted system and link to it. The register should help resolve charges without becoming an unnecessary second customer database.
Separate dates and currencies
Shopify explains app charges and billing cycles, including why app periods can differ from the Shopify subscription period. An invoice is a collection of charges; it is not proof that every line represents the same calendar month.
Record the invoice date, service start, service end and payment date separately. This makes it possible to compare two statements without declaring an overlap merely because both mention the same month. It also gives your accountant the evidence needed to decide how costs should be treated in your accounts.
For UK budgeting, retain the original billed currency alongside the GBP amount paid. A higher sterling cost does not automatically mean the provider raised its price. Currency conversion, tax treatment, usage and plan changes are separate explanations that should be checked individually. This article describes operational checks, not accounting or tax advice.
Use consistent comparison periods. Comparing a campaign-heavy thirty-day usage window with a quiet calendar month will not tell you whether the invoice is correct. Match the provider’s reporting window first, then analyse the business reason for the change.
Reconcile usage and plan changes
Ask what the app actually meters. An email tool might count contacts or sends; another system might bill on orders, tracked shipments, stored records or a combination. The familiar word “usage” is not a sufficient definition. Save the plan terms that applied when the usage occurred.
Compare the reported quantity, included allowance, unit rate and adjustment separately. If a bill is £240 higher, the useful question is which quantity or rule explains that amount. Avoid guessing that sales growth caused the change until you have matched the billed event to the provider report.
Plan changes need their own timeline. Record when an upgrade was approved, when it became effective and whether a credit or proration appears elsewhere. Do not add two lines together and label them a double charge without checking their coverage. Equally, do not accept an unexplained adjustment simply because the final amount looks plausible.
Consider an illustrative homeware retailer that increases its email audience before a launch. Finance sees a higher bill after the launch ends, while marketing has already reduced the audience. The right comparison is the audience definition and service window used for billing, not today’s dashboard. That evidence determines whether the amount follows the agreement.
Investigate unexpected charges
Sort discrepancies into categories before contacting support. A missing approval, an unexplained quantity, an apparent duplicate and a refund that has not arrived need different evidence. Send a precise question with invoice reference, store, dates and expected calculation; avoid attaching unrelated customer exports.
| Finding | First check | Next action |
|---|---|---|
| Same app appears twice | stores and service periods | compare identifiers before escalation |
| Usage is higher | event definition and window | request the supporting report |
| Removed app appears | charge generation date | match against uninstall date |
| Credit is missing | credit type and destination | trace its application |
| Unknown direct debit | supplier identity and contract | investigate through finance controls |
Maintain a discrepancy status: open, explained, awaiting adjustment or closed with evidence. “Support said it is fixed” should not close a financial reconciliation until the agreed correction can be found. A credit for future use and a refund to a payment method have different practical effects.
Separate correctness from value. A valid invoice may still pay for an underused tool. An incorrect invoice does not mean the underlying app should be removed during a trading campaign. Resolve the bill, then consider optimisation through a controlled Shopify support and audit review.
Make cancellation verifiable
Before removing a tool, identify what depends on it: customer forms, product options, scheduled exports, subscriptions, tracking or fulfilment processes. Export required records and agree a replacement where necessary. A finance cleanup should not accidentally interrupt the storefront or erase access to operational history.
Record the cancellation or uninstall timestamp and retain the confirmation. Check whether a separate provider contract exists outside Shopify billing. Follow that contract’s cancellation process rather than assuming an uninstall button terminates every commercial relationship.
Review the next statement for remaining charges and adjustments. Shopify’s guidance notes that previously generated charges can still appear after uninstalling. Match each remaining line to its period, and ask the developer about unexplained items. Do not promise a refund until it has been agreed and verified.
For a trial, assign an owner and decision date at installation. “We will remember to cancel it” is fragile when a launch gets busy. The decision should cover whether the tool passed its acceptance checks, what paid plan would follow and who is authorised to continue the spend.
Run a monthly review
A useful review can be short when the evidence is organised. Finance identifies new or changed lines; the app owner explains usage; the ecommerce lead confirms the business purpose. Escalate exceptions instead of repeatedly debating every unchanged subscription.
Track unresolved discrepancies, unowned subscriptions and cost changes by cause. Report verified adjustments separately from estimated future savings. Cancelling a £50 monthly tool is a projected reduction until the next billing cycle confirms that the charge has stopped.
Keep the review connected to trading plans. Forecast usage before major campaigns, catalogue imports or international expansion. An approved temporary increase is easier to manage than an unexplained surprise. For broader tool selection, use the existing app stack governance guide.
StoreBuilt point of view
The best app budget is explainable. Every material charge should have an owner, a service period and evidence connecting the price to the work being done. Cutting software before establishing those facts can create expensive operational gaps while leaving the original billing question unanswered.
Contact StoreBuilt to map your Shopify tools to their operational owners and plan a controlled review.