Commercial and SME lending built so your paper stands up to the people funding it.

Bank statements, a void cheque from the operating account, articles of incorporation, sometimes a lease: a commercial file arrives as a stack, not a form. Camera capture and the visual progress tracker are how a principal or a broker gets those in without a courier, and a saved file is resumed later while the applicant chases a missing statement. Two-step pre-qualification screens for time in business, revenue and product before anyone completes a full application, and the embeddable form with domain whitelisting is what a broker puts on their own site. The form designer gives each product its own fields: an advance asks for card volume, a term loan asks for a use of funds. Your staff open and amend files on the applicant’s behalf throughout, and the pipeline view keeps every live deal in one queue, which is how a brokered deal moves.

• Multi-step online application, mobile-friendly
• Save and resume: borrowers return later through a signed email link
• Two-step pre-qualification before a full application, with criteria set per product
• Embeddable pre-qualification form for your own website, with domain whitelisting
• Application form designer: fields, sections and validation per product
• Camera capture for document upload on mobile, with a visual progress tracker
• Staff can create applications on a borrower’s behalf
• Application pipeline and queue management
• Customer records with import and export

The same bank connection, read in commercial terms: business revenue instead of personal income, the operating entity instead of the applicant, revenue frequency instead of a pay cycle. The affordability ratios are built on that: revenue-to-loan, annualised operating income, expense breakdown by category, and for an advance, remittance as a percentage of business revenue. NSF pattern analysis matters more here than a single count, because a merchant with seasonal swings and a merchant in trouble look alike in one month and not across a season. The affordability metrics and the KYB data stay on the staff side of the file and are never shown to the borrower, which is what lets an underwriter record a concern without it reaching the principal. Scheduled refresh keeps a funded advance’s remittance ratio current while it is still being repaid.

• Six bank-verification providers supported, including Flinks, Inverite and ZumRails
• One normalised insights view whatever the provider: income, expenses, balance, NSF count, account age, days negative
• Risk-level badges, income and balance trends, expense breakdown, full accounts and transactions
• Underwriting scorecard derived from verified bank data
• Scheduled refresh by product, with risk-tiered intervals and a monthly budget cap with alerts
• Financial-distress monitoring on refreshed data, with staff alerts
• Borrowers can start or re-trigger verification from their own dashboard
• Duplicate-send protection with separate cooldowns for personal and business requests

You are lending to the entity, not to the person who signs for it, and the lifecycle shows it: Draft, Under Review, Conditionally Approved, Approved, Awaiting Signature, Signed, Funded, with Conditionally Approved doing most of the work while a guarantor is added or a KYB check clears. Eligibility and stipulations are configured one product and one jurisdiction at a time, which is how a lender writing in both Canada and the US keeps a product for each. Stipulation checklists hold funding until the required documents are in. The re-review path sends a Signed file back to Under Review with the signed contract voided, the audit trail kept and a re-review counter on the file, the situation that arises when a funder asks a question late. Loan notes keep the underwriter’s reasoning where the file is, not in an inbox.

• Clear lifecycle: Draft, Under Review, Conditionally Approved, Approved, Awaiting Signature, Signed, Funded
• Conditional approval with outstanding conditions
• Rules engine for eligibility, rate caps and stipulations per product and jurisdiction
• Stipulation tracking with required-document checklists before funding
• Status history recording every transition, who made it and when
• Loan notes and internal staff communication on every file
• Decision reasons feed directly into the adverse-action notice

Count the signatures on a commercial deal: a co-borrower, a personal guarantor, sometimes a corporate guarantor. The recipient picker makes that routine, each one its own recipient, validated as you add them. Send for Review is the path consumer lending has no use for: it puts the unsigned contract in front of the borrower’s counsel, or answers a US state commercial-disclosure regime, before anyone is asked to sign. Sign as Admin covers the deal closed in a room. A merchant cash advance generates from its own Purchase and Sale Agreement template rather than a loan agreement, and two-document signing with funding confirmation is the ordinary shape of an advance. Document OCR lifts the figures off a scanned statement so nobody retypes them. Frozen acceptance timestamps embedded in the signed PDF are what a funder’s diligence reads to establish when the deal was struck.

• Built-in e-signature, plus DocuSign, SignNow, GoDocs and a local signing path
• Document generation from contract templates, and document OCR
• Three send paths: Send for Signature, Send for Review, Sign as Admin
• Recipient picker for every co-borrower and guarantor, with inline validation
• Acceptance timestamps frozen at the original acceptance and embedded in the signed PDF
• Protection against duplicate agreements and duplicate notifications

Daily or weekly, computed from the purchased amount and held against the factor rate: an advance carries a remittance where a term loan carries a schedule. The calculators cover both, alongside interest-only draws and odd-days interest where funding and the first period do not line up. EFT, ACH, Interac and card rails are all here because a lender writing in Canada and the US runs two at once. A funding desk reaches for mass payment entry, reschedule, hold and restructure when a merchant’s week goes wrong. Amend an advance amount and the factor rate holds. The purchased amount and the remittance are recomputed, and the borrower re-signs. Processing runs through ZumRails, with additional processors available on request. Payoff quotes and letters cover the merchant clearing an advance early to take another, the ordinary renewal path on an advance.

