Visa Rate Explained: Approval Rate vs Issuance Rate
“Our visa rate is 99%.”
If you sell travel, that sounds reassuring, until you ask a simple follow-up: 99% of what, exactly?
In visa operations, the word “rate” is often used loosely. Some teams mean approval rate, others mean issuance rate, and many mix them with application completion or booking attach rates. The result is bad forecasting, mismatched partner expectations, and avoidable customer friction.
This guide defines the two most commonly confused metrics, shows how each is calculated, and explains which “visa rate” to use depending on whether you care about compliance, revenue, or customer experience.
What “visa rate” usually refers to (and why it’s ambiguous)
In practice, “visa rate” tends to be shorthand for one of these:
- Approval rate (decision outcome).
- Issuance rate (a visa was actually issued and delivered to the traveler).
- Completion rate (a traveler finished the application you presented).
Only the first two describe government outcomes. If you are comparing visa vendors, reporting KPIs to airline leadership, or estimating the risk of denied boarding, you need to separate them.
Approval rate: the cleanest decision KPI
Approval rate measures how often submitted applications that receive a decision are approved.
Standard definition
The most defensible definition in visa operations is:
Approval rate = Approved decisions / (Approved decisions + Refused decisions)
This mirrors how many authorities publish decision statistics. For example, the European Commission publishes Schengen visa statistics that include issued visas and refused applications, enabling approval-style calculations from decided cases.
What approval rate does (and does not) tell you
Approval rate is excellent for measuring:
- Application quality (accuracy, completeness, correct visa type selection)
- Document readiness and validation
- Effectiveness of guided flows and error prevention
Approval rate does not measure:
- Whether the traveler actually received the visa in time
- Whether the application was abandoned before submission
- Whether the trip happened
In other words, a strong approval rate can coexist with poor business outcomes if travelers drop off, miss deadlines, or get stuck in post-approval steps.
Issuance rate: the operational and traveler outcome KPI
Issuance rate measures how often a visa is actually issued. This matters because in many processes, “approved” is not the final state.
Why approval and issuance can differ
Depending on the destination and visa type, a traveler may be “approved” but not yet “issued” due to:
- Administrative processing or additional checks
- A request for more documents after a preliminary approval
- Payment confirmation issues
- Passport submission and return logistics (for sticker visas)
- Traveler non-response or missed deadlines
For digital authorizations (many eVisas and eTAs), approval and issuance may be nearly the same event. For consular processes, they often are not.
Common issuance rate definitions (and why you must ask which one is used)
Unlike approval rate, “issuance rate” is reported with different denominators.
| Issuance rate variant | Formula | When it’s used | Risk if misused |
|---|---|---|---|
| Issuance per decided | Issued / (Issued + Refused) | Similar to approval rate but “issued” replaces “approved” | Can hide operational failures after approval |
| Issuance per submitted | Issued / Submitted | Measures end-to-end success from submission to delivery | Sensitive to pending cases (timing) |
| Issuance per started | Issued / Started | Measures full funnel health (UX + compliance) | Looks “worse,” but is often the most honest |
| Issuance per booking | Issued / Eligible bookings | Useful for travel sellers forecasting compliance and attach | Needs clean eligibility logic |
If a partner claims a high “visa issuance rate,” ask for the exact formula and how pending and abandoned cases are treated.
A practical example: same performance, three different “visa rates”
Here is how easy it is to inflate or deflate a “visa rate” without changing real-world performance.
Assume in one month:
- Eligible travelers shown a visa offer: 1,000
- Travelers who start the application: 800
- Travelers who submit: 700
- Decisions received: 650 (50 still pending)
- Approved: 585
- Refused: 65
- Visas issued (delivered): 560 (25 approved cases not issued yet)
| Metric | Calculation | Result |
|---|---|---|
| Approval rate (decided) | 585 / (585 + 65) | 90.0% |
| Issuance rate (per submitted) | 560 / 700 | 80.0% |
| Issuance rate (per started) | 560 / 800 | 70.0% |
| “Visa rate” (per eligible shown) | 560 / 1,000 | 56.0% |
All four can be technically “true,” but only if you declare the denominator. Without that, comparing vendors or channels becomes meaningless.
Which KPI should a travel business prioritize?
Different teams care about different outcomes. A good reporting pack includes both approval rate and issuance rate, plus at least one funnel metric.
Recommended KPI mapping by goal
| Business goal | Primary KPI | Secondary KPIs | Why |
|---|---|---|---|
| Reduce denied boarding and compliance risk | Issuance rate per eligible booking | Time-to-issue, pending rate, exception rate | Issuance is what prevents airport failures |
| Increase ancillary revenue | Issuance per eligible booking (or per booking) | Attach rate, take rate, application start rate | Issued documents correlate with realized revenue |
| Improve customer experience | Issuance per started (end-to-end) | Completion time, CSAT, rework rate | Captures both UX friction and outcomes |
| Improve application quality | Approval rate per decided | Error rate, document rejection rate, resubmission rate | Focuses on the correctness of submissions |
If you already track post-deployment visa KPIs, SimpleVisa has a complementary view in their guide: 5 KPIs to Track After Deploying a Visa Management Platform.
Reporting pitfalls that distort approval and issuance rates
Most “rate” confusion comes from inconsistent counting rules. These are the pitfalls that most often break comparability.
1) Mixing “submitted” and “started” applications
Started applications are heavily influenced by UX, traveler confidence, and device constraints. Submitted applications are more influenced by compliance and document quality. If you compare channels, keep them separate.
2) Ignoring pending cases (the timing problem)
If you calculate issuance rate on a short window (for example, weekly) you may undercount cases still in progress.
Two fixes are common:
- Use a cohort approach (measure outcomes for applications submitted in a given month after enough time has passed).
- Report a separate pending rate alongside issuance.
3) Counting withdrawals and duplicates inconsistently
Travelers sometimes submit twice, change passports, or withdraw to reapply with corrected data. Decide whether you count:
- Per traveler
- Per application
- Per booking
Then stick to it.
4) Blending eVisa, eTA, and consular visas
Approval-to-issuance timelines differ dramatically between a digital authorization and a sticker visa requiring passport logistics. Segment your reporting by visa type.
5) Treating “approval” as a guarantee of entry
Even with an issued visa or travel authorization, final admission is typically decided by border officials. This does not invalidate issuance metrics, but it is why operational teams also track denied boarding and border incident rates.
How to vet a vendor’s “visa rate” claim (a quick checklist)
If you are evaluating providers (or sanity-checking an internal dashboard), you can usually clarify the truth in five questions:
- What is the denominator? (started, submitted, decided, eligible bookings)
- How are pending applications handled? (excluded, included as failures, or tracked separately)
- Is the metric segmented by destination and visa type?
- Are reapplications and duplicates deduplicated by traveler or counted separately?
- Does the rate include only guided applications, or all traffic including DIY drop-offs?
If you want a deeper procurement framework, SimpleVisa’s partner-facing guide is relevant: How to Evaluate a Visa Processing Company.
How SimpleVisa fits into approval and issuance outcomes (without the metric confusion)
Travel sellers typically improve both approval rate and issuance rate by reducing preventable errors before submission and by managing the “after submission” journey better.
Based on SimpleVisa’s public positioning, their platform supports this through:
- Guided customer visa applications that reduce incorrect entries and missing documents
- Visa processing automation to streamline steps that often create rework
- Integration options (API, white-label app, and no-code implementation) so travelers can complete requirements closer to the booking moment
- Premium eVisa management for tracking and handling applications at scale
For an example of how a provider may explain a high approval metric, see: Inside Look: SimpleVisa’s 99% Approval Rate Explained. When you read any such claim, apply the denominator checklist above to confirm it matches your reporting needs.
A simple reporting template you can adopt
If you need one internal slide that eliminates “visa rate” ambiguity, use this structure:
| KPI | Definition (declare denominator) | Segment by | Report with |
|---|---|---|---|
| Approval rate | Approved / (Approved + Refused) among decided | Destination, visa type, traveler nationality | Pending rate, rework rate |
| Issuance rate | Issued / Submitted (or Issued / Started) | Destination, visa type | Median time-to-issue, pending backlog |
| Completion rate | Submitted / Started | Device, channel, funnel step | Abandon reasons |
| Attach rate (commercial) | Visa purchases / eligible bookings | Route, market, booking window | Revenue per booking |
This makes it hard for stakeholders to accidentally compare a decision metric with a funnel metric.
Frequently Asked Questions
What is the difference between approval rate and issuance rate? Approval rate measures the share of decided applications that are approved. Issuance rate measures the share of applications that result in a visa actually being issued, and it can use different denominators (submitted, started, decided, or eligible bookings).
Which “visa rate” should I use for compliance risk? Use an issuance-based metric tied to bookings, for example issued documents per eligible booking, because an issued document is what reduces airport and border issues.
Can approval rate be higher than issuance rate? Yes. Some applications can be approved but not issued due to pending steps (additional checks, document requests, passport logistics, or traveler non-response).
Why do some dashboards show very different visa rates for the same period? Usually because they use different denominators (started vs submitted vs decided) or different timing rules (pending cases included or excluded).
Is an issued visa or eTA a guarantee of entry? Typically no. Most countries state that final admission is decided at the border. Issuance is still the best operational KPI for “document readiness,” but it is not identical to entry success.
How can we improve both approval and issuance rates? Focus on preventing errors before submission (data validation, document checks, correct visa selection) and on reducing post-submission drop-offs (status tracking, reminders, fast handling of additional document requests).
Make your visa KPIs comparable (and easier to improve)
If your team is trying to forecast ancillary revenue, reduce denied boardings, or compare providers, stop using “visa rate” as a single catch-all number. Report approval rate and issuance rate side by side, declare the denominator, and segment by destination and visa type.
If you want to operationalize this with an embedded flow or white-label experience, SimpleVisa offers visa processing automation and integration options (API, white-label app, and no-code implementation) designed for travel businesses. Explore the platform at SimpleVisa or request a demo to see how it fits your booking flow.