PT PMA Monthly Tax Close: Withholding, VAT, Payments, and Filing Evidence
A monthly tax return is not ready because a portal draft exists; the transaction population, tax decisions, payments, receipts, and ledger must reconcile first.
A PT PMA monthly tax close should identify which obligations were triggered by the month's real transactions and which were not. Start from payroll, vendor, customer, bank, fixed-asset, expense, related-party, financing, and cross-border populations. Classify each item, then bridge applicable withholding, payroll, VAT, final tax, installments, payments, returns, and official receipts back to the books. A copied calendar cannot determine the company's current obligations without the underlying facts and registrations.
Run an evidence-led month-end close that proves the transaction population is complete, records every tax classification, reviews exceptions, authorizes payments and submissions, and carries unresolved items forward with a named owner and due date. Use the PT PMA compliance calendar to schedule recurring deadlines, then reconcile each completed obligation to the ledger, official receipt, filed return, and retained source evidence.
In this article
Key takeaways
- Start with a complete transaction population, not last month's returns.
- Use separate statuses for calculated, reviewed, paid, filed, receipted, and reconciled.
- Confirm current deadlines and any official transitional relief for the exact period.
- Close every difference or record a controlled exception with an owner and deadline.
Map this month's tax triggers
Reconcile transactions first, then identify withholding, payroll, VAT, final tax, payment, and return obligations.
Build the monthly tax trigger map
Extract the month's general ledger, trial balance, bank activity, accounts payable, accounts receivable, payroll, expense claims, fixed assets, contracts, purchase orders, invoices, credit notes, intercompany entries, and manual journals. Reconcile each source population to control totals. Then tag potential triggers: employee remuneration, services, rent, royalties, interest, dividends, imports, foreign payees, customer advances, taxable supplies, asset transfers, related parties, and transactions with special facilities or final-tax treatment.
DGT's Coretax overview shows that registration, return, payment, audit, and collection processes are integrated. Integration improves visibility but does not create missing vendor data, validate commercial facts, or decide the correct tax article. Build the trigger map from books and source documents, then compare it with the obligations and drafts visible in the tax account.
For each trigger, record taxpayer and counterparty identity, contract and activity, invoice and service period, recognition and payment dates, gross and net amounts, currency, tax basis, classification, evidence, preparer, reviewer, due date, and filing destination. Put missing NPWP or foreign residency evidence, disputed invoices, unmatched bank entries, and late payroll adjustments into an exception queue immediately. Do not postpone classification until the filing day.
| Source population | Tax questions | Control total |
|---|---|---|
| Payroll and benefits | Worker, residency, payment type, period, withholding, annualization | Gross-to-net payroll and ledger |
| Vendors and expenses | Service, rent, final tax, withholding, counterparty identity, timing | AP, expenses, payments, accruals |
| Sales and advances | PKP, taxable supply, invoice timing, output VAT, correction | AR, revenue, cash, invoice register |
| Cross-border and related party | Recipient, treaty evidence, beneficial entitlement, pricing, import or service | Intercompany ledger and bank remittance |
Prepare and review tax workpapers
Create one workpaper per applicable tax stream and a master bridge across all streams. Each workpaper should state the legal entity, period, population source, scope, exclusions, tax classification, calculation, rounding, payment timing, document requirement, draft return line, ledger account, preparer, reviewer, and unresolved items. A zero or nil position needs a reviewed evidence basis; it should not be copied from the previous month without checking current activity.
DGT's official Coretax periodic unified income tax manual explains the operating process for the unified return, while the periodic VAT return manual covers VAT return preparation and posting. Use the current manual for the relevant period, but retain independent review of the underlying legal and factual treatment.
Review by exception and materiality without ignoring qualitative risk. Focus on new vendors, changed contracts, related parties, foreign recipients, unusual descriptions, rounded or repeated amounts, manual journals, negative entries, invoice corrections, missing identities, tax facility claims, off-cycle payroll, director expenses, shareholder funding, and differences from prior months. Document why each exception was cleared or escalated.
Population control
Tie row counts and values from source exports to the ledger and preserve the extraction time and filters.
Technical review
Test classification, base, rate, timing, identity, documentation, currency, return mapping, and current authority.
Management review
Challenge unusual facts, related parties, cash movements, missing evidence, late entries, and business explanations.
Review the filing pack
Test calculations, approvals, billing, bank debit, final returns, official receipts, and ledger mapping.
Authorize payment, filing, and receipt evidence
Separate payment and filing approvals. A tax amount may be calculated but not approved, approved but not paid, paid under the wrong code or period, filed without the payment, rejected, or submitted without a retrievable receipt. The payment pack should contain the approved calculation, billing details, taxpayer identity, tax type, period, amount, bank authorization, debit evidence, and posting. The filing pack should contain the final return, attachments, authorization, submission response, official receipt, and account-status check.
DGT publishes an official tax payment and filing deadline page . Confirm the current rule for each tax type and period, including any specific official relief; do not reuse a temporary extension from another period. Release payments early enough to resolve rejected billing data, bank limits, signatory absence, or system maintenance without assuming a grace period.
Use company-controlled accounts and maker-checker authority. Prohibit personal tax payments or provider-controlled credentials unless a lawful, approved exception is documented and reconciled. After submission, verify the official receipt against the legal entity, tax type, period, amount, and return version. A PDF saved by an agent is not enough if the company cannot retrieve the corresponding status from its own records and account.
Payment gate
Approved tax workpaper, correct billing identity and period, bank authority, debit, and ledger posting.
Filing gate
Final return and attachments, named approver, accepted submission, receipt, and version control.
Failure gate
Rejected payment or filing, preserved error, help request, contingency, new deadline, and corrected evidence.
Reconcile and roll forward the tax close
Complete a post-filing bridge from the final workpapers to payments, returns, official receipts, tax-account balances, and general-ledger accounts. Reconcile tax payable, prepaid tax, input and output VAT, withholding payable, payroll tax, penalties or interest, and suspense accounts. Explain timing differences and clear duplicated, rejected, misapplied, or unmatched items. Lock the close pack only after the ledger posting and evidence references are complete.
DGT's Coretax manual library and account-management features support current service workflows, but the company must retain its own evidence index and access continuity. Review the official manual library when the workflow changes. Preserve export dates, user roles, submission versions, and support correspondence so a later reviewer can distinguish a system issue from an incomplete company process.
Roll forward unresolved items into the next month and the annual return bridge. An exception record should show origin, amount, tax stream, periods affected, temporary accounting, missing evidence, technical question, decision owner, adviser, deadline, planned correction, and closure proof. Connect the close to the PT PMA annual tax return workflow so year-end reconciliation begins with twelve controlled monthly packs rather than a reconstruction.
Ledger bridge
Tie every tax balance to returns, payments, receipts, credits, corrections, and explainable timing items.
Exception roll-forward
Carry open facts, amounts, periods, risks, temporary treatment, owner, adviser, deadline, and closure evidence.
Annual bridge
Aggregate monthly populations and corrections into the year-end trial balance, fiscal reconciliation, and return evidence.
Official references and review basis
The following primary sources were checked on August 1, 2026. They establish the regulatory or service boundary used in this article; bank, tax office, OSS, AHU, and immigration decisions can still depend on the current record and the facts of a particular application.
- DGT — Coretax — Official overview of integrated registration, return, payment, audit, and collection services.
- DGT — Periodic unified income tax return manual — Primary operating manual for the Coretax unified periodic income tax return.
- DGT — Periodic VAT return manual — Primary operating manual for periodic VAT return preparation and invoice posting.
- DGT — Tax payment and filing deadlines — Official deadline reference; verify the exact tax type, period, and any current relief.
The PT PMA monthly tax close release pack
Release the month only when source populations reconcile to the ledger, applicable obligations are mapped to facts, workpapers are reviewed, payment and filing approvals are separate, official receipts are verified, tax accounts and ledger balances reconcile, and every unresolved item has a controlled roll-forward. Portal preparation or provider confirmation alone is not a complete close state.
Confirm current rules and deadlines for the exact period with DGT sources and qualified Indonesian advisers, particularly for foreign payees, related parties, VAT facilities, corrections, and unusual transactions. If the company is still building its full operational control chain, compare tax close readiness with the Indonesia company registration framework .
Close tax exceptions
Assign every missing fact, rejected item, difference, correction, and notice to evidence, advice, owner, and date.
Frequently asked questions
