An AI contract tool is seductive. You feed it a deal summary, it spits back 15 pages in 10 minutes, and for a moment you think: that's it, paralegal work automated. Then you hand it to a lawyer, or worse, you sign it, and you find gaps that cost you later. Not small gaps. Ones that shift liability, expose you to regional tax penalties, or leave payment terms loose enough to trigger disputes. We tested AI contract drafting against real-world enterprise and SMB deals across Southeast Asia and found three categories of systematic failures. None are the AI's fault exactly—they're baked into how language models work. But they're predictable, and they're avoidable if you know what to look for. Gap 1: Tax indemnification and withholding clauses get templated, not negotiated AI will generate an indemnification clause. It will look fine. It will probably reference "breach of representations and warranties" and "third-party claims." What it almost always misses: the tax indemnification bucket. Here's the bind: in Malaysia, Singapore, and Indonesia, if you engage a contractor or vendor and don't withhold tax correctly, you get hit with the penalty—not them. The tax authority doesn't care that the contractor was supposed to handle it. You're the payor, you're liable. An AI contract will have a standard indemnity. It won't have a clause that says: "Contractor indemnifies Client for any withholding tax obligations, penalties, or interest arising from Contractor's failure to register with [LHDN / ACRA / DGT] or provide required tax documentation." It won't specify what tax documents you need before payment clears. It won't address what happens if the withholding certificate arrives late. Regional specificity breaks AI. It doesn't know that Malaysia's LHDN has different rules than Singapore's ACRA, or that Indonesia's e-Faktur system gates invoicing before payment. So it generates a generic template, you sign it, and six months later an audit flags unpaid withholding. What to check: Does the contract name the specific tax authority (LHDN, ACRA, DGT)? Does it specify what tax documents you need and by when? Does it say who bears the cost of late or missed withholding? Does it address what happens if the vendor is unregistered when you pay? Gap 2: Regional withholding language stays vague or missing entirely Malaysia requires a "Request for Relief at Source" (RAS) or withholding certificate before you can reduce withholding below the statutory 3%. Singapore has different rates for different vendor types. Indonesia's withholding is tied to e-Faktur status. An AI tool trained on generic English-language contracts will not know any of this. What you'll usually get: "Contractor shall comply with all applicable tax laws." That's not a clause. That's a liability time bomb. It pushes the burden onto the contractor without specifying what they have to do, when , or what happens if they don't. The practical result: you withhold money, the contractor says you shouldn't have, no one has a clear contract to point to, and you're stuck negotiating mid-payment or bleeding cash to refund disputed withholding. What to check: Is the withholding rate tied to a specific tax authority rule (e.g., "3% per LHDN Circular 1/2024")? Does it name what documents prove withholding eligibility (e.g., "valid NPWP and Certificate of Relief at Source")? Does it say who applies for relief and by what deadline? Does it account for different rates if the vendor type changes? Is there a fallback if documents don't arrive on time? Gap 3: Payment terms stay fuzzy on currency, timing, and contingencies AI is allergic to precision. It will write: "Invoice due 30 days from invoice date." That sounds clear until you need to know: 30 calendar days or business days? Invoice date or receipt date? Which timezone, if both parties are remote? In which currency? What happens if you dispute a line item—do you hold the whole invoice or just that line? Cross-border deals in SEA multiply the ambiguity. A Malaysian vendor invoices in MYR but your accounting is in SGD. The contract says "30 days" but doesn't specify settlement currency or FX timing. One party assumes payment on invoice date, the other assumes 30 days from when they receive it. Cash flow forecasts diverge by weeks. AI will generate a "Payment Terms" section that reads like every other contract template. It won't capture: Currency lock: Is the rate locked on invoice date, payment date, or settlement date? Who absorbs FX swings? Timing precision: "30 days" from what, exactly? Is it calendar or business days? Which calendar (Malaysia, Singapore, client's country)? Partial payment rules: If you dispute $500 of a $5,000 invoice, do you hold the whole thing or just the disputed amount? Late payment: What interest applies? Is it compounded daily? Which country's interest rate law? Delivery contingency: Do you pay on invoice, on delivery, or on acceptance? What triggers acceptance? Each gap seems small until cash flow pre