> For the complete documentation index, see [llms.txt](https://docs.ai.insly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ai.insly.com/nora/configuration-guide/insly-ledger-integration/exporting-to-ledger.md). # Exporting to Ledger It is a good idea to test many different submissions in demo → beta to encounter as many validation issues as possible. Formflow does hold a copy of all dependency requirements and does its best to validate all related requirements, but very complex schemas deserve thorough testing. ### "No binder available for quote" This issue appears if Ledger is unable to assign a binder. This is chosen based on three key pieces of data: * `broker.shortName` – this is pulled from the payload, and the field must remain in the Formflow template. Make sure it is an enum with allowed values and remember that suitable values may be different between pre-production and production environments. * `policy.dateInception` – this date field is pulled from the payload. It must exist, be valid, and fall within the start and end dates of a valid binder. * `schema.name` – this is passed with the template if the Ledger integration is correctly configured, and is unlikley to be the issue. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ai.insly.com/nora/configuration-guide/insly-ledger-integration/exporting-to-ledger.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.