Blog

SAP Business One for Pharma: 12 Tests Before ERP Go-Live

By IngoldNovember 10,2026

SAP Business One for Pharma can provide a sound operational core for a small or mid-sized pharmaceutical company. But the software should go live only after your team has proved that batch, expiry, warehouse, production, tax and recall processes work with your own data.

A polished demonstration isn't proof. Your SAP Business One agency should show that the configured system can stop an ineligible batch, calculate a real purchase scheme and trace a recall without relying on a consultant to repair the result afterwards.

Key takeaways

  • Approve go-live from completed business scenarios, not a feature demonstration.
  • Batch and expiry tracking aren't enough if FEFO, quarantine and returns controls fail.
  • Some pharma requirements need configuration, integration or an add-on beyond standard SAP Business One.
  • Run a mock recall and reconcile opening stock by batch before production use.

What must SAP Business One for Pharma prove before go-live?

The system must prove that it can process the transactions your people handle on an ordinary Monday, including the awkward exceptions. A demonstration using six clean items and one warehouse won't expose problems in a database containing 8,000 products, several pack sizes and years of inconsistent master data. Classify every promised control before testing it:
Control type What it means
Standard capability Available in the SAP Business One core
Configuration Depends on master data, rules, permissions or layouts
Integration Depends on another system or data exchange
Add-on Requires an extension beyond the core product
SAP lists purchasing, inventory, financial management and reporting among the product's standard areas. That doesn't make every pharma quality or regulatory process standard. Your solution document should identify the boundary in writing.

Can the master data handle real pharmaceutical transactions?

Poor master data makes a correctly configured ERP produce bad results. Before go-live, one named owner from operations, finance or quality must approve each important field and the rules for changing it.

Test 1: Can every item be identified without ambiguity?

Pull a sample that covers finished medicines, raw materials and packaging items. For each one, check the product name, dosage form, strength, pack size, manufacturer, HSN code, GST treatment and storage condition. Then check every unit it’s bought and sold in. Here’s a simple way to test it. Take a product sold as single tablets, strips of 10 and cases of 20 strips. Ask someone in the warehouse to receive one case. Ask someone in sales to invoice three strips. Now look at what’s left. The remaining quantity, the stock value and the invoice description should all match. While you’re at it, find out who is allowed to change the conversion factor once transactions already exist.

Test 2: Are batch, manufacturing and expiry dates mandatory?

Try to get bad data into the system on purpose.
  • Receive stock with no batch number.
  • Enter an expiry date that falls before the manufacturing date.
  • Use a supplier batch reference that already exists.
Each attempt should be blocked or flagged, depending on the rule your team has approved. CDSCO’s distribution guidance asks for batch numbers and expiry dates to be recorded at receipt, so that stock can be traced later. That means sales invoices alone aren’t enough for this test. Run it on purchase receipts, transfers, production receipts, returns and opening stock uploads as well.

Test 3: Do pack conversions and free-goods schemes calculate correctly?

Enter a purchase of 100 boxes on a 10+1 scheme. That gives you 10 free boxes. Check what they do to the stock quantity, the item cost and the tax treatment. Then look at the margin your finance manager will see later. Next, post a partial return to the supplier and sell some of the stock to a customer in a smaller unit. Compare the finance report, the warehouse balance and the purchase document. If they don’t agree, the configuration isn’t ready, and you shouldn’t sign it off. Before the test, decide how scheme stock will be handled: either its cost is spread across all units, or it’s tracked on its own. Put that decision in writing.

Will warehouse controls prevent the wrong stock from being sold?

When you test the warehouse, try to break the allocation rules. Users tend to pick whichever batch is easiest to select on screen. Your job is to prove that expired, blocked or unreleased stock still can’t reach a customer when they do.

Test 4: Does FEFO work during actual order allocation?

Set up two eligible batches of the same product. Batch A expires in four months. Batch B expires in nine. Now enter an order for a customer who needs at least six months of shelf life remaining.
BATCH A

Expires in four months

Plain FEFO would pick batch A, since it expires first. With the customer rule in place, batch A should be ruled out.
BATCH B

Expires in nine months

The system should offer batch B.
CDSCO’s distribution guidance says the stock that expires first should go out first, with controls that stop expired stock from being supplied. Your setup also has to cope with genuine exceptions, and this customer rule is one of them.

Test 5: Can users separate released, quarantined and rejected stock?

Place 500 units in quarantine, 200 in released stock and 40 in a returns area. Try to reserve, pick, transfer and invoice from each location or status. A sales order should see only the quantity the business has approved for sale. Test the physical process too. A system block is of little use if warehouse staff store released and rejected cartons in the same bin. CDSCO guidance calls for segregated storage of quarantined, rejected, expired, recalled and returned products.

Test 6: Can multiple warehouses maintain accurate batch balances?

