KRA eTIMS integration
KRA eTIMS integration for ERP invoicing in Kenya
Connect the invoices your team raises in VisionONE to the eTIMS workflow. Review submission responses, exceptions and credit notes alongside the ERP records, with an agreed integration setup and support scope.
Planning the project? Work through the eTIMS and ERP integration checklist. Prefer paper? Download the printable eTIMS integration checklist (PDF).
ERP invoice submission
Connect invoices raised in VisionONE to the configured eTIMS submission flow, with the source record kept in view.
Responses & invoice details
Review returned submission details, control information and the invoice output before treating the record as complete.
Exceptions & review
Keep rejected records and returned messages available for follow-up, with a clear owner for the correction.
Linked credit notes
Keep a credit note tied to its original invoice. Review the reason, amount and its own submission result.
Branch & bulk invoicing
Scope the integration around your entities, branches and invoice volumes. Confirm the supported route and version.
Receipts & reconciliation
Review invoices, credit notes and matched payments together, without treating a payment as an eTIMS response.
Connected invoicing through the VisionONE eTIMS add-on
Discuss your invoicing workflowOn this page
Part of VisionONE ERP
Invoice, response and credit-note workflow
From the invoice
to its returned response.
Follow one fictional invoice through submission, response review and a linked credit note. Keep document status and financial amounts distinct at each stage.
Stage 1 of 4 · Prepare
Start with the invoice you intend to send.
The fictional invoice INV-DEMO-009 has a total of KES 10,000. Review the customer information, item references, branch and applicable invoice settings. The example does not calculate tax or model a particular KRA payload.
Illustrative record
- Invoice
- INV-DEMO-009
- Customer
- CUSTOMER-DEMO-A
- Branch
- Nairobi · example
- Invoice total
- KES 10,000
Stage 2 of 4 · Submit
Keep submission separate from acceptance.
Send through the configured integration and retain the invoice reference with its submission history. In this illustration, a pending response means the result has not yet been confirmed; sending a request alone does not prove acceptance.
Illustrative record
- Invoice
- INV-DEMO-009
- Request
- Illustrative submission
- Response
- Awaiting confirmation
- Confirmed acceptance
- Not yet recorded
Stage 3 of 4 · Review
Review the returned invoice details.
The illustration now assumes an accepted response for INV-DEMO-009. Keep the returned information with the original invoice and review its printed output. In a product demo, use a redacted real response to confirm the fields and returned QR details.
Illustrative record
- Invoice
- INV-DEMO-009
- Illustrative result
- Accepted
- Invoice total
- KES 10,000
- KRA identifiers
- Not fabricated here
Stage 4 of 4 · Credit
Link the correction to its original invoice.
A fictional KES 2,000 credit note, CN-DEMO-009, references INV-DEMO-009. The example assumes that its separate submission is also accepted. Retain both records: KES 10,000 invoiced less KES 2,000 credited gives KES 8,000 net invoicing.
Illustrative record
- Credit note
- CN-DEMO-009
- Original invoice
- INV-DEMO-009
- Credit amount
- KES 2,000
- Net invoicing
- KES 8,000
This is an educational illustration, not a live submission, product screenshot or KRA-issued invoice. No taxpayer PIN, control number or QR code has been invented. Actual fields, tax treatment and supported correction flow are reviewed during setup.
Invoice records, credit notes and receipts
Know what sits
behind each invoice status.
Keep the source invoice, returned submission details and customer account in view. A financial balance and an integration result answer different questions.
See the invoice and its response together.
Review the ERP invoice reference against its submission result. The illustration assumes acceptance of the KES 10,000 invoice and the linked KES 2,000 credit note; the original invoice remains in the trail.
- Original invoice
- KES 10,000Net after illustrated credit: KES 8,000
| Source record | Result |
|---|---|
| INV-DEMO-009Original invoice · KES 10,000 | Illustrative acceptance |
| CN-DEMO-009Linked credit · KES 2,000 | Illustrative acceptance |
| Returned identifiersControl details and QR output | Real sample needed |
Keep actual response fields and their timestamps with the original source record. A copied ERP document is not evidence of a new accepted submission.
Correct the account without losing the trail.
CN-DEMO-009 credits KES 2,000 against the original KES 10,000 invoice. Net invoicing is KES 8,000. Review the credit reason, original reference and its own returned status.
- Net invoicing
- KES 8,000KES 10,000 − KES 2,000
| Document | Invoiced | Credited |
|---|---|---|
| INV-DEMO-009Original invoice retained | 10,000 | — |
| CN-DEMO-009References INV-DEMO-009 | — | 2,000 |
| Totals | 10,000 | 2,000 |
The two documents have separate response histories. The example assumes acceptance of both; a credit note still awaiting confirmation must be investigated separately.
A receipt settles the account, not the response.
A fictional KES 6,000 M-Pesa receipt is matched to the customer account after reference review. Net invoicing of KES 8,000 less that receipt leaves KES 2,000 outstanding.
- Outstanding balance
- KES 2,000KES 8,000 − KES 6,000
| Record | Amount |
|---|---|
| Net invoicingInvoice less linked credit | 8,000 |
| Reviewed M-Pesa receiptRCPT-DEMO-009 · matched | 6,000 |
| Remaining receivableAfter allocation | 2,000 |
A payment does not demonstrate eTIMS acceptance. Review invoice responses and payment allocations as separate records linked to the same account.
The views share one consistent fictional account. Amounts illustrate reconciliation, not a tax calculation or statutory return. Ask to see a permitted, redacted invoice and response from the current product version.
Who needs system-to-system invoicing
Choose the route
around your invoicing operation.
For a business already issuing invoices in an ERP, eTIMS API integration can connect that invoicing system to KRA. Start with invoice volume, branches and connectivity, then confirm the integration route in your proposal.
- OSCU: KRA describes this route for invoicing systems that operate online.
- VSCU: KRA describes this route for bulk invoicing and systems that are not continuously online.
- Confirm the route and specification version supported by your proposed VisionONE deployment.
OSCU and VSCU describe different routes.
These are KRA’s route definitions, not a claim that every deployment supports both. Ask for the named integrator, supported version and tested setup for your business.
Review the returned information against the invoice and keep exceptions visible for follow-up.
Use official guidance to review taxpayer onboarding, the integration route and certification evidence.
Review receipt references and customer allocations alongside the connected finance records.
Logos identify the referenced services; they are not evidence of vendor certification or endorsement.
Exceptions, retries and connectivity
Keep the message,
the correction and the history together.
A rejected record and a request without a confirmed response need different follow-up. Give the finance and support teams the evidence to understand what happened before the next submission.
Read the returned message
Identify the document, message and responsible team member. Review the customer, item or invoice settings relevant to the issue before correcting the source.
Investigate a missing response
Check the recorded submission and connection history before assuming rejection. An uncertain result needs review so a repeat request does not create a duplicate.
Confirm retry and recovery behaviour
Test interruption, reconnection and duplicate handling with your implementation team. Agree who reviews queued records and how unresolved responses reach support.
Registration, testing and verification
Make the setup
worth verifying.
Agree who handles each implementation step and which evidence confirms it. Review the taxpayer records, system route and integration evidence before production use.
Taxpayer and branch records
Confirm the business PIN, branch identifiers and authorised users relevant to the deployment. Keep the onboarding records with the implementation scope.
Named route and system version
Document the supported OSCU or VSCU route, integration version and operating environment. Review what is included before agreeing to go live.
Integrator certification evidence
Request dated evidence identifying the legal integrator, product, version and applicable route. If a partner delivers the integration, identify that partner and its responsibilities.
Credit-note testing
Test a permitted correction against its original invoice. KRA guidance says a credit note is generated through the solution that raised the original invoice.
Connectivity and response review
Test accepted, rejected and unconfirmed outcomes. Agree recovery steps, duplicate checks, exception ownership and the support escalation path.
Registration is a separate record
Keep taxpayer onboarding distinct from integrator or system certification. Completion of one process does not by itself establish the other.
Connected ERP records
Keep the ledger
and invoice evidence in view.
Connect the integration review to the finance and invoicing work your team already performs, with clear ownership of the records.
Start with your eTIMS integration requirements. Bring the invoices, branches, volumes and exceptions you need to handle. Review the add-on, configuration, supported route and ongoing support as one agreed scope.
Add-on scope, costs and support
Pricing, testing
and go-live.
Review what the eTIMS add-on includes and what needs configuration. Agree the implementation responsibilities and support terms around your invoicing operation.
Agree the add-on and scope
VisionONE describes eTIMS integration as an add-on. Confirm licensing, entities, branches, invoice volumes, supported route and any related finance or payment workflow in writing.
Configure and test the setup
Agree customer and item mappings, invoice settings, authorised users and the required onboarding work. Review a redacted invoice, response and linked credit note in the test environment.
Verify go-live and support
Reconcile a pilot’s invoice results and finance records. Confirm connectivity tests, exception ownership, training, support contacts and the agreed acceptance evidence before production use.
eTIMS-ready invoicing for Kenyan businesses
Connect the invoices your team raises in VisionONE to the eTIMS workflow. Review submission responses, exceptions and credit notes alongside the ERP records. VisionONE describes eTIMS integration as an add-on. Confirm the integration setup, testing plan and support scope in your proposal.
Step-by-step guide: how to integrate your ERP with KRA eTIMS.
After invoices are in eTIMS, finance still needs to reconcile VAT, revenue and expenses. See how to reconcile VAT, eTIMS and iTax and tax reporting and KRA workflows.
What to ask any eTIMS vendor (including VisionONE)
Use these checks in every vendor conversation, including a VisionONE demo:
- The proposed integration approach, product version and testing plan
- Dated evidence of any integrator status, checked against current KRA publications. Taxpayer onboarding alone is not vendor certification.
- How credit notes and rejected invoices are handled
- What happens if connectivity is interrupted
- The printable eTIMS integration checklist (and PDF checklist) and the guide to what KRA eTIMS is
- Explore the connected platform under Kenya ERP and compliance
Questions, answered
Before your
eTIMS integration demo.
Bring the records you issue today and one exception you need to explain. Confirm the route, add-on scope, responses and support your team needs.
What are OSCU and VSCU?
These are KRA's names for two system-to-system eTIMS routes. KRA describes OSCU for invoicing systems that operate online, and VSCU for bulk invoicing or systems that are not always online. This page does not claim that VisionONE supports OSCU, VSCU or both. For official definitions, see KRA's system-to-system integration guidance. Confirm the integration approach for your business in your proposal.
Is VisionONE a KRA-approved third-party eTIMS integrator?
No. This page does not describe VisionONE as a KRA-approved third-party eTIMS integrator, and it does not claim KRA certification. If you need to verify any integrator, ask for the legal name, product, version and dated evidence, then check those details against current KRA publications. Taxpayer onboarding alone is not vendor certification.
Which eTIMS integration route is supported?
KRA describes OSCU and VSCU as two system-to-system eTIMS routes: OSCU for invoicing systems that operate online, and VSCU for bulk invoicing or systems that are not always online. This page does not claim that VisionONE supports OSCU, VSCU or both. Discuss the eTIMS invoicing integration proposed for your business and confirm the setup in your proposal. For official route definitions, see KRA's system-to-system integration guidance.
Is the integration included or an add-on?
VisionONE’s published integration page describes it as an add-on. Confirm licensing, setup, testing and support in your written proposal, including which connected ERP modules your workflow requires.
What happens when an invoice is rejected?
Review the returned message against the original document, correct the relevant source information and follow the agreed resubmission process. Keep the response history and responsibility for the exception visible. If the result is unknown, check it before repeating the request.
How are credit notes handled?
Keep the credit note linked to the original invoice and review its reason, amount and returned status. KRA states that credit notes are generated through the solution that raised the original invoice. Test the supported correction workflow using a permitted sample during setup.
How can we verify the integrator and system approval?
Request the legal integrator name, product, version, route and dated certification evidence. Verify those details against current KRA information or directly with KRA. If a certified partner is involved, confirm its role. Taxpayer onboarding alone does not establish vendor or system certification.
What happens if connectivity is interrupted?
Confirm the behaviour of the actual route and deployment during testing. Ask to see queued records, response checks, recovery, retry and duplicate handling. Agree which outcomes require staff review and how unresolved records are escalated; do not assume every outage behaves the same way.
What should we bring to an eTIMS demo?
Bring an anonymised sales invoice, a linked credit note, branch and volume details, and an exception you need to resolve. Include the finance and payment records you want to reconcile. Ask to review a redacted real response and the proposed integration scope.
See it with your records
Bring one invoice.
Follow the whole response.
Review the source invoice, returned details and a linked credit note. Include one exception so the demo covers the follow-up behind a completed submission.
A focused demo around your invoicing workflow, with no obligation.