Compliance with an experience dividend

The situation

In Japan, businesses issue a monthly consolidated “invoice summary” — a document format deeply embedded in local business culture. Japan’s Qualified Invoice System, effective October 2023, imposed strict new requirements on tax invoices. Every ERP had to comply. Deadline fixed, scope legally defined.

The easy path: bolt the new tax fields onto the existing flow. But the existing Invoice Summary experience carried a decade of accumulated friction:

• Generation was painfully slow. Customers complained about long waits; some partners had built workarounds — running saved searches instead of the feature, scheduling generation overnight with RPA, even rebuilding the whole flow in Microsoft Access. When your customers engineer escape routes around your feature, the feature is the problem.
• The design was ten years old and no longer fit how Japanese businesses actually work: no way to customize the template (in Japan, invoice summary layouts are industry-specific — one standard template fits almost nobody), no draft or preview before generation, and no easy way to adjust a summary after generation — in a culture where the generated PDF is treated as the definitive legal record and checking it before release is non-negotiable.

We made a deliberate bet: use the compliance mandate as the catalyst to redesign the experience itself.

Question the expensive feature before optimizing it

The slowness had a specific cause: during generation, the system built a link between every invoice transaction and its summary. Engineering saw a performance problem to optimize. We asked a different question: does anyone actually use those links?

I framed it as a testable hypothesis — users verify their summaries from the PDF and their own saved searches, not by clicking through transaction links — and we put mockups in front of users: the current design with its long generation time versus a linkless design that generated fast. That reframing changed the solution space entirely: instead of spending engineering months optimizing how links were built, we could stop paying for something users didn’t value.

It’s my favorite kind of design work — the screen barely changes, but the product gets fundamentally better.

Understand the real workflow, not the legal text

• Journey mapping with the Professional Services team — the people who see how customers actually configure and use invoice summaries — structured around four explicit hypotheses: the unused links, the one-summary-per-transaction rule, setup frequency, and the confusing naming of “standard” versus “consolidated” summaries.
• Customer and partner interviews, run in both English and Japanese, which surfaced the cultural weight of the document: the invoice summary PDF is the definitive version of the issued invoices, so checking before release — and often sending a draft to the customer first — is standard practice.
• A design thinking workshop with dev & PM to align everyone on where the pain actually was.

Design the compliance and the experience together

• New tax invoice rules designed alongside a rethought Invoice Summary flow, aimed squarely at the researched pain: preview before generation so errors are caught early, easier adjustment of a generated summary, and template customization for industry-specific formats.
• The Void Invoice Summary feature: instead of deleting (an audit nightmare), voiding reverses the journal — compliance-safe and clearer for accountants. This directly addressed the delete-and-regenerate cycle users described in interviews.
• Later, the SuiteTax SuiteApp revamp carried the redesign further, building on our accumulated research.

Verify like it’s a compliance project — because it is

• Click tests on the new tax rule and invoice summary features.
• Guerrilla tests on prototypes before launch.
• A post-launch survey on the new financial reports and templates, feeding the next iteration round.

Sweat the physical detail

Japanese invoices are mailed in windowed envelopes. Our new PDF templates position the receiver’s name to stay visible through the envelope window — a detail no requirements document asked for, and exactly the kind users notice.

Outcome

• Customers compliant with the Qualified Invoice System on deadline.
• Invoice Summary experience redesigned end-to-end, not patched — the research from this arc powered the SuiteTax SuiteApp revamp and further report and template work.
• Research-integrated delivery became the norm: surveys, guerrilla tests, and expert interviews are now standard steps, not nice-to-haves.

What I learned

Compliance projects are the best-disguised UX opportunities in enterprise software: budget is guaranteed, attention is guaranteed, deadlines are immovable — the only variable is whether design shows up with ambition. And the highest-leverage question a designer can ask isn’t “how should this look?” but “should the system be doing this at all?”