> For the complete documentation index, see [llms.txt](https://docs.verygoodsecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verygoodsecurity.com/enterprise-platform/core-platform/reports/scheduled-report-delivery.md). # Scheduled Report Delivery ### Overview VGS supports delivering reports of customer data on a scheduled basis. These reports can include detail-level data that give you granular, event-level understanding of your VGS activity. They allow you to see the underlying details that make up the aggregated numbers in your Usage Reports. These report schedules are useful when you need to reconcile, audit, or analyze what happened at the level of a single card, token, or lifecycle event. ### Delivery Cadence VGS supports delivering reports on a daily, weekly, or monthly cadence. ### How It Works * **Customers request a report.** Reach out to your VGS Account Executive and let them know which report you would like, and how often you want it delivered. * **VGS provisions a** [**Drop Zone**](/enterprise-platform/developer-resources/drop-zones.md)**.** A dedicated SFTP endpoint is set up for your account, using a public key provided by the customer. * **Reports are delivered automatically.** On the schedule, VGS writes each report as a file to the Drop Zones `from_vgs` folder. Customers pull the files from the SFTP endpoint when they are ready. ## Frequently Asked Questions * **What reports are available?** * Availability depends on the VGS products you use. Your VGS team can walk you through the reports available for your account. * **How do I access my Drop Zone?** * VGS provisions a dedicated SFTP endpoint and shares the credentials with you securely. See [Drop Zones](/enterprise-platform/developer-resources/drop-zones.md) for more details. --- # 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.verygoodsecurity.com/enterprise-platform/core-platform/reports/scheduled-report-delivery.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.