You run three invoicing tools—or maybe you migrated from one to another six months ago. Your bookkeeper runs a reconciliation report and finds a ₹47,000 discrepancy. Not a rounding error. Not a timing thing. A real, unexplained gap between what your invoicing platform says you invoiced and what your accounting system shows as revenue. This is not rare. It happens because invoicing platforms and accounting software don't agree on how to calculate, round, apply taxes, handle proration, or timestamp submissions. The gaps are silent—no error message, no failed sync, just a number that doesn't match. Here are the five places where invoice totals split, which platforms fail first, and how to audit each one before it becomes a compliance problem. Break 1: Tax code miscalculation across borders Your customer is in Malaysia. You invoice them ₹100,000 for services. One platform calculates SST at 6% (₹6,000). Another applies it to the subtotal before discounts (₹5,400). A third doesn't apply it at all because your tax profile wasn't synced. The culprit: most invoicing platforms let you set a default tax rate, but the sync to accounting software often doesn't include the tax code metadata. Your accounting system then applies its own default rule—which might be GST, not SST, or none at all. QuickBooks + FreshBooks: QuickBooks syncs the line item and total, but not the tax code. If your FreshBooks tax profile is SST and your QB default is GST, they diverge by 0–6% depending on the jurisdiction you select in QB. Xero + Wave: Xero's tax codes sync cleanly to Wave if you use the same tax region. If you mix regions (e.g., invoice Malaysia, book in Singapore), Wave applies its default GST rate instead. Custom API integrations: If you're syncing via Zapier or a custom webhook, the tax code is often lost because most APIs only return the calculated tax amount, not the rule that generated it. How to audit: Pull 10 invoices from your invoicing platform that span at least two tax jurisdictions. For each, note the tax code applied and the calculated tax. Then check your accounting software's invoice record for the same invoice number. If the tax codes don't match, you've found the break. Export both records as CSV and compare the total columns. Break 2: Currency rounding on multi-currency invoices You invoice a customer in USD but your books are in INR. Your invoicing platform converts at the rate of the day: USD 1,000 = ₹83,452. Your accounting software uses the rate from your bank statement: USD 1,000 = ₹83,421. The difference is ₹31—which compounds across 200 invoices to ₹6,200. Worse: some platforms round to 2 decimals, others to 4. If you're syncing totals without the exchange rate metadata, your accounting software rounds again on import, creating a cascade of rounding errors. Stripe + QuickBooks: Stripe rounds to 2 decimals (USD 10.005 → USD 10.01). QuickBooks then applies your default exchange rate on import, rounding again. If Stripe used a live rate and QB uses a manual rate you entered, they diverge. Wise + Xero: Wise provides both the invoice amount and the settlement amount, including fees. If you sync only the settlement amount, Xero recalculates the exchange rate and rounding independently, creating a phantom gain/loss. In-house invoicing + Wave: If you're invoicing in multiple currencies via a spreadsheet or custom tool and exporting to Wave, you're responsible for rounding. A customer invoice might be 5 significant figures; Wave truncates to 2. How to audit: For every invoice in a non-home currency, verify three numbers: the original foreign amount, the exchange rate applied, and the home-currency total. Check these across both platforms. A ₹1–5 variance per invoice is rounding. Anything larger means the rates don't match. Break 3: Midcycle proration and subscription amendments A customer downgrades their plan mid-month. Your invoicing platform prorates the credit correctly: ₹5,000 plan, 15 days used, ₹2,500 credit applied. But proration rules vary wildly. Daily proration: Charge per day actually used. Most accurate; hardest to reconcile if the invoice date and service date don't align. Monthly proration: Some platforms divide annual/quarterly plans by 12 months, creating rounding error on monthly refunds. No proration: A few legacy systems charge the full period regardless. The credit is issued as a separate line item (or never issued). Your invoicing platform might use daily proration; your accounting software might use monthly. The sync pulls the invoice total but not the proration method, so the two systems calculate the credit differently on the next billing cycle. Real example: A SaaS company invoices monthly in INR. A customer cancels on day 15 of a 30-day month. The invoicing platform (Chargebee) credits ₹2,500 for the remaining days. But their accounting software (Xero) applies a different month length for the same invoice month, crediting ₹2,419. The ₹81 gap is invisible until month-end reconciliation. Ho