Invoice admin
Submitting an invoice through a customer portal: check fields and status
To submit an invoice through a customer's portal, first confirm the portal and supplier account, then match each required field to the issued invoice and customer instructions. Save the result of submission and check what the displayed status actually means. A saved file or upload confirmation alone does not establish that accounts has accepted the invoice for payment.
By PayerPing · Published
Confirm the portal and account before entering details
Use instructions verified through your known customer contact. Confirm which business entity and supplier account the invoice belongs to, whether an invitation is needed and where the customer's help instructions are. A portal address in an unexpected message is a reason to verify the route before entering credentials or invoice information.
Read that customer's current submission instructions. This workflow is generic: field names, accepted files and status meanings vary. It cannot substitute for a particular portal's documentation. If the invoice was already emailed or uploaded, find out whether there is an existing record before creating another submission.
Map required fields to a checked source
In this fictional example, Mara is submitting INV-522 for £840. The map distinguishes known information from a missing customer reference. It is a preparation worksheet, not a set of fields every portal requires.
| Requested field | Checked source | Value or gap | Decision |
|---|---|---|---|
| Supplier account | Customer setup confirmation | SUP-62 | Check displayed business matches |
| Invoice number | Issued invoice | INV-522 | Copy exactly; do not use PO here |
| Total | Issued invoice | £840 | Check currency and field instructions |
| Order reference | Customer confirmation needed | Not yet confirmed | Ask project contact; do not guess |
| Invoice file | Current invoice record | INV-522.pdf | Open and check before selecting |
Use the invoice details checklist to check the document itself. If a required field conflicts with your invoice or agreement, ask accounts how to proceed rather than altering a value solely to make validation pass.
Record what happened after you pressed submit
PORTAL STATUS CHECK Invoice number: Customer / supplier account: Submission date and time: Portal record or receipt identifier: Exact displayed status: Customer's explanation of that status / help-page reference: Evidence saved in invoice record: Known missing field or approval: Next action / owner / review date: Original issue date and agreed due date checked:
Record the exact status rather than translating it into “approved”. In a fictional portal, “file stored” could describe a saved attachment while a separate submission button remains unused. In another, “submitted” may be the final supplier action. Only the customer's instructions or confirmation can resolve the meaning in your case.
Save the relevant receipt or status record without copying unrelated invoice or customer details. If the page gives no confirmation, check whether a record exists before pressing submit again.
Follow up on the unconfirmed stage
For INV-522, Mara receives receipt R-73 but the status says “awaiting validation”. Her next question is whether validation found a missing item, not whether payment was made. She asks accounts to confirm that stage using the invoice and receipt identifiers.
If accounts confirms receipt but names a pending approver, use the approval delay workflow. If no one answers, use the no-reply follow-up guide with the submission evidence. Keep the agreed due date visible; a later portal action is not evidence that both parties agreed to replace it.
Keep reading
- Invoice approval delay email: find the next step and owner
- Overdue invoice and no customer reply: what to check next
- Invoice details checklist: remove payment admin blockers