• EFT, ACH, Interac and card rails
• Payment processing through ZumRails, with additional processors available on request
• Seven payment-schedule calculators and configurable frequencies
• Pre-authorised debits, with payment-method detection and an advisory when a schedule changes
• Automated collection runs, retries and failure handling
• Reschedule, hold, restructure and mass payment entry
• Payoff quotes and payoff letters
• Grace periods, late fees and disclosure
• Nominal-to-effective interest conversion and APR calculation

When a commercial file goes past due, someone phones the principal. The collections workspace and delinquency tracking are the same tools used on far fewer files, with more riding on each: a stalled advance is usually a merchant whose revenue dropped, and the restructuring tools exist so a remittance can be reset against what the business is now taking in. Reschedule and hold, repeated reschedules included, cover a seasonal business directly: a retailer whose January does not look like its December. Write-off and account-status reporting are what a funder or a syndication partner reads on paper it holds a share of. Communication status tracking keeps the record of who was contacted and when. A demand on a guarantor later has to rest on that record, which is why every step of it stays on the audit trail.

• Delinquency tracking and a collections workspace
• Payment restructuring tools
• Reschedule and hold, including repeated reschedules for seasonal hardship
• Write-off and account-status reporting
• Communication status tracking on collections activity

Two people sign in to a commercial file: the principal, and whoever keeps the books. The dashboard’s balance and schedule, and payment history exported to PDF, are what a bookkeeper reconciles against; annual and monthly statements are what an accountant asks for at year end. Payoff letters on demand carry more weight here than on a consumer file, because a merchant refinancing an advance needs a current figure before a new deal can be written. Bank account management and self-service verification let a business change its operating account without calling your staff, which a business does more often than a consumer does. A principal and a bookkeeper each hold their own sign-in, under the role each is given. Reschedule, payoff and restructure requests come in from the borrower side, and there is a native mobile app for the principal who is not at a desk.

• Dashboard with current balance and schedule
• Payment history with PDF export
• On-demand payoff letters, annual tax statements and monthly statements
• Bank account management: add, view, remove
• Self-service bank verification when required
• Reschedule, payoff and restructure requests
• Native mobile app companion

Fewer messages, more recipients. The parties on a file are a principal, a guarantor, sometimes a broker, and the lifecycle emails address those parties instead of a single borrower. What carries a commercial deal is the state notice: a hold on funding with its retry date, a verification still outstanding, a document amended after signature, a file sent back for re-review. Those are the states a deal stalls in, and they are what a broker chases. SMS both ways over Twilio reaches a merchant who does not read email during a working day, and in-app chat keeps the thread on the file rather than in someone’s inbox. Reminder sequences run against a daily or weekly remittance the same way they run against a monthly instalment, and the recipient set on the file decides who receives each one.

• Email templates for every lifecycle event
• Two-way SMS through Twilio
• In-app chat and notifications
• Payment-due and past-due reminder sequences
• Notifications for funding holds, verification requests, amended documents and re-review

Rate caps matter less here, and disclosure and record-keeping matter more, though the rules engine still holds a cap wherever a jurisdiction and a product between them call for one. A declined business applicant gets the same adverse-action notice, with the same nineteen reason codes behind it. What a funder’s or an auditor’s diligence reads is the change record: who moved the file, into which state, when, and on what reasoning, kept for the whole lifecycle. Seven roles decide who sees the affordability ratios and the KYB data, and neither ever reaches the borrower’s side of the file. Query-level brand separation matters to a lender originating under one name and servicing under another, or holding syndicated paper beside its own, and the guarantor identifiers such a file carries are encrypted, with a signature verified on every payment webhook.

• Adverse-action notices with 19 structured decline reason codes, generated as PDF, emailed, re-sendable
• Provincial rate-cap enforcement
• Cost-of-borrowing disclosure
• Cooling-off period tracking
• French-first support for Quebec: French interface and contract documents
• Audit logs, status history and change tracking across the loan lifecycle
• Role-based permissions across seven roles
• Brand-scoped data separation enforced at query level
• Encrypted personal data, and webhook signature verification on payment providers

Entities and funding sources, not brands: that is the administration problem on a commercial book, and one instance answers both. It can hold a broker-facing originating name beside the name the servicing is booked under, separated at query level so the two sets of files never meet. A term loan, an interest-only draw and a merchant cash advance are each defined on their own (day-count convention, factor rate or interest, remittance frequency, brokerage fee layers), and that is where external funding with deferred servicing is switched on for paper funded off the balance sheet. A public API opens the book to a funder-facing reporting stack or a broker portal. Running on a dedicated instance puts the environment, the data and the branding under your own name while we host and maintain it, with a sandbox per client on AWS.

• Company settings, product configuration, user and role management
• White-label branding, with multiple brands in one instance
• Analytics and reporting
• Public API
• Dedicated instance option: your environment, your data, your branding, hosted and maintained by us
• Hosted on AWS with continuous deployment, and a sandbox environment for every client