# SAP Business One Business Partner Master Data Request Form

> Source: https://netray.co/tools/sap-b1-business-partner-master-data-request-form
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A fill-in request form for creating or changing a customer or vendor in SAP Business One, with the fields finance needs and an approval block.

## Category

sap

## Erp

SAP Business One

## Audience

- Finance controller
- Purchasing
- Master data owner
- B1 super user

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Hartwell Fabrication Inc.

#### Request date

**Key:** request_date

**Type:** date

**Default:** 2026-10-20

#### Requested by

**Key:** requester

**Type:** text

**Default:** A. Morales, Purchasing

#### Request type

**Key:** request_type

**Type:** select

**Options:**

- Create new
- Change existing
- Block or deactivate

**Default:** Create new

#### Business partner type

**Key:** bp_type

**Type:** select

**Options:**

- Customer
- Vendor
- Lead

**Default:** Vendor

#### Legal name

**Key:** bp_name

**Type:** text

**Default:** Ridgeline Heat Treating LLC

#### Business partner group

**Key:** bp_group

**Type:** text

**Default:** Subcontractors

#### Tax ID

**Key:** tax_id

**Type:** text

**Default:** 00-0000000

#### Bill-to / pay-to address

**Key:** address

**Type:** textarea

**Default:** 1200 Foundry Road
Dayton, OH 45402
United States

#### Main contact and email

**Key:** contact

**Type:** text

**Default:** J. Patel, jpatel@example.com

#### Currency

**Key:** currency

**Type:** text

**Default:** USD

#### Payment terms

**Key:** terms

**Type:** text

**Default:** Net 45

#### Bank details verified by

**Key:** bank

**Type:** text

**Default:** Call-back to known number, A. Chen

#### Business reason

**Key:** reason

**Type:** textarea

**Default:** Approved subcontract source for heat treat of shafts, first PO expected in November.

**Blocks:**

#### Business Partner Request

**Body:** Company: {{company}}
Date: {{request_date}}
Requested by: {{requester}}
Request type: {{request_type}}

#### Identity

**Body:** Type: {{bp_type}}
Legal name: {{bp_name}}
Group: {{bp_group}}
Tax ID: {{tax_id}}

#### Address and contact

**Body:** {{address}}

Contact: {{contact}}

#### Financial settings

**Body:** Currency: {{currency}}
Payment terms: {{terms}}
Bank details verified by: {{bank}}

#### Justification

**Body:** {{reason}}

#### Documents attached

**Table:**

**Columns:**

- Document
- Attached (Y/N)
- Checked by

**Rows:**

**0:** W-9 / tax registration certificate

**0:** Signed credit application or supplier questionnaire

**0:** Bank letter or voided cheque

**0:** Approved supplier list entry (vendors)

#### Approvals

**Signatures:**

- Requester
- Department manager
- Finance (credit or bank check)
- Master data owner (entered in B1)

**Notes:** This form is a starting point for your internal control, not legal or tax advice. Match field names to your own Business Partner Master Data screen and any user-defined fields. Keep the person who requests a vendor separate from the person who enters bank details.

## Content

**Intro:** Business partner records are the most frequently abused master data in any ERP. A single request form with a defined approval path keeps duplicates, fraudulent bank changes and missing tax data out of Business One.

**Sections:**

#### How to use the form

**Body:** Fill in one form per new partner or per change. Choose the type first: customer, vendor or lead, because Business One stores them in the same business partner master data table (OCRD) with a card type that drives which document types you can post. Attach the registration and bank evidence, collect the signatures, and only then let the master data owner key the record.

#### Fields that matter most

**Body:** Group and payment terms determine default accounts, dunning behaviour and cash forecasts, so they should come from a controlled list, not free text. Currency decides whether the partner has its own control account or posts in all currencies. Tax data differs by country, so add the registration fields your jurisdiction needs. Bank details are the highest fraud risk and should be verified by a call-back to a number you already hold, never one printed on the new request.

**Bullets:**

- Search for duplicates by name, tax ID and bank account before creating
- Record who verified the bank details and how
- Use blocked or inactive flags instead of deleting partners with history

#### Approval and separation of duties

**Body:** The usual control is three roles: the requester states the need, finance checks credit or bank details, and the master data owner enters the record. If one person can do all three, you have no control. Business One authorizations can limit who may edit the business partner master and who can change payment terms and bank data separately.

#### Common mistakes

**Body:** Teams create a partner as both customer and vendor under two codes instead of using the linked or combined approach agreed in design, which splits the history. Others leave group and terms blank and rely on defaults. A third mistake is accepting email bank-change requests from suppliers without independent verification.

**Cta:** If you want business partner duplicates and missing fields found automatically in your live data, we can set up a read-only query layer on your ERP database.

**Faq:**

#### Which Business One table holds customers and vendors?

**Answer:** Customers, vendors and leads are all stored in the business partner master data table OCRD, separated by a card type value. Addresses and contacts sit in related tables. Check your version's data dictionary before writing queries.

#### Should I use this form for changes as well?

**Answer:** Yes. Select Change existing and fill in only what changes, noting the old value in the justification. Changes to bank details and payment terms deserve the same independent approval as a new record.

#### How do I stop duplicate partners?

**Answer:** Search by tax ID, bank account and a normalised name before creating. Require the search to be recorded on the form. Periodic duplicate reports against the master data catch what the form misses.

#### Does this cover credit approval?

**Answer:** It records that finance checked credit or bank data, but credit policy itself is yours to define. Add credit limit and review frequency fields if you want them on the same page.

## Search terms

sap business one business partner form, sap b1 customer creation form, sap b1 vendor creation request, business partner master data request template, vendor master data change request form, sap b1 ocrd fields, new customer setup form template

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json