How to Check VAT Invoice and Record-Keeping Requirements Before Choosing an Invoicing System in Sri Lanka

When establishing an invoicing process in Sri Lanka for the first time, a business should not compare systems only by price or user interface. It should first confirm whether the system can support the VAT invoice information, approval controls and traceable records required for its business activities.

A system that produces a well-formatted invoice does not necessarily mean that the underlying process will meet the documentation needs of tax filings, customer verification or a later audit. For foreign businesses, a more prudent approach is to have the business, finance and appointed tax advisers confirm invoicing scenarios and documentation rules first, then configure the system, user permissions and archive process around those requirements.

MMD Business Support may assist with requirements mapping, coordination of local resources and introductions to licensed professional firms. Specific tax assessments, filing requirements and professional opinions should be provided by appropriately qualified professionals.

Separate system capability from tax treatment

Before selecting an invoicing system, businesses should distinguish between what a system can do and what the business is required to do.

Tax-related assessments may include the business's current VAT registration status, the goods or services it intends to sell or provide, the location of its customers, how prices are presented, the timing of invoice issuance, and whether particular transactions or industries involve special requirements. These matters should not be decided solely from a software demonstration or another company's template. They should be confirmed with the appointed tax adviser and relevant authorities.

System configuration questions are different. They include whether required fields can be set up, whether separate templates can be used for different transaction types, whether amendment records are retained, whether data can be exported, and whether supporting documents and approval records can be linked to the underlying transaction. The business should prepare an internal requirements list before asking vendors to demonstrate each item, rather than accepting a general statement that the product “supports VAT invoices”.

Create an invoicing scenario list

Before reviewing systems, list the transactions the business expects to undertake. For each scenario, identify who initiates the transaction, who reviews it, when the invoice is issued, and which documents need to be linked.

Useful starting scenarios include:

• Sales of goods to local business customers;
• Services provided to local customers;
• Services provided to overseas customers or receipts from overseas;
• Advance payments, instalments or project milestone payments;
• Discounts, rebates, refunds or price adjustments;
• Corrections required because customer details, quantities or prices are incorrect;
• Intra-group charges, management fees or cost allocations; and
• Transactions where a distributor, agent or platform collects payment on the business's behalf.

For each scenario, the business should record at least the source contract or order, customer details, delivery or service evidence, payment method, person responsible for invoicing, reviewer, related documents and archive location. If the same business has goods sales, service income and cross-border income, its system should distinguish between transaction types rather than applying one template and one approval path to all income.

Check VAT invoice fields and numbering controls

The information that a VAT invoice should contain, and whether particular wording or numbering arrangements are required, should be confirmed against the latest guidance from the relevant authority and the appointed tax adviser. During demonstrations and testing, businesses should focus on the following capabilities:

Review item	Questions to ask the system vendor
Business and customer details	Can the system maintain business name, address, tax identification details and customer information, while retaining a record of changes?
Invoice numbering	Does it support sequential numbering, configurable numbering rules, retention of cancelled numbers and alerts for numbering irregularities?
Transaction details	Can it clearly show descriptions of goods or services, quantities, unit prices, discounts and transaction dates?
Tax display	Can it display amounts, tax amounts and totals according to the confirmed tax treatment?
Currency and exchange-rate records	For foreign-currency transactions, can it retain original currency amounts, conversion information and supporting documents?
Invoice status	Can it distinguish between draft, pending approval, issued, sent, corrected and cancelled statuses?
Document output	Can it produce readable invoice documents while retaining the original system data and generation time?

Numbering controls are particularly likely to cause problems where invoices are prepared manually, multiple sales teams issue invoices in parallel, or the business is changing systems. Businesses should avoid allowing users to overwrite issued invoices freely, delete historical invoice numbers or amend final versions offline. Where manual invoicing or a backup process is needed, the business should define in advance the activation conditions, registration method, person responsible for subsequent system entry and review steps.

Do not overlook approval trails and correction procedures

For a business entering Sri Lanka for the first time, the main risk is often not whether an invoice can be issued. It is whether, in the event of a dispute, customer non-payment, internal audit or tax review, the business can explain why an invoice was issued, who approved it and whether it was later changed.

The system should ideally retain at least the following audit trail:

1. The creator, creation date and source documents for each invoice draft;
2. The approver, approval comments and approval time;
3. The invoice recipient, delivery method and sending time;
4. Field-level differences before and after an amendment, together with the person making the change and the reason for it;
5. Linked records for cancellations, corrections, refunds or credit-note treatment; and
6. Links or attachments connecting the invoice to the contract, order, delivery evidence, customer confirmation and payment record.

If an invoice needs to be corrected, cancelled or adjusted through a credit note, the business should not rely on simply deleting the original invoice. Before go-live, it should confirm the applicable document, approval and record requirements with its tax adviser, then build those rules into system permissions and operating guidance. For correction, cancellation and credit-note processes after issuing an initial VAT invoice, businesses may also refer to the published article, “After Issuing Your First VAT Invoice: How to Establish Correction, Cancellation and Credit Note Procedures”.

Design an archive structure that can support verification

Record-keeping is not simply saving PDFs on an employee's computer. The objective is to ensure that the business can locate a complete, readable and connected evidence trail when needed. A consistent filing structure can be organised around “transaction — invoice — delivery — payment — adjustment”.

An archive package for a transaction may include:

• Approved contracts, quotations, purchase orders or customer confirmations;
• Customer entity information and relevant tax documents;
• The original invoice and system-generated records;
• Delivery notes, acceptance documents, service reports, project milestone confirmations or other delivery evidence;
• Payment evidence, bank-statement matching records and explanations of differences;
• Internal approvals and customer correspondence relating to discounts, refunds, corrections or credit notes; and
• Accounting records and filing support for the relevant period.

The business should also clarify who stores electronic records, who may access them, who may delete them, how departing employees' accounts are handled, and how historical data will be migrated and accessed if the system changes. Archive periods, acceptable electronic record formats and retention requirements should be confirmed with the relevant authority and appointed professionals. Software default settings should not be treated as sufficient evidence of compliance.

Run a “contract to archive” test before go-live

Once a system has been selected, it is generally preferable not to use a real customer's first invoice as the test case. The business can use several simulated transactions covering expected situations such as local sales, service fees, advance payments, discounts and corrections. Sales staff, finance personnel, approvers and external advisers can then review the workflow together.

Key testing questions include:

• Starting from a contract or order, can the basis for invoicing be identified?
• Do invoice fields match the confirmed business and tax treatment?
• Can approvers view the necessary attachments in the system?
• After an invoice has been issued, can ordinary users alter or delete it without an audit trail?
• After payment is received, can it be linked to the relevant invoice and can any difference be explained?
• If a correction is needed, can the original record be retained and a clear adjustment trail created?
• Can finance staff export review data by period, customer, invoice status and transaction type?

After testing, the business should prepare a concise invoicing procedure, permissions matrix and exception-handling checklist. The system vendor is responsible for explaining product functionality; management is responsible for internal-control design; and the tax adviser is responsible for professional advice on applicable requirements. These responsibilities should be clarified at the start of the project.

Official information and review recommendations

Businesses can review publicly available tax information through the official website of Sri Lanka's Inland Revenue Department: https://www.ird.gov.lk/. For VAT registration, invoice content, filing, record retention or special transaction treatment, businesses should rely on the latest views of the relevant authority and appointed licensed professionals, and retain internal confirmation records.

This content is provided for general information only and does not constitute legal, tax or immigration advice. Specific requirements should be confirmed with the relevant Sri Lankan authorities and appointed licensed professionals.