E-invoicing by country
E-invoicing workflows for Kenya and India
Choose the country where your business invoices. Compare the routes, follow the official guidance and explore the VisionONE integration that fits your operation.
Kenya
KRA eTIMS
Connect your invoice records to Kenya’s electronic invoicing workflow. Start with the supported eTIMS route, returned details and the checks your finance team needs.
India
GST e-invoicing
Explore GST invoice registration, the returned Invoice Reference Number (IRN) and signed QR details. Review the related e-way bill workflow where it applies.
Compare the route.
Keep the country context.
ERP integration connects your invoice to a country-specific service. The registration details and review requirements differ.
Scroll the table sideways to compare both countries.
| What to compare | Kenya · KRA eTIMS | India · GST e-invoicing |
|---|---|---|
| Connection route | KRA describes system-to-system integration through OSCU or VSCU. Confirm the route supported for your deployment. KRA source | Eligible invoice data is reported to an Invoice Registration Portal (IRP). NIC source |
| Evidence to review | Keep the source invoice, submission outcome and returned eTIMS invoice references together. | Retain the IRN and signed invoice / QR details with the source document. IRP source |
| Before configuration | Confirm business obligations, applicable exclusions, onboarding and the integration arrangements. | Confirm taxpayer and document applicability, exemptions and current reporting requirements. |
| Corrections & follow-up | Agree the selected eTIMS solution’s correction process and how your team reviews an unconfirmed or rejected request. | Confirm the current IRP correction or cancellation procedure and review any linked e-way bill. |
A successful invoice response is one part of the record trail. Reconcile it with your source document and review the separate return-filing or goods-movement work that applies to your business.
Give the integration
clear review owners.
Agree the scope and responsibilities before configuration, then use actual records to test the complete workflow.
Your finance or tax reviewer
Confirms applicability, document treatment and current official requirements for each entity and country.
Your implementation team
Agrees the supported connection, mappings and output fields, then tests successful, rejected and unconfirmed requests.
Your operational owner
Checks the source records, assigns exception follow-up and approves the reconciled pilot before go-live.
Start with
official guidance.
Confirm rules, exclusions and current procedures for your own business with the relevant country sources and tax reviewer.
Official sources checked
Kenya sources
resources
India sources
The date records when these sources were checked for this overview. Confirm the current rules and record your reviewer’s approval when configuring or changing a deployment.
Choose the right
country workflow.
Start with where the entity invoices, then confirm the documents, connection and review process it needs.
How do Kenya and India invoicing workflows differ?
Kenya uses KRA eTIMS, with official system-to-system routes including OSCU and VSCU. India uses an Invoice Registration Portal for eligible documents, with an IRN and signed QR details returned after registration. Each setup needs its own applicability and workflow review.
Where can we confirm current rules?
Use the official country links above. Check current notifications, relevant exclusions and supported procedures with your finance or tax reviewer. The source-check date on this page is not a qualified review of your business.
Which integration page fits our business?
For Kenya invoicing, start with KRA eTIMS Integration. For India registration and dispatch workflows, use GST e-Invoicing India. If you operate in both countries, scope each entity and country workflow separately with the team.