An overpayment in a Kenyan tax account can be useful only when the business understands what the balance represents and how it may be used. This guide follows the Overpayment Adjustment Voucher, or OAV, from a supported claim to an approved voucher and a reconciled offset. It is written for finance teams preparing that specific iTax workflow.
1. Identify the credit before choosing a route
Start by writing down the tax obligation, period and transaction that produced the apparent overpayment. A payment made twice, a withholding credit and an amended return can require different evidence. A negative balance in an internal spreadsheet does not explain what KRA has recorded. Compare the business ledger with the official account before deciding what to request.
The KRA OAV guide describes an application for offsetting overpaid tax. It requires officer verification and approval before voucher generation. It also excludes PAYE, withholding income tax, withholding rent and withholding VAT as destination liabilities. These restrictions concern the described offset workflow; they should not be read as a universal statement about every refund entitlement.
Use a simple decision note: the credit's origin, the desired destination, whether cash repayment or offset is intended, and the official procedure being followed. Keep unresolved classification questions in that note. The finance reviewer should be able to see why this is an OAV application rather than an ordinary payment, a return correction or a different refund request.
Prepare a non-sensitive evidence index with the PDF workspace if documents need organising. Keep identifiers, bank details and full tax records in your private working file. A local export helps organise evidence; it does not lodge the application, authenticate an official document or determine the amount KRA will accept.
2. Build a traceable overpayment schedule
Separate the calculation of the underlying liability from the calculation of the available credit. The first explains what was due. The second explains why paid or credited amounts exceed that liability. Put a reference beside every line so that another person can return to the original record without searching through a folder of unrelated receipts.
A useful schedule has columns for obligation, tax period, return reference, assessed or declared amount, payment or credit reference, recorded amount and explanation of the difference. Add the date of the account extract and the name of the reviewer. This is a suggested reconciliation format, not a claim that KRA prescribes this exact spreadsheet.
Do not count the same payment in two periods or reuse a credit already applied elsewhere. Compare the proposed claim with previous applications and offsets. Where an amended return affects the amount, retain both the earlier record and the accepted correction so the change is visible. An unexplained difference should remain open rather than being rounded away.
Use the Kenya withholding tax guide for the underlying deduction context when certificates are part of the evidence. This OAV article addresses a different job: following the supported overpayment through approval and utilisation. Receiving a certificate, having a credit and completing an offset are separate events in the working file.
3. Check the application window and the actual tax deadline
The OAV manual states application windows of five years for income tax and excise duty, and twelve months for other taxes, measured from overpayment. Its income-tax and excise statement includes an effective-date reference of July 1, 2017. Treat this as the manual's description of the workflow and confirm case-specific limitation questions with KRA before relying on it.
Record the payment date, applicable window, intended application date and supporting source together. If the relevant date is unclear, identify the uncertainty before submission. Do not reset the clock to the date a staff member discovered the discrepancy without verifying that treatment. Historical balances, amended assessments and disputed amounts merit specific review.
Keep the destination liability's deadline on a separate calendar. A claim under review is not evidence that the next tax payment has been settled. Ask the responsible tax reviewer how that liability will be met if the voucher is unavailable in time. Record the decision and its basis rather than silently reducing a payment because approval is expected.
4. Prepare the iTax application and record what was submitted
KRA's manual places the application under Refunds, then the option for refund or offset of overpaid tax. The applicant selects offset, reviews the populated taxpayer details, chooses the originating obligation and period, adds remarks and supporting documents, and sends the request through the voucher-generation action. Confirm the current screen against the manual when working in the account.
Before that action, compare the selected obligation and period with the approved schedule. Write remarks that explain the overpayment clearly and refer to the attached evidence. Avoid a vague description that only repeats the requested amount. Have the reviewer check that each attachment opens, is legible and supports the amount actually entered.
Keep one final submission packet and an index of its contents. Save the acknowledgement or other confirmation actually produced by the account. Record the submission date and application reference when available. If a technical interruption occurs, check whether a request already exists before submitting again; duplicate requests can make the internal evidence trail harder to follow.
5. Separate application, approval and available balance
Use different status entries for prepared, submitted, awaiting a response, approved and applied. These are suggested internal tracking labels. They prevent an application reference from being treated as a spendable balance and make the next action clear. Attach the observed official status or decision to each update rather than substituting an internal label for it.
When KRA requests a correction, identify exactly what is questioned: the period, liability, payment, evidence or amount. Preserve the original submission and create a revised schedule showing the change. Resolve the requested assessment, data correction or return amendment through the appropriate official route, then confirm the current amount before reapplying if required.
After approval, compare the voucher with the application. Check the taxpayer, reference, obligation and available amount. Record any difference and the supporting decision. Do not change the original claim to conceal a partial approval. Put unresolved questions beside the voucher so the person arranging the offset knows what still needs attention.
6. Apply the voucher to an eligible liability
The OAV guide directs approved users to the payment set-off workflow, where they enter the voucher reference and choose a liability and period. For a future liability, the respective return must first be filed. For instalment tax, the manual describes use during payment-slip generation, including separate references for a voucher-covered amount and a remaining balance.
Build a destination schedule before using the voucher. List the obligation, period, posted liability, proposed offset and remaining amount. Check the destination restrictions in the current OAV instructions at this point. Approval of an originating credit does not make every destination appropriate, and a familiar menu label does not establish eligibility.
For the arithmetic review, use remaining liability = confirmed liability minus the accepted offset and other verified settlement amounts. This is a reconciliation identity, not a tax assessment formula. If the result differs from the official account, investigate the difference. Do not force the account and spreadsheet to agree by entering an unsupported adjustment.
KRA's March 2024 RAV utilisation manual describes acknowledgement receipts and credit entries after set-off. It is useful for understanding the evidence trail, but its older PAYE example should not override the exclusions in the later OAV guide. Check the particular voucher type and current instructions before applying it.
7. Reconcile both sides after utilisation
Review the originating credit and destination liability together. Confirm the amount used, the period credited and the balance left on the voucher. Keep the utilisation confirmation with a fresh account extract. A saved screenshot of the application screen alone cannot demonstrate how the transaction was finally posted.
Update the internal ledger using the actual outcome and a reference to the evidence. If cash was also required, connect its payment record to the same destination schedule. Avoid reporting the total liability as settled where only part was offset. State the unresolved balance, who owns it and the next verification date.
Where the portal appears to show a different amount, first check the extract date and the obligation and period selected. Then compare the voucher reference, acknowledgement and ledger entry. Escalate the specific mismatch with the supporting records. Keep the application and utilisation history intact while the query is resolved.
8. Keep voucher types and older instructions distinct
KRA's December 2024 iTax enhancement note describes reprinting RAVs, OAVs and IAVs under different business processes. That distinction is useful when collecting evidence: copy the voucher type and exact reference from the official record instead of calling every adjustment a refund voucher.
The KRA refund FAQ explains cash-refund applications, including bank details and supporting documents. Cash refund guidance provides context but does not turn an offset into a bank payment. Keep the chosen outcome explicit so treasury, bookkeeping and the tax reviewer use the same interpretation.
Store the claim schedule, original records, submission, decision, voucher and utilisation evidence together. Use a short index and restrict access to the people handling the account. Retain correspondence about disputed or corrected amounts. For broader account readiness, the Kenya tax compliance certificate guide covers a separate status-check workflow.
Final OAV review checklist
- The originating obligation, period and overpayment evidence agree.
- The requested route and destination are checked against current instructions.
- The application window and destination deadline are recorded separately.
- The submitted amount matches the reviewed schedule and attachments.
- The official decision and generated voucher are retained.
- The offset reference, destination period and accepted amount match.
- Any remaining liability or voucher balance has an owner.
- The ledger and private evidence index reflect the observed outcome.
Close the task only when another reviewer can follow the money and the records from origin to destination. If one stage is incomplete, report that exact stage. A clear partial status is more useful than a general statement that a refund has been handled.
Frequently asked questions
Does submitting an OAV application settle another tax liability?
No. Retain separate evidence of the decision, generated voucher and actual utilisation. The destination account needs its own reconciliation.
Can the PDF workspace apply to KRA on my behalf?
No. It organises documents locally. The application and any official account action require the appropriate separate KRA workflow.
Should an older voucher example decide which destination I use?
No. Check its date and voucher type against the current instructions. An older example is context, not authority for a changed workflow.
Does this guide promise a processing time or approved amount?
No. The observed official decision and account records determine the outcome. Seek specific advice for limitation, eligibility or dispute questions.
Official sources and verification limits
Public primary material reviewed on October 5, 2026:
- KRA OAV application guide, 2025 file, including the August 2025 destination restriction.
- KRA tax refunds FAQ, background on refund types and the separate application route.
- KRA RAV utilisation guide, March 2024 historical set-off and acknowledgement context.
- KRA December 2024 iTax enhancements, voucher reprint distinctions.
The public manuals support preparation, not proof that a private account has the same menus or that a particular claim qualifies. Dated older material is identified above. Confirm changed instructions directly with KRA and obtain case-specific professional review before relying on disputed treatment.