How to Batch-Generate PND.1, PND.3 & PND.53 Filings in Thailand

If you run an accounting firm in Thailand and handle payroll or vendor payments for multiple clients, manually preparing PND.1, PND.3, and PND.53 filings one by one is a serious drain on staff time. The good news is that batch generation—processing all three form types across multiple clients in a single workflow—is achievable with the right setup. This walk-through covers how Thai accounting firms actually implement it, from data structure through to Revenue Department submission.

Understand What Each Form Requires Before You Automate Anything

PND.1 covers monthly withholding tax on salaries paid to employees under Section 40(1) and 40(2) of the Revenue Code. PND.3 applies to payments made to individuals under other income categories such as service fees, commissions, and rental income. PND.53 covers payments to juristic persons, meaning companies and partnerships, for similar categories of assessable income.

The reason this distinction matters before you automate is that each form draws from different source data. PND.1 pulls from payroll records. PND.3 and PND.53 pull from accounts payable or payment voucher records, filtered by whether the payee is an individual or a juristic entity. If your source data does not already tag payees correctly, batch generation will produce errors across every client, not just one. Fix the data model first.

Standardise Your Client Data Structure

The single biggest obstacle to batch generation is inconsistent data across clients. Before building any automated workflow, you need a unified data schema that every client's records conform to. At minimum, each payment record should store the payee's tax ID or personal ID number, payee type (individual or juristic), income type code as defined by the Revenue Department, gross payment amount, withholding rate applied, and tax withheld.

For payroll specifically, each employee record needs their personal ID, full name as it appears on their ID card, assessable income for the period, cumulative income for the tax year, and the calculated withholding amount. Many firms use a master template spreadsheet or a shared accounting platform to enforce this structure across all clients during data entry. If you are onboarding a new client mid-year, you will also need cumulative figures from the period before they joined your firm, otherwise PND.1 calculations will be incorrect.

Build or Configure Your Batch Processing Workflow

Once your data is clean and structured, you need a system that can read across multiple client datasets and generate the correct form output for each. There are a few common approaches Thai firms use. Some use accounting software with multi-client portals that have built-in withholding tax modules. Others build semi-automated workflows in Excel using structured templates connected to a central data file, with macros that loop through client tabs. More technically advanced firms use scripted solutions that query a database and output the required text or XML files directly.

Whatever the tool, the logic is the same. For each client, the system groups payment records by form type, aggregates by income type code, calculates totals, and maps the output to the correct fields in the Revenue Department's specified format. The Revenue Department's e-Filing system accepts structured text files for PND.1, PND.3, and PND.53 uploads. You can download the official file format specifications from the Revenue Department website. Building your batch output to match these specifications means you can upload directly without re-keying data.

Run Validation Checks Before Generating Final Files

Batch processing amplifies both efficiency and errors. A validation step before final file generation saves significant rework. Build checks into your workflow that flag records where the tax ID is missing or has the wrong digit count, where the withholding rate does not match the income type code, where the tax withheld amount exceeds the gross payment, or where cumulative payroll figures look inconsistent with prior months.

For PND.1 specifically, check that the number of employees on the current month's filing matches expectations relative to the prior month, and investigate any significant variance. For PND.3 and PND.53, verify that every payment voucher tagged for withholding has a corresponding record in the batch output. Running these checks as a separate pass before file generation, rather than hoping the output is correct, is what separates a reliable batch process from one that causes problems with the Revenue Department.

Submit Through e-Filing and Manage Confirmation Records

Thailand's Revenue Department e-Filing portal allows bulk upload of PND.1, PND.3, and PND.53 using the structured text file format. Once your batch files are generated and validated for each client, the submission process involves logging in to the portal under each client's tax account or using agent access if your firm has registered as an authorised tax agent, uploading the file, reviewing the portal's summary of totals before confirming, and retaining the submission receipt reference number.

Some firms manage this step in a submission log, recording the client name, filing period, form type, total tax payable, submission date, and receipt reference for each filing. This log becomes important when clients receive queries from the Revenue Department or when you need to reconcile payments made against filings submitted. If payment is due with the filing, confirm whether the client is paying online through the portal or at a commercial bank, since the deadline is the same but the process differs.

Handle Year-End Reconciliation as Part of the Same Workflow

Batch generation for monthly filings should feed into your year-end process rather than being a separate exercise. For PND.1, the cumulative figures you maintain throughout the year become the basis for the annual personal income tax reconciliation. For PND.3 and PND.53, the withholding tax certificates you are required to issue to payees under Section 50 Bis of the Revenue Code draw from the same payment records.

If your batch workflow has maintained accurate cumulative data per payee throughout the year, generating withholding tax certificates at year end is a further output from the same dataset rather than a new data collection exercise. Firms that treat monthly filings and year-end reconciliation as connected parts of one workflow reduce the risk of discrepancies that clients have to explain to the Revenue Department. Document your workflow clearly enough that any staff member can run the batch process, not just the person who built it.