Your accountant sends a list of required features. Your finance director compares three platforms. They look identical on the surface: invoicing, expense tracking, reports. One gets implemented. By month three, your team is doing manual workarounds, your tax liability data is fragmented, and you're wondering why you paid for software that fights your actual business. The problem is not that these platforms are bad. They are built for a specific business model—usually product companies with clean revenue lines, single-entity operations, and standard tax jurisdictions. If your revenue is messier than that, the platform won't fit. And you won't know until you're already using it. Here are ten questions that expose the gap between what your accounting software promises and what your business actually requires. 1. Does it split one invoice across multiple tax codes? A retainer invoice for ₹1 lakh covers: ₹70,000 in consulting (GST 18%), ₹20,000 in software (GST 5%), ₹10,000 in reimbursable costs (no tax). Most platforms assume one tax code per line item. They will not let you split a single service line across GST brackets. Your workaround becomes: Three separate invoice lines with manual quantity/pricing math. Risk of invoice formatting confusion when clients review the PDF. GL posting that requires manual adjustment because the system doesn't understand the split. What to ask: "Can I apply two tax rates to a single line item on one invoice?" If the answer is no, or involves creating sub-line items, you will be doing this work manually every month. 2. Does it handle recurring revenue that doesn't renew on a calendar date? Your retainer client signs on March 15. The contract is for 12 months. Their renewal is March 15 next year, not December 31. Most accounting platforms assume subscriptions renew on calendar month boundaries. They build their recurring billing logic around "first of the month" or "end of month." If your contracts live on anniversary dates, the platform will either: Force you into a month-boundary model that doesn't match your contract terms. Require manual invoice creation for each anniversary, defeating the purpose of automation. What to ask: "Can I set a renewal date that is not the first or last day of a month?" If it requires custom fields or manual workarounds, you are managing your recurring revenue in spreadsheets, not your accounting system. 3. Does it validate tax ID rules before you send the invoice? A contractor in Malaysia supplies an NPWP (Indonesian tax ID) on their invoice. Your system accepts it, you issue the invoice, and the contractor's finance team flags it as invalid during their audit. Basic platforms assume all tax IDs are valid if they look like numbers. They don't validate against regional rules. Malaysia uses NRIC or BRN. Indonesia uses NPWP. Singapore uses UEN. Singapore contractors cannot have NPWPs. If your software doesn't know this, your invoices will fail compliance and create friction with clients. What to ask: "Does the system validate tax IDs in real-time against the country I'm invoicing? What happens if I enter an invalid ID?" If it just accepts any 15-digit number, you are liable for compliance errors. 4. Can it issue one invoice with line items to multiple entities in different countries? You deliver a project that spans two companies: your Singapore entity and your Malaysia entity. The client is one entity. One purchase order. But the revenue splits: 60% to Singapore, 40% to Malaysia, both on the same invoice. Most platforms tie invoices to a single entity. You will need to create two invoices, two POs, or do a manual GL split post-invoice. This creates: Reconciliation complexity. One client PO now maps to two of your invoices. Tax exposure. If the split is not documented clearly, auditors will question it. Client confusion. They received a split invoice when they expected one. What to ask: "Can I invoice one client, but split the revenue across two legal entities on the same invoice, with different tax treatments?" If not, ask how the platform handles multi-entity projects. 5. Does it automatically calculate prorated amounts when a contract spans fiscal year boundaries? Your financial year ends December 31. A client contract runs October 1 to September 30 (their fiscal year). You invoice them monthly. The October invoice includes 92 days in your fiscal year (Oct 1–Dec 31) and 8 days in the next year (Jan 1–8). For tax purposes, you need to split revenue across fiscal years. Most accounting platforms don't prorate invoices across year boundaries automatically. You will either: Record the full invoice in one year and adjust via journal entries at close. Manually calculate the daily rate and split the invoice. What to ask: "Does the system automatically identify when a single invoice line spans two fiscal years and split the revenue accordingly?" If not, you are building a spreadsheet model to track this. 6. Can it reconcile invoices that have been partiall