Finaxis White-Label Borrower Portal Configuration (Onboarding)

Finaxis White-Label Borrower Portal Configuration (Onboarding)

1. 01

   Map the client's loan products in the Finaxis product configuration screen before touching branding

   Define principal ranges, term lengths, interest accrual method, and fee schedules per product. Finaxis runs interest accrual and payment scheduling off these parameters, so a wrong term length propagates into every downstream servicing record.

2. 02

   Attach the client's domain, logo, and email sender to the white-labeled borrower portal

   Borrowers must never see the Finaxis brand. Verify the sender domain resolves before the first application is submitted, because a mismatched sender breaks the client's own deliverability reputation.

3. 03

   Build underwriting logic in the visual drag-and-drop decision engine

   No code required. Layer rules in this order: credit bureau pull thresholds first, then ecommerce data signals, then manual review fallbacks. Rules that reference ecommerce data will fail silently if the OAuth connection is not live.

4. 04

   Connect ecommerce OAuth for Amazon, Shopify, Google Ads, and Meta where the client's borrowers sell

   Skip any connector the client's borrower base does not use. Each live connector adds a data source to the decision engine, and unused connectors create noise in underwriting review queues.

5. 05

   Load compliance rule sets for TILA and ECOA inside the platform

   These are configuration items, not defaults. Confirm the client's legal reviewer signs off on the rule set before origination goes live, since the platform enforces what you configure and nothing more.

6. 06

   Import existing loan management system data using the vendor's data migration support

   Plan for high setup complexity here. Reconcile migrated balances against the client's prior system before switching origination on, or servicing records will carry forward the discrepancy.

7. 07

   Verify GAAP-compliant double-entry accounting posts correctly per tenant

   Run one test loan through full origination, servicing, and a payment, then check that the accounting entries land in the client's tenant ledger and not a shared one.

8. 08

   Hand the configured portal to the client's operations lead with a written runbook

   Cover collections workflow triggers, payment scheduling overrides, and who to contact at your agency when a borrower dispute escalates. Retainer scope should name the monthly health check explicitly.