> For the complete documentation index, see [llms.txt](https://wageflow.gitbook.io/docs.wageflow/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wageflow.gitbook.io/docs.wageflow/background-and-problem-definition.md). # Background and Problem Definition Wages are not settled immediately after work is completed; instead, they are tethered to a distribution system built around fixed pay cycles, approval workflows, and intermediary institutions. While this system was historically rational, are now failing in a modern economy defined by flexible labor, cross-border collaboration, and high-frequency expenses. From a legal and accounting perspective, wages are recognized once work is completed. In practice, however, workers often have to wait several weeks before accessing disposable funds. This delay stems from rigid settlement cycles, internal corporate processes, and reliance on cross-border clearing. As employment model evolves, the focus shifts from income sufficiency to income availability. Many workers do not lack earning capacity; rather, they lack the ability to access the value of completed work in real time. For employers, real-time payment is not a lack of will—it is constrained by cash flow management, audit requirements, and regulatory compliance. Therefore, the question is not “whether to pay wages early,” but:\ “How can workers access the value of their completed labor more flexibly, without disrupting corporate cash flow or compliance structures?” --- # 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://wageflow.gitbook.io/docs.wageflow/background-and-problem-definition.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.