Link4 Integration Guide - Malaysia (MY)

Link4 Integration Guide - Malaysia (MY)

Idea
Technical Requirements & Mandatory Data

🎯 Purpose

This guide explains the mandatory technical and data requirements for organizations integrating with Link4 to send and receive electronic invoices.

Before integration, ensure your ERP, Accounting System, or Middleware can supply all required data.

Missing or incorrect information may cause:

  • Invoice rejection

  • Validation errors

  • Delivery failures with Peppol or the Inland Revenue Board of Malaysia (LHDN)

1️⃣ Supported Integration Method

API Integration

Your system connects securely to Link4 via API.

Requirements

  • API endpoints provided by Link4

  • OAuth or API key authentication

  • Valid JSON payload structure

  • Data validation compliance

2️⃣ Supported Transaction Types

Document Type
Description

Invoice
Standard commercial invoice
Credit Note
Reduces/cancels the invoice
Debit Note
Increases the payable amount
Self-Billed Transactions
The buyer issues transactions on behalf of the supplier
Other
By agreement

Every document MUST include:

  • Header data

  • Supplier details

  • Buyer details

  • Line items

  • Tax information

3️⃣ Contact Data (Customers & Suppliers)

Accurate contact data is mandatory for:

  • Routing (Peppol)

  • Tax validation (LHDN)

  • Delivery notifications

3.1 Mandatory Fields (Per Contact)

FieldRequired
Legal name✅
Email (active)✅
Full address✅
TIN✅
SST numberIf applicable
MSIC code✅
Business activity description✅

Applies to BOTH customers and suppliers

3.2 Optional

  • Address line 2

  • Contact person

  • Secondary email

  • Internal reference/ID

3.3 How to Provide Contact Data

Option A – API

  • Unique identifier per contact

  • Return all mandatory fields

  • Prevent duplicates

Option B – CSV Upload

  • All mandatory columns included

  • Unique reference column required

  • Format confirmed by Link4

4️⃣ Tax Information

All tax data must follow Malaysian regulations and Peppol rules.

Mandatory (Header Level)

  • Supplier TIN

  • Buyer TIN

  • Currency = MYR

  • Tax basis

5️⃣ Line Item Requirements

Each document must contain at least one valid line item.

5.1 Mandatory Per Line (STRICT – LHDN)

  1. Line number
  2. Item description
  3. Quantity
  4. Unit of measure
  5. Item classification
  6. Unit price
  7. Line subtotal
  8. Tax rate
  9. Tax amount
  10. Tax category code
  11. Exemption reason (if 0%)
  12. Exemption reference (if applicable)

5.2 Optional

  • SKU/Product code

  • Discount

  • Delivery date

  • Service period

6️⃣ Document Header Requirements

Mandatory

  • Unique document number

  • Issue date (YYYY-MM-DD)

  • Due date

  • Document type

  • Supplier full details

  • Buyer's full details

  • Currency

  • Tax exclusive amount

  • Total tax amount

  • Tax inclusive amount

  • Order reference / Purchase Order Number (if applicable)

Optional

  • Buyer reference

  • Contract/project reference

  • Payment terms

  • Bank/payment details

  • Internal notes (if allowed)

7️⃣ API Integration Standards

Authentication

  • Secure credentials (OAuth/API keys)

  • Read & write permissions

Data Coverage

Must support:

  • Header data

  • Line items

  • Tax details

  • Contact lookup via unique ID

System Behaviour

  • No duplicate documents

  • Clear HTTP errors

  • Stable identifiers for retries

8️⃣ Validation & Submission

All documents are validated against:

  • Peppol specifications

  • LHDN e-Invoice rules

  • Other authority requirements

Possible outcomes if the data is invalid:

  • Rejection

  • Validation errors

  • Delivery failure



    • Related Articles

    • Understanding General TIN Usage for E-Invoicing in Malaysia

      As part of the Inland Revenue Board of Malaysia's (IRBM) e-Invoice framework, businesses are required to include a Tax Identification Number (TIN) for both buyers and suppliers in their e-Invoice submissions. However, there are cases where specific ...

    • MY - Link4 Product Guide

      Link4 Integrated Solution 1️⃣ Product Features 1️⃣ Dashboard The dashboard offers a concise summary of financial activity, displaying both incoming and outgoing funds over the last 30 days. Users can easily track: Invoices Purchases Credit Notes A ...

    • LHDN Guidelines on Country Codes

      Country codes are used to supply precise country information when providing address information as part of the document submission. Country codes used in documents are following ISO-3166 alpha-3 approach. Country codes are also used for the “Country ...

    • 📢 Release Note - 25/08/2025 - UI & Invoice Status Enhancements

      Release Date: 25/08/2025 Audience: All Malaysian Users ? Update Overview We have enhanced the Invoices Dashboard UI to provide a clearer view of invoice routing and statuses across LHDN, Peppol, and Email delivery layers. This update simplifies ...

    • 📝 Release Note: Purchase Review Workflow – Accept & Reject (29-05-2025)

      ? Feature: Accept & Reject Buttons for Purchases We’re excited to introduce the Purchase Review Workflow featuring "Accept" and "Reject" buttons. This enhancement streamlines the invoice approval process and aligns with LHDN’s e-Invoice validation ...