> For the complete documentation index, see [llms.txt](https://docs.eiva.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eiva.money/what-we-fund.md). # What we fund Short-dated trade receivables: invoices for work that's already been delivered, owed by the business that commissioned it. Today they come from the creative industries. Creative professionals and agencies submit them through Eiva's platform at eiva.co: producers, directors, musicians, models and creators, and the agencies that represent them. The payers are agencies, labels, brands, studios and production companies, from independent studios up to global corporations. In the ledger and the app they're shown by sector and type, never by name. ## What qualifies * Work completed and accepted before the invoice reaches us * Face value from \[minimum face value: Alpha] to \[maximum face value: Alpha] * Payment terms of 30 to 90 days * A payer that passes underwriting and is within its concentration limit, its cap as a share of the vault ## What doesn't * Work not yet delivered, milestones, retainers or deposits * Invoices already assigned or financed elsewhere * Payers outside our criteria, or over their limit in the vault * \[Other exclusions, such as sectors, jurisdictions or invoice types: Alpha] Eiva pays the creative up to \[advance rate, 90%: Alpha] of face value within \[time to pay, 72 hours: Alpha] of approval, for a fee agreed per invoice, \[6.7% of face value: Alpha] on average across the invoices funded so far. The rest, less the fee, goes to the creative when the payer settles. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.eiva.money/what-we-fund.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.