You close the month, reconcile invoices to accounting, and find a $1,200 discrepancy. One software says revenue is $287,450; the other says $286,250. You've checked for duplicate invoices, spotted no obvious transaction gaps, and your team swears nothing was deleted. The problem isn't missing data—it's transformed data. Seven specific handoff points between invoicing and accounting platforms eat precision in ways that don't show up until you're deep in month-end. 1. Tax code mismatches on the same invoice line Your invoicing tool lets you pick from twenty tax codes. Your accounting software recognizes twelve. When a sync runs, the unfamiliar code gets mapped to a default—usually "tax exempt" or "other." The invoice total matches, but the tax component diverges. Real example: Pipedrive allows "GST (10%)" and "GST (15% local)". QuickBooks Online only knows "GST (10%)". One $1,000 invoice line syncs at $1,150 (with 15% applied in Pipedrive) but posts to QuickBooks at $1,100 (10% applied as the nearest match). The $50 difference spreads across hundreds of lines over a quarter. Where to audit: Pull a sample of ten invoices from each tool in your accounting software's tax report. Compare the tax amount line-by-line, not just the invoice total. If an invoice shows $100 tax in invoicing but $85 in accounting, a code mismatch is your culprit. 2. Rounding rule divergence across multi-line invoices One tool rounds tax per line. Another rounds tax per invoice. A third applies rounding only if the total exceeds a threshold. On a three-line invoice with 7% tax, the differences stack: Line 1: $100 × 1.07 = $107.00 (rounded) Line 2: $200 × 1.07 = $214.00 Line 3: $150 × 1.07 = $160.50 Per-line total: $481.50 Aggregate then round: ($100 + $200 + $150) × 1.07 = $481.45 Over 500 invoices, this 0.01–0.05 cent gap per invoice compounds to $50–$250 drift. Accounting flags it as a reconciliation error; invoicing shows a clean, synced number. Both are technically correct—they just disagree on when to round. Where to audit: Export the same invoice from both tools. Calculate tax line-by-line in invoicing, then invoice-level in accounting. If the tax component differs by more than a cent, your rounding order is misaligned. Document the rule in each tool and pick one standard for all new invoices. 3. Multi-currency conversion timing gaps You invoice a Singapore client in SGD on the 15th at an exchange rate of 1 SGD = 0.92 USD. Your invoicing tool records the USD equivalent: SGD 1,000 = USD 920. The sync runs immediately. But accounting waits until month-end to pull actual rates from your bank feed. On the 28th, the rate is 1 SGD = 0.94 USD. The same invoice now shows as USD 940 in accounting. The $20 difference is real, but it's a timing gap, not a data gap. If you have fifty multi-currency invoices per month, conversion timing can swing your monthly revenue by $500–$1,000 depending on currency volatility. Where to audit: Set a policy: lock exchange rates at invoice creation date in both systems, or both use month-end spot rates. If invoicing freezes rates on invoice day and accounting updates them on month-end, your sync will always show drift until the accounting entry is reversed and re-posted with the correct rate. Document this in your reconciliation template and account for the expected variance. 4. GST/SST application order—inclusive vs. exclusive pricing You invoice RM 1,000 (inclusive of 6% SST) to a Malaysia client. One tool backs out the tax: RM 1,000 ÷ 1.06 = RM 943.40 (base) + RM 56.60 (SST). Another applies tax to the stated amount: RM 1,000 (base) + RM 60 (SST) = RM 1,060. Your invoicing tool shows revenue of RM 1,000; accounting shows RM 943.40 or RM 1,060 depending on how it interprets the sync. This gap widens across invoices because it's systematic: every invoice is off by the same percentage error. Xero typically handles inclusive tax cleanly; Zoho sometimes struggles if your sync tool doesn't explicitly set the "inclusive" flag on each line item. Where to audit: Pull five paid invoices. In your accounting software, reverse-calculate the base amount: if the invoice line shows "RM 1,000 inc. tax," the base should be RM 943.40 and SST should be RM 56.60. Check invoicing: does it match? If invoicing shows RM 1,000 and accounting shows RM 943.40 on the same invoice, your sync isn't honoring the inclusive flag. This is common in Pipedrive-to-Xero integrations if the sync map doesn't explicitly set tax treatment. 5. Discount application timing and sequence A discount can apply before tax or after tax. Most regions apply it before. Some locales apply it after. If your invoicing tool applies discounts before tax and your accounting software applies them after, the effective tax amount changes: Invoice subtotal: $1,000 Discount (10%): -$100 Invoicing (discount before tax): ($1,000 - $100) × 1.10 = $990 Accounting (discount after tax): ($1,000 × 1.10) - $100 = $1,000 On a 500-invoice month with an average 5% discount, this di