Request Submission: Forms, Fields & Attachments Explained
Request submission is the moment a decision enters the governed pipeline: a user completes the workflow's form — name, amount, vendor, documents — and the request routes to its first approval stage automatically.
The submission form is where data quality is decided: everything downstream — matching, routing, reporting — depends on what arrives here. This guide covers the fields, the attachments, and the auto-fill that makes errors structurally impossible. Part of the product guide.
What a complete request carries
- Request name — what this is, in one line ("Q3 Facebook Ad Spend")
- Amount and currency — the number the matrix routes on
- Vendor — selected from the verified master, which auto-fills the bank details, read-only
- Description and notes — the why, captured where the approver will actually read it
- Attachments — the invoice, PO, quotes; viewable inline by approvers
- Department — inherited from the submitter automatically, for analytics
Why auto-fill is a control, not a convenience
The two most expensive submission errors are mistyped IBANs and invoices submitted without the right documents. Auto-fill eliminates the first (nobody types bank details — the master file provides them); required fields and mandatory attachments stop the second at the form, before a stage ever waits on missing paperwork. The form enforces completeness so approvers never chase it.
Frequently Asked Questions
What fields should an approval request form have?
Name, amount with currency, vendor from the verified master, description, and required attachments — plus the department and bank details the system supplies automatically.
What happens right after submission?
The workflow routes the request to its first stage automatically — named approvers notified, deadline running, audit trail opened. No forwarding, no CC.
Approvdit's submission forms enforce required fields and attachments, auto-fill verified bank details, and route instantly on submit. Book a live demo.