Party Identification
Legal entity name, DBA if any, and taxpayer identification where required to enable payment or tax reporting.
A well-prepared Business Match Document reduces ambiguity about roles, timing, and compensation, supports audits, and creates a record that can be enforced if disputes arise. For interstate transactions, electronic signatures executed under the ESIGN Act (15 U.S.C. ch. 96) and state UETA frameworks generally make electronically signed matches legally enforceable.
The Business Match Document is used by business development, procurement, legal, finance, and third‑party referral partners to document an introduced relationship and any associated terms.
In small organizations these roles may overlap; larger enterprises usually assign ownership to a single team to maintain version control and approvals.
Signs to confirm the introduction, provide contact verification, and accept any referral terms. They must ensure the counterpart information matches CRM records and that commission terms are recorded accurately for finance.
Approves supplier details, confirms documentation completeness, and signs to trigger the onboarding workflow. Their signature usually authorizes setup in procurement and initiates any required vetting checks.
Legal entity name, DBA if any, and taxpayer identification where required to enable payment or tax reporting.
Full name, role, email, phone, and physical address for both parties to support notices and onboarding.
Clear description of the introduction, services or goods anticipated, geographic limits, and exclusions where applicable.
Referral or commission rate, payment triggers, invoicing instructions, and any holdbacks or clawback provisions.
The effective date and any expiration or review triggers that define the period the match covers.
Signature blocks, signer role declarations, and a statement that electronic signatures are acceptable under ESIGN/UETA.
| Field | Configuration |
|---|---|
| Signer Order | Sequential or parallel routing |
| Authentication | Email, SMS code, or KBA as required |
| Audit Trail | Timestamp, IP, and action log |
| Storage | Retention location and format |
Choose a platform that supports the file formats, integrations, and compliance controls your organization needs.
Verify platform security (TLS/AES), audit trails, and any required BAAs for protected data before sending the document for signature.
Use MM/DD/YYYY to determine when obligations begin.
Record NET terms (e.g., NET 30) tied to invoicing events.
Specify the period during which the referral fee can be claimed.
Set a notice period for automatic renewals or reviews.
Date that starts retention and audit timelines.
Document drafted and initial fields validated by owner.
Finance and legal approve compensation and terms.
All signers execute the document electronically.
Executed copy stored and stakeholders notified.
The interface is simple and easy-to-use for our team
I can process and execute all of these documents online with 100% compliance