WhatsApp has become the de facto sales channel in Indonesia. Your team quotes customers there, closes deals there, and sends invoices there. But the moment you invoice on WhatsApp, you've crossed into regulated territory—and Indonesia's tax authority (LHDN) has specific rules about NPWP matching, e-Faktur submission, and what audit trails you must keep. If you get this wrong, your invoices get flagged, payment doesn't settle, and you spend weeks correcting records that regulators have already questioned. This is not theoretical. Indonesian resellers and agencies are already running into rejection chains: invoices rejected because NPWP doesn't match the sales record, e-Faktur submissions blocked because the WhatsApp conversation lacks a date timestamp, and audit queries because no one can prove the customer agreed to the tax treatment on the invoice. The pattern is the same across all of them: they did not validate tax identity at the point of sale. Why NPWP Validation at Point-of-Sale Stops Rejection Chains NPWP (Nomor Pokok Wajib Pajak) is Indonesia's tax identification number. It's mandatory on every invoice. The rule sounds simple until you realize that a customer may have multiple tax IDs, may use a different NPWP for different business lines, or may register one NPWP but operate under a different one for your contract. When the NPWP on your invoice doesn't match the NPWP in LHDN's system for that customer, the e-Faktur submission fails silently or triggers an audit request weeks later. The only way to prevent this is to validate the NPWP against LHDN's registry the moment the customer confirms it. Not after the invoice is sent. Not after the payment clears. At the point of sale, when you're still in the conversation. What validation means in practice: Ask for NPWP in the WhatsApp quote or order form—not as a field buried in a follow-up email. Check it against LHDN's real-time lookup API (most Indonesian accounting software integrates this; your CRM should too if you're invoicing in-region ). Flag mismatches immediately: wrong format, not found in LHDN, or registered to a different business name. Log the validation timestamp and result in the deal record. This becomes your audit trail. Do not proceed to invoice until NPWP is validated. A customer says "my NPWP is 12.345.678.9-012.345." You copy it into the validation tool. LHDN returns: found, registered to PT Maju Jaya Abadi, active status, last filed 2024. You log this in your deal notes with a timestamp. Now when you submit the e-Faktur later, the NPWP and business name match what LHDN expects. No silent rejection. No audit question. If the NPWP doesn't validate (wrong digits, not registered, or mismatch), you ask the customer to correct it or confirm with their accountant before you invoice. This costs you 10 minutes now and saves you weeks of back-and-forth later. E-Faktur Submission Rules: What WhatsApp Invoices Must Include An e-Faktur is not just an invoice. It's a legally binding tax document that must be submitted to LHDN within a specific window (usually within 30 days of issuance, but rules vary by invoice type and business classification). Indonesia's tax authority does not accept screenshots of WhatsApp conversations or forwarded PDFs as proof of issuance. They expect structured data submitted through approved channels—usually through your invoicing software's integration with the e-Faktur system. Here's what often goes wrong: a team sends an invoice on WhatsApp (good). The customer pays (good). Then, when the accountant sits down to file e-Faktur, they realize the PDF doesn't include a proper issue date, the customer's full registered name doesn't match what's in LHDN, or there's no line-item breakdown. The e-Faktur submission fails. The accountant has to ask the sales team to re-issue the invoice, but by then the payment has already been banked under a different date, and reconciliation breaks. What your WhatsApp invoices must contain to submit as e-Faktur: Customer NPWP (validated at point of sale, as above). Customer full legal name exactly as registered with LHDN (not a shortened version, not a trading name). Seller NPWP and legal name (your own, on every invoice). Invoice issue date in YYYY-MM-DD format, never ambiguous. Line items with item code or description , quantity, unit price, and tax treatment (taxable, exempt, or zero-rated). No lump-sum invoice without breakdown. PPN (Value Added Tax) calculated and itemized . Indonesia's standard rate is 11%, but some items are exempt or zero-rated. Do not guess. Grand total including PPN and any withholding tax (PPh). Payment terms and due date , if not immediate. Invoice number in a sequential format that your system tracks (no gaps, no duplicates—LHDN flags these). If you're issuing invoices directly from WhatsApp (e.g., a PDF sent through the app), you must ensure that the PDF generator or invoicing tool embeds all of these fields. A generic invoice template that lacks PPN detail or u