Client Billing Without Chargify: A Complete Cutover

Managing coaching client billing without Chargify starts with the obligation already agreed, not with recreating the original product in another checkout. Identify the buyer, the total commitment, money already received, services still owed and the next collection that can actually occur. Then choose a destination that supports those requirements without leaving two systems entitled to collect the same balance.

Coachful is our #1 recommendation for coordinating the coaching relationship, selected service records and client communication around a simpler billing arrangement. This is our editorial workflow recommendation, not a measured market ranking or a claim that it replaces specialist billing, accounting or revenue-recognition controls. A deliberate external invoice authority can remain part of the workflow.

Understand what you would be replacing

Chargify's billing capabilities are now part of Maxio. Maxio's official login identifies Advanced Billing as formerly Chargify, separately from its financial-operations product. Its owner guidance describes fixed recurring, usage-based and more complex rated pricing. A practice that actually needs those capabilities should compare them carefully rather than treating a coaching portal as an equivalent metering system.

A coach with a small set of stable services may need a simpler arrangement. The relevant question is whether the change preserves the controls the business uses while making the client's obligation easier to understand. Lower software cost alone does not establish a worthwhile migration; include lost reporting, manual work and transition risk.

Do not assume every Maxio customer needs custom development or that every coach should move. Inventory actual dependencies, including tax workflows, refunds, disputes, exports and finance integrations. A decision to retain the specialist system for one business line and simplify another can be reasonable.

Develop five billing distinctions before changing systems

1. Package commitment versus a renewal

Three payments of £600 can settle a fixed £1,800 package. They can also look like an ongoing £600 subscription if the implementation is wrong. The label “monthly” does not settle which arrangement the client bought. Write the total, number of payments, dates and service period together.

When migrating after two installments, the remaining collectible balance may be £600, not the original £1,800. Copying the original product price can create a second demand for money already paid. Conversely, canceling a collection mechanism does not automatically waive a legitimate balance. Reconcile the contract and actual transactions before deciding what to request.

If it is an ongoing service, define what the next renewal buys, notice requirements and unused delivery treatment. Do not convert a finite package into a renewal without a new agreement, or imply that a billing-system change determines consumer rights.

2. Invoice authority versus payment evidence

An invoice requests payment; a receipt acknowledges it. GOV.UK explains that distinction and the conditional UK VAT business-to-business invoicing requirement. Its invoice guidance identifies required information, with additional business-form and VAT considerations. Requirements depend on the actual jurisdiction and transaction.

Choose one authoritative document workflow for each amount owed. If an external accounting system issues the final invoice, a supporting CRM entry should not become a second invoice or collection request. Preserve the external identifier, currency, payment date and relevant transaction reference so another person can reconcile the records.

Check actual document output before relying on a note field. Coachful's native invoice PDF recipient block uses the selected recipient's name and email. An internal note does not establish that a buyer's company address, purchase order or bespoke commercial wording appears in that PDF. Use a supported document authority that actually includes the required fields.

3. A cancellation request versus collection having stopped

Maxio's current cancellation guidance distinguishes scheduling a future cancellation from its taking effect. Existing issued invoices are not automatically removed; scheduled timing also needs checking against the site's billing clock. Do not treat a saved future cancellation as proof that no old collection can still occur.

Inspect open invoices, pending attempts, unbilled usage, credits, refunds and disputes. The relevant product configuration may require additional handling. An end-of-period cancellation is not a universal refund or proration mechanism, and canceling mid-period does not settle an existing invoice.

Create a release condition for the new payment request: the old balance and collector are reconciled, the relevant recurring collection has actually stopped and any exception has an owner. If evidence is missing, hold the new request. A delayed migration is preferable to sending a client two competing demands and hoping to repair them later.

4. Money received versus delivery owed

A successful transaction does not prove that the agreement is signed, an appointment is booked or the correct resource is available. Likewise, four sessions delivered do not tell you whether the first two installments settled. Keep separate money and delivery records and reconcile them at a defined review.

For a finite package, calculate remaining sessions from the actual agreement and service history. Do not grant the whole original package again while moving a final balance. A payment-only CRM record is not an entitlement grant. Existing appointments may remain manually reserved under the service agreement.

If a client pauses or the coach cannot deliver, apply the relevant agreement and obligations to both money and service. Dividing a payment by sessions after the fact does not establish the correct refund. Retain the client's rights and seek appropriate professional advice for an uncertain case.

5. Gross receipts versus bank cash and profit

Provider transaction totals, fees, refunds and payouts answer different questions. Check actual settlement identifiers and bank records rather than assuming a “paid” status means cash has reached the bank. A transfer instruction or screenshot also needs reconciliation with receipt.

