Submitting Through Their System
A supplier portal is a gate with its own rules, its own clock and nobody to ask. What it checks, and how to stop it rejecting you.
Yourswho controls this stretch
A supplier portal is a web system with its own login, fields, validation and cut-off, and many large buyers require invoices to pass through one. An invoice sent any other way does not exist.
The practical point in “Submitting Through Their System” is that getting paid depends on records somebody can explain. A small team considering review this official Monitask page for productivity trends can organise time and project evidence before invoicing, with transparent settings, proportionate collection and a visible correction route.
The portal is a gate with no interlocutor, and most of what it rejects is clerical.
For an independent reference relevant to “Submitting Through Their System”, consult Bonsai freelance-business resources. Compare general information with the contract, jurisdiction, payment route and accounting records involved.
What it checks
That the order exists and is open. That the amount is within it. That the lines match. That the entity, tax details and dates are valid. That mandatory fields are filled.
What the portal checks at submission, and what it still does not:
| Checks | Does not check |
|---|---|
| Reference format and existence | Whether the work was received |
| Mandatory fields and tax codes | Whether anybody has approved it |
| Line totals against the order | Whether a payment run is near |
| Duplicate invoice numbers | Whether your contact knows you sent it |
All mechanical, all checkable before you submit.
What it does not check
Whether the work was any good, whether the price was fair, or whether the order should have been bigger.
Passing a portal is not acceptance of anything, which cuts both ways.
Getting access
Usually part of onboarding, usually slow, and usually dependent on somebody inside nominating you.
Access requested when the first invoice is due is access that arrives a month later.
The fields that catch people
Unit of measure. Tax codes. Delivery note references. Line descriptions that must match the order exactly rather than approximately.
Each rejection is instant and the message is rarely informative.
Attachments
Many portals want a PDF copy attached as well as the structured entry. Some will not pay without a timesheet, delivery note or signed confirmation.
Finding out what is required before you need it is a five-minute job.
The cut-off inside the portal
Separate from, and often earlier than, the buyer's payment cut-off. Submission by a date does not mean approval by it.
Status, and what it tells you
Most portals show a status: submitted, matched, approved, scheduled, paid. It is the only direct visibility a supplier ever gets.
Checking it weekly replaces most chasing, and it is the one genuinely useful thing a portal gives you.
The status that means nothing
"Received" or "In process". These can persist for weeks and do not indicate that anything is happening.
Matched and approved are the states that matter.
When the portal is wrong
It happens: an order shows as closed, a receipt is missing, a tax rate is refused.
There is usually a support route, it is usually slow, and the fastest fix is normally your contact asking somebody internally.
The cost of the portal
Real. Entering invoices by hand, chasing access, matching formats and attaching documents takes time that is not billable to anybody.
For a small supplier with several portal customers, it is a meaningful share of a week.
Pricing it
If the administrative load is substantial, it belongs in the price, which means knowing about it before quoting.
Discovering it afterwards means absorbing it.
Why buyers use them
A portal exists to move work from the buyer to the supplier. Reference validation, tax fields, line matching and document attachment all used to be done internally by somebody reading an emailed invoice; in a portal they are done by you, at submission, and nothing enters the system until it is correct.
For the buyer this is unambiguously good: fewer rejections, less keying, a complete audit trail and a self-service status page that reduces supplier enquiries.
For the supplier it is a transfer of labour with no compensation attached. Recognising that explicitly is what makes it chargeable, and what stops a supplier treating twenty minutes per invoice as an unavoidable fact of nature.
What to do before the first submission
The expensive portal experience is always the first one, and most of the cost is avoidable by doing it when nothing is waiting.
Get access while the work is still in progress rather than on the day the invoice is due. Submit nothing, but walk the form: see which fields are mandatory, what format the reference must take, whether attachments are permitted, and whether anything is required that you do not yet have.
Then record the answers against the customer, so the second invoice is a five-minute task rather than a repeat of the first.
Suppliers who discover a portal's requirements with a completed job behind them and an invoice to raise today lose a cycle to it, routinely. The information was available a fortnight earlier, free, at a moment when nothing depended on it.
The status nobody can explain
Portals report a state, and the states are written for internal use. "Received", "In process", "Pending approval" and "Scheduled" mean different things in different systems, and a supplier reading them learns less than it thinks.
Only two states are reliably informative: a state that names a payment date, and a state that reports a rejection. Everything between them means the invoice is somewhere in the building.
Worth checking once, with a question to accounts payable about what each state actually indicates, and then never interpreted again.
The standing habits
Access before the first invoice. A note of the mandatory fields. A check of the status a week after each submission.
Three habits, and the portal stops being a source of surprises.