LOS integration scope
Snapdocs supports more workflows than any first release should carry. Scope the integration around the workflows customers request most, and release in phases as each milestone lands.
| Workflow | Summary | Priority |
|---|---|---|
| Closings Create | Create a closing from a clear-to-close event in the LOS and attach the unsigned closing document package. | MVP |
| Redraw (full/partial) | Send an updated package, with or without field updates. Leverages 95% of Closings Create code — see the redraw guide. | MVP |
| Signed document retrieval | Download the completed package(s) when signing events finish — see the scanbacks guide. | MVP |
| Compliance downloads | At post-closing, download the audit trail and tamper-sealed originals, then auto-close the closing — see compliance downloads. | Phase 2 |
| Status updates | Receive events tracking the closing's progress — see the status guide. | Phase 2 |
| Accelerated eNote | Create eNotes from LOS data instead of having Snapdocs parse the PDF note, by sending the eNote object within Create a New Closing — see eNote MISMO mapping. | Phase 3 |
| Post Close QC | Snapdocs reviews the closing, credit, and origination packages against the lender's QC checklist — the Post Close QC API. | Phase 3 |
| CD Balancing | Compare CDs to highlight fee changes and push results back to the LOS — the CD Balancing API, in active development. | Phase 3 |
For the Phase 3 products, plan the data path now even if you build later: QC and CD Balancing both need the LOS to send loan data points and documents beyond the closing package, so an integration that can already ship arbitrary loan fields to Snapdocs layers them in easily.
Data mapping comes first
The largest body of work in Closings Create is mapping loan fields from the LOS into the closing objects for the initial POST. The required fields per closing type are listed on Create a New Closing.
Two kinds of gaps surface during mapping, and both are cheaper to find early:
- Field identification. Snapdocs has a field per borrower called Borrower Name Suffix; an LOS may call it Borrower Generation (Jr, Sr). Every field needs this reconciliation.
- Field customization. Lenders map the same target field differently. Lender A maps borrower email from the primary email of the first borrower; Lender B maps the same field only when an eConsent flag is true. Snapdocs has historically handled this with per-lender field-mapping overrides on a single codebase; if your platform lacks field-level override flexibility, plan an alternative.
Do this discovery at the start of the integration. Fields that don't exist in the LOS, fields with unexpected names, and fields populated later than the integration reads them have all delayed launches.
Drawn documents are a prerequisite
Closings Create assumes the lender has access to the drawn closing package returned from their doc prep provider, with all ancillary signable documents identified. Snapdocs expects to receive every document meant to be signed as attachments on the closing.
For the return direction, decide with each lender how signed documents come back: as they become available or as one final combined package (timing), as a fully executed package versus separate eSign and wet-sign sets (size), and to what location, named and organized how (location). The platform's Doc Pushback setting per lender produces an event matching the document shape the lender wants; the scanbacks guide covers the options.
Other supported workflows
A few functions exist in the API but have historically stayed out of integrations — lightly used, or early access. Worth joint exploration for a later release:
- Comments — read closing comments in the LOS and respond via the integration.
- Close closings — Snapdocs prefers signed-and-returned closings to be completed, so successful signings are tracked.
- Cancel closings — let the LOS cancel when a loan is no longer going to close.