Tax paid but debt remains in the DPS e-Cabinet: what to check
Why a Ukrainian FOP can still see tax debt after payment, and how to check the IKP, payment details, earlier debt, overpayments, and correction routes.
Why a Ukrainian FOP can still see tax debt after payment, and how to check the IKP, payment details, earlier debt, overpayments, and correction routes.
A bank receipt and debt in the DPS e-Cabinet do not necessarily contradict each other. The bank may only have accepted the instruction for processing, the funds may have reached a different budget account or integrated taxpayer card, or the correct card may have used the payment to settle earlier debt before the current liability.
The review therefore has three separate questions: was the payment executed, which Treasury account received it, and how did the DPS allocate it in the integrated taxpayer card, or IKP? The broad guide to FOP tax settlement status explains the columns; this article focuses on the case where money was sent but debt remains.
Do not create a duplicate payment because of one figure on the summary screen. Preserve the evidence, open the relevant card detail, and identify the cause first. This guide is current as of November 10, 2026.

Open the complete bank receipt or payment instruction. Its status must mean execution rather than creation, signature, waiting, or acceptance for processing. Confirm that the funds were actually debited and that the payment was not returned or rejected after the receipt was generated.
Record the execution date, amount, document number, payer, beneficiary, IBAN, and payment purpose. A screenshot of one status without the details does little to explain the mismatch: the DPS needs a document that identifies the specific transaction.
If the bank returned the instruction without execution, no tax payment occurred. If it was executed but is absent from the expected IKP, trace the account and allocation instead of paying again at random.
In Tax Settlement Status, select the year and DPS office, then open the relevant payment. Single tax, military levy, SSC, personal income tax, and other payments are accounted for separately. A positive balance in one card does not automatically settle debt in another.
Do not stop at the debt field in the summary. Find the payment row by date and amount, then review the transactions before and after it. Debt may be current or historical, consist of a remaining principal liability plus separate late-payment interest, or come from another accrual.
If the FOP changed tax address or paid from an old template, review the cards for different DPS offices. What matters is where the payment was actually recorded, not where you expected to see it.
| What you see | Likely line of inquiry | Next action |
|---|---|---|
| No payment in any expected card | Unexecuted transaction, another office, or a payment under clarification | Match the bank record, tax number, and IBAN, then contact the relevant DPS office |
| Payment in another IKP | A different tax, account, or territory was paid | Do not treat the debt as settled; identify the transfer or refund route |
| Payment in the correct IKP but debt remains | Funds covered earlier debt, interest, or only part of all accruals | Read the chronology and calculate the unpaid remainder |
| Overpayment in one card and debt under another payment | The balances belong to different cards | Submit the required application if the funds should be directed to another payment |
Compare the bank document with the current details for the specific tax and territory, not with a saved template. Check the beneficiary, IBAN, budget revenue classification code or payment name, territorial office, and tax number of the person whose liability was paid. Tax payment accounts depend on the community, so the correct amount sent to an old or unrelated account does not automatically settle the intended card.
Review the payment-type code separately. Code 101 is used for an ordinary payment. Not every typo in Additional Information explains debt, however: the DPS states that an absent or invalid code for a budget-account payment is treated as code 101, while Procedure No. 148 does not provide a payer-led correction of that field. The critical question remains which account received the funds and which taxpayer they identified.
If the payment document does not identify the taxpayer or purpose, the amount may enter an IKP under the special Payments under Clarification code. After identification, the DPS reallocates it using the Treasury credit date when clarified in the same reporting month; after month-end, it posts the reallocation on the current date while retaining the original Treasury credit date. This is not a promise to resolve every error within 24 or 48 hours.
When tax debt already exists, the DPS credits funds against that debt in the order in which it arose, regardless of the payer’s direction for the current liability. The IKP may therefore contain the payment while current debt remains: the money closed an older unpaid item first.
Within repayment of tax debt, funds cover the principal tax liability first, penalties second, and late-payment interest last. Do not combine these components by guesswork. Review the transaction sequence, remaining principal debt, and the separate interest field.
Do not search for earlier debt only in the current year. Review prior periods and obtain an Extract for the necessary range. If the amount or basis is unclear, identify the source document first: a return, adjustment, tax notice-decision, or demand.
An overpayment in one tax IKP can settle a future liability in that same card. A single-tax overpayment does not automatically become a military-levy payment, however, and a tax overpayment does not automatically move to SSC. Directing funds to another budget payment requires the statutory application.
For taxes other than SSC, an application to refund or transfer an erroneous or excess amount must be filed within 1,095 days after the amount arises. The application may direct the funds to another tax liability or tax debt. As of publication, an individual uses the current F13020XX version in the e-Cabinet and attaches payment documents; check the current form suffix in the official registry.
A refund to the taxpayer’s own account while tax debt exists occurs only after that debt is fully repaid. This does not prevent the application from directing an available overpayment to another liability or debt when the Article 43 requirements are met.
SSC is not a tax, and its overpayments and erroneous payments are not corrected through a Tax Code Article 43 application. Excess amounts paid to the proper account 3556 are applied to future SSC payments under that same account in chronological order. Refunds and erroneous payments are governed by Ministry of Finance Procedure No. 417.
An SSC refund application is submitted through the e-Cabinet’s “Correspondence with the DPS” section to the DPS office where the erroneous or excess amount is recorded, using the Procedure No. 417 form and a copy of the payment document. Outstanding SSC or financial-sanction debt is one reason the application may be left unsatisfied.
Do not use a tax overpayment to explain SSC debt or vice versa. Open the separate SSC card and check the account, period, exemption, and any payment demand already issued.
If the details were correct and the payment was initiated and executed on time, but a bank, non-bank payment provider, or the Treasury disrupted the transfer, collect evidence of that institution’s fault. A statement that the issue was technical is not enough. Ask the bank to confirm submission, execution, return, or the failure reason.
The Tax Code recognizes circumstances that exempt a taxpayer from financial liability and require cancellation of late-payment interest for violations caused by a bank, the Treasury, or specified payment participants. The DPS advises submitting an application with copies proving that the payment instruction was given to the bank. The exception does not cover an instruction returned without execution or an unfinished initiation through an insolvent bank.
Even with evidence, do not assume the debt will disappear automatically. Submit the documents to the DPS, preserve the correspondence registration number, and review later IKP transactions and any decision on penalties or interest.
Sometimes the payment is credited correctly but the liability is wrong: the wrong period was filed, a later new reporting return became effective, an adjustment increased the amount, the card contains a DPS decision, or an accrual was duplicated. Match every accrual row with its source document instead of reasoning only from the closing debt.
If the return was accepted but the expected accrual is completely absent, that is the opposite issue with a separate workflow; use the guide FOP return accepted but no accrual. If your own return contains an error, correct the reporting through the applicable route; an arbitrary extra payment does not change the declared liability. A liability self-assessed by the taxpayer is not subject to administrative appeal, so distinguish your own reporting error from a DPS decision first.
Do not file an adjusting return merely to remove debt from the screen. First establish that the accrual is wrong rather than the account, payment order, or amount.
For a documented snapshot, request an Extract using the current F13002XX request. As of November 10, 2026, F1300208 is current for individuals; the response is F1400208, F1420401, or F1420501 depending on the selected format. The DPS provides an electronic Extract no later than the second working day after accepting the request. This is the Extract delivery deadline, not a promise to correct the IKP or credit a payment within two days.
For an IKP discrepancy, send evidence-backed correspondence through Correspondence with the DPS to the office administering the payment. State the tax, period, amount, DPS office, payment-instruction date and number, intended and actual account, and the exact IKP row to review. Attach the receipt, Extract or saved IKP detail, and the return and filing receipts when relevant.
When debt is based on a tax notice-decision or another DPS decision rather than a technical mismatch, ordinary correspondence may not be enough. The general administrative-appeal deadline is 10 working days after receipt; the Code provides 30 calendar days for certain determinations unrelated to a tax-law violation. An SSC arrears demand has a separate 10-calendar-day period from receipt for payment or appeal. Identify the document and follow its procedure without waiting for a reply to ordinary correspondence.
| Situation | What to submit | What to include |
|---|---|---|
| You need an official settlement snapshot | F13002XX request for an Extract | Period, payment breakdown, and signature when needed |
| Payment is missing or incorrectly allocated | Correspondence with the DPS | Full payment instruction, IKP/Extract, and the requested correction |
| Funds are an overpayment in another budget account | F13020XX application under Article 43 | Payment dates and documents plus the transfer direction |
Follow these checks in order. They separate an unexecuted payment from a wrong account, incorrect allocation, earlier debt, and a mistaken accrual.
Check upcoming obligations in the FOP tax calendar. The calendar helps prevent a new missed deadline, but the reason for an existing debt must be established from payment evidence and the IKP.
These answers describe the general rules as of November 10, 2026. For a specific debt, review your IKP, payment document, and the source of the accrual.
Not automatically. Confirm execution of the first payment, locate it in the IKP, match the account, and check earlier debt. A duplicate payment can create another overpayment without correcting a misallocation.
The funds may have settled earlier debt, covered only part of the accruals, or left separate late-payment interest. Read the transaction chronology and balance after each row.
Not automatically. They are different payments and IKPs. To direct a tax overpayment to another budget payment, submit an Article 43 application specifying the transfer direction.
Find the card holding the funds and submit the appropriate transfer or refund application. Potential relief for timely erroneous payment requires proof and compliance with Article 43; SSC follows a different procedure.
There is no universal 24- or 48-hour promise for every case. The IKP records Treasury data by the credit date, while erroneous or unidentified payments require separate identification. Review the evidence and contact the DPS without relying on an invented service level.
Not through the ordinary Tax Code Article 43 route. SSC is accounted for separately, and its excess or erroneous payments are governed by Ministry of Finance Procedure No. 417.
Use the formal procedure and specific deadline when challenging a tax notice-decision, another DPS decision, or an SSC demand. Ordinary correspondence is suitable for reconciliation or a technical discrepancy but does not replace a timely appeal.
MYFOP UA helps FOPs view tax deadlines, amounts, and DPS data in one workspace. It does not make payments or submit correspondence or appeals on your behalf; bank documents, the IKP, the Extract, and DPS decisions remain the authoritative evidence.
Create a MYFOP UA account and reconcile amounts, deadlines, and DPS data before a discrepancy becomes debt.
What accrued, paid, balance, overpayment and tax debt mean in the DPS e-Cabinet, and how a Ukrainian FOP can check discrepancies.
Read articleFOP return accepted no accrualWhy a Ukrainian FOP return may be accepted while no accrual appears in the DPS e-Cabinet: receipts, IKP date, period, tax card, overpayment, and escalation.
Read articlePayment accountsPayment accounts for single tax, military levy, and SSC depend on the region and community. The service shows details after choosing the main FOP community.
Read article| You received a tax notice-decision, other decision, or SSC demand |
| Formal administrative or judicial appeal under the applicable route |
| Challenged document, evidence, and calculation filed within the specific deadline |