Keep currency units consistent. A payment entered in GBP is not evidence of conversion from another currency, and a displayed fee estimate is not the final fee. Use observed amounts for the reconciliation and state what is excluded.

Bank cash after processing fees is still not profit. It may precede bookkeeping costs, software costs, service delivery, tax and drawings. A migration case with one client cannot establish typical processing rates, a market price or a permanent administrative saving.

Test the cutover before releasing a new request

Use four release checks: the remaining amount agrees with the contract and settled receipts; the old collection has actually ended; the destination document requests only that balance in the agreed currency; and the payer has received usable instructions. Test an error deliberately, such as a draft retaining the original package price. Identify who can hold release and who can correct the authoritative record. Keep the incorrect draft out of the client-facing route. If a check fails, record the exception and a next review rather than treating a partially configured destination as ready.

A complete fictional final-installment migration

Jay Mercer coaches Elle Sato under a fixed agreement, reference JM-ES-2054. The total is £1,800 for six sixty-minute sessions during April–June 2054, paid in three £600 installments. This is a finite commitment. The names, account references, dates, amounts and observations are invented teaching examples, not real account actions or recommended prices.

Elle's first two £600 payments settle on 1 April and 1 May. Four sessions are delivered on 7 and 21 April and 5 and 19 May. The remaining two appointments are reserved for 8 and 22 June, 10:00–11:00 London time. The service record therefore shows four delivered and two still owed; the money record shows £1,200 received and £600 outstanding.

On Tuesday 26 May, bookkeeper Theo spends thirty minutes on the opening cutover account: twenty checking the records, five documenting and five sending the result to Jay. Jay uses twenty minutes reading it and reviewing the transition. Theo confirms that this example has no metered usage, advance invoice, unpaid old invoice, credit balance, dispute or refund awaiting action. That is a checked case condition, not an assumption about every subscription.

Obtain the payer's actual agreement

On 27 May, Jay spends fifteen minutes preparing and sending this transition notice to Elle, copying Theo for the billing administration:

Your fixed package remains £1,800, with £1,200 received and £600 left. We propose replacing the final automatic collection with one external invoice for £600, payable by bank transfer on 4 June after Theo verifies the old collection has ended. The two June appointments remain reserved. We will check funds received by 5 June at 17:00 before confirming that the 8 June appointment goes ahead. This does not create a renewal or change your other agreement terms. Please tell us whether this payment route and date work for you.

Elle spends ten minutes on 28 May reading and replying: “I can use bank transfer by 4 June. I do not want another recurring card setup. Please confirm that this is only the remaining £600 and that my June appointments have not been sold again.”

On 29 May, Jay uses ten minutes to read her reply and send the agreed confirmation: “Yes. It is the final £600 of JM-ES-2054. There is no new package or renewal. The same two appointments remain reserved, with the 5 June funds check described above.” Jay copies Theo on that confirmation. Elle spends five minutes reading it and sending her acceptance to Theo. Her agreement to a bank transfer is not permission for an unrelated future charge.

Hold the destination until the old route is closed

After that acceptance, Theo uses fifteen minutes on 29 May to read the final instruction and Elle's acceptance, schedule the old subscription's end-of-period cancellation, and save its status in the cutover record. The status still describes a future change. He does not mark the old route stopped or release a replacement collection that day.

On Monday 1 June, Theo spends ten minutes inspecting the actual subscription, invoice and transaction records. In this fictional observation, the cancellation has taken effect and no new June charge or invoice was created. He records that evidence. It is the observed result that releases the replacement invoice, not a promise that every UI-scheduled cancellation executes at a precisely chosen minute.

If he had found an issued invoice or pending payment, the release condition would have failed. He would first resolve that specific position, including any supported void, settlement or refund handling. The example does not establish that cancellation erases issued debt or that a payment method can be moved between providers.

Catch a real preparation error before issuing the invoice

On Tuesday 2 June, Theo uses ten minutes for five two-minute steps: build a draft, compare it with the cutover account, correct it, repeat the check and send the final invoice. The first draft copied the original £1,800 package price. The comparison catches that it would demand £1,200 already paid. Theo changes the draft to the remaining £600 and checks it again before sending. Elle never receives that erroneous draft.

The issued external invoice JM-2054-003 identifies Jay's actual business and Elle as the buyer using their checked legal details. It describes the final installment of JM-ES-2054, identifies the relevant service period, states £600 due on 4 June and carries the agreed bank-payment instructions. Theo checks the applicable invoice and tax treatment for this fictional transaction; this is not a complete reusable tax-invoice template or a claim that coaching is universally VAT-exempt.

Elle's ten-minute invoice and transfer block covers reading the issued invoice and instructing the £600 transfer on 4 June. She does not re-enter card details, purchase another offer or pay a second invoice. Stored card data is not copied into messages, notes or spreadsheets.

