> For the complete documentation index, see [llms.txt](https://docs.biscit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.biscit.com/biscit-spend-management/bsm-payment-flow.md).

# BSM Payment Flow

The BSM Payment Flow outlines how payment runs transition securely from Epicor Kinetic to suppliers via OFX. It provides external clients and stakeholders with a clear, end-to-end view of the eight operational stages and automated safeguards. This structured process ensures accurate ledger posting, transaction tracking, and reconciliation while keeping internal mechanics abstracted.

#### The Eight Stages of the Payment Journey

| **Stage**    | **Actor**                       | **Description**                                                                                                                                                              |
| ------------ | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1. Prepare   | AP Team (in BSM, inside Epicor) | <p>Build a payment group by picking the invoices due within the BSM app.<br></p>                                                                                             |
| 2. Submit    | AP Team (in BSM, inside Epicor) | <p>Review rates, fees, and purpose codes before initiating payment processing.<br></p>                                                                                       |
| 3. Check     | BSM (Automated)                 | <p>Lock the group and perform pre-flight checks on suppliers, bank details, ledger settings, and rates. Failed checks trigger a correction loop to fix and resubmit.<br></p> |
| 4. Send      | BSM & OFX                       | <p>Each payment is sent to OFX once and booked at the quoted rate, with results returned to the user.<br></p>                                                                |
| 5. Pay       | OFX & BSM                       | <p>OFX funds, converts, and pays out to the supplier's bank, while BSM tracks each status and bank fee in Epicor.<br></p>                                                    |
| 6. Close     | BSM                             | <p>Once OFX has started paying every payment, the group is posted in Epicor and books are closed. Remittance advice can optionally be emailed at this stage.<br></p>         |
| 7. Arrive    | Supplier's Bank                 | <p>Funds arrive in the supplier's bank account, with transit times varying based on currency, country, and transfer method.<br></p>                                          |
| 8. Reconcile | AP Team & BSM                   | <p>The AP team chooses accounts and initiates reconciliation. BSM matches OFX account activity to payments and fees, posting the statement when it ties.<br></p>             |

#### Key Safeguards and Exceptions

* Pre-Flight Validation: BSM automatically inspects supplier and banking details prior to dispatch to prevent transaction errors.
* Correction Loops: If pre-flight checks fail, the group is automatically routed back for adjustments and resubmission.
* Single-Dispatch Integrity: Each payment is rigorously tracked and transmitted to OFX strictly once to eliminate duplicate processing.<br>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.biscit.com/biscit-spend-management/bsm-payment-flow.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
