Trusted by national to multinational businesses, Insimen meets the needs of legality, certification, and cross-sector compliance with a neat and professional process.
Coretax DJP is increasingly able to integrate tax and taxpayer transactions data into a single administrative system.
Finance Minister Purbaya Yudhi Sadewa said that the system is being improved to collect, match, and process data more accurately. The government has placed technology and data utilization as an important part of its strategy to expand the acceptance base without relying on tax rate increases.
However, the term transaction recording needs to be understood in proportion. Coretax does not automatically look at all the private activities of the public.
Coretax is designed to unite the various processes that were previously spread across a number of applications, linking registration, payment, SPT reporting, issuing tax invoices, proof of deductions, taxation services, checks, to billing.
DJP explained that such integration could improve data analytics capabilities. Tax information that is in one system environment can be processed to support more targeted service, monitoring, and decision-making.
The matching mechanism can be seen when two companies make transactions. For example, PT A purchases services from PT B for Rp100 million. PT A records the payment as a cost, while PT B should acknowledge it as income.
If the transaction has a tax deduction obligation, PT A must also produce proof of deduction.
The system can also match the proof of the cut, tax invoice, VAT Period SPT, tax credit, as well as payments related to the transaction.
Disputes may arise as a result of returns, cancellations of transactions, differences in revenue recognition times, identity errors, or recording errors.
Coretax DJP has an automated data-filled feature known as prepopulated. Through this feature, certain information can appear in the SPT design without having to be re-typed by the taxpayer.
The data may be from PPh deduction or collection evidence, tax invoices, third party reported transactions, as well as previous reporting history. Income and tax credit information may also appear if the income provider has made the deduction evidence using the correct taxpayer identity.
However, automatic data does not remove the taxpayer's liability. Each taxpayer must always check whether the information in the SPT is correct, complete, and in accordance with the actual conditions.
Errors can still occur if the counterparty to the transaction uses the wrong NPWP, publishes double-cross proof, lists the wrong transaction value, or is late in correcting.
The ability to link data makes Coretax help DJPs identify discrepancies faster. The system can identify links between turnover, tax invoices, proof of deduction, tax payments, and third-party data.
The DPA also uses risk analysis to determine the priorities of surveillance. Special inspections can be performed when there are indications of non-compliance based on concrete data or the results of risk analysis.
The system may provide a mark when the turnover in the Annual SPT is different from sales recorded through tax invoices.
The difference can also be seen when a company records a large amount of service costs, but no evidence of appropriate tax deductions is found.
In addition, the DPI can compare the SPT for the period to the annual SPT. If sales in the VAT report do not match the income in the financial statements, the company needs to explain the cause of the difference.
The marking may also include transactions with affiliates, tax credits without supporting documents, tax payments that do not match the business profile, as well as incompatibilities between purchases and inventory.
The Director-General of Taxation previously stated that the prepopulated feature could identify and combine data on taxpayer transactions.
The signals that appear in the system do not automatically become a Letter of Request for Explanation on Data and or Details.
The SP2DK is a letter to ask for taxpayer explanations of data or evidence indicating the possibility of a non-fulfilment of tax obligations. The letter is not a tax regulation and is not a decision directly requiring payment.
Where explanations and supporting documents can prove that the tax liability has been properly met, data differences do not always result in additional taxation.
Statements regarding transactions recorded in Coretax do not mean that taxpayers can open the entire balance and mutation of public accounts freely.
The DJP once asserted that Coretax is not a system for opening balances and account mutations.
Funds entered into corporate or individual accounts do not always constitute taxable income. These funds may come from capital deposits, shareholder loans, repayment of loans, interbank transfers, deposits, or replacement of expenses.
A company may also receive funds from the sale of assets, which will be taxed according to the type of assets, book value, sale price, status of the parties to the transaction, and applicable tax terms.
Therefore, the analysis cannot be based solely on the presence of incoming funds. The officer should look at the nature of the transaction, the relationships of the parties, legal documents, accounting records, and the treatment in the SPT.
The company needs to separate the receipts from the capital transactions or loans. The shareholder's deposits should be supported by the company's decisions, transfer proof, accounting records, and capital change documents if necessary.
The company should have an agreement that explains the value of the loan, the term, the purpose of use, the terms of repayment, and interest when applicable.
The DJP may receive data and information from government agencies, institutions, associations, and other parties in accordance with regulations, such as business activities, business circulation, income, or taxable wealth.
In 2026, the government issued PMK No. 8 Year 2026 which updated the provisions on the submission of tax data. The rules adjust the details of the data as well as the procedures for providing information to the DJP to support the interests of the state's admission.
Other party data serve as a comparison. For example, reports from employers can be compared to employee income. Supplier data can be compared to company purchases. Meanwhile, customer cut evidence can be compared to the income of the recipient of payments.
In this context, the quality of identity becomes important. An incorrect NPWP, NIC, company name, or business activity identification number can lead to documents entering the taxpayer's profile in an incorrect manner.
The development of Coretax increases the need for companies to maintain data consistency. Financial reports, Annual, Periodic, Tax invoices, proof of deduction, and tax payments should all describe the same transactions.
Differences may not necessarily indicate violations, but companies should be able to explain the reasons for any differences quickly and with verifiable documentation.
Companies need to match their turnover in the financial statements with the revenues reported in the Annual VAT return.
The difference can occur because not all income is an object of VAT.
Reconciliation is also required on the cost side. Companies need to match the cost of services, rent, royalties, interest, and other transactions with the proof of cut that has been published.
For example, a consultant's fee of Rp500 million may result in a PPh cutting obligation.
On the contrary, the receiving company needs to ensure that all the cutting evidence published by the customer has been recorded as income or as part of the transaction that can be explained.
Documentation is a major defense when there are data differences: contracts, invoices, tax invoices, proof of cut, newspaper accounts, news, proof of receipt, and business correspondence must be kept in a structured manner.
The company also needs to document transactions with shareholders, directors, and affiliates. Withdrawals of company funds by directors should be recorded according to their nature, for example as salaries, dividends, loans, advances, or replacement of costs.
Withdrawals without registration may raise questions, and the officer may need to know the purpose of the funds, the recipients, the basis of the transaction, and the tax treatment.
In addition, companies should reconcile each month. Monthly checks help to find errors before entering the Annual SPT and before the different data come to the attention of the DJP.
If material errors are found, the taxable person may consider correcting the SPT as provided for in the provisions.
Coretax DJP did not create a new type of tax on all public transactions. The system reinforced administration, data matching, and oversight of obligations already set out in the tax regulations.
The main change lies in DJPs' ability to connect data faster, and as a result, revenue, expense, tax credit, capital, loans, and inter-party transactions reporting must be more consistent.
For companies, the best preparation is not to avoid record keeping, but to build an administration that can explain each transaction transparently.
0 comments on this article.
No comments yet.