> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-administrators/admin-settings-product-settings/bookings-overview/bookings-rtp-settings/configuration-steps.md). # Configuration Steps ### 1. Create a new GL Account for flaik Clearing * This is similar to the Aspenware Clearing GL Account but should be distinct from that account, so you have visibility at the GL level into what is being posted by flaik. * The resort Finance/Accounting team should provide this new GL Account, and it should be added to RTP under Administration/Location Administration/Accounting Management/GL Account ### 2. Create a new Payment Method for flaik Bookings * In RTP under Administration/Location Administration/Location Management/Payment, clone the existing Payment Method for Aspenware Clearing. * Change the default GL defined on the General tab to be the new GL Account you created above. * Update the GL Accounts defined in the Locations tab to be the new GL Account you created above. * This new Payment Method will need to have any location that could Return/Refund a sale made in flaik Bookings. ### 3. Create a new Location for flaik Bookings * This is done in RTP under Administration/Location Administration/Location Management/Location. * We require that the location be a Sale Location and an Audit Location. * We do not require it to be a Revenue Location or Inventory Pool location. * The location should have the following Payment Methods at a minimum: * Flaik Clearing * Cash (Payment Method Code 1) * Over/Short ### 4. Add the new Location to Taxes * This is done in RTP under Administration/Location Administration/Location Management/Tax. * The new location should be added to any Tax types you have defined (keeping in mind the tax calculation types we support, defined above). * Best practice is that all taxes should have the location added, even if they won’t initially be used by product headers sold at that location. If RTP sells a product that has a certain tax and the tax doesn’t exist at that location, it can throw RTP’s GL out of balance. ### 5. Define Security for the new Location * This is done in RTP under Administration/Security Administration/Security Management/Security Group. * Add the Sale and Audit Location you created to any Security Groups that may need to run reports for that location. * Note that Sale and Audit Location security in RTP only impacts a user’s ability to run reports (and run manual Location Closes, if you have that enabled). ### 6. Create a new Client for flaik Bookings * This is done in RTP under Administration/Location Administration/Client Management/Client. * We recommend cloning the existing eCommerce client (such as the one used for Aspenware). The client can be switched from 'eStore client' to 'Standard'. * You will then need to change the Sale and Audit Locations for the client, and remove any credit processing configurations from the client. * You will also need to have this new client added to your Auto-Client Close SQL Agent job. ### 7. Bulk Update the Product Headers * In RTP, find the Product Headers you wish to be available to flaik Bookings * Bulk Update them to add the new location. * This will allow flaik to retrieve pricing and tax details for them. ### Not Required for the flaik Bookings Location We do not currently require the following to be configured for flaik Bookings: * Payment Authorization Action * Audit Location Credit Card Authorization * Resort Charge Process Order * Resort Charge Sale Location * Sale Location Lock Type Though if these items are configured, it will not impede the processing of bookings from flaik. --- # 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://knowledgebase.flaik.com/flaik-knowledge-base/for-administrators/admin-settings-product-settings/bookings-overview/bookings-rtp-settings/configuration-steps.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.