Back to all posts
App Design7 min read·November 15, 2026

Designing GST Invoice Screens for a Billing App

TB
ThynkBlox Apps Team
App Engineering

To design the GST invoice feature in a billing app, plan each invoice screen around rules the business can configure rather than rules hard-coded into the app. Tax fields, invoice numbering, what happens after an invoice is issued, sharing and offline creation each need their own decisions before design starts. The tax calculation itself is a requirement that the business's accountant supplies. The app's job is to apply it consistently and make it easy to check.

This guide covers screen design and product decisions. It does not cover GST rates, e-invoicing rules, registration thresholds or legal advice. For those, ask a chartered accountant or check the official GST portal.

Last reviewed: November 2026

Who decides how tax is calculated?

The business decides, with advice from its accountant. Product owners should not copy tax logic from another app or guess it from examples. Ask the accountant for a written specification that covers how each line is taxed, how place of supply affects the tax split, how rounding works and which details must appear on the invoice.

Treat that specification as an input, like a brand guide. Design the screens so that whoever has permission can update tax settings later without an app release. Rules change, and an app that needs new code for every change will fall behind.

Before design starts, confirm three things with the accountant:

  • Which tax fields are required on an invoice, and which are optional.
  • How tax is calculated at line level and at invoice level, including rounding.
  • Which details must stay unchanged once an invoice is issued.

What should each invoice screen handle?

The table below shows the main screens, what each one does and the decision you need to make before design.

ScreenWhat it doesDecision to make first
Tax settingsStores the business's registration details, tax categories and rounding rulesWho may edit settings, and whether changes apply only to new invoices
Party and item setupHolds customer details and item tax categories that invoices reuseWhich fields are mandatory, as defined by the accountant
Create invoiceAdds the party, line items, quantities and discounts, then shows the calculated taxWhether tax is shown per line, as a summary or both
Invoice numberingAssigns the next number in a seriesPrefixes, separate series per branch or financial year, and when a number is reserved
Review and issueShows the final invoice before it is issuedWhat becomes locked once the invoice is issued
Edit or cancelHandles corrections after an invoice is issuedWhether corrections use a credit note, an amendment or cancellation, as the accountant advises
Share and exportSends a PDF, prints or exports dataFormats needed by the business and its accountant
Offline draftsLets users create invoices without a connectionHow numbers are assigned when the device reconnects

Map how users move between these screens before drawing any of them. The guide to mapping mobile app user flows explains how.

How should configurable tax fields work?

Keep the tax settings separate from the create-invoice screen. Users creating an invoice should pick a party and items and see tax calculated from stored settings, not type tax values by hand.

Good tax settings screens:

  • Label every field in plain words, with a short help line written by or checked with the accountant.
  • Apply changes to new invoices only, so issued invoices keep the values they were issued with.
  • Record who changed a setting and when.
  • Restrict editing to roles that should have it. Our guide to planning user roles and permissions covers how to set this up.

On the create-invoice screen, show the taxable value, each tax component and the total clearly. A person checking the invoice should be able to follow the arithmetic without opening another screen.

What rules should invoice numbering follow?

Invoice numbers need to be unique and in order within each series. The accountant should confirm the exact format, including prefixes and when a new series starts.

Design decisions to settle:

  • When a number is assigned. Assigning it at the moment of issue, not when a draft is created, avoids gaps from abandoned drafts.
  • Multiple series. Some businesses need separate series for branches, devices or financial years. Let the business configure this.
  • Double taps and retries. A slow connection can make a user tap Issue twice. The app must never create two invoices or use two numbers for one sale. See preventing duplicate submissions in a mobile app for the patterns that help.

Show the number only once the invoice is issued, and never let users type over it.

How should editing and cancelling work after issue?

Once an invoice is issued, treat it as a record, not a document anyone can freely edit. Ask the accountant which corrections the business uses: cancellation, a credit or debit note, or a revised invoice. Design one clear path for each.

On the invoice detail screen:

  • Show the status (draft, issued, cancelled) clearly at the top.
  • Offer correction actions only to roles allowed to use them.
  • Ask for a reason when an invoice is cancelled, and keep the original visible with a cancelled label.
  • Link related documents, such as a credit note, to the original invoice.

Keep drafts fully editable. The lock applies to issued invoices only.

What should sharing and exporting include?

Most users need to send an invoice to the party straight away and hand records to their accountant later. These are different jobs.

For sharing, generate a PDF that matches the layout the accountant has approved, and let users send it through the phone's share sheet or print it. Show a preview before sending.

For export, ask the accountant which format and fields they need, usually a list of invoices over a chosen period. Make the date range and filters obvious, and say clearly what the export includes.

If a PDF or export takes time to prepare, show progress and a clear error if it fails. Our guide to designing loading, empty and error states covers these screens.

How should offline invoice creation work?

Shops and field staff often bill without a reliable connection. Decide early whether offline invoices are drafts that get numbered on sync, or whether each device gets its own number series that works offline. Both approaches can work. The accountant should confirm which numbering approach is acceptable.

Whichever you choose:

  • Show clearly which invoices are waiting to sync.
  • Use the tax settings saved on the device, and flag if settings changed while the device was offline.
  • Handle conflicts, such as the same party being edited on two devices, without silently losing data.

The guide to planning offline data sync goes into sync design in more depth.

What common mistakes should you avoid?

Hard-coding tax logic. Rules change. Keep tax settings configurable and owned by the business.

Designing tax from screenshots of other apps. Get the specification from the accountant instead.

Numbering drafts. Abandoned drafts leave gaps. Assign numbers on issue.

Letting issued invoices be edited freely. Use a defined correction path and keep the original.

Treating sharing and export as the same feature. Customers need a clear PDF. Accountants need complete, filterable data.

Ignoring offline use until late. Offline numbering affects the data model, so decide it at the start.

When does this not apply?

If the app only records sales for internal tracking and never issues tax invoices, most of the numbering and correction rules here are more than you need. If the business must also connect to a government e-invoicing system, that integration needs its own requirements from the accountant and is outside the scope of this guide.

What questions do founders often ask?

Can the app calculate GST without an accountant's input?

The app can do the arithmetic, but it should not decide the rules. Ask the accountant for a written specification of fields, calculation and rounding. Build the settings screen around it so the business can update values when rules change, without waiting for a new app release.

Should invoice numbers be generated on the device or the server?

It depends on how much offline use you need. Server numbering is simpler to keep unique and in order. Device-level series support offline billing but need careful setup. Confirm with the accountant which approach is acceptable before the team builds the data model.

Do I need an admin panel for invoice settings?

Not always. A small business may manage tax settings and roles from a restricted screen in the app. Several branches, many users or accountant access usually justify a web panel. Our guide on whether a mobile app needs an admin panel helps you decide.

How do I keep the invoice feature small for a first release?

Start with tax settings, creating and issuing invoices, PDF sharing and one correction path. Add multiple series, detailed exports and offline numbering once the core flow works. The guide to scoping an app MVP explains how to make these trade-offs.

Ready when you are

Planning an app of your own?

Tell us where your project is today. We will help you work out the scope before you commit to a budget.