How to Replace Expense Spreadsheets and Shared Cards

Replacing expense spreadsheets is not a row import. Shared cards, personal reimbursements, recurring suppliers, approvals, receipts, and accounting records may represent different obligations in one file. The migration must assign identity and ownership before software becomes authoritative.

Buyer scenario: one shared card has no stable owner

Imagine a company where several employees use one card, write purposes in a spreadsheet, and send receipts by email. One recurring supplier belongs to a departed employee, a personal reimbursement remains unpaid, and a refund is expected after cutover.

List every card, bank or payment rail, reimbursement process, recurring supplier, travel account, and accounting upload. Assign entity, current owner, business purpose, approver, evidence, and successor. Do not create named cards until current issuer eligibility and user rules are verified.

Create a decision log for data cleanup. Link every employee merge, supplier rename, dimension mapping, duplicate removal, and status conversion to source rows and an approver. Automate only visible, reversible rules. Ambiguous items should enter quarantine with an owner rather than inheriting guessed purpose or payment status so the import can appear complete.

Inventory secrets and physical assets separately from transactions. Shared card credentials, stored merchant profiles, unused checks, receipt archives, and travel accounts need controlled transfer or retirement. A clean spreadsheet import does not close these access paths.

Reconcile employee obligations before and after cutover. Produce an approved list of unpaid claims, rejected claims, advances, excess repayments, and failed payments. Give employees a clear status and contact path during transition. Do not close the prior workflow until each amount has a designated system and owner. This prevents a technically successful migration from shifting unresolved personal cash out of view while company card transactions receive priority.

IRS Publication 463 offers general travel and expense context. Data migration cannot establish tax treatment or accountable-plan qualification.

Decision criteria for migration-ready records

Clean employee identity, entity, department, manager, supplier, project, ledger dimensions, currencies, approval status, reimbursement status, and receipt links. Distinguish company-funded charges from amounts owed to employees. Quarantine ambiguous or duplicate records rather than guessing.

Create a mapping log for every transformation and approver. Inventory recurring card credentials, cancellations, refunds, disputes, and open authorizations. Define source of truth and retention for original spreadsheets and receipts.

Reproducible migration evaluation and rehearsal

Build a representative extract containing shared-card charges, personal claims, missing receipts, duplicate supplier names, an open refund, a departed employee, and invalid dimensions. Transform with documented rules and import into a nonproduction environment.

Run approval, reimbursement, refund, offboarding, and accounting-rejection scenarios. Export and reconcile back to approved source records. Repeat by fixing the transformation, not through hidden manual edits. Spend Management Guide has not executed a buyer migration; teams should rehearse their own data.

Edge case: transactions continue during cutover

Use a freeze or delta log for new card settlements, claims, reimbursements, refunds, and recurring charges. Assign one owner to sequence them and prevent duplicate replay. Keep open employee obligations visible throughout.

If a shared credential cannot be retired immediately, document temporary access, monitoring, replacement date, and successor rather than pretending migration is complete.

Ask a reviewer outside the migration team to trace several opening items back to original evidence. If that person needs private transformation notes, the mapping and retained history are not yet sufficient for cutover.

Conclusion: migrate accountable ownership

The new platform should begin with named users, governed suppliers, separated payment rails, clean dimensions, controlled open items, and retained source evidence. Resolve or quarantine ambiguity before import. A smaller trustworthy opening set is better than a complete spreadsheet copied into new screens. Migration succeeds when finance can explain the first close and employees know where every outstanding reimbursement stands.