Application detail (customer)

/contractor/applications/<id> reads, from the top: a next step banner (who has the move), status, requested and approved limits with payment terms in days, the decision, the signed answers, reference progress, the latest messages, your signature, activity and the signed decision history.

Next step banner#

One sentence above the fold (next-step): sent and not yet reviewed, "reviewing, references 2 of 3 answered", "waiting for your reply" (the supplier wrote the latest message and nobody on your side answered since; button Reply jumps to the messages), approved (limit and "Net 30, 60 or 90"), declined (with a link to Find vendors), or "not sent" for a draft. A decision always wins over a waiting message.

Progress tracker and the credit agreement#

Under the banner, a four step tracker shows Submitted, In review, Decision, Active. After an approval, Active is reached when the credit agreement the supplier sent is signed by both sides and stored; until then the tracker stays on Decision and the banner says what is open:

• Sign your credit agreement: the signing link was emailed to the person named on the agreement. The page never shows or links the signing address; the email is the only way in.
• You signed. Waiting for the supplier to countersign, then Both signatures are in while the signed copy is checked and stored, then Your credit agreement is signed with the account active.
• The credit agreement was declined or could not be sent: contact the supplier through Messages.

An approval with no agreement sent (the supplier does not require one) is Active at once. The agreement is the latest credit agreement for the application that is not cancelled or expired.

Decision#

The decision-summary block states the approved limit and terms. For a decline it lists the supplier's reasons in plain language (decline-reasons, from the decision record) and the supplier's note. Specific reasons are required for a decline, and the supplier's written notice was also emailed to the contact address on the application.

Who can use it#

The customer who created the application, and colleagues in the same organization whose role holds applications.view at organization scope (Owner, Administrator, Buyer Manager). Decision history and mark-as-read follow the same rule, so a colleague's application no longer shows a 404 or 403 on those parts.

Actions (each opens on demand)#

• Add reference (references.create), Edit and Remove (references.edit), Send reminder (references.remind): dialogs and confirmations, only while the application is undecided. A role without the key sees the status and dates but no button (Add is disabled and says who may). Statuses use the shared words: Awaiting response, Responded, Declined, No response. Answers stay confidential to the supplier.
• Reply or Message the credit team: opens a dialog with the message box and attachments. A half-written draft survives closing the dialog. The thread stays read-only on the page.

Related: Customer applying.

Forms the supplier asked for#

When the supplier asks for more details, a card per form appears under the application (needs forms.respond, which the applicant's own account holds). Fill it in, Save progress to come back later, and Submit when it is complete. Submitting checks every visible question and lists what needs attention under each one. Questions that depend on an earlier answer appear only when they apply. File questions upload the file right away through the normal checked upload (4 MB per file); the file also shows among the application's documents. Once submitted the form is read-only; if something was wrong, message the supplier. Forms cannot be answered after a decision is recorded.