Reconcile Singapore Import GST Permits in NetSuite

Use the permit as import-tax evidence and trace how its amount enters the books.

Why do the supplier bill, Customs permit and agent statement show different amounts for the same shipment? Each document answers a different question: what was bought, what was declared for import and what the agent is collecting. Reconcile them together before deciding how import GST appears in NetSuite.

IRAS requires an eligible import input-tax claim to be supported by a permit showing the business as importer, together with the relevant supporting evidence. Its guidance also requires reconciliation where the supplier invoice value differs from the import permit. That difference may be legitimate, but it needs an explanation.

For a NetSuite finance team, the main control is a shipment-level evidence pack that links each permit tax amount to its accounting representation and checks whether the same tax has entered through more than one route.

Begin with the valuation boundary

Singapore import GST is not necessarily a percentage of the supplier's invoice converted at the ERP book rate. Customs valuation can include freight, insurance and other relevant charges. Duties, when applicable, also affect the GST base. Particular arrangements, reliefs or schemes require their own assessment.

Ask the import or logistics owner to identify the declared valuation basis and its supporting documents. Finance should be able to distinguish the goods price, relevant transport costs, Customs conversion evidence and any other adjustments. Do not make the ERP supplier bill the default explanation for every permit value.

The accountant should also distinguish tax recovery from inventory costing. Review freight and other cost allocation through the separately approved landed-cost process. A landed-cost calculation does not independently prove that an import-tax claim is eligible or that its permit has been recognised only once.

Trace one illustrative shipment

The following shipment and values are fictional. The example assumes ordinary non-dutiable goods, no special relief or suspension scheme and no additional valuation adjustments. It is a reconciliation exercise, not a declaration or a prescribed accounting entry.

Shipment SHIP-041 has an overseas supplier invoice of USD 10,000 with no Singapore GST charged on that invoice. The illustrative NetSuite book-conversion input is SGD 1.34 per USD, giving a goods amount of SGD 13,400.

For this exercise, the permit evidence shows goods valued at SGD 13,500, plus SGD 800 freight and SGD 200 insurance. The total declared taxable value is SGD 14,500. At the assumed 9% GST rate, import GST is SGD 1,305. The SGD 13,500 goods value is a supplied fictional permit input; it must not be taken as a real Customs rate determination.

The difference between the permit value and the book-converted supplier goods amount is SGD 1,100:

• SGD 100 difference in the goods valuation.
• SGD 800 freight included in the permit basis.
• SGD 200 insurance included in the permit basis.

Those components add to SGD 1,100. The working paper should attach the underlying evidence for each component in a real shipment. A mathematical bridge is useful, but it cannot validate an incorrect declaration.

Now suppose the declaring agent's statement requests reimbursement of the same SGD 1,305 import GST. It also contains a separate illustrative service fee of SGD 100 and SGD 9 GST on that service. The statement total is SGD 1,414.

The SGD 1,305 reimbursement points to the tax already evidenced by the permit. It should not become a second import-tax claim merely because it appears on another document. The separate SGD 9 service tax has its own invoice and eligibility review. Its treatment must not be assumed from the import permit.

Build a permit, bill and tax-account pack

Use one reconciliation cover sheet per shipment or other defensible matching unit. Where one shipment has several permits or a permit covers several invoices, retain a one-to-many mapping rather than forcing a one-to-one match.

The pack should contain:

1. Commercial evidence: supplier invoice, purchase reference and relevant shipping documents.
2. Permit evidence: permit identifier, importer identity, permit date, declared value and SGD GST.
3. Valuation bridge: differences between commercial value and permit value, with source evidence and import-owner explanation.
4. Accounting map: related NetSuite bills, receipts, tax entries or other approved records, each identified by its actual reference.
5. Payment or agent evidence: records explaining how import GST was paid or reimbursed and how any service fees were treated.
6. Review decision: eligibility, period, unresolved discrepancies and the person authorised to resolve each one.

These are proposed working-paper fields. They do not assert a native NetSuite Customs connector or a standard screen that automatically builds the pack. The technical team must demonstrate the chosen references, attachments or controlled external reconciliation in the actual account.

Use the tax amount to expose duplicate recognition

For SHIP-041, the permit supports an import GST amount of SGD 1,305, subject to the claim conditions. Suppose a provisional accounting extract shows two entries tagged as recoverable import GST, each for SGD 1,305: one from the permit process and one from the agent-bill process.

The comparison is SGD 2,610 in the provisional extract against SGD 1,305 of permit tax, leaving a potential duplicate of SGD 1,305. This is a review finding. The controller must inspect the entries and approve any correction through the supported process; the worksheet should not automatically reverse whichever entry arrived last.

Conversely, if the extract contains zero import GST while the permit shows SGD 1,305, investigate the period, posting route and eligibility. Absence from the selected account could reflect an unposted item, a different approved treatment or a filter error. It is not sufficient evidence to create another tax entry immediately.

The reconciliation should identify the remaining difference after approved actions, not merely mark the documents “matched”. Preserve the original extract and the correction evidence so a later reviewer can explain the movement.

Separate three decisions at sign-off

Is the declaration supported? The import owner explains the valuation and identifiers. A wrong importer name or incorrect declared value needs the applicable correction process. Do not solve a Customs evidence problem by relabelling an ERP field.

Is the tax claim eligible and in the correct period? The tax owner checks the conditions, supporting permit and documents, and applicable period. A permit alone does not establish every input-tax condition. Retain unresolved eligibility questions instead of presenting all permit tax as automatically recoverable.

Is the accounting recognition complete and unique? The controller traces the approved representation to the books and checks agent reimbursements, separate service tax and any corrections. One payment can settle several components with different supporting evidence.

There is also a separate InvoiceNow boundary. Current IRAS guidance lists import permits for goods among the data not required to be submitted under the GST InvoiceNow Requirement. That exclusion does not remove the need to retain import evidence or satisfy GST reporting obligations. Any separate supplier or service invoice requires its own scope assessment.

For the next implementation review, choose a shipment where the invoice, permit and agent statement all differ. If finance can explain the value bridge, establish the claim evidence and identify one approved recognition of the import GST, the pack is doing useful work. If any of those answers is missing, assign the precise discrepancy before closing the period.