Stipulations Workflow With Upload to Fulfill

Every stip a lender asks for, listed on the application, fulfilled by upload, shared with the lender that asked. No sticky notes, no photos in a text thread.

A stipulation is the condition a lender attaches to an approval: proof of income, proof of residence, a copy of the license, a phone bill, a reference. The deal funds when the stips are in, and it stalls while they are out. The stipulations workflow in SecureWebX puts every one of those conditions on the credit application record, tracks whether it is outstanding or on file, and lets the store fulfill it by uploading the document directly against the request that asked for it.

That last part is what separates a workflow from a checklist. In most stores the stip list lives in the finance manager's head, on a sticky note on the deal jacket, or in a text thread where the customer sent a photo of a pay stub three days ago. When the lender asks whether the proof of income came in, the answer involves scrolling. In SecureWebX the answer is on the application: the stip, the upload against it, when it arrived and who uploaded it.

This page is the product side of the feature. For the category view of how a dealership's application and document handling should work end to end, the online credit application software page is the place to start.

A lender approves a sedan deal on Monday afternoon through the lender response portal and lists what they still need: two recent pay stubs and a current utility bill. Those items land on the application as stipulations. The finance manager opens the file, sees both marked required, and emails the customer from the application's own thread with a plain request. Tuesday morning the customer replies to that email with photos of the stubs. The finance manager uploads them against the pay stub stip with Upload for this lender, which shares them straight into the lender's existing secure view of the application. One stip down, one to go.

The utility bill takes longer, as utility bills do. Wednesday the salesperson asks whether the deal is funding. The finance manager does not have to check a notebook; the application shows one stip outstanding and which one. The salesperson texts the customer from the CRM, the bill comes in that evening, the finance manager uploads it, and the lender sees the complete set on Thursday morning. The deal funds with a record of exactly what was asked for, what was provided and when.

Multiply that by a dozen open deals and a stack of lenders with different habits, and the value is clear: nothing is remembered, everything is recorded.

Leave your number and a lead specialist calls you back to answer your questions about pricing, coverage, and setup. Mon - Sat, 9:00 AM - 6:00 PM Pacific.

Prefer to talk right now? Call or text 844-376-2274.

Stips are added from the Stipulations section of an open application. The console keeps a list of common stipulations, the items lenders ask for on nearly every deal, so adding proof of income is one pick rather than one typed line. Anything unusual is typed as a custom item. Each stip can be marked required, so the application shows plainly which items block funding and which are nice to have.

Stips also arrive without anyone at the store adding them. When a lender reviewing a Send to Lender share uses Request more information and lists the items they still need, those items land on the application as stipulations tied to that lender. The finance office sees what the lender wants without a phone call, and the lender sees the documents as they are uploaded.

A store that knows what its lenders always ask for can collect much of it before the application arrives. Each apply link can carry document upload fields, so the special finance link can request a pay stub and a proof of residence during the application itself. Those documents attach to the submission as supporting documents, and the stip is fulfilled before it is ever opened. The apply links page covers customizing a link that way.

Fulfilling a stip means uploading the document against it. The upload accepts a file up to 20 MB, which covers a scanned bill, a phone photo of a pay stub or a PDF from an employer. Every upload is virus scanned before it is stored, and it is encrypted at rest with the rest of the application. Once uploaded, the stip shows as on file, with the document attached, and the application's audit log records who uploaded it and when.

Where the document comes from is up to the store. The customer may have attached it during the application through a document upload field on the apply link. They may have replied to an email sent from the application's thread, which the console's Mailbox handles inbound. They may have handed a paper copy to the salesperson, who scans it at the desk. In every case the finance office uploads it against the stip that asked for it, and it lives there.

When the stip belongs to a lender, Upload for this lender uploads the requested document and shares it with that lender in the same secure, watermarked view they already have. The lender never receives an email attachment; they see the document inside the share, with the same code gate, expiry and revoke the store set on the application.

