> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lead.bank/llms.txt
> Use this file to discover all available pages before exploring further.
# Network Settlement Funding Obligations
> How Lead funds daily card network settlement for debit, prepaid, credit, and push-to-card BINs — the funds flows, the report data points that drive them, timing, and weekend behavior.
In order for Lead to fund the network settlement account, Lead requires daily network settlement reports for each network your BINs are active on ([formats per network](/file-reference/reports/network-settlement-reports)). Those reports drive the funds flows on this page: Lead parses each report's components and moves the corresponding funds between the accounts involved.
**Drawdowns.** Network drawdowns and reports can be aggregated across BINs of the same type. For example, two debit BINs can be funded together — but credit and debit/prepaid BINs must be separated at the reporting level in order for Lead to perform the funds flows below.
## BIN Settlement by Type
### Debit / Prepaid
The process of steps marked 1.\* is repeated twice — once for the primary network and again for the secondary network.
For debit/prepaid BINs, the net of transactions minus refunds is funded from the **source of funds, typically your FBO** — it's your customers' money settling their own spend.
### Credit
For credit BINs, the day's net transaction activity is funded from **Lead-owned funds — these are loans.** That is why settled credit spend creates **receivables** on Lead's books, which flow into your program's daily sale ([Receivables & the Daily Sale](/file-reference/sales/request-schema)). Refunds are remitted to you for collections purposes, and interchange is first remitted to Lead as owner of the related receivables, then sent to you per your contract — see the data-point table below for every component's path.
The credit BIN process is performed once per day based on the network settlement report; subsequent steps then depend on other inputs.
### Push-to-Card
In general, push-to-card has the same funds flow as a debit/prepaid BIN (net funds outflowing from a source of funds). There are differences around the accounts involved; your implementation team will provide details.
## Report Data Points
Lead parses each daily network settlement report into these values, which determine how funds move:
| **Data point** | **Description** | **Debit/Prepaid BIN** | **Credit BIN** |
| :----------------- | :------------------------------------ | :------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------------------------------------------- |
| Transaction amount | Gross sales | The amount totaling transaction amount minus refund amount is taken from the source of funds, typically an FBO | Funded from Lead-owned funds, as these are loans |
| Refund amount | Gross returns | Included in the above | Remitted to the client for collections purposes |
| Interchange amount | Net interchange sent from the network | Interchange revenue is remitted from the network settlement account to the client per the contract | Interchange revenue is first remitted to Lead as owner of the related receivables, then sent to you per your contract |
| Dispute amount | Net chargebacks sent from the network | Funds related to disputes are sent to the appropriate account for dispute management | Same as debit/prepaid |
| Fee amount | Net fees charged by the network | Fees charged by the network are passed on to the client per the contract | Same as debit/prepaid |
## Timing and Workflow
Lead receives network settlement reports for all applicable networks, then performs the funds flows above. If a program has multiple networks (e.g., Visa primary and Maestro secondary on a debit program), Lead funds network settlement once **all** of the day's files are in place. Typically, issuer processors deliver these reports in the morning to Lead via [SFTP](/file-reference/sftp-setup), with each network having its own [folder](/file-reference/delivery/overview).
Network settlement funding happens **independently of any other workflow** at Lead: Lead processes settlement files regardless of what other data has been shared, to ensure the networks receive funds on time. There is also **no T-1 dependency** — if the files for settlement on T don't appear until T+1, Lead still processes the T entries on T+1.
## Weekend Behavior
Reports are sent every calendar day, but funds move to the network only on business days: Lead processes reports every day and performs the funds flows the same day if it's a business day, otherwise the next business day.
| **Transaction day** | **Report day** | **Settlement day** |
| :------------------ | :------------- | :----------------- |
| Monday | Tuesday | Tuesday |
| Tuesday | Wednesday | Wednesday |
| Wednesday | Thursday | Thursday |
| Thursday | Friday | Friday |
| Friday | Saturday | Monday |
| Saturday | Sunday | Monday |
| Sunday | Monday | Monday |
Illustrative only; assumes the network's transaction window aligns with the calendar day. On Monday, three days' worth of transactions are requested from the network in a single drawdown — Lead processes each day separately, so cashflow is identical but funding appears as three individual steps (one per day).
## Settlement at a Non-Lead Bank (Local Currencies)
If the BIN and program are configured to settle transactions in local currencies (e.g., GBP transactions settle in GBP rather than the USD equivalent), Lead does not perform those funds flows but still requires the data for oversight:
* Network settlement data reflecting the non-USD activity in each relevant currency.
* Transaction data that reconciles to both the non-USD currency and USD — `settlement_amount` and `settlement_currency` become required fields.
Reach out to your implementation team for details.