| Australian 8-digit item, stat code and duty rate | Often guessed or invented; models cannot see the current Working Tariff and routinely produce codes that do not exist. | Chosen only from the real items in the published Schedule 3, with the version recorded on every line. |
| Reads the whole shipment, not one product | You paste one description at a time, then retype the answer. | Upload the invoice and packing list; every line is extracted, classified and checked in one pass. |
| Cross-checks the documents | Only if you ask, every time, and only for what you paste. | Quantities, weights, values, parties, origin and incoterms compared across every document automatically, plus arithmetic checks. |
| Audit trail for the ABF | A chat history on someone’s personal account. Auditors do not accept “we asked an AI” as reasonable care. | Every suggestion, reason, alternative, edit, reviewer and timestamp is stored with the documents and exportable for the five-year record period. |
| Consistency across shipments | None. Each chat starts from zero; the same product can get three different codes in a week. | Product memory reuses what your team approved and flags any difference before it reaches the entry. |
| Confidentiality of client documents | Depends on which account and settings staff happen to use. Industry bodies warn against uploading client documents to unrestricted platforms, and some PI policies exclude it. | Company-controlled workspace, roles, logging, encryption, no training on your data, and a published sub-processor list. |
| A review step you can’t skip | Whatever the person reading the chat decides to do. | Operators prepare, reviewers approve, nothing exports as final until a licensed broker signs it off. |
| Fits the team’s day | Copy, paste, copy, paste. | Email the documents in, get the draft back, export the approved lines to your customs system. |