Prompt for E-Invoice Rejection Codes
Rejected e-invoices are usually a data problem, not a code problem. This prompt locates the layer, asks whether to resubmit or cancel and reissue, and refuses to guess at codes it does not know.
My e-invoice submission was rejected. I need to decode the error. ERROR CODE: [CODE] ERROR DESCRIPTION: [DESCRIPTION] INVOICE TYPE: [TYPE] MY SITUATION: [SITUATION] STEP 1 — INTERPRET THE CODE Explain what this code means. If you are not sure, write "I do not know this code reliably, it needs verification" — do not fabricate an explanation. STEP 2 — LOCATE THE LAYER Which of these four is it? Say why. (A) IDENTITY: tax or national ID wrong, taxpayer not registered, name mismatch (B) AMOUNT/TAX: wrong VAT rate, taxable base does not add up, withholding code missing (C) SCHEMA: mandatory field empty, date format invalid, wrong currency code (D) TIMING/SEQUENCE: invoice date in the past, cancellation window missed, duplicate submission STEP 3 — CORRECTION ORDER Give a numbered correction list, maximum 7 steps. For each: what to do, which screen, what to verify. STEP 4 — RESUBMIT After fixing: do I send the same document again, or cancel and issue a new one? Say which is correct and why. STEP 5 — PREVENTION What must change in the invoicing process so this does not recur? One line. Rule: do not write a code list from memory. Flag any code you do not know as "needs verification" and tell me where to check (the tax authority's e-invoicing guide, your service provider's support).
A rejected e-invoice is almost always a data problem in the buyer record, not a software problem.
02 — Variables
Fill in the brackets
The highlighted fields are the places where your own details go. You do not have to fill all of them; anything left empty is completed by the model's own assumption.
[CODE]
[DESCRIPTION]
[TYPE]
[SITUATION]
03 — How to use
How to use it, step by step
- 01
Paste the error description verbatim. Truncating it breaks the diagnosis — the system's own text is more informative than the code number.
- 02
Before interpreting any code, confirm the buyer is registered in the tax system. It is the single most common rejection cause and it precedes everything else.
- 03
Do not skip the "same document or new document" question. Choosing wrong creates a duplicate invoice, which is a tax problem, not a technical one.
- 04
Hand the resulting correction order to your provider's support line. It shortens the call considerably.
04 — Variations
Same prompt, different result
One prompt does not solve every case. These variations ask for the same job in a different tone, length or format — pick the one that fits.
Bulk rejection analysis
Here are all rejection codes and descriptions from this month: [LIST]. Group them by layer (identity, amount/tax, schema, timing), show counts per group, rank by fixability, and name the one process change that would remove the largest group.
When you get dozens of rejections a month.
Pre-submission checklist
Give me a pre-submission checklist for invoice type [TYPE] in the order a finance clerk should run it. Maximum 12 items, each one a yes/no check, grouped by buyer data, amounts, and document metadata.
To stop rejections before they happen.
05 — Tips
Notes that take the result up a level
- An unregistered buyer tax number is the most common rejection cause — check that first whatever the code says.
- When the VAT rate is wrong, check the taxable base too. A correct rate on a wrong base produces the same code again.
- The cancellation window is short (commonly around eight days). Past it you need a corrective invoice rather than a cancellation, and the code explanation will not tell you that.
06 — FAQ
Frequently asked about Money and Budget
Does AI interpret tax authority error codes correctly?
Often partially. It is reliable on common codes and mixes up rare ones. The safe pattern is using the prompt for the layer and the correction order, then verifying the code explanation against your provider's documentation.
Should I cancel the invoice or issue a correction?
If the submission was never accepted, no document exists — fix and resubmit. If it was accepted and you find an error afterwards, cancel within the window; after that you need a corrective invoice. Step 4 exists to separate these.
Does this reduce duplicate invoice risk?
Yes, because it forces the "same document or new document" question after every correction. Duplicates usually come from resubmitting the same invoice twice after a rejection.
Next
You may also find these useful
Personal Budget Plan Prompt (With Tables)
Give income and expenses, get a monthly budget table, category breakdown and a savings recommendation.
Beginner ChatGPTClaudeDebt Payoff Plan Prompt (Avalanche vs Snowball)
Which debt should be cleared first? This prompt puts all balances in one table, compares both methods and produces a month-by-month schedule.
Intermediate ChatGPTClaudeUtility Bill Dispute Letter Prompt (Power, Water, Internet)
Writing to the wrong authority is the most common dispute mistake; this prompt builds the addressee, grounds and demand correctly.
Beginner ChatGPTClaudeSavings Goal Plan Prompt (Month-by-Month)
Turn a target amount and a date into a monthly schedule, with an inflation scenario and an automation plan.
BeginnerThis page was prepared by the CopyPromt editorial team, first published 25 October 2026. Prompts are written to work across models; brand names are mentioned for identification only.