Everything you need to run the Folks BackOffice ERP — the side of the suite that owns travel reservations, operational fulfilment, approvals and the receivable-payable money flow. From a single hotel booking to a multi-service package invoiced and paid, this is your User Manual and your hands-on Training Workbook in one place.
Browse the manual when you need a reference, or follow the workbook to build hands-on competence in every BackOffice module.
The complete reference for Folks BackOffice ERP. 33 chapters covering Reservation, Operations, Approval, Payments, Accounts and the Accounts Gateway — plus a status reference, troubleshooting and glossary.
Open the manual Hands-on15 progressive labs and a final assessment. Build a multi-service package, push it through Operations and Approval, generate Proforma + Customer Invoice, collect payment and trace the postings into the Accounts ledger.
Start trainingThe platform's core principles — and what you'll see throughout these docs.
Every read and write goes through a named stored procedure. Predictable, auditable — no LINQ surprises in the codebase.
Menus, sub-menus and actions gated by role privileges. SuperAdmin sees all; reservation, ops, approval and payments staff are scoped.
.NET Blazor with SignalR for live updates. Inboxes light up the moment a booking, proforma or payment lands.
Every booking is keyed to a Customer or an Agent — billing, commissions and downstream postings reflect the relationship correctly.
One package can mix Hotel, Flight, Tour, Visa and Transfer service lines — totals, taxes and currency are kept consistent.
Operations sees a unified per-service indent (hotel, flight, tour, visa, transfer) before they prepare a quotation.
Receivables (Customer) and Payables (Supplier) walk separate paths but post into the same Accounts Gateway.
Bridges Payments into the GL. Customer and supplier postings flow into Accounts without cross-module coupling.
Popular destinations across the docs.