Credit decision

The decision is made on the application detail page (/applications/<id>) in the Decision panel, and stored by POST /v1/applications/:id/decision.

Who can decide#

• The caller needs the applications.decide permission. By role defaults that is ORG_ADMIN and CREDIT_MANAGER (and legacy ADMIN). SALES_MANAGER, ACCOUNT_ADMIN and VENDOR_USER see "Your role cannot record credit decisions". Per-user overrides can change this (see Team and permissions).
• The application must belong to the caller's organization. Platform staff operators can act across organizations.

Steps#

1. Open the application and read the Overview, Application, References, Messages and Activity tabs. The panel shows the requested limit and how many references responded.
2. Choose Review approval (shortcut A), Counter-offer or Decline (shortcut D).
3. Enter the approved limit (whole dollars, required for approve and counter-offer) and payment terms in days (30, 60 or 90, shown as Net 30, Net 60, Net 90 and prefilled from the organization's default, Net 30 if none; the panel also shows the terms the applicant asked for), an optional note up to 2000 characters, the signer's name and a drawn signature. For a decline, also tick at least one specific reason (checkboxes, up to four, for example "Slow or late payment history with other suppliers"). "Other" needs an explanation in the note. The reasons are stored with the signed decision and are sent to the applicant. Below the note, "What the applicant will read" previews the picked reasons, your note and the equal credit opportunity notice that the email carries, so you see the notice before you sign.
4. Confirm with Sign and approve, Sign and send counter-offer or Sign and send decline; the dialog says the applicant is emailed the decision. The decision, its audit event, the activity entry and the applicant's notification are written in one database transaction; the email is queued in the durable outbox and retried if the first attempt fails.

Outcomes#

Errors#

• 403: missing applications.decide or the application belongs to another organization.
• 400: invalid body (missing signature or name, limit missing for approve and counter-offer, a decline with no reason, or Other without a note).
• 404: unknown application. 409: the application already has a final decision, or it changed while you reviewed; refresh and decide again.
• 429: more than 30 decisions per minute per user.

Every decision is appended as signed evidence (name, signature image, IP, time) and can be listed with GET /v1/applications/:id/decisions. Decisions are never edited.

What the applicant receives when you decline#

The decline email states that credit cannot be extended, lists the reasons you picked and your note, names the supplier as the creditor, and carries the Equal Credit Opportunity Act statement with the Federal Trade Commission as the agency. For trade credit the law (12 CFR 1002.9(a)(3)(ii)) only requires the written reasons and that statement when the applicant asks in writing within 60 days, but they go out every time. The exact email is kept with the decision. Pick reasons about the applicant's credit file; never write or imply anything about race, color, religion, national origin, sex, marital status, age or public assistance. The legal background is in the developer document docs/audit/us-compliance.md.

Signing#

By signing you intend your typed name and drawn signature to act as your electronic signature (E-SIGN Act, 15 U.S.C. 7001).

For tests#

Test ids: decision-approve, decision-counter, decision-decline (and -sticky on the phone bar), in the dialog decision-limit, decision-terms, decline-reason (one decline-reason-<code> checkbox each), decline-note, ecoa-preview, decision-submit, decision-cancel.

Related#

• Credit applications list

Payment terms#

Payment terms are one fixed list in days: 30, 60 or 90 (shown as Net 30, Net 60, Net 90). The same list is used by the supplier default in Settings, the customer's "Preferred terms" question and the decision. Each is stored as a whole number of days on the application (requestedTermsDays, approvedTermsDays), on the signed decision record and on the organization (defaultTermsDays), so reports can compare them. A customer request outside the list (older forms offered Net 15) is stored as not specified. The product stops at the decision: it records the approved terms but does not issue invoices, due dates or reminders.