Website

Coretax Invoices Flip From Approved to Saved Invalid: Four Causes and How to Prevent Them

November 13, 2026 · 5 min read · Etzal Group Team

On 5 November 2026 Kring Pajak, the information service of Indonesia's Directorate General of Taxes (DJP), explained on social media why an output tax invoice in Coretax, the country's core tax administration system, can change status from Approved to Saved Invalid. DDTCNews reported the explanation the same day: there are four possible causes around data validation, the passphrase and the digital certificate, and the remedy is to check the signer's authorisation code and upload again.

The source does not say how often this happens. What is clear is that for a company issuing invoices from an ERP in volume towards year end, one invoice that quietly changes status may only be noticed when the buyer complains or when the tax return is prepared. This article summarises the helpline's explanation, then offers ways to prevent the Coretax tax invoice error from costing you time.

What the helpline explained

Every point in this section comes from DDTCNews, 5 November 2026. It is our only source for this topic.

The helpline's first suggestion is simple: check and click refresh periodically before doing anything else.

If the status stays at Saved Invalid, the four possible causes are:

  1. The invoice data failed the system's validation.
  2. The passphrase entered was wrong.
  3. The digital certificate appears to be registered but is not actually registered in DJP's system, particularly in Coretax's early phase.
  4. The passphrase contains characters the system does not allow.

The steps to fix it:

  1. Log in to the signer's Coretax account.
  2. Open Portal Saya (My Portal), then Profil Saya (My Profile), then Nomor Identifikasi Eksternal (External Identification Number), then Digital Certificate, to check the status of the authorisation code.
  3. If it is not valid, request a new code through the Permintaan Kode Otorisasi (Authorisation Code Request) menu.
  4. Upload the invoice again with the new passphrase.

If the problem persists, the channels are a MELATI ticket at the helpdesk of the local tax office (KPP), Kring Pajak on 1500200, or an email to DJP with a detailed description of the problem.

Menu names in Coretax can change. If you cannot find the path above, check DJP's latest official guidance.

Why this is a process problem, not only a technical one

Look at the pattern in the four causes. Three of them concern one person and that person's credentials: the signer's passphrase and certificate. In many mid-sized companies the invoice signer is a single individual, only that individual knows the passphrase, and nobody records when the authorisation code needs renewing. While everything works, nobody thinks about it.

The second problem is a status that changes after the process is considered finished. A staff member sees Approved, closes the task and moves on. If the status changes later, nobody sees it, unless there is a second check.

What follows is our practical advice, not DJP guidance.

Prevention on the finance side

Check the status twice

  • Add a second check of invoice status, for example on the next working day and once more before the tax period closes.
  • Record the result. An invoice list with one column for status at upload and one for status at recheck is enough.
  • Do not send an invoice to the buyer as final before the second check, particularly for large amounts.

Manage the authorisation code like an asset

  • Record who the signer is, when the authorisation code was last checked, and who is authorised to request a new one.
  • Schedule a routine status check in the Digital Certificate menu, for example at the start of each month, not only when something breaks.
  • Agree an internal passphrase rule that avoids unusual characters. The helpline says some characters are not allowed, but the source does not list them. Test a new passphrase on one invoice before using it for a large upload.

Prepare a backup signer

One signer is a single point of failure. Leave, illness or a resignation in the last week of December will stop invoicing. Prepare a second authorised person who has already signed at least one invoice successfully, so that the credentials are proven to work.

The trade-off is real. The more people who can sign, the greater the risk of misuse and the more credentials there are to protect. Two people with a usage log is usually a reasonable middle.

Prevention on the ERP and IT side

Companies that issue invoices from an ERP often store only the result of the first upload. Three small improvements close the gap:

  • Store status as data that can change. Alongside the invoice number, keep the latest status and the time it was checked. Status is not a stamp applied once.
  • Build an exception list. A daily report showing only invoices whose status is something other than Approved is far more useful than a list of thousands that all look fine.
  • Separate two kinds of failure. A data validation failure is about content: buyer identity, amounts, codes. A passphrase or certificate failure is about credentials. If the report tells them apart, the right person acts at once.

For the first cause, data that fails validation, the best prevention is upstream. Validation rules in the ERP that reject incomplete buyer data before an invoice is created cost less than repairing an invoice after rejection.

One warning: never store the signer's passphrase in a script or configuration file for the sake of automation. A few minutes of convenience are not worth the risk.

If it has already happened

The order we suggest, following the helpline's explanation:

  1. Click refresh and wait before drawing conclusions.
  2. Check the authorisation code status in the signer's account.
  3. If it is not valid, request a new code and upload again with the new passphrase.
  4. If the code is valid, suspect the invoice data and check the fields one by one.
  5. If it still fails, raise a ticket with details: invoice number, upload time, status before and after, and screenshots.
  6. Tell the buyer if an invoice they have already received is affected.

If you want to add status monitoring and exception reports to the invoicing flow in your ERP, Etzal Group's enterprise software team can help, or contact us.

This article is not tax advice. For the tax consequences of an invoice that has changed status, confirm with your tax consultant or tax office, and check DJP's latest official announcements.

Sources

Frequently asked questions

Why can an Approved invoice become Saved Invalid?

According to the tax helpline, possible causes are: data failed validation, a wrong passphrase, a digital certificate not actually registered in the tax system, or a passphrase with characters the system does not allow.

What is the first suggested step?

The helpline suggests checking and clicking refresh periodically first, then checking the status of the signer's authorisation code.

Where do we report it if the problem persists?

According to DDTCNews: a MELATI ticket at the tax office helpdesk, the helpline on 1500200, or an email to the tax office with a detailed description.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Website Development

Fast, SEO-ready websites that turn visitors into customers.