Зачем нужны несколько гостевых folio?

01:49 · Narrated in Urdu · English transcript

Разбираемся в работе с несколькими folio

Watch on Vimeo

English transcript

The narration is in Urdu. This is a machine translation into English — click any timestamp to jump to that point in the video.

Whenever you enter a reservation in Munshi10, Munshi10 automatically opens three sub-folios. The first folio is named BTC folio, the second is named folio 2, and then there's folio 3.
Then, whenever you enter charges for a guest, you can use this folio number there. For example, let's open any guest from here.
So, if you need to enter charges for them, you select here which folio to enter them in. And if you need to enter a payment, you can also select which folio to enter it in.
Right now, I have displayed a guest's folio where you can see there is a column named F, in which '2' is appearing. This is a transaction for folio 2. This is a transaction for folio 1. In this way, all the transactions are categorized.
Right now, the entire folio is visible. If you want to see the transactions for folio 1, you will select BTC folio from here and continue, and you will get the transactions for BTC folio, or folio 1.
In this one, only the room rent is appearing.
And if you want to display the transactions for folio 2, you will continue, and you will get the transactions for folio 2.
The purpose of folios is that when companies send their guests, their usual terms and conditions—the company's terms that are agreed upon with you—are that we will pay for the room rent, the company will pay.
And if this guest eats here or uses any other services, they will pay for that in cash.
So then, whenever we charge this guest, we select this folio from here.
And when the guest comes to check-out, we take the amount that is in folio 2 from them in cash, and then for the amount that is in folio 1, which is also called the BTC folio, we then send an invoice for that to the company.

Transcribed and translated automatically (gemini-2.5-pro, 2026-10-28). Spotted a mistake? Tell us.