Sri Lanka Tax Invoice Format 2481/22: Full VAT Field Mapping for ERP

Businesses searching for the Sri Lanka tax invoice format, VAT invoice format, or Gazette 2481/22 specimen usually want one practical answer: which fields must the ERP produce correctly every time? Gazette Extraordinary 2481/22, dated 27 March 2026, provides a specimen TAX INVOICE layout effective from 1 July 2026, and rescinds the earlier November 2025 specification from that date.

The format is more than a document design. It is a data model for VAT invoicing: supplier identity, purchaser identity, invoice number, invoice date, supply date, taxable line details, VAT amount, total value, optional supply information, and payment method must all come from controlled ERP records—not free-text notes.

This page is Capricon’s field-mapping pillar for Gazette 2481/22. Pair it with the RAMIS VAT e-invoicing Sri Lanka overview when you need API and schedule readiness, not only PDF layouts.

Required invoice header fields

• The document title should clearly read TAX INVOICE in a conspicuous position.
• The supplier section should include the supplier’s 9-digit TIN, name, and address from VAT registration records.
• The purchaser section should include the purchaser’s 9-digit TIN, name, and address where required.
• The invoice date and date of supply should be available in MM/DD/YYYY format.
• The tax invoice number should follow the standardized serial number structure without spaces and within the 40-character limit.

Line and value fields the ERP must control

1. Reference or item identifiers for goods or services supplied.
2. Clear goods or services descriptions that match operational records.
3. Quantity or volume for measurable supplies.
4. Unit price and amount excluding VAT in Sri Lankan Rupees.
5. Total value of supply, VAT amount, and total consideration including VAT.
6. Optional total amount in words and mode of payment where available.

Serial numbers, TINs, and common template mistakes

Most failed VAT invoice audits start with weak master data. TINs typed into a Word footer drift from the VAT registration file. Manual serials collide across branches. Date formats differ between print and PDF. ERP mapping prevents those failure modes by treating the gazetted layout as output—not as the source of truth.

• Never allow blank or duplicate serials at post time; block save if the sequence rule fails.
• Validate 9-digit TIN length and forbid spaces in serial and TIN fields at entry.
• Keep branch or unit codes inside the serial rule if multi-branch retailing needs unique numbering.
• Store supply date separately from invoice date so delayed billing stays accurate.
• Reject mixed taxable and non-taxable lines on a tax invoice when rules require a clean taxable supply document.

ERP mapping checklist

• Map supplier and purchaser TIN fields from master data, not from free-text invoice notes.
• Generate invoice serial numbers from controlled ERP sequence rules instead of manual typing.
• Separate VAT-taxable goods or services from non-VAT items so the tax invoice contains only appropriate lines.
• Keep original invoice, credit note, and debit note references linked for audit traceability.
• Test printed invoice, PDF invoice, email invoice, export file, and API payloads against the same source transaction.
• Confirm VAT schedules and credit/debit notes still reconcile after template changes—see VAT schedules and credit/debit notes.

From tax invoice format to RAMIS e-invoicing

A correct Gazette layout is necessary but not sufficient once invoice and schedule data must move into RAMIS. If ERP fields are inconsistent, Web API submissions fail even when the printed PDF looks right. Use this pillar for field truth, then the RAMIS VAT e-invoicing checklist and RAMIS Web API questions for ERP teams for transmission readiness.

How Capricon Core supports the format

Capricon Core can support Gazette 2481/22 readiness through configurable invoice templates, TIN-aware customer and supplier records, controlled serial-number rules, VAT line calculations, approval workflows, and audit-ready reporting. These controls help finance teams produce consistent invoice data for print, digital sharing, and future integration workflows. See ERP software in Sri Lanka, the RAMIS VAT e-invoicing lander, or evaluate Capricon Core ERP. For a personalised gap list, book the cash & VAT readiness audit or read the retail ERP case study.

As with any tax configuration, businesses should validate final invoice layouts, field rules, and rollout timing against the latest IRD publication and professional tax advice before issuing live invoices.