How to Export Applications in SecureWebX

Every lender and every DMS wants the same application in a different shape. SecureWebX exports it in the layout the receiving side asks for, over the transport it asks for, without anyone at the store retyping a customer.

1. Find the application

   Open Applications from the console. Type a last name, a phone number or the Application ID into Search applications, or narrow the list from Applications by status on the dashboard when you are working a whole stage at once, like everything approved and waiting to be funded.

2. Open the record and check it is complete

   Click Open application. Read the review section the way the lender will: applicant, co applicant, residence, employment, income, down payment and trade. An export sends what is on the record, so a blank employer field is a blank employer field on the other end and a call back to your store.

3. Pick the format the other side asked for

   Choose the layout the receiving system expects. SecureWebX writes the standard STAR XML layout that DMS platforms read, fixed width for the older systems that still want it, and CSV or JSON for anything modern. If you do not know which one, the lender's implementation contact does, and it is a one line answer.

4. Pick how it travels

   Then choose the transport: a secure file transfer drop, a REST or SOAP call into their system, encrypted email, a structured email their intake reads, or a secure portal the receiving side signs into. Each destination keeps its own pairing, so the store sets up a lender once.

5. Send it and confirm the handoff

   Send the export and check the record. The application shows the export on its history with the time and the destination, and the audit log carries the user who sent it. If the far end needs a human to look at one deal instead of consuming a file, use Open the credit application to read it yourself and send a secure share instead.

6. Set the store default so it happens the same way every time

   In the apply link settings, How do you want to receive applications? decides what the store gets the moment a customer submits, and the Receiving applications panel shows the destination in force. Set it once and every new application follows the same path without anyone remembering to push it.

You need a SecureWebX login that can open applications, the submitted application itself, and one piece of information from the receiving side: which format and which transport they want. A lender's implementation sheet names both in a sentence. If your store is exporting into its own DMS, the DMS support desk has the same answer.

It also pays to know what an export is for. It is the fastest way to hand a complete application to a system that consumes files. When a person on the other end just wants to read one deal, Send to Lender is better: a code gated, expiring, watermarked share with a response page they can answer from. Most stores use both, for different lenders, on the same day.

Four answers cover almost everyone. STAR XML is the layout most DMS platforms and a lot of lender intakes were built around, so it is the first thing to ask about. Fixed width shows up wherever an older mainframe is still doing the work, and it is exact about column positions, which is why the mapping template matters. CSV goes anywhere a spreadsheet or an import tool is the destination. JSON is what a modern API wants.

The transport is a separate question from the format, and the pair is what you set up: a fixed width file over a secure file transfer drop, or JSON over a REST call, or a CSV inside an encrypted email. Lender and DMS export formats lists every combination the console supports. A format or a transport your lender uses that you do not see on the list is available on request, and our team puts it in production for your dealership.

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.

The application record showing the export on its history, with the destination, the format and the time, plus the user who sent it in the audit log. On the receiving side, the deal appears in their intake within their normal window, carrying the same fields your customer typed: identification, residence, employment, income, down payment and trade, with the co applicant attached when there is one.

Back in the console, the application inbox keeps its status, assignee, amount and notes, so the export does not move the deal out of your pipeline. Reports carry the same records into a PDF when a manager or an auditor wants the month on paper.

The search finds nothing. The list reads No applications found when the filter is tighter than you think, usually a status filter left on from earlier. Clear it and search by last name or by the application number from the customer's confirmation.

The far end rejected the file. Nine times out of ten it is the format, not the data: they read fixed width and you sent CSV, or their mapping expects a field your store leaves blank. Ask them which record failed, then match the mapping template to their sheet and send it again.

The application is missing pages the lender wants. Supporting documents and stipulation uploads live with the application; make sure the customer or the salesperson attached them before the deal goes out, so the funding package is complete on the first pass.

Nothing is arriving automatically from new submissions. Open the apply link settings and read Receiving applications. The destination you expect is either not chosen there or points at an old address from a previous provider.

If the goal is a lender decision rather than a file transfer, read the secure share guide instead: the lender opens a watermarked copy, answers on their own page, and the decision comes back onto the deal. If the goal is a clean application in the first place, the apply link customization decides which sections and fields a customer fills in before any of this starts.

The LeadLocate Help Center has the rest of the SecureWebX guides, including sending a fax and managing who can open applications. Every export is written to the audit log, so a store that gets asked where an application went can answer with a record instead of a memory.

What formats can an application be exported in?

Standard STAR XML for DMS platforms, fixed width for older systems, CSV for spreadsheets and import tools, and JSON for modern APIs, each with its own mapping template.

How does the file get to the lender?

Pick the transport the receiving side uses: a secure file transfer drop, a REST or SOAP call, encrypted email, a structured email their intake reads, or a secure portal.

Can I export more than one application at a time?

Yes. Filter the list by status or date range first, then export the set. Reports cover the same ground when a manager wants the month in a PDF rather than a data file.

Is exporting the same as submitting to a lender?

No. An export hands a file to a system that consumes files. Send to Lender is the other route: a secure, expiring link with a response page the lender answers on.

Four formats, six transports and a saved mapping per destination come with SecureWebX. See the console end to end in the pre-recorded demo, or ask us about the lender your store works most.

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