Reviewing a batch
Importing opens a review table for the batch. Each collection has been split into its charge lines, priced against your rate cards, and matched to your sites, streams and containers. Your job is to deal with whatever it couldn’t settle on its own.
A useful way to think about it: a clean commit means no banners left that you haven’t consciously dealt with. Work the banners first, then the individual rows.
The banners, and what to do about them
| Banner | What it means | What to do |
|---|---|---|
| Check site mapping | The site it matched doesn’t resemble what the invoice actually says | Open the invoice and confirm. See below — this is the one that bites |
| Won’t price | The lines will commit, but bill $0, because no sell rate covers them | Fix the rate card before committing |
| Supplier mismatch | These sites usually belong to a different subcontractor | Almost certainly the wrong profile. Delete the batch and re-upload |
| Duplicates | A line repeats within the file, or already exists in a committed batch | Confirm it’s genuinely a second collection, otherwise delete the row |
| Cost variance | The total WastePro modelled differs from the invoice total you entered | Investigate before committing — this is your completeness check |
Site mapping is where the real risk sits
The matcher scores on address, and it deliberately ignores unit numbers — which means a neighbouring business at the same street address can look like an excellent match while being completely the wrong customer.
So the rule is: the name and the unit number both have to fit, not just the street. If the venue on the invoice isn’t in WastePro at all, create the customer and site properly first. Never accept a nearby suggestion because it scores well.
Every wrong-site incident so far has had the same signature — a suggestion that matched the address strongly and the business name not at all. If the two names share no words, treat that as a stop sign rather than a formality.
Won’t price is not the same as broken
A “won’t price” line is loaded and correct. It just has nothing to bill against, because the site’s service has no rate for that stream and container combination — or has the lift rate but not the excess-weight rate.
Fix it on the service’s rate card, not in the grid. And fix it before you commit, while you’re still looking at it.
Mapping streams and containers
Map to the codes your rate cards actually use. It’s possible to map a supplier’s “Cardboard” to a perfectly sensible-looking code that no rate card references — in which case every cardboard line loads cleanly and bills nothing, month after month.
Typing a code by hand in a row edit will accept an invalid one, and it fails at commit with an unhelpful error. Choose from the suggestions rather than typing.
Working efficiently
- Suggest fixes asks WastePro to propose mappings from this supplier’s codes and the decisions you’ve made before. Review what it proposes — it’s a shortcut, not an authority.
- Bulk fixes only apply to unresolved rows. They can’t repoint rows that already matched, deliberately. To change a row that resolved, edit that row.
- If mappings or rates changed since you uploaded, re-run the transform from the batches list to pick them up. Edits you’ve pinned survive it.
- Reconcile every batch by entering the invoice’s total excluding GST. A small tolerance is allowed for rounding.
Next: Committing.