Indonesian VAT (PPN) reporting is unforgiving in exactly the places a standard Business Central install is silent. A Faktur Pajak needs a controlled Nomor Seri Faktur Pajak (NSFP) drawn from the range DJP allocated to your NPWP, in strict sequence, with no gaps you cannot explain. It needs the buyer's NPWP/NIK, address and transaction code carried correctly onto the document. It needs a DPP and PPN calculation that survives rounding to whole rupiah, prepayments, freight and discount lines. And when a document is rejected or the customer's data was wrong, it needs a formal replacement or cancellation that leaves the original visible, not overwritten. Business Central out of the box gives you VAT posting setup, a VAT statement and document number series — none of which model an externally allocated tax invoice serial, a kode transaksi, or the correction lifecycle. Teams end up rekeying posted invoices into a spreadsheet or the DJP application, and the ERP and the tax filing quietly drift apart.

What ECOSIRE builds is an AL extension for your Business Central tenant that treats the e-Faktur record as a first-class object beside the posted sales invoice. An E-Faktur Setup page holds your NPWP, branch codes, default transaction and status codes, rounding policy and export destination. E-Faktur Serial Range tables record every NSFP block DJP issued, with a low-watermark warning and a hard stop when a range is exhausted, so you never post past your allocation. Table extensions on Customer, Sales Header and Sales Invoice Header carry NPWP/NIK, buyer type, transaction code and the assigned serial; page extensions surface them where the finance team already works, and validation runs through event subscribers on OnBeforePostSalesDoc so a document with a missing NPWP or an invalid code is stopped before it posts, not discovered at filing time.

One posting produces both outputs. A codeunit builds the machine format — the DJP CSV/XML layout your filing route requires, structured to your current e-Faktur schema and validated field by field before the file is written — while a Report object renders the human-readable Faktur Pajak PDF, so the document you hand the customer and the record you file are generated from the same posted lines and can never disagree. Master data mapping is table-driven, not hardcoded: item and G/L mappings, unit-of-measure translation, currency handling and DPP Nilai Lain rules live in setup tables your accountant can maintain. Batch export runs from a Job Queue Entry on your VAT period cadence, or on demand from a filtered E-Faktur Worklist page.

Rejection handling is the part most spreadsheet workflows get wrong, so it is modelled explicitly. Each e-Faktur record carries a status — Draft, Exported, Approved, Rejected, Replaced, Cancelled — and a rejection reason returned from your filing route. A Replace action generates the correction document under the correct replacement code with a link back to the superseded record, and the archive keeps both. Every state change, serial assignment, export and reprint is written to an audit log table with user, timestamp and file hash, and archived export files are retained under your policy so a DJP audit can be answered from Business Central rather than from someone's Downloads folder. Dedicated permission sets separate who may assign serials, who may export and who may cancel. Everything is reachable over API pages (REST API v2.0 / OData v4) if you want Power BI reporting or a Power Automate flow watching for rejected documents in Dataverse.

This is build-to-order, not an AppSource download. We start with a scoping call, confirm your Business Central version and deployment (SaaS or on-premises, current release wave), your filing route, your existing customisations, and the exact document layouts and codes you use. From confirmed scope, typical delivery is one working week: we build the extension against your version, deploy it to your sandbox for UAT with your own data, run the correction and rejection paths with you, then install to production behind a rollback plan. You receive the AL source, the git repository, technical and user documentation, a training session and a post-go-live support window.