Keep historical SaaS invoices usable after changing billing platforms

Identify the invoices, credits, receipts and payment allocations needed to explain each customer's account. Preserve the original issued documents together with structured data linking them to the customer and service period. An opening balance alone cannot answer why an older invoice was reduced, when it was paid or which agreement it covered.

Ask accounting and the appropriate advisers to confirm retention and access requirements for the business. Then define how the archive will meet those needs. Keep the scope concrete: which document types, which periods, which attachments and which users need access. A vague instruction to export everything can still miss linked credits or leave files impossible to search.

Keep the original invoice number and source-system identifier on archived records. Choose the destination's numbering configuration with the relevant local requirements in mind. Stripe supports customer-level or account-level schemes and configurable future numbering; changes to those settings do not rewrite existing invoices.

Check for collisions between old and new numbers before go-live. A readable source or entity reference in the archive can help distinguish documents where numbering overlaps. Avoid recreating historical paid invoices as new collectible bills just to populate a portal. Any import representation should be reviewed for its effect on receivables, customer messages and reporting.

Select a customer with several invoices, a partial payment and a credit. Ask someone who did not perform the migration to retrieve the original invoice, explain the remaining balance and locate the adjustment. Record where the process fails. A folder of PDFs may preserve documents while still being unusable for account reconciliation.

For illustration, a customer might ask for the invoice paid by a transfer six months before migration. The archive should support a search from the payment reference or customer account to the allocation and document. If that relationship exists only in the old interface, export the necessary mapping before access ends.

Decide whether customers retain access to the old portal, use a new archive or request documents through support. Communicate the arrangement clearly where it affects them. Verify that only authorized people can retrieve a customer's documents and that links do not depend on the personal account of the employee who ran the export.

Give support a short retrieval procedure with the relevant account mapping and escalation owner. Test a customer who has changed its billing contact since the original invoice. Access to current service should not automatically expose historical invoices to a person whose authority has not been established through the business's normal process.

Compare document counts and totals with the source exports by period and document type. Investigate missing attachments, unreadable files and records without customer references. Sample links between invoices, credits and payments, because a matching total does not prove the relationships survived. Keep the final export date and any subsequent changes documented.

Only then confirm the ongoing access arrangement with the system owner. Retain an accountable owner for the archive, its permissions and future retrieval tests. The migration deliverable should leave finance able to explain an old customer balance and support able to provide the correct document without depending on the migration team's memory.