The Pledged platform
One platform, from source data to credit decision.
Pledged is the infrastructure between a borrower’s operational data and a lender’s credit decisions. Connect brings the data in. The Ledger establishes what is claimed and what supports it. Monitor, Advance and Recovery answer the credit questions that follow, and the Workspace gives every participant their own view of the same record.
Pledged Connect · data connectivity
Connect your collateral data.
Where does each figure come from, and how fresh is it?
The horizontal layer that feeds the platform. Connect is designed to bring ERP and accounting, warehouse and 3PL, commerce, and lender and appraiser sources into one collateral workflow, starting with the exports a borrower already produces and moving to scheduled files and authorized, read-only feeds.
Boundary. A connection is not verification. Connecting to an ERP does not prove that stock exists, who owns it, or what it is worth, and a source’s trust level never rises because of what its own file says.
- Borrower file ingestion, stored as receivedSHA-256, ingestion time and row-level lineage
- Field mapping with analyst approvalDeterministic proposals; credit-sensitive fields reviewed by a person
- CSV and XLSX exportsThe permanent fallback for any system
- Scheduled files, SFTP and an intake APICompleteness checks, idempotent re-delivery
- Read-only ERP, WMS/3PL and commerce connectorsBuilt for the stack of a committed facility
- Reusable, revocable authorizationsLeast-privilege scopes, consent per source
- Source health: coverage, freshness, exceptionsA result is never labelled current if a material input is stale
- Model-assisted mapping proposalsProposes and explains; never approves
- Lender loan-management system integration
Representative systems. Names are trademarks of their owners, shown to illustrate the systems Pledged Connect is designed for; they are not integrations or partnerships.
Pledged Ledger · collateral system of record
The record every decision rests on.
What collateral exists, and what supports it?
One canonical record of every position: SKU, lot, entity, warehouse and location, with ownership, possession and control kept as separate facts, each with the source that supports it. Originals stay immutable, and every figure keeps its lineage and its history.
Boundary. The ledger separates what a source declares, whether sources agree, and what has been independently corroborated. It does not certify physical existence, title or the legal priority of a security interest.
- Canonical inventory and receivables positionsMapped, deduplicated, with source lineage
- Ownership, possession and control as separate facts
- Evidence register: waivers, appraisals, documents by locationStatus as recorded; dates and coverage confirmed by your team
- Historical BBC reconstruction and certificate bridge
- Point-in-time replay of retroactive adjustments
- Point-in-time history for every sourceERP rows, receivables, shipments, transfers
- Source verification: ERP against custodian recordsConflicts and unsupported units reported apart
- Independently authenticated custodian provenance
- ERP · WMS · 3PL · GL reconciliation
Pledged Monitor · continuous collateral intelligence
From operational change to credit attention.
What changed, and what requires attention?
Monitor goes beyond alerts. It ties each operational change, such as aging stock, a lapsed waiver, a hold or a warehouse discrepancy, to its possible effect on availability, and routes it to the analyst with the evidence it would take to resolve it.
Boundary. Monitor prioritizes review; it does not detect fraud infallibly or promise lower losses. Every signal shows its source, its as-of date and its freshness.
- Period-over-period change in the collateral position
- Exceptions ranked by effect, with suggested next step and evidence required
- Scheduled monitoring between reporting dates
- Aging, slow-moving and obsolete inventory signals
- Warehouse discrepancies, movements and stock in transit
- SKU and category concentration
- Returns, holds, consignment and exceptions
- Source freshness, coverage and data quality
- Alerts and analyst workflow
- Portfolio-level monitoring and risk trends
Pledged Advance · credit availability
Your credit agreement, executed and explained.
How much credit can this collateral support?
Advance runs the lender’s approved policy on the ledger: eligibility and exclusions, advance-rate pools, lower of cost and NOLV, reserves and availability. It compares the borrower’s certificate with the reconstruction line by line, and runs scenarios on isolated copies so a policy question never touches the record.
Boundary. Policies are approved by the lender and NOLV comes from an appraiser the lender accepts. Pledged suggests; it does not make credit decisions or change reserves on its own.
- Eligibility and exclusions, each with its rule ID
- Facility-specific rules and advance-rate pools
- Lower of cost and NOLV caps
- Reserves, availability and headroom
- Borrower-declared vs reconstructed BBC, line by line
- Policy scenarios and what-if analysisRun on isolated copies; never an approved change
- Suggested reserve and eligibility actions for review
- Concentration rules
- Recurring, dynamic borrowing base
Pledged Recovery
Recovery intelligence, on the same record.
What could be recovered if conditions deteriorate?
Recovery extends the ledger toward the question every secured lender eventually asks. It is designed to combine appraisal inputs, inventory characteristics and history into a view organized for liquidation analysis, and to learn from how appraisals compare with what was recovered.
Boundary. Pledged does not replace the appraiser and does not offer an independent NOLV. Valuation stays with the professional your policy names.
- Appraisal NOLV as a governed, versioned input
- Appraisal integration and valuation history
- Recovery-oriented collateral segmentation
- Distressed-inventory characteristics and condition exposure
- Liquidation scenario support and recovery sensitivity
- Successive appraisals compared with outcomes
- Feedback from actual recoveries
Pledged Workspace
One platform, distinct workflows.
Who sees what, and who decides?
Lenders, borrowers and authorized reviewers each work in their own surface over the same record: not four applications, one platform. The decision history keeps what was known, which policy applied, what was recommended and what the lender decided.
Boundary. The lender keeps credit authority. Approvals happen under the lender’s controls, never automatically.
- Read-only lender view of a facility
- Decision history: inputs, policy version, replay dateEvery run reproducible from what was known
- Lender workspace: portfolio, facilities, alerts, reviews, approvals
- Borrower portal: authorize, upload or sync, resolve exceptions, submit schedules
- Decision log: what the lender decided and what followed
- External review: appraisers, field examiners, independent reviewers
Category
Collateral Decision Infrastructure.
The infrastructure between operational collateral data and credit decisions, starting with inventory credit. Which also makes clear what Pledged is not.
- an ERP
- a WMS
- a treasury system
- a borrowing-base calculator
- an analytics dashboard
- an appraiser
- a balance-sheet lender
- a generic AI platform