> For the complete documentation index, see [llms.txt](https://docs.bill-z.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bill-z.com/billz-pro/how-it-works.md).

# how it works

This page explains the **high-level Billz Pro execution workflow**.\
Sensitive implementation details are intentionally omitted.

## Two execution modes (high-level)

### A) Direct conversion execution

Use crypto directly to fund a fiat payment execution.

### B) Collateralized liquidity execution (lending/borrowing-based)

Use crypto as collateral to access liquidity, then route that liquidity toward fiat payment execution.

{% hint style="info" %}
Availability depends on configuration, jurisdiction, risk policy, and supported workflows.
{% endhint %}

```mermaid
flowchart TD
    A[Initiate Payment Intent] --> B{Funding Mode}
    B -->|Direct| C[Direct Conversion Path]
    B -->|Collateralized| D[Collateral + Lending/Borrowing Path]
    C --> E[Compliance & Operational Checks]
    D --> E
    E --> F[SEPA / ACH Execution]
    F --> G[Proof & Confirmation]
```

> ### Workflow (visual)

## Standard execution flow

{% stepper %}
{% step %}

### Initiate payment

You provide:

* recipient name
* bank details (**IBAN** for SEPA / routing+account for ACH)
* fiat amount (EUR or USD)
* reference / memo (recommended when supported)
* optional internal reconciliation metadata (invoice ID, vendor tag)
  {% endstep %}

{% step %}

### Select funding approach

Depending on workflow and configuration:

* direct crypto-funded execution, or
* collateralized liquidity route (lending/borrowing-based)
  {% endstep %}

{% step %}

### Compliance and operational checks

Billz Pro may apply:

* KYC / KYB / EDD review (when required)
* risk thresholds
* jurisdiction checks
* rail constraints / cutoffs
  {% endstep %}

{% step %}

### Conversion / liquidity orchestration

Billz Pro orchestrates the required steps to prepare fiat execution.
{% endstep %}

{% step %}

### Fiat execution (SEPA / ACH)

A fiat transfer is initiated on:

* **SEPA (EUR)**
* **ACH (USD)**
  {% endstep %}

{% step %}

### Proof & confirmation

Billz Pro generates structured artifacts to support accounting and audit workflows.
{% endstep %}
{% endstepper %}

## Indicative timelines (not guaranteed)

| Rail | Typical range (indicative)                      |
| ---- | ----------------------------------------------- |
| SEPA | Same day / next business day (cutoff dependent) |
| ACH  | 1-3 business days (rail dependent)              |

> Timelines are not guaranteed and may be affected by banking cutoffs, compliance review, and operational conditions.

## Mini FAQ

<details>

<summary>Are timelines guaranteed?</summary>

No. Banking cutoffs, compliance review, and operational conditions can affect timelines.

</details>

<details>

<summary>Does collateralized mode remove liquidation risk?</summary>

No. It introduces collateral management and liquidation risk that must be monitored.

</details>

<details>

<summary>Can Billz Pro share the exact routing logic publicly?</summary>

No. Public docs intentionally avoid disclosing sensitive execution details.

</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.bill-z.com/billz-pro/how-it-works.md?ask=<question>&goal=<endgoal>
```

`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.