What Integration Points Does Custom Business Management Software Need?
A vague request for 'ERP integration' produces quotes that cannot be compared. This guide shows how to turn stock, order and receivables problems into integration points a developer can scope and price.
Custom business management software needs four integration points with accounting: customer and credit data, sales orders and invoices, purchase orders and supplier bills, and stock movements that post to inventory accounts. Before commissioning, define which system owns each data field, what triggers a posting, and how failed postings are handled. If a wrong answer would cost money, the citation column decides the purchase.
For a distributor or family-run trading company, the expensive part is rarely the screen where staff type an order. It is the handoff between the order, the warehouse, the invoice and the receivables ledger. Each handoff is an integration point, and each one needs an owner, a trigger and an error path before a developer can quote it.
What is the difference between ERP and CRM, and which one owns the customer record?
An ERP owns transactions and financial postings; a CRM owns the relationship history before an order exists. The integration question is not which system is better but which one is the master for each field.
In practice, a distributor needs the CRM to hold contact details, call notes and quote history, while the ERP holds the credit limit, the price list and the invoice. If sales and accounting disagree about a customer's credit limit, the ERP record must win, because that is the number that blocks a shipment.
Write the field ownership down as a table before you talk to any developer. The exercise exposes contradictions early, when they are cheap to fix.
| Data field | Owning system | Direction of sync | Trigger |
|---|---|---|---|
| Customer name and address | CRM | CRM to ERP | On customer creation or edit |
| Credit limit and payment terms | ERP | ERP to CRM (read-only display) | On credit review |
| Price list and discounts | ERP | ERP to order system | On quote creation |
| Sales order header and lines | Order system | Order system to ERP | On order confirmation |
| Stock on hand | Warehouse system | Warehouse to ERP and order system | On goods receipt or pick |
| Invoice and receivables balance | ERP | ERP to CRM and reporting | On invoice posting |
This table is the core of a specification. A developer can price each row as a defined interface rather than guessing at an open-ended 'integration'.
How does an inventory and order management system work across several staff?
An inventory and order management system works by giving each stock movement a reason code and each order a status, so that two staff members cannot promise the same unit to two customers. The integration with accounting is what turns those movements into financial records.
For a wholesaler, the minimum integration points are: goods receipt updates stock and creates a supplier liability; a pick reduces stock and marks the order as fulfilled; an invoice posts revenue and a receivable. If stock can be adjusted without a reason code, the inventory valuation will drift from the ledger within one accounting period.
Warehouse management system development often starts with barcode scanning, but the specification should state which scan events post to accounting and which are internal to the warehouse. That distinction keeps the accounting interface small.
- Goods receipt: creates a supplier bill or accrual and increases stock on hand.
- Pick and pack: reduces stock and changes order status; no accounting entry if the invoice is raised separately.
- Invoice: posts revenue, tax and a receivable to the customer account.
- Stock adjustment: requires a reason code and posts to an inventory adjustment account.
- Return: reverses the invoice and returns stock, with a separate approval step.
Each of these is a candidate integration point. You do not need all of them on day one; you need to decide which ones are in scope and which are manual for the first release.
What should an order to cash workflow include before it reaches accounting?
An order to cash workflow should include credit checking, stock allocation, dispatch confirmation, invoicing and receivables follow-up, with a defined handoff to accounting at the invoice step. The workflow is only as good as its exception handling.
In Los Angeles, a distributor selling to trade customers often deals with sales tax rules that differ by county and with customers who expect same-day will-call pickup. If the order system cannot hold a tax jurisdiction per delivery address, the accounting integration will produce invoices that need manual correction.
Receivables and credit control software belongs inside this workflow, not beside it. A credit hold that is checked only at month-end is too late; the check must run when the order is confirmed, using the ERP's current balance.
The purchase side mirrors this. A purchase order approval workflow needs a threshold table: who approves up to a value, who approves above it, and what happens when the approver is unavailable. Set the approval threshold in the specification, not in a conversation, because the developer will build exactly what is written.
If you are documenting these flows for the first time, our guide to business management software development covers the same decisions from the delivery side. For family-run trading companies, the ownership question is often harder than the technical one, and the notes on software for family businesses address who signs off on each integration.
How do you migrate from Excel to a business system without losing the audit trail?
You migrate from Excel by freezing the spreadsheets as read-only historical records and loading only open balances and active master data into the new system. The migration is a data exercise, not a software feature.
The specification should list every spreadsheet that currently feeds a decision: the stock list, the price list, the receivables ageing, the purchase order log. For each, state whether it becomes a system screen, a report, or is retired. If a spreadsheet is still edited after go-live, the integration is not finished.
Opening balances are the riskiest part. Customer receivables, supplier payables and stock valuation must reconcile to the accounting system on the cutover date. Ask the developer to describe the reconciliation report they will produce, and who signs it off. That report is a deliverable, not a courtesy.
For food wholesale clients, lot and expiry data often lives in Excel because the accounting system cannot hold it. If that data must survive migration, it becomes an integration point with the inventory system, and it should be priced as one. Our food wholesale software notes describe how lot tracking interacts with invoicing.
How do you turn a vague problem into a specification a developer can price?
You turn a vague problem into a priceable specification by writing one sentence per integration point in the form: trigger, data moved, owning system, error handling. A developer can estimate that sentence; they cannot estimate 'make our systems talk to each other'.
Use this sequence:
- Name the business event that currently causes a manual step, such as 'accounts re-keys the invoice into the accounting package'.
- State which system should own the data after the change, and which systems only read it.
- Define the trigger: what action in which system starts the integration.
- Define the error path: where a failed posting appears, who sees it, and how it is retried.
- State the volume: how many orders or stock movements per day, because that decides whether a batch file or a real-time interface is appropriate.
- Agree the reconciliation report that proves the integration is working.
The delivery team controls the interface design, the error handling and the test plan. The client controls the field ownership decisions and the sign-off on opening balances. If the client cannot name the owner of a field, that integration point is not ready to be priced.
Readers in Los Angeles sometimes ask about local presence. We deliver from Chengdu and work with clients on Pacific time where the project requires it; the Los Angeles delivery notes describe how handover and support hours are arranged.
Frequently asked questions
What is the difference between ERP and CRM?
An ERP manages transactions and financial postings, while a CRM manages contact history, quotes and sales activity before an order exists. In an integrated setup, the ERP usually owns credit limits and prices, and the CRM reads them. The ownership decision matters more than the product labels.
How does an inventory management system work?
An inventory management system records every stock movement with a reason code, so receipts, picks, adjustments and returns each change the balance in a traceable way. When integrated with accounting, those movements post to inventory and cost-of-sales accounts. The integration is what keeps the physical count and the ledger aligned.
How do you migrate from Excel to a business system?
You migrate by freezing the spreadsheets as read-only history and loading only open balances and active master data into the new system. The cutover should include a reconciliation report that matches receivables, payables and stock valuation to the accounting records. A spreadsheet that remains editable after go-live signals an incomplete migration.
What should an order management system include?
An order management system should include credit checking at order confirmation, stock allocation, dispatch confirmation, invoicing and receivables follow-up. It should also define the error path when a posting to accounting fails. The order to cash workflow is only complete when every exception has an owner.
How many integration points does custom business management software need?
A distributor typically needs four to six integration points: customer and credit data, sales orders and invoices, purchase orders and supplier bills, stock movements, and receivables balances. The exact number depends on how many systems currently hold duplicate data. Each point should be specified with a trigger, a data owner and an error path before pricing.
Questions we are asked
What is the difference between ERP and CRM?
An ERP manages transactions and financial postings, while a CRM manages contact history, quotes and sales activity before an order exists. In an integrated setup, the ERP usually owns credit limits and prices, and the CRM reads them. The ownership decision matters more than the product labels.
How does an inventory management system work?
An inventory management system records every stock movement with a reason code, so receipts, picks, adjustments and returns each change the balance in a traceable way. When integrated with accounting, those movements post to inventory and cost-of-sales accounts. The integration is what keeps the physical count and the ledger aligned.
How do you migrate from Excel to a business system?
You migrate by freezing the spreadsheets as read-only history and loading only open balances and active master data into the new system. The cutover should include a reconciliation report that matches receivables, payables and stock valuation to the accounting records. A spreadsheet that remains editable after go-live signals an incomplete migration.
What should an order management system include?
An order management system should include credit checking at order confirmation, stock allocation, dispatch confirmation, invoicing and receivables follow-up. It should also define the error path when a posting to accounting fails. The order to cash workflow is only complete when every exception has an owner.
How many integration points does custom business management software need?
A distributor typically needs four to six integration points: customer and credit data, sales orders and invoices, purchase orders and supplier bills, stock movements, and receivables balances. The exact number depends on how many systems currently hold duplicate data. Each point should be specified with a trigger, a data owner and an error path before pricing.