Transfer 120 units of one batch between two warehouses. Receive only 118 and record two damaged units. Check the dispatch record, in-transit balance, receiving difference, batch ledger and accounting result. If the warehouses sit under different GST registrations or locations, include the tax documents and approval steps in the same test. Temperature monitoring and cold-chain records may depend on sensors, a transport system or another application. If so, the integration owner and failure procedure must be named before go-live.

Can production and quality teams release the correct batch?

For a manufacturer, keeping stock under control is only half the job. A production order has to use the approved formula and record what was consumed. It also has to keep the batch from being sold until quality has signed it off.

Test 7: Are formulations, BOMs and revisions controlled?

Set up version 2 of a test formula and give it an effective date of 1 December. On 2 December, try to release a production order that still uses version 1. See what the system does. Then check who is allowed to approve a substitute when the planned raw material is out of stock. SAP Business One handles bills of material and production processes. Specialised formulation control is another matter, and it may need extra configuration or an industry solution. Ask the implementation team to show you four things:
1Version history
2Effective dates
3Permissions
4A record of every approved change
Be wary of a spreadsheet kept outside the ERP as the permanent control. It’s acceptable only if your team chose that exception on purpose and someone is responsible for it.

Test 8: Does batch completion reconcile material, yield and quality status?

Raise a test production order for 10,000 units. Record 9,750 units as good output and 150 as rejected. That leaves 100 units unaccounted for. Production, quality and finance should all see the same figures, and each should understand what that gap does to the cost. Now try to deliver the finished batch before quality has released it. The system should hold you to the approved process. Bear in mind that a standard production order is not a full electronic batch manufacturing record. List every record that still sits in a quality system, a document platform or an approved paper process.

Can sales, finance and compliance reconcile every movement?

The ERP passes when one transaction tells the same story at every stage: sales order, stock movement, tax reporting, accounting and any return that follows. If finance has to rebuild that transaction in Excel at month-end, it hasn’t passed.

Test 9: Do pricing, credit and near-expiry rules survive order entry?

Pick a customer who has contract pricing, a credit limit and a minimum shelf-life rule. Enter an order for them, add a bonus quantity and then push the order past the credit limit. Now watch what happens.
?Which approval kicks in?
?What can the approver see?
?Is the decision saved anywhere?
Run the same test with a sales return against the original batch. At a wholesaler with 40 users, one order can pass through sales, the warehouse, credit control and finance. Every role needs enough information to do its part. None of them should get rights to change tax or batch data unless the job calls for it.

Test 10: Does the order-to-invoice process produce correct tax documents?

Take one test transaction and follow it all the way:
STEP 1

Quotation or order

STEP 2

Delivery

STEP 3

A/R invoice

STEP 4

Journal entry

STEP 5

Return

At each step, check the HSN code, GST rate, place of supply and document series. Look at how freight and discounts are treated too. Add an interstate sale and a credit note. Where they apply, include an e-invoice and an E-Way Bill. SAP publishes a detailed guide to GST in the India localisation and advises customers to stay on the latest relevant patch for the GST functions available. Two people share the responsibility here. Your tax adviser approves the statutory setup. Your SAP Business One agency then has to prove that the approved setup works in the system as configured.

Can the business trace a recall and survive cutover?

Two checks decide whether you can go live: a mock recall and an opening stock reconciliation at batch level. If either one fails, the project team can’t yet say what stock exists or where an affected batch ended up.

Test 11: Can the team complete a mock recall?

Invent a batch of 2,400 units for this test. Say it arrived from a single supplier, moved through three warehouses and was sold to 18 customers. First, have the team work backwards until they reach the supplier record. Then have them work forwards. They should be able to name every customer who received the batch, along with the quantity, the delivery date, any returns and whatever is still sitting in stock. CDSCO’s 2024 recall guidelines cover the whole chain: manufacturers, importers, exporters, stockists, distributors and retailers. Voluntary and statutory recalls both fall under them, and there’s a section on mock recalls too. When you review the result, look at two things. Did the team find everything, and was it correct? As for timing, only measure against a target if your approved recall procedure already sets one. Don’t invent a number for the test.

Test 12: Do migrated data, permissions and opening balances reconcile?

Reconcile opening stock by item, warehouse, bin, batch and expiry date. After that, compare customer balances, supplier balances, open orders and inventory value against the migration totals that were signed off. Test permissions using named roles: warehouse picker, quality approver, sales manager, finance manager and system administrator. Find out who can change master data, release stock, backdate documents and alter reports. Check the backups and run through the recovery procedure.
One rule shouldn’t bend here. If batch differences are still open, go-live waits, even when the total inventory value happens to match.

How should buyers judge standard features, configuration and add-ons?

Ask your implementation partner for a written solution map that classifies every pharma control. For each control, it should name the system, the owner, the test evidence and who supports it.
  1. Mark what is standard SAP Business One.
  2. Record every configured rule and approval.
  3. Name each external integration and what happens when it fails.
  4. List the add-ons, licences and support owners.
  5. Test with migrated data, exceptions and everyday users.
  6. Turn down any demo that only uses clean sample data.