The Year That Puts You In Scope
The short version, first
Singapore's packaging report is decided by one number and made of another. Whether you are in scope turns on your annual turnover, or the quantity of packaging you put out, or both — the criteria are set by regulation. What you then have to file is an account of the specified packaging you imported or used, which is a physical property of every item you sell and one that no commercial system records. Our item is a name, a free-text category, a description, a stock count and two prices. It has no weight, no material and no packaging. The turnover half we can answer to the cent. The packaging half we cannot answer at all — and the Act gives you a year to start, because the year that puts you in scope is not the year you report on.
Most compliance shapes we look at are about a date or a permission. This one is about a unit. Part 4 of the Resource Sustainability Act 2019 asks a producer to report the specified packaging it imported or used, and packaging is measured in mass by material — so many kilograms of paper, of rigid plastic, of glass, of metal. Every operations system on earth records what it sold in counts and in money. The gap is not a missing feature. It is a missing dimension, and it is one you can start collecting today.
Who is a producer
The word is doing unusual work here. Under section 19(2) a producer of specified packaging is not the company that manufactures cardboard. It is a person who <em>imports</em> specified packaging — by importing regulated goods contained in it or wrapped with it — or who <em>uses</em> it, which the Act spells out four ways: by packing or wrapping regulated goods with it, by providing it to a retailer, by providing it to a consumer who buys regulated goods, and by putting regulated goods into it.
So a distributor who brings in boxed goods is a producer. A manufacturer who wraps its own output is a producer. A brand owner who supplies packaging to the shop that sells its product is a producer. And packaging itself is defined broadly — any material or combination of materials used for the containment, protection, handling, delivery or presentation of goods, with one carve-out that repays attention: material that stays in the producer's possession to be re-used for those purposes is not packaging. Reusable crates that come back to you are outside; the same crate sent one way is not.
Three years, and only one of them is the reporting year
Section 20(1) is one sentence and it carries three different years. A producer who fulfils the prescribed threshold criteria in any year — call it T — must, in year T plus two, submit a report relating to the specified packaging imported or used in year T plus one.
-
Year T — the year that puts you in scope
Your annual turnover, or the quantity of specified packaging you imported or used, or both, meets criteria set by regulation. Nothing is reported about this year. It is the qualifying test and nothing else.
-
Year T+1 — the year you report on
Everything you import or use in packaging terms this year is what the report will describe. If you were not capturing packaging data on 1 January of this year, the year is already partly unrecoverable.
-
Year T+2 — the year you file
The report goes to the Agency, in the form the regulations prescribe, together with a plan to reduce, re-use or recycle packaging in Singapore.
-
And afterwards, if it is wrong
Where a report or plan is incomplete or inaccurate, the Agency may direct you in writing to rectify or re-compute any matter in it and to resubmit within a specified time.
The gap between qualifying and reporting is the whole operational message
A great deal of compliance advice reduces to "keep good records". Here the Act tells you precisely when to start: the moment year T closes, because year T+1 is the one that will be filed. That is unusually kind, and it is the only warning you get. It also means the trigger and the content sit in different systems — the trigger is a turnover figure your finance reports produce without being asked, and the content is a physical attribute nobody has ever entered. You can be certain you are in scope and unable to produce a single line of the return.
Two more provisions shape who files. Where the producer is a franchisor, the turnover and the packaging of <em>all</em> franchisees count towards the threshold, and references to packaging the franchisor imported or used include the franchisees'. Conversely, a franchisee whose franchisor is a Singapore-connected person does not report separately. So a franchise network is one producer for this purpose, and the aggregation runs upward.
And the offence provisions say two things worth noticing together. The fines escalate — not more than five thousand dollars on a first conviction, not more than ten thousand or three months or both on a second, with a further daily fine while a continuing offence continues. And it is not necessary to prove that the defendant intended to commit the offence: the Act says in terms that this is a strict liability offence. The same is true of the 3R plan requirement. Whether you meant to miss it is not a question anybody has to answer.
What we hold, and the one column that is missing
The inputs to a packaging report, against our schema
| The input | Held today | Per item | Reportable across a year |
|---|---|---|---|
| Annual turnover, per currency | Yes | No | Yes |
| Quantity of each item sold | Yes | Yes | Yes |
| Quantity of each item purchased or imported | Yes | Yes | Yes |
| The supplier and order a batch arrived on | Yes | Yes | Yes |
| A unit of measure on an item | No | No | No |
| The mass of packaging on an item | No | No | No |
| The material that packaging is made of | No | No | No |
| Whether the packaging comes back to you | No | No | No |
Built and maintained Configurable by you, not maintained by us Not built
The first four rows are the ordinary machinery of a business system and they are complete. The last four are one build: a per-item attribute set describing the packaging on a unit. The last row is the carve-out in the definition — material that stays in your possession to be re-used is not packaging — and it is a flag rather than a figure.
The item record in this product is a name, a free-text category, a description, an integer stock count, an inventory account, a reorder point, a buying price, a markup and a selling price, with a photograph. It has no unit of measure — something we ran into from a different direction when <a href="/blog/five-things-a-price-has-to-be">a British price marking rule</a> asked for a price per unit — and consequently no mass, no material and no packaging. Every line in every document is a count.
The threshold is denominated in money and the return is denominated in kilograms. One of those we can produce for any period you name. The other has never been typed into the system by anybody.
What is genuinely useful here is that the missing half is addable without waiting for us. Custom fields on the item record reach the web, the API, the mobile app, reports, exports, <em>imports</em> and the workflow engine. That last one matters more than it sounds: a packaging mass and material per item is a spreadsheet exercise across your catalogue, and being able to bring it in as a bulk import rather than a screen-by-screen edit is the difference between a week and a quarter. Once the attributes exist as values, the arithmetic is a report over quantities you already hold.
The one thing worth thinking about before you start is what happens to last year's figure when the catalogue changes. The Agency may direct you to rectify or re-compute a report and resubmit it, which means both versions matter — and a report in this product is regenerated from live data rather than frozen at submission. We have written about that distinction in <a href="/blog/certified-reports-single-source-kenya">Certified Reports</a> and about what happens the moment a report becomes a file in <a href="/blog/every-export-is-a-fork">Keeping a Report Live Instead of Exporting It</a>; for this obligation the practical answer is to keep the export you filed, and to date the packaging attributes so a re-computation can be done on the values that were current then.
Turnover for any period, per currency
Till sales and customer invoices both carry totals and a currency code, and both are report datasets, with unlike currencies disclosed rather than summed.
Quantities in and out, per item
Purchase order lines, sale lines and invoice lines all carry a quantity, so units imported and units supplied are countable for any window.
A per-item attribute you define
Custom fields on items reach the web, the API, the mobile app, reports, exports, imports and the workflow engine.
Bulk import of catalogue attributes
The same custom fields can be populated from a file across the whole catalogue rather than item by item.
A unit of measure on an item
Stock is an integer count and price columns are money, so an item has no dimension in which a mass could be expressed natively.
Packaging mass by material, as a first-class attribute
A set of masses per material against an item, so a return is a sum rather than a spreadsheet built beside the system.
A returnable-packaging flag
The definition excludes material that stays in your possession to be re-used, which is a property of the packaging rather than of the goods.
A figure frozen as filed
A report is regenerated from live data, so what you submitted and what the same report says today are two different things once the catalogue moves.
What AWRA OpsHub does today
- Turnover for any period, in each currency it was earned in, from till sales and customer invoices, with the composition disclosed rather than converted into one figure.
- Quantities in and out per item, on purchase order lines, sale lines and invoice lines, so units imported and units supplied are countable for any window.
- A supplier and a purchase order against a received batch, so goods that arrived can be attributed to the shipment they came on.
- Custom fields on the item record, reaching the web, the API, the mobile app, reports, exports, imports and the workflow engine.
- Bulk import of those attributes, so a catalogue-wide data collection exercise is a file rather than a thousand screens.
- A report builder over the datasets that matter here, including till sales, customer invoices and items, with saved definitions and scheduled runs.
- A certification workflow on a report definition, so the organization can mark the definition it stands behind.
More we can add to your workspace
- A unit of measure on an item, which is the dimension a mass would be expressed in and which several other obligations want for their own reasons.
- Packaging mass by material as a first-class attribute, so the quantity of each material placed on the market is a sum over documents rather than a spreadsheet built alongside them.
- A returnable-packaging flag, marking material that stays in your possession to be re-used and therefore sits outside the definition.
- A figure frozen at the moment it was filed, held alongside the live report so a re-computation can be compared against what was submitted.
- A dated history on a catalogue attribute, so a report can be re-computed on the values that were current in the year it covers.
- Group aggregation across related entities, for a threshold that adds up a franchisor and every franchisee.
- A filing calendar keyed on a qualifying year, so an obligation triggered by one year's figures produces a task for the next year's data capture.
Where we point you to a specialist
- We will not tell you whether you are over the threshold. The criteria are annual turnover, the quantity of specified packaging, or both, and the figures are set by regulation rather than by the Act — we read the Act and not the regulations, and we will not print a number we did not verify. Get the current criteria from the National Environment Agency, and get advice on whether your goods and your packaging fall inside the prescribed definitions at all.
- We will not compute a packaging mass from a photograph or an item name, and we would decline to build something that guessed. The return asks for a physical quantity, the offence is one of strict liability, and an estimated figure that looks precise is worse than an admittedly rough one. What software should do is hold the number you measured, show its provenance, and multiply it by quantities it can vouch for.
- We hold a position on when to start, and it is the day year T closes rather than the day the return is due. The Act gives you a full year of notice by design, and the year it gives you notice about is the one that will be filed. A quotation from us for this work is a catalogue data-capture exercise first and a report second, in that order, because the report is trivial once the attribute exists and impossible before.
The second item is the build and it is small — a set of masses by material against an item, populated by import, and a report that multiplies them by quantities we already hold. The first is the wider fix underneath it and is worth doing at the same time, because a unit of measure earns its keep across pricing, shipping and stock as well. The third is a flag. The fourth and fifth belong together and are the difference between a return you can defend and one you can only re-run. The sixth and seventh are worth scoping if you operate as a group or a franchise, since the threshold aggregates upward and the calendar is keyed on a year that has already closed.
What we can build for Singapore on top of the standard product
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point for Singapore, not a limit on what AWRA OpsHub can do there. Kenya's eTIMS integration and its maintained payroll engine are in the product because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If an InvoiceNow access point, a CPF engine, a bank or mobile money feed, a statutory return format, a rule specific to how your operation runs, or a link to a system you already have is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
InvoiceNow, Peppol and GST reporting
Sending and receiving structured invoices through a Peppol access point on the InvoiceNow network, invoice data transmitted to IRAS on the schedule your registration date puts you in, and GST returns assembled from the underlying documents rather than from a summary. Worth stating plainly: Peppol is a receiving network as much as a sending one, and the inbound half is the one most implementations leave until last.
PayNow, GIRO and multi-currency banking
PayNow collection matched to the invoice, GIRO files, and multi-currency bank feeds wired into the Payments Register — which is most of the point in a market where the bank account and the operation are usually in different countries.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
Payroll and statutory returns
CPF contributions by age band and residency status, the Skills Development Levy, IR8A submission and IR21 tax clearance for departing foreign employees, computed on live records rather than assembled at year end.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedFour questions for a system that will produce a physical return
Can an item carry a weight?
What you will probably hear
There is a custom field for that.
How to read it
Good, and then ask two follow-ups: can it be bulk-imported, and can a report multiply it by a quantity. A value that only renders on a screen is a note; a value that participates in arithmetic is a column. The difference decides whether the return takes a day or a quarter.
How would we split one figure by material?
What you will probably hear
Add a field per material.
How to read it
Workable and worth testing at scale — ask what happens when a material is added or renamed across ten thousand items. A repeating set attached to an item behaves differently from six parallel fields, and the second is much harder to change later.
What did last year's report say when we filed it?
What you will probably hear
You can re-run it for that period.
How to read it
That is a different question and a different answer. Ask whether the figure as filed is stored, because a regulator who directs you to rectify and resubmit is comparing two versions, and a system that only knows the current one cannot show what changed.
Can a threshold be tested across a group of companies?
What you will probably hear
Each entity reports separately.
How to read it
Ask specifically about aggregation upward, because this obligation adds a franchisor to every franchisee. If each workspace is an island, the group figure is assembled by hand, which is exactly where a threshold test goes wrong.
Tell us what unit your obligation is denominated in
When a return asks for money or for counts, an operations system can usually produce it. When it asks for mass, area, volume or energy, the question becomes whether anybody ever recorded the attribute — and the answer is almost always no, with a year of notice to fix it. The companion piece to this one, from Japan, is <a href="/blog/four-figures-and-the-column-they-all-need">a statutory report blocked on a single missing column</a>, for very different reasons.
Talk to us about your workspace