Attachments

A bank statement tells you a payment happened. It does not tell you why. Attachments close that gap: upload the invoice, loan agreement, or management services agreement that justifies a payment, and it stays on the transaction for anyone who can see it. This matters most when the two sides of a payment are related entities. An intercompany transfer with a service agreement attached to it is a documented, arm’s-length record. The same transfer with nothing attached is a number an auditor has to ask about.

​

Where you can attach a file

Attachments are optional everywhere. Accepted files are PDF, PNG, and JPEG, up to 10 MB each — a photographed or scanned agreement works as well as a PDF.

​

Who can see an attachment

This is the part worth reading carefully, because it differs by the kind of payment. An attachment on an external transfer is never sent to the recipient. It is bookkeeping evidence for your own records. If you need to send a document to someone you are paying, mail it with a check instead — see Move money.

• Transfer within Lemma, between two entities. The receiving entity sees the attachment on its side of the transaction. The upload step names the entity that will receive it, so you know before you send.
• Transfer within Lemma, between your own accounts. There is no counterparty, so the attachment is only for your records.
• Invoice. The entity you bill sees the attachment, and can read it before deciding whether to pay. That is the point: an invoice for a management fee is easier to approve when the agreement setting that fee is attached to it.
• Send externally. Only your team. See the warning above.

Every screen that shows an attachment repeats which of these applies, so you never have to remember.

​

Finding attachments later

Open any transaction from Transactions and its documents appear in the drawer. Where a transaction has more than one, numbered buttons switch between them. A paid invoice is the common case for several: the receipt is the first document, and anything the sender attached follows it. You can read every one of them from either side of the payment, and download each individually.

​

Attachments and approvals

If a transfer needs an owner’s sign-off under your approval rules, the attachment travels with the request, and the reviewer can open it while they decide. An agreement is only useful to an approver who can read it before approving. Once the transfer sends, the attachment follows the money rather than the request: anyone on your team who can see the transaction can open it. If a payment is later returned or reversed, the attachment appears on that transaction too. You do not need to attach anything again. The justification stays with the money for the life of the payment, including the parts you did not plan for.

​

MSO-PC structures

For groups running a management services organization alongside a physician-owned practice, attachments are where the paper trail lives. Attach the management services agreement to the fee transfer, or the loan agreement to a capital contribution, and the justification sits on the transaction instead of in someone’s inbox. Because a cross-entity attachment is visible to both entities, the practice and the MSO are looking at the same document — neither side has a private version of the record. See MSO-PC compliance for the other controls we configure around this structure.

​

Next steps