Financial Carry Memo
What a Financial Carry Memo Is and When It’s Used
Why a Clear Carry Memo Matters for Compliance and Accounting
A precise Financial Carry Memo reduces disputes, supports accurate accounting, and documents governance decisions. Legally, electronic execution and record retention must satisfy federal rules such as the ESIGN Act (15 U.S.C. ch. 96) and applicable state UETA provisions to ensure enforceability and admissibility.
Who Typically Prepares and Reviews a Carry Memo
Internal finance, fund administration, and legal teams commonly prepare the memo; investors and auditors use it to verify distributions.
- Fund managers and CFOs preparing allocation calculations for partners and tax reporting
- Fund administrators and accountants verifying waterfall mechanics and journal entries
- In-house counsel and external counsel reviewing legal language and governance implications
Step-by-Step: Preparing and Signing a Financial Carry Memo
-
01Draft and attach model: Create memo and attach modeled calculations and exhibits.
-
02Internal review: Finance and legal review assumptions and waterfall language.
-
03Approval routing: Route to authorized signatories in the prescribed order.
-
04Execute and retain: Capture signatures, save signed record, and log version history.
How to Configure an Online Carry Memo Workflow
| Field | Configuration |
|---|---|
| Upload Document | PDF or DOCX; attach supporting schedules as separate files. |
| Signature Fields | Place signature, date, and initials; require all signers to complete. |
| Authentication | Use email plus SMS or KBA for higher assurance where needed. |
| Notifications | Enable auto-reminders and completion receipts. |
Typical eSigning Flow for a Carry Memo
-
Sender prepares: Upload memo, add fields, set signer order.
-
Signers notified: Email or secure link delivered to each signer.
-
Signer authenticates: Signers confirm identity via email, SMS, or stronger methods.
-
Record stored: Signed PDF and audit trail saved to repository.
Technical Considerations for eSubmission and Storage
Choose a platform that supports required authentication, audit trails, and the file types you use.
- Integrations: Salesforce, NetSuite, Microsoft 365, Google Workspace supported for routing and storage
- File formats: PDF, DOCX, and Excel are supported for attachments and signed output
- Security: TLS in transit and AES-256 at rest required
Primary Risks When the Carry Memo Is Incorrect
Common Preparation Mistakes to Avoid
- Using inconsistent versions of the financial model across drafts causes reconciliation failures and incorrect carry calculations.
- Leaving ambiguous waterfall language (undefined hurdles or catch-up terms) leads to differing interpretations among partners and increases dispute risk.
- Failing to document signer authority and corporate capacity can render signatures unenforceable in investor challenges or court review.
- Neglecting to archive the audit trail and supporting exhibits prevents reliable reconstruction of the distribution process during audits.
Real-World Examples of Carry Memos in Practice
Optica Ventures
Brian Fitzgibbons led internal rollouts of a standardized memo format to align accounting and legal teams.
- The memo tied distributions to a single model version.
- This reduced reconciliation time and improved clarity for LP statements while preserving an audit trail for compliance reviews.
Martin Properties
Tim Martin used an online signing workflow to execute carry memos across remote offices.
- Signers completed authentication via mobile devices.
- The approach enabled timely distributions, consistent version control, and secure storage accessible to auditors and stakeholders.
Practical Tips for Accurate, Efficient Carry Memos
Timing Considerations and Typical Deadlines
Board approval deadline:
Set a cutoff at least 10 business days before distribution dates for review and adjustments
Distribution date:
Align memo effective date with scheduled payout and confirm ledger entries beforehand
Tax reporting window:
Ensure carry allocations are finalized in time for relevant informational returns and partner schedules
Document retention check:
Verify signed memo archived before fiscal close for audit readiness
Revision cutoff:
Freeze memo edits 48 hours prior to execution to prevent version confusion
eSignature Pricing and Feature Snapshot for Carry Memo Workflows
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes (premium tier) | Yes | Yes | Yes | Yes |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Frequently Asked Questions and Troubleshooting
-
Can a carry memo be signed electronically?
Yes. Under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, electronic signatures are generally valid if the record meets intent, consent, attribution, and retention criteria.
-
What authentication is sufficient for signers?
Email plus access code is common. For higher assurance, use multi-factor authentication or KBA depending on investor sensitivity and internal policies.
-
Do I need a notary or witnesses?
Most internal carry memos do not require notarization. If a jurisdiction or counterparty requires notarization or witnesses, follow local rules and document the requirement in the memo.
-
How should version control be handled?
Keep a single source model, increment version numbers, and attach the model reference in the memo. Archive previous signed versions with explanatory notes.
-
What records should be retained for audits?
Retain the signed memo, supporting schedules, audit trail, and signatory authority documents. Follow IRS retention guidance (IRC §6501(a)) and industry-specific rules.
-
How do I correct a signed memo?
Issue an amendment or restatement and have authorized signatories execute the new document. Maintain both the original and revised records for audit transparency.