When an accountant opens a client's books and sees unmatched invoices piling up, they already know the next four hours are gone. The invoice amount doesn't reconcile. The tax code is wrong. The payment applied three weeks late and split across two line items. No amount of coffee fixes this. We spoke with 10 accounting practitioners—bookkeepers, controllers, and tax advisors—about their top three pain points with client accounting software. The same three landmines appeared in nearly every conversation. None of them are new. All of them are preventable. Landmine One: Rounding errors that cascade across currency and tax When an invoice crosses a currency boundary or a tax calculation, small fractional amounts appear. Most accounting software rounds these automatically. The problem: no two platforms round the same way, and when they don't match the vendor's invoice, the reconciliation breaks. A bookkeeper we spoke with handles 60 invoices a month for a tech startup that buys software subscriptions in USD, EUR, and GBP. The accounting platform rounds to the nearest cent on currency conversion. The vendor's invoice system rounds at a different step. By month-end, she has 12–15 invoices with ₹2–₹5 discrepancies. None of them match. She manually adjusts each one—a process that takes 90 minutes per month. Here's what happens next: she creates a penny-rounding account, posts the difference manually, and makes a note. This works. It also creates a hidden expense category that no one can audit without calling her. Scale this to 40 clients and a firm spends 60 hours a month on rounding reconciliation. The fix before you hire: Ask the vendor: where does your platform round? Before or after tax? Before or after currency conversion? Test with a sample: load 10 multi-currency invoices with tax. Export the posting. Compare line-by-line to the vendor PDF. Check the audit trail: can you see where the rounding happened and reverse it if needed? Verify that small discrepancies (under ₹1) can be written to a separate account automatically, not orphaned as unmatched. Landmine Two: Tax code mismatch between invoice and GL posting An invoice arrives with one tax code. The accounting software applies a different one—either because it auto-guesses based on the vendor category, or because a user misselected it before posting. The invoice amount matches. The GL posting matches. But the tax reconciliation doesn't. The tax advisor calls, the bookkeeper digs, and 90 minutes later you find that 30 invoices posted to the wrong tax code. We interviewed a tax advisor in Malaysia who audits three clients monthly. In each firm, she finds 2–4 invoices where the GST code doesn't match the invoice header. Some are GST-exempt services posted as standard-rated. Others are reverse-charge invoices posted to the regular intake account. None of them were caught during entry because the amount matched. The tax report is now wrong, and she has to file an amended return. The root: most accounting platforms let a user apply any tax code to any transaction, with no validation against the invoice. They assume the human got it right. They didn't. The fix before you hire: Can the platform enforce tax code by vendor type? (e.g., no standard-rated tax on GST-exempt vendors.) Does it warn if the tax code on the invoice doesn't match the account default? Can you run a pre-post tax code audit report? Mandatory approval workflow? Test by deliberately entering the wrong tax code. Does the software block you or warn you? Landmine Three: Payment application delays that orphan matched invoices A payment arrives. The software matches it to an invoice. But the payment posts two days later—or sometimes after the month-end close. During the gap, the invoice shows as unpaid in the aging report, but the cash is already gone from the bank. The reconciliation looks broken even though it isn't. An accountant has to manually verify that the payment is in transit. One bookkeeper handles receivables for a services firm. Invoices go out. Payments come in three days later via ACH. The software matches payments to invoices at the same time it posts the cash—but the posting delay is a day. For three days every cycle, 20+ invoices show as unpaid even though the cash cleared the bank. She gets calls from the sales team asking why invoices aren't marked paid. She has to explain that the match is pending. It creates noise and looks like a reconciliation error even though it's just timing. The real cost: when payment matching delays, accountants manually mark invoices as paid before posting, or they skip the match entirely and post cash in a separate workflow. Either way, you lose the audit trail between invoice and cash receipt. When your invoicing system doesn't sync payment status in real time , this gap widens. The fix before you hire: Can the platform match invoices to payments in a pending state before the payment posts to cash? Does it show the expected payment date and an alert if a