It lives on the application, in the SecureWebX console, which opens from the SecureWebX button in the LeadLocate CRM dock with one login. Open any application from the credit application inbox and the Stipulations section is on the record alongside supporting documents, the lender shares, the worksheets and the audit log. There is no separate stip screen to keep in sync with the deal, because the stips are part of the deal.

From the CRM side, the salesperson sees the application's status and opens it in SecureWebX when they need the detail, so the question of what is holding up funding has an answer the rep can find alone. Users are invited into the console with roles, so a store decides who can add and fulfill stips and who can only see them.

It replaces the sticky note on the deal jacket, the highlighted line on the lender's call sheet, the personal text thread that holds a customer's pay stub, and the question, asked in every finance office every week, of whether we ever got that utility bill. It replaces the email to the lender with three attachments and a subject line of the customer's last name, and the reply asking for the one you forgot.

It also replaces the exposure. Documents proving a customer's income and address are among the most sensitive things a store handles, and a workflow that keeps them in a text thread or an email attachment leaves them somewhere the store no longer controls. Uploading against the stip keeps them inside the application, encrypted, scanned, watermarked when viewed and logged when touched. The dealership CRM with credit application page covers the wider argument for keeping deal documents under one system rather than scattered across personal devices.

A store that handles stips through personal phones and email has no reliable record of what it collected, from whom, or where the copies went. The stipulations workflow gives the store that record by default. Every stip shows when it was added and by whom, whether it was required, when it was fulfilled and by whom, and which lender it was shared with. Documents open in a watermarked viewer with print and download gated. Uploads are virus scanned and encrypted at rest. The audit log on the application ties it together, and records are archived, never deleted, so the file answers questions years later.

None of this makes a store compliant on its own; a compliance program is the store's, and its counsel decides what it requires. What the workflow provides is evidence that the program was followed on every deal, without asking the finance office to keep a second set of notes.

There is nothing to turn on. Stipulations are part of every application in the SecureWebX console, which is created with your LeadLocate account and is part of every plan, month to month, on the pricing page. Because SecureWebX runs as its own system, stips can be added and fulfilled even when the CRM is unavailable, and anything uploaded is retained.

Pair the workflow with Send to Lender, since a lender's request for more information becomes a stip and the upload for that lender lands in the lender's share. Pair it with document upload fields on your apply links so the most common stips arrive with the application. Pair it with the adverse action notice when a deal cannot be made, so the file that was declined carries the record of what was asked for and what was received. The rest of the platform is on the all features page, and the pre-recorded live demo shows a stip added, fulfilled and shared with a lender on one application.

What is a stipulation on a car deal?

A condition a lender attaches to an approval before funding, such as proof of income, proof of residence or a copy of the license. SecureWebX tracks each one on the credit application and fulfills it by uploading the document against it.

How do I add a stip to an application?

Open the application in the SecureWebX console, go to Stipulations, and pick from the common stipulations list or type a custom item. Mark it required if it blocks funding. A lender's request for more information through a share also lands as a stip.

How is a stip fulfilled?

By uploading the document against it, up to 20 MB per file. The upload is virus scanned, encrypted at rest and logged. Upload for this lender shares the document into that lender's existing secure view of the application.

Can the customer provide stips during the application?

Yes. Each apply link can carry document upload fields, so a store can request a pay stub or a proof of residence inside the application itself. Those documents attach to the submission as supporting documents.

Does the lender get the documents as email attachments?

No. An upload for a lender appears inside the lender's watermarked, code gated share of the application, with the same expiry and revoke the store set. The lender never receives a loose attachment.

Is the stipulations workflow included with LeadLocate?

Yes. It is part of SecureWebX, which is part of every LeadLocate plan, month to month. Plans are listed on the pricing page.

The stipulations workflow is part of SecureWebX and every LeadLocate plan, month to month. See a lender's request become a stip, get fulfilled by upload and land in the lender's share.

Prefer to talk right now? Call or text 844-376-2274.