Case study · EDITAGE · 2022
Advance VAT Issuance
A self‑serve flow that lets customers pre‑pay and generate a compliant VAT invoice in minutes, cutting issuance time by 88% and clearing a manual finance backlog.
Context
Editage provides academic editing and publication support to researchers worldwide. In China and Japan, two of its largest markets, researchers typically pay from institutional budgets or grants, and many pre‑pay before the fiscal year closes to lock in funds. To get it reimbursed, every one of them needs a formal, compliant VAT invoice.
Problem
VAT invoice was issued manually by customer support team. A customer emailed a request, a finance associate validated the company details, generated the document, and mailed it back, which took 2–4 business days. At fiscal year‑end the queue exploded, and became a business bottleneck.
- Customers missed deadlines. Slow invoices meant reimbursement requests slipped past fiscal‑year cut‑offs.
- Pre‑payment stalled. Without an instant invoice, customers hesitated to commit to the budget at all.
Solution
I owned the end‑to‑end flow, talked to the PM and engineer to understand the existing flow and constraints. Customers wanted to know the invoice was correct, reliable ETA, and not just fill it out faster. I explored single‑page and stepped layouts; single‑page flow tested better for a high‑stakes financial task as context was maintained.
- A single page, different sections. Amount → reward type → invoice type → VAT details.
- Single vs. split invoices. A clear toggle to issue one invoice or split the amount across people.
- Validation. Tax registration field validates in real time, and gets saved for future invoice requests.
- Trust at payment. Pre‑payment is high‑stakes, highlighting total amount and reassuring reward amount kept customers certain about what they were committing to.
Impact
Online VAT application flow reduced advance VAT invoice issuance time by roughly 88%. Pre‑payment conversion rose and invoice‑related support tickets fell as the experience became instant and self‑explanatory.
Reflection
What I'd do differently: I under‑invested early in the finance team's side of the system. Automating the customer experience surfaced edge cases that used to be fixed manually, we built for those paths reactively.
Go deeper
Want the full story? The deck walks through problem framing, user journey, final shipped screens and prototype.