> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/workflow/standard-workflow-builder/material-ordering-and-processing-workflow.md).

# Material Ordering and Processing Workflow

Explore the step-by-step workflow for material ordering, goods receipt, and invoice processing with INFOR ERP and DocBits integration. Effective supplier and document management in one.

This document outlines the workflow for ordering materials from suppliers, receiving goods, and processing invoices with integration between suppliers, INFOR ERP system, and DocBits for document management.

### Process Overview

1. **Ordering Materials**
   * Initiate order with the supplier.
   * Send the order to the supplier through INFOR.
2. **Receiving Order Confirmation**
   * Supplier confirms the receipt of the order.
   * Creation and sending of order confirmation.
3. **Goods Receipt and Inspection**
   * Receive goods from the supplier.
   * Post goods receipt in INFOR and check against the delivery bill.
4. **Invoice Processing**
   * Receive invoice and send to DocBits for processing.
   * Check and verify invoice details with order and goods receipt.
5. **Final Steps**
   * Archive the order and related documents in DocBits.
   * Update INFOR with transaction details for financial accounting.

### Decision Points and Actions

* **Does the received goods match the order?**
  * Yes: Proceed with invoice processing.
  * No: Manual check and update required.
* **Is the invoice correct according to the goods received and order details?**
  * Yes: Complete the transaction and update financial records.
  * No: Further examination and corrections needed.

### Integration Points

* **INFOR ERP**: Main system for order processing, goods receipt, and financial accounting.
* **DocBits**: Document management for processing and archiving invoices and order confirmations.

### Notes

* Ensure all documents are verified and archived for record-keeping.
* Discrepancies in order or invoice details must be resolved promptly to avoid delays.

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-e437588132a5c903d248f5ebea3470a108db676f%2Fembed.svg?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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.docbits.com/administration-and-setup/workflow/standard-workflow-builder/material-ordering-and-processing-workflow.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.