Your accountant flags it in month three: the total invoiced in your billing platform doesn't match the revenue recorded in QuickBooks or Xero. You pull a report from each, and the variance sits somewhere between 2% and 8%—enough to derail a tax filing, too small to pinpoint without digging into transaction-level logs. The culprit is rarely a bug; it's a silent data divergence across seven handoff points where invoicing and accounting platforms make different decisions about what counts as recorded revenue. We've audited hundreds of these reconciliation gaps across small teams using standalone invoice tools synced to accounting platforms, and the pattern is always the same: the platforms agree on simple, one-off invoices but diverge on edge cases—tax calculation timing, payment application logic, multi-currency conversion, proration, refunds, and recurring adjustments. Each platform has its own ruleset, and each ruleset is invisible until you run a line-by-line audit. This guide maps those seven sync points and gives you a monthly audit script to catch divergence before your accountant does. 1. Invoice Creation Date vs. Revenue Recognition Date The first split happens before any payment even hits. Most invoicing platforms record revenue the moment you mark an invoice "sent." Most accounting platforms recognize revenue on the invoice date field—which may or may not be the same as creation date. The gap: If you create an invoice on the 28th but postdate it to the 1st of the following month, your invoicing platform's "monthly revenue" includes it; your accounting platform's monthly P&L does not. Over a year with 50+ invoices, this can shift month-end revenue by 3–5%. The audit: For each month, pull invoices created in that month and invoices dated in that month as two separate lists. Compare the totals. If they differ by more than 0.5%, you have a dating mismatch. Set a rule: always invoice on the date you expect payment to start, or use a separate "invoice date" field distinct from creation date. 2. Tax Calculation: Amount Ex-Tax vs. Inclusive This is the most common silent failure. You have an invoice for ₹10,000 plus 18% GST. Your invoicing tool calculates tax as ₹1,800 and records the line as "₹10,000 + ₹1,800 tax." Your accounting platform's import rule interprets the same CSV row as "₹10,000 gross, calculate tax from that"—so it computes ₹1,526 tax on the assumption the ₹10,000 is already inclusive. The invoice total drifts by ₹274. Worse: if your invoicing tool supports both exclusive and inclusive tax on the same invoice (common in SE Asia with SST/GST mixed goods), and your accounting platform only recognizes one or the other globally, you'll get mismatches on mixed-tax invoices. The audit: Pull 10 invoices with tax from each platform. For each, calculate: recorded gross amount in invoicing tool vs. recorded gross in accounting tool. If they differ by more than the rounding error (usually ±₹1), you have a tax calculation divergence. Check your sync settings: most platforms let you specify "tax inclusive" or "tax exclusive" on the import. Make sure both platforms use the same assumption. 3. Multi-Currency Conversion: Exchange Rate Timing You invoice a US client ₹10,000 USD on the 15th. Your invoicing platform locks in today's rate (say, 83.5) and records revenue as ₹835,000 INR. Your accounting platform, if it syncs on the 20th after the bank holiday, uses the RBI rate on that day (say, 83.2), and records ₹831,000. The difference compounds across 20+ foreign-currency invoices per month. If you have invoicing configured to net multi-currency amounts (total USD, then convert to local), but your accounting platform imports as individual line-item conversions, the rounding errors compound further. The audit: For all multi-currency invoices in a month, pull the exchange rate used by the invoicing tool vs. the rate recorded by the accounting tool. Calculate the variance as a percentage of total foreign revenue. If it exceeds 0.3%, you need to lock an exchange-rate snapshot date: either invoice in local currency only, or freeze rates at month-end and reconcile actual bank rates later. 4. Proration: Invoice-Level vs. Line-Item Timing You have a 3-month contract at ₹30,000 starting mid-month. Your invoicing platform prorates the first month as ₹10,000 (1/3 of the full month, rounded to the nearest rupee). Your accounting platform, if it syncs individual line items, may round at the line level instead—resulting in ₹10,001 or ₹9,999. On 50 prorated invoices, that's ₹25–50 of noise. Worse: if your invoicing tool prorates from the start date but your accounting platform prorates from the invoice date, you'll have systematic divergence on all subscriptions with a gap between signing and invoicing. The audit: Pull all prorated invoices (usually subscription-based or usage-based). For each, calculate the proration manually: full monthly amount × (days in period / days in month). Compare your calculation to both the inv