Compliance

7 min read

EXDOC to NEXDOC: What Actually Changed for Australian Meat Exporters

EXDOC to NEXDOC: What Actually Changed for Australian Meat Exporters

EXDOC to NEXDOC: What Actually Changed for Australian Meat Exporters

Meat certification moved to NEXDOC on 6 July 2026 and the EXDOC grace period closed at the end of July. Changing the system was the easy part. The documentation work sitting either side of it never moved, and that is where the hours still are.

Meat certification moved to NEXDOC on 6 July 2026 and the EXDOC grace period closed at the end of July. Changing the system was the easy part. The documentation work sitting either side of it never moved, and that is where the hours still are.

Identical stamped plates passing through sequential stations, representing certification stages

If you export meat or poultry, you have spent the last month inside a new system. Meat and meat products moved from EXDOC to NEXDOC on 6 July 2026, certificates for China had to be complete and printed by 3 July, and the transition window for other destinations closed on 31 July. That work is done.

What most exporters are finding now is that the system change did not touch the part of the process that was actually expensive. The certificate was never the bottleneck. Assembling the information that goes into it was, and still is.

01 What genuinely changed

The visible changes are straightforward. A Request for Permit is now a Request for Export, so RFP becomes REX. Certificates print on plain paper rather than blue security stock, with a QR code as the verification feature. Statuses are renamed and re-sequenced, running through draft, final, in review, certificate ready and completed. Registration works differently: you register a client group and an exporter, and permit declarant status depends on being registered first.

One practical detail catches people out. The NEXDOC portal does not carry every function that integrated third party software does. Forwarding a REX so a certificate prints in your freight forwarder’s office is one of them. If you moved to the portal to avoid a software conversation, you may have moved a task back onto your own desk without noticing.

02 What did not change at all

Before anyone lodges anything, someone in your business assembles a consignment record. Product and establishment codes. Destination requirements pulled from Micor, which differ by market and change without much warning. Net and gross weights. Lot and batch numbers. Container and seal numbers that arrive by email from the forwarder, usually late. Halal certification where the market requires it. The commercial invoice and packing declaration that have to agree with all of it.

In most meat and poultry businesses under one hundred million in turnover, that record does not exist in one place. It is assembled by one experienced person reading a production system, a spreadsheet, and an inbox, then typing the result into a certification system. Changing which certification system they type it into does not reduce that work by a minute.

03 The errors are all in the same place

Nearly every documentation problem we see in food export traces back to a single cause: the same data entered twice, by hand, from two different sources.

A transposed digit in a container number. A weight that matches the packing list but not the invoice. An establishment number that was right last quarter. None of these are complicated mistakes. They are attention mistakes, made at speed, usually late in the day, by someone doing three other things.

The cost is not the amendment. It is the consignment sitting while it gets corrected, the forwarder chasing, and in the worst cases a hold at the destination border on product with a shelf life. That is a commercial cost that never appears on a line item, which is exactly why it survives for years.

04 What actually helps

Three things, in this order.

One consignment record. A single structured record per consignment that everything else reads from: the pick, the invoice, the packing declaration, the certification request. Not a new system necessarily. Often it is a layer that reads what your production system already holds and fills the gaps that currently live in someone’s inbox.

A checking step before lodgement. Weights that must agree, fields that must be present for that destination, codes that must match the establishment. A checklist that runs in a second and flags mismatches to a person, rather than a person holding the checklist in their head at 4pm.

Generated supporting documents. The packing list, the commercial invoice, the declarations and the supporting pack all built from the same record rather than re-typed from each other. This is the piece that removes the most hours, and it is usually the least difficult to build.

05 What should stay with a person

The lodgement decision. Market access requirements shift, importing country conditions get amended, and the judgement about whether this consignment meets this market’s conditions today belongs to someone accountable, with the documentation in front of them.

The useful goal is not an unattended certification process. It is a person who spends ten minutes checking a complete, consistent record instead of ninety minutes building one.

Where to start

Find the point where consignment data is typed a second time. In almost every business we have looked at, it is between the production or dispatch system and the documentation pack, and it is being done by the one person who knows how. That person is also your single point of failure the week they take leave.

If you export meat or poultry and your documentation pack is built by hand, send us a week of consignments and we will map exactly where it is being re-keyed.

Related reading: Where the hours go in a third party logistics operation, and our recent work in food distribution.

Frequently asked questions

What is the difference between EXDOC and NEXDOC?

EXDOC is the legacy export documentation system. NEXDOC is the department’s replacement, rolled out commodity by commodity, with meat and meat products transitioning on 6 July 2026. NEXDOC issues certificates on plain paper with a QR code, changes several process terms, and offers a self service portal alongside integration with third party software.

What replaced the Request for Permit?

A Request for Permit (RFP) in EXDOC is a Request for Export (REX) in NEXDOC. The status names changed with it, moving through draft, final, in review, certificate ready and completed.

Can I use the NEXDOC portal instead of third party software?

Yes, registered exporters can lodge directly through the portal. The portal does not include every function available through integrated software, including forwarding a REX so a certificate can be printed in a freight forwarder’s office. If that matters to your dispatch process, confirm it before you commit.

Can export documentation be automated?

The assembly and checking can be. Pulling consignment data from one source, generating the supporting documents from that record, and flagging mismatches before lodgement all remove manual work without touching the compliance decision. The lodgement itself should stay with an accountable person, because importing country requirements change and judgement is required.

Have a process worth improving? Let’s find the highest-value place to begin.