One-customer pilot
Move billing one verified step at a time.
A practical checklist for moving from spreadsheets or another billing tool. Start with one customer, explain the invoice, then validate collection before expanding.
Step 1
Choose one test customer
Start with a representative subscription and a copy of the pricing rules. Use sample data before importing personal or payment information. Define who reviews the results and what counts as a successful pilot.
Step 2
Export and map the current records
Inventory customers, product prices, currencies, subscriptions, renewal dates, usage, outstanding invoices, and credit balances. Keep stable source IDs and a backup. Check the available fields and import route with us before assuming an automated migration.
Step 3
Write down the billing rules
Specify included usage, overage rates, proration dates, discounts, credit order, tax configuration, timezones, and rounding. Compare a manual calculation with the sample workflow, then with a test workspace invoice.
Step 4
Reconcile a full period
Check usage event counts and retry behavior, line items, totals, existing payments, and remaining credits. Re-running an import must not duplicate customers, subscriptions, or charges. Record and resolve every mismatch.
Step 5
Validate collection separately
Use your provider’s test environment where available. Check webhooks, success and failure states, payment reconciliation, and recovery messages. Avoid running two collectors for the same subscription. The website sample never collects payments.
Step 6
Approve the cutover and rollback plan
Pick the effective billing period, confirm which system owns each renewal, preserve the previous records, and nominate a reviewer. Expand beyond the pilot only when both billing and payment reconciliation are understood.
Step 7
Keep an exit path
Verify what you can export from the workspace, including the identifiers needed to reconcile invoices, usage, and credits. Test that export before depending on it. Keep source backups and document how future billing would resume if you stop using Floatless.
Bring one billing scenario
Tell us your pricing model, current tool, and where the calculation gets difficult. Do not send customer records, payment credentials, or sensitive exports through a general contact message. We can agree a pilot and a suitable data-sharing route first.
This checklist is guidance, not a promise of an automated importer or a managed migration service.