You've found a invoicing platform that costs half what you're paying now and actually integrates with your CRM. You're ready to switch. Then you mention it to your accountant, and they go quiet. That silence means trouble. Accountants block software migrations for one reason: they fear losing the record trail that tax authorities and auditors demand. A careless switch can orphan invoice records, break your audit trail, or corrupt GST/SST data in ways that cost thousands to fix—or worse, expose you to penalties. The switch is still possible. But it has to start with your accountant, not your spreadsheet. Here are the 12 questions to ask them before you touch anything, the features your new platform must preserve, and how to migrate without creating compliance debt. The 12 questions to ask your accountant upfront Walk through these in a single conversation. Bring a pen. Their answers will dictate which platforms you can actually use. What happens to invoices older than [your cut-off date]? Most accountants will say: keep them where they are. If you're switching now, invoices from 2023 or 2024 often stay in the old system. Your accountant needs to confirm the exact date and sign off on it. This is not negotiable—it's the boundary between a managed migration and audit chaos. Do you need a real-time audit trail, or will a monthly export do? Some accountants need every invoice change logged with timestamps and user attribution. Others can live with a monthly snapshot. This determines whether you need a platform with full audit logging ( platforms like Orin handle this natively ), or whether you can get away with a simpler tool backed by spreadsheet exports. What tax codes and GST/SST rates are live in your books right now? Write them down. Your new platform must support every one of them, and it must apply them the same way. If your old platform rounded GST to the nearest cent but your new one truncates, you've introduced a $0.01 variance per invoice—which compounds and flags on audits. Are there any invoices that are still 'open' for reconciliation or tax adjustments? If an invoice from six months ago is still being disputed or adjusted, you can't move it to the new system yet. Your accountant will tell you which ones are frozen and which are safe to export. Do you need to preserve the original invoice number sequence, or can we restart numbering in the new platform? Some tax authorities in Southeast Asia care deeply about this. Others don't. If you restart and your old invoice 2024-001 becomes 2025-001 in the new system, does that create a gap that auditors will question? Get this in writing. Which invoices need to stay in the old system for tax filing? Some jurisdictions require the original software's proof of submission (e.g., e-Faktur submission receipts or MyInvois validation logs). Your accountant will tell you which invoices have been filed and cannot move. How do you validate that the totals match after migration? This is the first thing your accountant will check. Ask them now: what report do they need from the old system, and what report do they need from the new one, to confirm that revenue, GST collected, and accounts receivable all reconcile to the penny? Do you reconcile invoices to bank deposits or payment records? If yes, your new platform must be able to match invoices to payments the same way the old one did. If the old system used invoice ID and amount, the new one must too—or your accountant's reconciliation breaks. Are there any tax penalties or audits currently open that involve these invoices? If so, don't migrate anything until they're resolved. Moving data during an audit is a red flag. What's your cut-off date for the data export from the old system, and when do you want the new system live? This determines how long you'll run both systems in parallel. Most accountants want at least two weeks of overlap to catch reconciliation issues before the old platform is shut down. Do you use any special fields or custom coding on invoices that the new platform won't support? Some accountants add project codes, department codes, or cost center tags. If the new system doesn't have those fields, ask how to preserve them (often as a memo or description field, but your accountant needs to confirm it won't break their workflows). If we hit a reconciliation error after the switch, what's your process to fix it? Know upfront: can you issue a credit memo in the new system, or do you need to keep the old one running to issue corrections? This affects how aggressively you can move customers over to the new platform. The features your new invoicing platform must have Once your accountant answers those questions, use their answers to audit the new platform. Here's what must work: Configurable tax codes and rates. Your new platform must let you enter every GST, SST, and regional tax code your old one supported. If you're in Malaysia, it must handle Service Tax, Sales Tax, and Regional Sales Tax. If you're in