Retain the delay and separately confirm delivery

The bank records the £600 received on Friday 5 June. That is one day after the 4 June payment date, so the late receipt remains in the account. Elle uses five minutes checking her bank confirmation. Theo spends ten minutes reconciling the received amount and reference to JM-2054-003.

The separate 5 June, 17:00 funds check succeeds. Theo spends five minutes sending Elle and Jay a paid notice at 14:00: “£600 has been received against JM-2054-003. The package balance is now zero. The funds condition for 8 June is met; the same 8 and 22 June appointments remain in place.” Elle spends five minutes reading and briefly replying that she understands; Jay spends five minutes reading. No further acknowledgment is claimed.

The missed payment date and successful service-funding check are different results. Neither changes the other retrospectively. There was no duplicate charge, no refund and no new authorization to renew.

Record the actual receipt in Coachful

Theo has authorized payment access to Elle's client record. Within a separate ten-minute block on 5 June, he opens the manual recording dialog and chooses All settings if Record type is hidden. He selects Payment log, described as CRM only, no receipt, and records £600 GBP, paid date 5 June, bank transfer, and the description “JM-2054-003, final installment JM-ES-2054.” His internal note references the external invoice and bank receipt record.

This logs money already received. It does not create another invoice, send a receipt, request a new payment, grant sessions or mark an external invoice paid automatically. The paid state and authoritative invoice remain in the external accounting system. The first £1,200 is not entered again as new revenue; anyone viewing only this CRM payment must not mistake £600 for the whole package's receipts.

For a different engagement, a configured native Offer may be appropriate. Check the actual price, currency and included items in What they get. A template can prefill session-access defaults, including a builder-provided session type; that is not proof that the saved quantity or type matches the promise. Do not create a new full-price checkout merely to make an existing client visible in the portal.

Use Coachful's features for the connected coaching workflow. The billing and invoicing guide develops document authority, and the session-allocation guide covers delivery allowances. The payment log in this case performs neither a new sale nor automatic entitlement migration.

Close money and delivery with an actual summary

The two June sessions occur on 8 and 22 June as reserved. Jay spends sixty minutes in each and twenty minutes per session preparing and writing internal notes. Elle attends both sixty-minute sessions. Together with the four earlier sessions, all six agreed sessions have been delivered; no further session is owed under this package.

On 24 June, Theo spends ten minutes on the final reconciliation, including reading Elle's existing paid-notice reply. Jay spends ten minutes reading the reconciled position and composing/sending the final client summary. It states £1,800 total received, zero remaining balance, six of six sessions delivered and no continuing subscription. Elle spends five minutes reading and replying, “That matches my record. I am finishing this package without a new booking.” Jay spends five minutes reading that reply. No renewal or outcome testimonial is inferred.

The observed £36 fee is a fictional statement amount, not a processor rate recommendation. The £1,764 is before other costs, tax and drawings, so it is not profit. Historical records and the new external invoice remain available under the practice's appropriate retention arrangements; ending collection does not justify deleting unresolved financial history.

Include the receiving and reconciliation work

The following account covers 26 May–24 June, including the two remaining sessions. It counts reading, sending and client receipt as active work rather than treating an entire period as uninterrupted editing. Existing April–May delivery is shown separately below.

This interval totals 485 person-minutes against 540 reserved, leaving 55. The four earlier sessions add 480 person-minutes across Jay and Elle, with eighty minutes of Jay's preparation/notes and twenty recorded minutes of earlier payment handling, split ten each between Elle and Theo. The known time across the described history and cutover is therefore 1,065 person-minutes. Original setup time and wider practice overhead are not measured here; the account is not a whole-business cost or ROI estimate.

Frequently asked questions

Should every coach leave Chargify or Maxio?

No. Keep a specialist system when its actual metering, finance or subscription controls are needed. Compare a simpler destination against those requirements and the full transition work.

Does scheduling cancellation stop every old payment?

No. Inspect the actual effective state, issued invoices and pending transactions. A future cancellation is not current closure, and existing invoices may need separate handling.

Can a Payment log replace an invoice?

It records an actual receipt in the CRM. It does not create an invoice or send a receipt in payment-only mode. Keep the chosen document authority and reconciliation reference clear.

Can payment details be copied to the new system?

Use a supported provider-led transfer where available, or a secure new authorization if required. Do not copy card numbers into ordinary records. This example deliberately uses an agreed bank transfer.

What if the client has paid more than the remaining service?

Calculate the actual position from the agreement, delivery and applicable obligations. Do not assume a session-count ratio alone determines a refund or that canceling billing resolves the service commitment.