⏱ 8 min read

Looking at a sales purchase database example of a GST number before pulling your own is a useful step — it sets expectations for what the fields actually mean and how the data is typically structured, so the real thing doesn’t come as a surprise.

This guide walks through what a typical record contains, how to read each part of it, and what commonly differs once you’re working with your own data instead of a sample.

This isn’t a topic that needs to be treated as more complicated than it actually is, though a few of the details below are easy enough to get wrong on a first attempt.

What a Typical Example Looks Like

Header-Level Details

A typical record starts with identifying information — the registration number, the business name on file, and the period the record covers. These fields anchor everything else in the record.

Confirming these header fields match what you expect is the first and easiest sanity check on any sample or real record.

Line-Item Detail

Below the header, individual line items typically break the total figure down further — by transaction, category, or sub-period, depending on how detailed the source data is.

Not every source provides this level of breakdown; some only offer a summarized total, which is worth confirming before assuming line-item detail will be available.

Walking Through a Sample Record

Reading the Transaction Value Fields

Value fields are usually labeled by type — gross, net, or taxable value, for example — and mixing these up when comparing across sources is a common and easy mistake to make.

Before comparing two figures from different sources, confirm they represent the same type of value.

Reading the Date and Period Fields

Period fields indicate the filing cycle a record belongs to, which may not be exactly the same as a calendar month or quarter depending on how the underlying filing system works.

Misreading a period boundary is a common source of an apparent discrepancy between two otherwise-correct figures.

Why Reviewing an Example First Helps

Setting Expectations Before a Real Pull

Knowing in advance what fields to expect, and in what format, makes it much easier to spot something wrong quickly once you’re working with your own real data.

It also helps set realistic expectations about how much detail a given source actually provides, before committing time to a real request.

Spotting Formatting Differences Early

Different sources structure similar data slightly differently — column order, date formats, naming conventions — and reviewing a sample first surfaces these differences before they cause confusion in a real analysis.

This is especially useful if you plan to combine data from more than one source, since formatting mismatches compound quickly.

From Example to Your Own Data

Adjusting for Your Actual Use Case

A generic example won’t perfectly match every real registration’s data — some businesses have more line-item detail, others less, depending on their filing history and how the source aggregates it.

Treat the example as a template for what to look for, not a guarantee of exactly what you’ll receive.

Common Differences From the Sample

Real records more often have gaps, partial periods, or inconsistent formatting across periods than a clean sample suggests — this is normal and not usually a sign of anything wrong with the underlying data.

Building in a quick validation step for your own pulls, rather than assuming they’ll look exactly like the sample, saves confusion later.

Frequently Asked Questions

Does a sample record always match what a real pull will look like?

Broadly, yes for the field structure, but real records vary more in completeness and formatting consistency than a clean example typically shows.

What if my real data is missing a field the example includes?

Not every source provides the same level of detail — check with the specific source about what fields it actually includes before assuming something is missing in error.

Why do figures from two sources sometimes not match?

This is usually a mismatch in value type or period boundary rather than an actual error — confirm both are measuring the same thing before assuming a discrepancy.

Quick Recap

Reviewing a sales purchase database example of a GST number before pulling real data helps set accurate expectations for field structure, formatting, and level of detail — making it much easier to spot something genuinely wrong once you’re working with your own records.

For a broader overview of sourcing this kind of information, see our gst data.